![]() ![]() If this is the case (you want to stay in the same subnet and just change the IP address inside this subnet), then you'll have to delete the previous IP address first. g.: vlan 1 ip address 10.10.10.11/8īut if you stay on the same subnet, the switch will complain: The IP address (or subnet) 10.10.10.11/8 already exists. You normally would just overwrite it with e. If you have console (out-of-band) access, none of this mess is required. Change the address, go to the machine in the other network and continue your work. If you have machines in both networks, and changing the address of the switch will not otherwise break the network, then logging in to each network allows you a local path (not through a gateway) to the switch in either subnet. You'll lose contact the instant either the gateway or address are changed. When moving to a different subnet, the gateway has to be changed as well. ![]() The instant the command is entered, your telnet session will stop, but you should be able to telnet to the new address and continue. In your case, it's still in the same subnet with the same gateway, so you can just telnet in and change it. To move the switch to a different subnet, that is indeed what is required. The best option is to do it in person from the directly attached console. It can be problematic to change an address remotely. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |