Turn on suggestions
![]() Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
|
09-05-2013 11:28 AM
We have a mixture of new and older switches in our redundant fabric. The older switches need to be moved onto a different subnet. Can this be done "on the fly" without affecting the production SAN on the fabric? We have redundant fabrics with everything dual ported. I was trying to plan downtime if needed. The FOS on the switches in question is 6.2 switch type is 32 (4100), if I remember correctly.
Regards,
Louis
09-05-2013 11:36 AM
Oh...and "yes I know" dual ported redundant fabric switches will allow for this. Upper managment doesn't want ANY fabric reconfigurations that will generate a fabric event that would cause a failover.
Regards,
Louis
09-05-2013 12:07 PM
I like this
Upper managment doesn't want ANY fabric reconfigurations that will generate a fabric event that would cause a failover.
Then best to never touch anything again which is hooked up to the switches. Your never going to get 100% guarantee, best for upper management to realize that.
That said setting new ipadresses should not impact what so ever, apart from management interface being unavailable for a brief moment.
Make sure you have a working (tested) serial connection in the event something goes wrong (typo in the netmask/gw or whatnot)
The command you're looking for is ipaddrset on the CLI, webtools will allow you to do the same.
09-10-2013 12:30 PM
Dion.v.d.c,
Additional question: When we have had problems with a switch and it dropped out of the fabric, I have noticed that the fabric tries to find the switch via IP (message on web gui) trying to resolve IP. Will changing the IP, cause the fabric to refresh?
Thanks,
Louis