Re: Lost Switch [7:63469]

2003-02-21 Thread John Neiberger
The simplest and least-intrusive method I can think of would be to use
mobile arp.  Simply add 'ip arp mobile' or whatever the exact command is
to the router interface leading to that switch.  Then perhaps an a
static host route on that same interface pointing to that oddball IP
address.  That would allow you to access that specific IP address
without causing any other routing issues should you be using that same
subnet somewhere else in your network.

Regards,
John

>>> "Kevin Wigle"  2/20/03 9:19:42 PM >>>
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=63513&t=63469
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Lost Switch [7:63469]

2003-02-21 Thread Dave Swink
Kevin,

How about adding a secondary address to the router interface, that would
allow you to telnet to the switch and change it's address.

Dave Swink

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Kevin Wigle
Sent: Thursday, February 20, 2003 10:20 PM
To: [EMAIL PROTECTED]
Subject: Lost Switch [7:63469]


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=63491&t=63469
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Lost Switch [7:63469]

2003-02-20 Thread Priscilla Oppenheimer
Scott Nelson wrote:
> 
> Yep. I forgot about that trick.  
> 
> If he is on the same vlan and can arp with it, I would just
> setup a laptop with the same network range and go from there
> actually.

Oh, that's a good point. If the switch he can get to is just a L2 switch, it
doesn't care. :-)

So he could just make his PC be something like 10.255.1.1 and get to the bad
switch that way through the good L2 switch that doesn't care.

But maybe it's a L3 switch (argh). :-) Then he has to do more tinkering,
like I said.

Priscilla

> 
> Scotty
> 




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=63479&t=63469
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Lost Switch [7:63469]

2003-02-20 Thread Scott Nelson
Yep. I forgot about that trick.  

If he is on the same vlan and can arp with it, I would just setup a laptop
with the same network range and go from there actually.

Scotty



Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=63475&t=63469
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Lost Switch [7:63469]

2003-02-20 Thread Priscilla Oppenheimer
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]



RE: Lost Switch [7:63469]

2003-02-20 Thread Scott Nelson
That blows!!  

Uh, can you give me a clue as to which model switch you are talking about?

Maybe a secondary address on the port going to the second switch, with the
wrong address as the secondary?
Does it have trunking to the second switch? Can you put yourself in the vlan
with the switch and with a computer on the same vlan, set the laptop in the
same subnet as the switch and do it that way?

Just tossing stuff out here  ;-)

Scotty



Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=63472&t=63469
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]