We have 2 NIC's in our Server running CCM4.X. Currently teaming is not enabled and Static IP is assigned to one of the NIC only and other is in disabled state.
Now we are planning to enable teaming on the same server. We will follow the below steps for doing the same:
1, Will enable other NIC also.
2, Will remove the Static IP assigned to the first NIC.
3, Then we will enable the teaming using HP tool.
4, Will then assign the same static IP to the new Teaming interface.
5, Will then reboot the server.
Now my question is that we are going to perform this activity remotely . So while performing step 2 we will loose the connectivity to the server.
So please suggest the way so that we can carry out this activity remotely successfully without loosing the connectivity or is it must that we need to have onsite support for the same.
Do you have a KVMoIP at the remote site? I presume not. TBH, I don't recall whether you need to remove the IP address on the primary NIC (it has been several years since I touched a 4x system in production) but I presume that is correct. I checked one of my old implementation plans and we followed a similar procedure (though we had KVMoIP deployed).
I recommend you take a look at this product: http://www.lantronix.com/it-management/kvm-over-ip/securelinx-spider.html
It is a very handy tool to have around and it is small enough to travel with a person or via carrier.
Please be kind and rewind - oh and if this helps, please rate...
Thanks for your quiuck response. I dont think we have any KVMoIP deployed. I need some solution on this without KVMoIP.
Please suggest is it possible to carry out this activity successfully remotely or not ?
Is onsite support must ?
OK. Again, it has been a while and I would always prefer to have a person on site for this ... but based on this Cisco doc:
It doesn't look like you need to remove the IP address on the primary NIC (like you had in your procedure) before building the team. If you look at steps 1-11. It looks you can go right to enabling the second NIC and then proceed directly to enabling the NIC team. This suggests that you can do this remotely. But I can't guarantee anything so maybe this info is useless to you. I do recommend having a method to either connect to the console or having a low level tech on site you can guide through the process. But that's just me.
Maybe someone on the forum has done this recently and can provide a more definitive answer.
Woops. Sent the partner version of the link. Try this:
Please remember to rate helpful posts.
Well that's frustrating. Sorry about that. Both links are working for me. Oh well, I attached the PDF.
Yes, iLO is a good idea; though if that's not been configured already then it will require someone to go to site anyway in order to patch it in and set up the authentication (or read it off the tag).
Essentially, when you create a NIC team it creates a new 'team' adapter, the old IP config is disabled (IP is unbound from the NI) and you lose your connection. The new NIC has default settings, which include TCP/IP bound to it and configured for DHCP.
So if you have DHCP running on that subnet (or can configure it temporarily), and have access to the DHCP server you should be able to work out what IP address it is allocated (by doing a 'show mac-address-table' on the attached switch) and comparing this to the DHCP lease table.
Once you have that IP, connect to the server again and assign the correct IP. You lose connection again, but should then be able to connect to the server again. It's probably sensible to reboot it at that point.
The problem is that if anything goes wrong in the process, you will need to go to site to recover it unless you have either ilO or remote KVM access.
Please rate helpful posts...
Excellent news! Thanks for keeping us posted. Remember, if a solution answered your problem please flag it so that others can benefit from the thread.