Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Can Fabric Interconnects be re-IPd?

We have decided to use a different IP range and was wondering if I need to do some sort of erase config or can I just go through the initital setup up again through the console and change the IPs?  The original "management" subnet range we were going to use is not available, so I never got to the VIP.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Can Fabric Interconnects be re-IPd?

You certainlu can change the IP's without having to erase the system.  Remember this is only a Management plane change, not Data Plane, so you can do this without disrupting your server traffic.

Here's how I'd suggest you do it:

1. Log into the Console of each FI with admin account.

2. Find out which FI is the secondary by issuing:

      show cluster state

3. From the secondary FI console session issue:

      scope fabric-interconnect [a/b]

4. Set the new IP parameters with:

      set out-of-band ip [New-IP-Address] netmask [New-Netmak] gw [New-Gateway]

      commit-buffer

*Note: If the subnet mask and/or Gateway aren't changing, you can omit them from the command above.

*At this stage you should be able to ping the new IP addresses assuming the upstream Management interface are setup correctly and assigned to the correct VLAN

5. Repeat for the Primary fabric interconnect from its console session.

6. Set the new VIP by issuing:

     scope system

     set virtual-ip x.x.x.x

     commit-buffer

7. Test connectivity to each IP & VIP.

8. If you have any issues you should be able to use the console session to correct any mistakes without any service interuption other than UCSM access.

Regards,

Robert

2 REPLIES
Cisco Employee

Re: Can Fabric Interconnects be re-IPd?

You certainlu can change the IP's without having to erase the system.  Remember this is only a Management plane change, not Data Plane, so you can do this without disrupting your server traffic.

Here's how I'd suggest you do it:

1. Log into the Console of each FI with admin account.

2. Find out which FI is the secondary by issuing:

      show cluster state

3. From the secondary FI console session issue:

      scope fabric-interconnect [a/b]

4. Set the new IP parameters with:

      set out-of-band ip [New-IP-Address] netmask [New-Netmak] gw [New-Gateway]

      commit-buffer

*Note: If the subnet mask and/or Gateway aren't changing, you can omit them from the command above.

*At this stage you should be able to ping the new IP addresses assuming the upstream Management interface are setup correctly and assigned to the correct VLAN

5. Repeat for the Primary fabric interconnect from its console session.

6. Set the new VIP by issuing:

     scope system

     set virtual-ip x.x.x.x

     commit-buffer

7. Test connectivity to each IP & VIP.

8. If you have any issues you should be able to use the console session to correct any mistakes without any service interuption other than UCSM access.

Regards,

Robert

New Member

Can Fabric Interconnects be re-IPd?

Thanks!

353
Views
0
Helpful
2
Replies
CreatePlease login to create content