Unsolved
This post is more than 5 years old
1 Rookie
•
94 Posts
1
11523
March 25th, 2014 10:00
Clear IP Address On Ethernet Device
I am setting up eth0b on my DD160 so I can use it for replication. I originally set my IP address on eth0b and then realized that I should have created a VLAN interface and specified the IP address for the ethernet interface on the VLAN interface. I've tried multiple ways to remove the IP address from the eth0b interface with no success (including clearing it then starting cleaning).
Nothing has worked so far. Can someone help me out and provide me with the steps to clear the IP address on eth0b?
Thanks.
No Events found!
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
March 27th, 2014 06:00
yes, ports are either set for native/access or for trunking. If you have plans to service multiple VLANs on the same physical port you enable trunking.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
March 27th, 2014 06:00
can you post "route show table" now
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
March 27th, 2014 06:00
you don't need to set static routes for networks that you can get to using your default gateway. I have 8 different VLANs on my DD890 so i have to deal with static routes pretty often.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
March 27th, 2014 06:00
can you post "show route table" though, you need to have a default gateway.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
March 27th, 2014 06:00
Your PC:
10.10.30.100
GW: 10.10.10.250
Your DD:
10.10.10.200
10.102.10.10 mask 255.255.255.0 default GW - 10.10.10.250
You do not say what is mask on your pc. If you are ping 10.102.10.10 as you claim in your post, how do you plan to get there? Given your gw I would assume you could ping 10.10.10.200, but not 10.102.10.200. Not sure if your 10.102 is routed or not, but it is different vlan and it either has different gw (most likely) or it is flat network meaning no gw will help you unless you will machine with IP on the same network.
snowmizer1
1 Rookie
•
94 Posts
0
March 27th, 2014 06:00
The port that eth0b is on is currently set as an access port on VLAN 102. This doesn't need to be a trunk port?
Crevelin,
Right now I've put my original problem of accessing the 10.10.10.200 network on my DD from my PC aside. Based on some configurations we had to do on Avamar to get this to work I'm not sure I want to go into this any further. So I've decided that I just want to make sure my DD at my primary site can talk to my DD at the DR site. Unfortunately I can't ping the gateway address for VLAN 102 on the switch from DD.
I know that I need to specify the correct default gateway for the 10.102.10.10 network when I set up eth0b.102 but I don't think I've done that properly. Any info on how to make sure that 10.102.10.10 is assigned the correct gateway when I set up eth0b.102 interface would be awesome. The "route show table" has a gateway set to 0.0.0.0 which I'm not sure is correct.
Thanks guys.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
March 27th, 2014 06:00
you are not going to see that and you should not because 10.10.10.250 is his default gateway.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
March 27th, 2014 08:00
did DDGridB name change ?
snowmizer1
1 Rookie
•
94 Posts
0
March 27th, 2014 08:00
Here's the final "route show config"
I am now able to ping my DR grid and vice versa. Now I need to modify the existing replication settings. I'm assuming that I need to add the new replication network as a system in the DD GUI and then select those hosts as the source and destination on my replication contexts and then change the context from the command line so it uses the correct NIC?
Thanks.
snowmizer1
1 Rookie
•
94 Posts
0
March 27th, 2014 08:00
Thanks for the link. Here's my new issue. Originally we had both DD boxes at our home office and replication was configured so that I could seed the target DD. Example of original config:
DD Primary: 1.1.1.1 - DDGridA.mycompany.com - VLAN 100
DD Secondary: 1.1.1.2 - DDGridB.mycompany.com - VLAN 100
Replication was set up using the source DDGridA.mycompany.com and destination of DDGridB.mycompany.com.
Flash forward to now where DDGridA is in the home office and DDGridB is at the DR site.
DD Primary Replication: 2.2.2.1
DD Secondary Replication: 2.2.2.2
I've modified the NIC being used for the replication contexts using the "replication modify rctx:1// connection-host DDGridXX_Repl" on both the source and target DDs. Now because there's no link from the home office to the DR site on VLAN 100 DDGridB can't be found and the replication is failing. I still need DDGridB to have the 1.1.1.2 on the eth0a NIC.
How do I get replication to work?
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
March 27th, 2014 08:00
take a look at my blog entry
Data Doman – manipulate interface used for replication | Storage Monkey
snowmizer1
1 Rookie
•
94 Posts
0
March 27th, 2014 12:00
I think I got it figured out. It was as simple as changing the DNS entry (or adding a host record to DD) that pointed to the 10.103.x.x or 10.102.x.x addresses. It would appear that now DD is happily replicating to my DD at the DR site. It's going to take a bit though because we haven't replicated since last Friday morning.
Thanks for the help guys.