TIL: no impact when changing physical port in Virtual Switch in a VSX Environment

[Christian_Froem]

Hello,

(as I didn't found any details to this subject, I want to document it for others.)

We have Virtual-Switches in an VSX-Environment, and on VSwitch I had to change the physical port from bond1 to bond4. The question was, how the impact on running sessions and traffic would be.

The interfaces in the VSwitch looked like this before:

[Expert@dev-mod1-mgmt:4]# ifconfig | egrep -v -e "^(\s|$)"
bond1.231 Link encap:Ethernet HWaddr 00:1C:7F:FD:F9:99
br4 Link encap:Ethernet HWaddr 00:12:C1:02:D0:05
lo Link encap:Local Loopback Media:unknown
wrpj64 Link encap:Ethernet HWaddr 00:12:C1:02:D0:07
wrpj129 Link encap:Ethernet HWaddr 00:12:C1:02:D0:05
wrpj512 Link encap:Ethernet HWaddr 00:12:C1:02:D0:11

After the change:

[Expert@dev-mod1-mgmt:4]# ifconfig | egrep -v -e "^(\s|$)"
bond4.231 Link encap:Ethernet HWaddr 00:1C:7F:FD:C9:C7
br4 Link encap:Ethernet HWaddr 00:12:C1:02:D0:05
lo Link encap:Local Loopback Media:unknown
wrpj64 Link encap:Ethernet HWaddr 00:12:C1:02:D0:07
wrpj129 Link encap:Ethernet HWaddr 00:12:C1:02:D0:05
wrpj512 Link encap:Ethernet HWaddr 00:12:C1:02:D0:11

The change was done via SmartConsole, in the Main-CMA. 

So the bond-interface changed, of course the mac-address of the VLAN-Interface (as the underlying interface changed), but nothing else.

This change had no impact. Neither on running sessions, nor pings. It just went through without any loss or downtime.

Regards, Christian

[_Val_]

Thanks for sharing, @Christian_Froem