[c-nsp] EoMPLS - redunancy?
Robert Crowe
rocrowe at cisco.com
Thu Jan 18 12:03:52 EST 2007
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120
limit/120s/120s31/fspseudo.htm
Rob
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Sean Watkins
Sent: Thursday, January 18, 2007 11:43 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] EoMPLS - redunancy?
Hi,
If I build a EoMLPLS tunnel from say a 3750-M to 3750-3750, I basically
build commands like this:
3750-M A
!
Int loopback0
Ip address 1.2.1.3 255.255.255.255
interface FastEthernet1/0/1
no switchport
no ip address
no cdp enable
xconnect 1.2.1.4 1000 encapsulation mpls no clns route-cache
3750-M B
!
Int loopback0
Ip address 1.2.1.4 255.255.255.255
interface FastEthernet1/0/1
no switchport
no ip address
no cdp enable
xconnect 1.2.1.3 1000 encapsulation mpls no clns route-cache
Which works great.
If I wanted to replace the 3750-B, with a 2 3750s for redundancy, how would
that work? Is there anything in EoMPLS to specify say a second peer?
Ie
Xconnect 1.2.1.3 1000 encapsulation mpls backup 1.2.1.5?
Sean
--
Sean Watkins
North Rock Communications
Phone: 441-540-4102
_______________________________________________
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/
More information about the cisco-nsp
mailing list