How were you able to get to the directly connected switch? What device are you using to talk to it and what is its IP address and subnet mask?
Depending on where you are, you could set your own address to something like 10.235.1.1/8 to get to the good switch. Then change the good switch to use a subnet mask of /8 also. And also put it on the 255 subnet temporarily. So give it an address like 10.255.1.1/8. Reconnect, since you would probably lose your connection. Then connect to the bad switch from the good switch. Fix its config. Then change the good switch back to its original IP address and mask. I think this would work, although depending on where you are, it could cause a cascade of changes you would need to make!? :-) Priscilla Kevin Wigle wrote: > > Our group got a support call that a port wasn't working on a > switch. > > A colleague started looking into the case and found that he > couldn't connect > to the switch. (or ping etc) > > He was able to get to another switch which is directly > connected. > > Using CDP he was able to see that the switch is incorrectly > configured with > the wrong IP address. > > The real subnet is 10.235.x.x but CDP nei det says that the > switch has > 10.255.x.x configured. > > Is there a way we can get to the switch and fix it over the > wire? > > Kevin Wigle > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=63473&t=63469 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
