If you wish to flip these two - just flip it.  In doing that, talk to network guys as you might be using different VLANs / switches and there might be some work for them as well.

Only your IPMI port will be 'potentially' limited to 10/100mb.

If your replication link is only running at 100 and not 1000, then you are proabably not going to fix this by switching physical NIC's on the DD.

The use catagory of the physical port on the DD is accademic, as long as the IP is something you can route to, you should be able to use it for backup, management or replication - as long as it is truly routeable and open from the environmental networking perspective.

As Hrvoje suggests, check out your VLAN's but also firewall considerations since they might be blocking the http (TCP 80) or https (TCP 443), maybe try an SSH session to the DD via your desired NIC/IP too. Maybe try it from a jump box which is closer to the DD, maybe a backup server if possible.t

Are you checking connectivity with IP or hostname, in which case you may want to consider DNS too.

It's entirely possible that a replication IP/NIC is in a VLAN only between only your 2x DD's - in which case you may not be able to get to that interface from your desk - I see this a lot. I assume you are not VLAN tagging.

Also maybe verify your default gateway and routes, this may affect things for you too.

route show gateway

route show config

This would be handy to clarify for you too, it makes things pretty clear to read;

net show hardware

net show settings

Regards, Jonathan

Hi,

This procedure really jumped up and bit me on the arse earlier this afternoon :-(  I had a foreboding that it would,...

I inherited the current config from a storage guy who left the company.

The plan was to swap the eth0a and eth0b ip addresses on both Data Doman boxes, because replication was occurring on eth0a and it was only set to (or capable of) 100mb. I wanted to make replication occur on eth0b at 1gb. Also planned to create an ifgroup using the four pci nics:

Before:

eth0a:  100mb  57.101.64.76    (replication)

eth0b:  1gb   57.101.71.198      (management gui & backups)

eth4a:  disabled 

eth4b:  disabled

eth4c:  disabled

eth4d:  disabled

After:

eth0a:  100mb    57.101.71.198      (management gui)

eth0b:  1gb   57.101.64.76    (replication)

eth4a:  57.101.59.1  (ifgroup backup data)

eth4b:  57.101.59.2  (ifgroup backup data)

eth4c:  57.101.59.3  (ifgroup backup data)

eth4d:  57.101.59.4  (ifgroup backup data)

But I was worried how to swap eth0a and eth0b settings because I would inevitably lose connection to the mgmt gui. So I temporarily enabled eth4a and configured an ip address of 57.101.170.63. I found I was able to access the web gui and cli through this ip address.

Then this afternoon on the web gui using the new ip address 57.101.170.63 on eth4a I disabled the eth0b nic through which we had previously accessed the web gui - and I lost access to the whole box....!!! No gui or cli access on eth4a or anywhere else. I could ping eth4a and telnet to it on port 80, but no cli or web gui access. :-O

Luckily a colleague was visiting the site and I talked him through accessing the console manually, performing a restart then a "net enable eth0b" to get eth0b working again. And lo and behold eth4a then leapt into life too. 

Even more mysteriously, I was able to do the same thing on the other DD box and got away with it (although there was a scary pause for a minute or so before access on the temporary eth4a came back.

Why did I lose access to data Domain when I disabled eth0b when the alternative eth4a was working perfectly well? I'm supposed to complete this change tomorrow and I'm very concerned the same thng will happen again.

Thanks for any help!  here are net show hardware and net show settings on the box that gave me trouble:

ostuser@AKDD002# net show hardware

Port    Speed      Duplex    Supp Speeds   Hardware Address    Physical   Link s

-----   --------   -------   -----------   -----------------   --------   ------

eth0a   100Mb/s    full      no autoneg    00:8c:fa:05:71:01   Copper     yes  

eth0b   1000Mb/s   full      10/100/1000   00:8c:fa:05:71:00   Copper     yes  

eth4a   1000Mb/s   full      10/100/1000   00:1b:21:d7:f3:30   Copper     yes  

eth4b   unknown    unknown   10/100/1000   00:1b:21:d7:f3:31   Copper     no   

eth4c   unknown    unknown   10/100/1000   00:1b:21:d7:f3:32   Copper     no   

eth4d   unknown    unknown   10/100/1000   00:1b:21:d7:f3:33   Copper     no   

-----   --------   -------   -----------   -----------------   --------   ------

ostuser@AKDD002# net show settings

port    enabled   DHCP   IP address                   netmask           type   g

                                                      /prefix length           

-----   -------   ----   --------------------------   ---------------   ----   -

eth0a   yes       no     57.101.64.76                 255.255.255.224   n/a    

                         fe80::28c:faff:fe05:7101**   /64                      

eth0b   yes       no     57.101.71.198                255.255.255.0     n/a    

                         fe80::28c:faff:fe05:7100**   /64                      

eth4a   yes       no     57.101.170.63                255.255.255.0     n/a    

                         fe80::21b:21ff:fed7:f330**   /64                      

eth4b   no        n/a    n/a                          n/a               n/a    

eth4c   no        n/a    n/a                          n/a               n/a    

eth4d   no        n/a    n/a                          n/a               n/a