From: Mingzhou Nie (mnie@yahoo.com)
Date: Thu Oct 03 2002 - 19:46:46 GMT-3
There were threads recently discussing about this. If purely for
testing purpose, You can create a tunnel interface with source as the
ethernet interface, and destination of loopback of the peer router, and
do backup interface on the tunnel. As soon as you shutdown switch port,
the loopback route will be gone and tunnel interface will go down.
Ming
--- Dave Stoddard <dstoddard@thrupoint.net> wrote:
> I am interested if someone knows a solution to this dilemma. I don't
> have a
> 3550 to play with, only a Cat5k. When a router uses the backup
> command to
> trigger a dial based on the ethernet going down, the only way to
> trigger the
> dial is for the router's ethernet port protocol to go down, i.e.
> Ethernet0
> is up, line protocol is down. If by shutting down the 3550 interface
> does
> not accomplish this, that could cause an issue when testing/verifying
> that
> your config works. Simply doing a shut on the router's ethernet port
> will
> NOT trigger the router to dial. I just tested this.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf
> Of
> Donny MATEO
> Sent: Tuesday, October 01, 2002 11:27 PM
> To: Pieter Jordaan
> Cc: ccielab@groupstudy.com; nobody@groupstudy.com
> Subject: Re: 3550 vs cat5k shutdown vs set port disable still no one
> has
> come up with a solution
>
>
> Hi,
>
> I dont know what is the problem of this. But if you can't shut down
> the link
> in the switch you can
> always do it on the router. If you shut one end of the link woudn't
> that
> automatically makes the
> other link down, except for L1 connectivity.
> As far as you argument goes, I can't find a good reason why you
> possibly
> want to plug out a cable.
> One thing for sure you can't do that during the test, you can't even
> touch
> the rack. beside what
> good will that do to you, all protocol are running on L2/L3. You just
> need
> to restart L2/L3 stuff, I
> don't suppose L1 will make a difference. If you really need to you
> can
> always reboot the switch /
> router.
> Most problem I found can be solved with either shutdown the interface
> or
> rebooting the devices. I've
> never found a case where I need to physically plug out the cable from
> the
> switch / router to solve a
> problem. If there is L1 problem you can be sure pluging out the cable
> or
> even changing the network
> devices wouldn't do any good.
>
> Donny
>
>
>
> Pieter Jordaan
> <pieterj@is.co.za To:
> ccielab@groupstudy.com
> > cc:
> Sent by: Subject: 3550 vs
> cat5k
> shutdown vs set port disable still no one has come up with a
> nobody@groupstudy solution
> .com
>
>
> 02-10-2002 13:42
> Please respond to
> Pieter Jordaan
>
>
>
>
>
>
> Group
>
>
>
> How do you test certain things if the switch port is still powered
> when it
> is shut down, IE: the attached router interface stays up even when
> you shut
> the 3550 switch port.
>
>
>
> Set port disable, disables the port. Shut just prevents the port from
> passing traffic but the port is still powered.
>
>
>
> Guys I think this is a serous problem. If you have to use the backup
> interface command on an ether interface but you can't make that
> interface go
> down/down how do you test it?
>
>
>
> Also when I debug for an IPX network number on the network I do a
> debug IPX
> packet. I found the debug often doesn't show anything unless you drop
> the
> link to the remote router and then bring it back up. But if shutting
> the
> port doesn't take down the interface on the remote router, the router
> doesn't re-broadcast onto the Ethernet segment and you don't get
> anything
> from it.
>
>
>
> I am sure many people will think of many reasons why they need to
> shut down
> a port on a device.
>
>
>
> Now in either of these scenarios if there may be sections dependant
> on the
> outcome of these tests, which means that you could lose a lot of
> points, on
> the other hand maybe you don't have any requirements in the lab to
> configure
> something like this or your router plugs directly into the other
> router, or
> maybe I'm just pulling this whole thing out of proportion and I worry
> about
> too many little thing.
>
>
>
> So please tell me what to do, but don't come back with answers like
> did you
> check the TTL or time-outs etc. the fact is that the port stays
> powered and
> the remote device attached to the switch still has a link lite, the
> interface is just not passing traffic. Maybe cisco must change the
> command
> on the switch from shut-down to block, cos that will be a more
> realistic
> description.
>
>
>
> And please tell me if I worry about too many little things.
>
>
>
>
>
> 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 message is for information purposes only and its content
> should not be construed as an offer, or solicitation of an offer,
> to buy or sell any banking or financial instruments or services
> and no representation or warranty is given in respect of its
> accuracy, completeness or fairness. The material is subject
> to change without notice. You should take your own independent
> tax, legal and other professional advice in respect of the content
> of this message. This message may contain confidential or
>
=== message truncated ===
=====
Mingzhou Nie, CCIE #10342
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:38 GMT-3