[c-nsp] redundant link

[Rey Martin]

thank you all,
decided to get another converter that has this feature.


rey

> Double check to see if your media converter already supports this
> feature.  On some I have used in the past, this is as simple as
> flipping a dip switch.
> 
> 
> On 8/17/05, Andris Zarins <andris.zarins at microlink.lv> wrote:
>> Hi,
>> 
>> Advice - keep things simple. Get yourself a pair of converters that
>> bring the port up only in case if there is end-to-end connectivity, so
>> port will not stay up if you plug out some wires. They will cost you
>> some extra money (10-20$), but you wouldn't need to configure anything
>> on your networking devices.
>> 
>> Of course you can go for object tracking too, but I'd definately vote
>> against it.
>> 
>> Hope this helps,
>> Andris
>> 
>> 
>> 
>> -----Original Message-----
>> From: cisco-nsp-bounces at puck.nether.net
>> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Rey Martin
>> Sent: Wednesday, August 17, 2005 8:41 AM
>> To: cisco-nsp at puck.nether.net
>> Subject: [c-nsp] redundant link
>> 
>> Hi there..
>> 
>> im setting up 2 redundant link for our customer, using 2 100fx
>> connection.
>> however both end using 10/100TX to 100FX converter because both end
>> devices
>> has only 100TX port available
>> 
>> the only reason we use 100FX between 2 device (cat 3550 and 3600)
>>  was because of the distance (400m+)
>> 
>> I thought the setup will be straight forward, 2 identical static route
>> with
>> different administrative distance.
>> however when we unplug the cat5 cable on one end, the other end
>> interface
>> line protocol still shows as "UP"
>> (because of the 100TX to 100FX converter) so the failover failed.
>> 
>> i was thinking to use object tracking (icmp echo),
>>  but the "ip route x.x.x.x  y.y.y.y track z" command seems not available
>> yet
>> for cat 3550.
>> although the other commands seems available.
>> 
>> cat3550(config)#ip route 1.1.1.1 255.255.255.255 2.2.2.2 ?
>>   <1-255>    Distance metric for this route
>>   name       Specify name of the next hop
>>   permanent  permanent route
>>   tag        Set tag for this route
>>   <cr>
>> 
>> any help would be highly appreciated!!
>> Thanks
>> 
>> 
>> rey
>> 
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>> 
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>> 
> 
> 
> -- 
> ----------------------------------------
> wojtek.zlobicki at gmail.com
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/