From: Pieter Jordaan (pieterj@is.co.za)
Date: Tue Oct 01 2002 - 03:01:01 GMT-3
Sam
That's exactly what this post is about. The set port disable works on the
cat5k switches but it doesn't work on the 2900/3500 series switches. The
router interface still stays up it just doesn't pass any traffic through the
switch, which means the backup interface parameter cant be tested.
I am looking for an alternative as pulling the cable out of the switch isn't
an option here is SA. We are tested remotely on the racks that are in
Brussels.
Any ideas
-----Original Message-----
From: SamB [mailto:sampeters20@hotmail.com]
Sent: 01 October 2002 07:55 AM
To: Pieter Jordaan
Subject: Re: How to shut a interface on a switch
There is no "other" Ethernet encapsulation. If your thinking of
PPP/HDLC/Frame... That's on serial interfaces (layer 2/3 and above) your
question is like what other encapsulation other than serial can you use on a
serial port?
Use the "set port disable <mod/port>" command to shut the port down.
-Sam
----- Original Message -----
From: "Pieter Jordaan" <pieterj@is.co.za>
To: <ccielab@groupstudy.com>
Sent: Monday, September 30, 2002 10:28 PM
Subject: RE: How to shut a interface on a switch
> How would one go about changing the encapsulation on an Ethernet switch
> interface. I only have a 2900 and can find an encapsulation command under
> the interface. Am I missing something here? I know this trick works for
> serial interfaces but what other encapsulations do you get for Ethernet
> interfaces?
>
> TIA
>
> -----Original Message-----
> From: Becky Qiang [mailto:becky.qiang@wincomsystems.com]
> Sent: 01 October 2002 02:46 AM
> To: Adam Crisp; Pieter Jordaan; ccielab@groupstudy.com
> Subject: Re: How to shut a interface on a switch
>
> If you just want to test the backup interface, why don't you encapsulate
the
> interface with another type, I am sure this will bring down the
> interface...Becky
>
>
> ----- Original Message -----
> From: "Adam Crisp" <adam.crisp@totalise.co.uk>
> To: "Pieter Jordaan" <pieterj@is.co.za>; <ccielab@groupstudy.com>
> Sent: Monday, September 30, 2002 4:31 AM
> Subject: RE: How to shut a interface on a switch
>
>
> > I think this is an Ethernet thing, the same happens on back ro back
> Routers
> > with a X-over cable
> > I think it's because the devices don't close down the electrical carrier
> > when admin shutting the interface and the electrical carrier is how the
> > interface is determined up.
> > I haven't tried it on a 3550, but I would imageing that the behavour is
> the
> > same!
> >
> > Adam
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Pieter Jordaan
> > Sent: 30 September 2002 11:45
> > To: ccielab@groupstudy.com
> > Subject: How to shut a interface on a switch
> >
> >
> > Hi group
> >
> > I was wondering if any of you could answer this question.
> >
> > I have noticed on the 2924 and 2950 switches that when I shut an
> interface,
> > the router attached don't go into a down/down state. The link stays up.
> >
> > This could be a potential problem if you want to test for example, your
> > backup interface command by shutting the port on the switch because the
> > router interface doesn't go down.
> >
> > Does this also happen on the 3550 and if so, how would you test things
in
> > the lab if shutting down the switch interface doesn't shut/kill the link
> > like on the cat5k
> >
> > TIA
> >
> >
> >
> >
> > "This e-mail may contain confidential information and may be legally
> > privileged and is intended only for the person to whom it is addressed.
If
> > you are not the intended recipient, you are notified that you may not
use,
> > distribute or copy this document in any manner whatsoever. Kindly also
> > notify the sender immediately by telephone, and delete the e-mail. When
> > addressed to clients of the company from where this e-mail originates
> ("the
> > sending company ") any opinion or advice contained in this e-mail is
> subject
> > to the terms and conditions expressed in any applicable terms of
business
> or
> > client engagement letter . The sending company does not accept liability
> for
> > any damage, loss or expense arising from this e-mail and/or from the
> > accessing of any files attached to this e-mail."
>
>
>
>
> "This e-mail may contain confidential information and may be legally
> privileged and is intended only for the person to whom it is addressed. If
> you are not the intended recipient, you are notified that you may not use,
> distribute or copy this document in any manner whatsoever. Kindly also
> notify the sender immediately by telephone, and delete the e-mail. When
> addressed to clients of the company from where this e-mail originates
("the
> sending company ") any opinion or advice contained in this e-mail is
subject
> to the terms and conditions expressed in any applicable terms of business
or
> client engagement letter . The sending company does not accept liability
for
> any damage, loss or expense arising from this e-mail and/or from the
> accessing of any files attached to this e-mail."
>
"This e-mail may contain confidential information and may be legally
privileged and is intended only for the person to whom it is addressed. If
you are not the intended recipient, you are notified that you may not use,
distribute or copy this document in any manner whatsoever. Kindly also
notify the sender immediately by telephone, and delete the e-mail. When
addressed to clients of the company from where this e-mail originates ("the
sending company ") any opinion or advice contained in this e-mail is subject
to the terms and conditions expressed in any applicable terms of business or
client engagement letter . The sending company does not accept liability for
any damage, loss or expense arising from this e-mail and/or from the
accessing of any files attached to this e-mail."
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:36 GMT-3