Mailing List Archive

Two VSRP Masters on XMR units
Hi all-

Having a little trouble with VSRP on a couple of XMRs running 5500e with BigIron-RX units in between. After configuration, both units claim to have mastership, which is no good. Hoping someone can scan the below configs and tell me how I'm not worthy. Any help is, as always, appreciated.

XMR1
Current configuration:
!
ver V5.5.0eT163
module 1 ni-xmr-20-port-1g-copper
module 2 ni-xmr-20-port-1g-copper
!
!
!
!

!
no spanning-tree
!
!
vlan 1 name DEFAULT-VLAN
!
vlan 50 name interconnect
untagged ethe 1/8
router-interface ve 50
!
vlan 133 name test
untagged ethe 1/20
router-interface ve 133
vsrp vrid 133
backup
track-port ethe 1/11
enable

<snip>
router ospf
area 0.0.0.0
redistribute connected
!
!
router vsrp
!
!
!
!
!
!
!
interface ethernet 1/8
enable
!
interface ethernet 1/11
enable
!
interface ethernet 1/20
enable
!
interface ve 50
ip ospf area 0.0.0.0
ip address 172.16.1.2/29
!
interface ve 133
ip ospf area 0.0.0.0
ip ospf passive
ip address 216.171.239.1/29


XMR2
Current configuration:
!
ver V5.5.0eT163
module 1 ni-xmr-20-port-1g-copper
module 2 ni-xmr-20-port-1g-copper
!
!
!
!

!
no spanning-tree
!
!
vlan 1 name DEFAULT-VLAN
!
vlan 50 name interconnect
untagged ethe 1/8
router-interface ve 50
!
vlan 133 name test
untagged ethe 1/20
router-interface ve 133
vsrp vrid 133
backup priority 150
track-port ethe 1/11 priority 60
enable

<snip>

router ospf
area 0.0.0.0
redistribute connected
!
!
router vsrp
!
!
!
!
!
!
!
interface management 1
ip address 192.168.10.106/24
enable
!
interface ethernet 1/1
enable
ip ospf area 0.0.0.0
ip address 216.171.224.237/29
!
interface ethernet 1/2
enable
ip ospf area 0.0.0.0
ip address 216.171.224.131/29
!
interface ethernet 1/8
enable
!
interface ethernet 1/11
enable
spanning-tree protect
cluster-l2protocol-forward disable
!
interface ethernet 1/20
enable
!
interface ve 50
ip ospf area 0.0.0.0
ip address 172.16.1.1/29
!
interface ve 133
ip ospf area 0.0.0.0
ip ospf passive
ip address 216.171.239.1/29


Thanks for any and all help, as always.

Dave Peters
415 795 2463 | AIM: terabitdave
Terabit Systems LLC, 2565 3rd St #218, San Francisco, CA 94107
[Description: TB-logo-new-150x46]<http://www.terabitsystems.com/>[Description: twitter_centered]<https://twitter.com/TerabitSystems>[Description: linkedin_centered]<http://www.linkedin.com/company/1098784?trk=tyah>
Re: Two VSRP Masters on XMR units [ In reply to ]
Be sure 'no route-only' is configured on every ethernet interface
involved. XMR/MLX default all interfaces to route only (which disables
layer 2 forwarding for packets that aren't being routed).

I'm not sure on the default for the bigiron, but I'd check that one first.
The default can also be changed globally. This has bit me more than once.

--
Eldon Koyle
--
Please excuse my autocorrect
On Sep 16, 2015 12:16 PM, "Dave Peters - Terabit Systems" <
Dave@terabitsystems.com> wrote:

> Hi all—
>
>
>
> Having a little trouble with VSRP on a couple of XMRs running 5500e with
> BigIron-RX units in between. After configuration, both units claim to have
> mastership, which is no good. Hoping someone can scan the below configs and
> tell me how I’m not worthy. Any help is, as always, appreciated.
>
> *XMR1*
>
> Current configuration:
>
> !
>
> ver V5.5.0eT163
>
> module 1 ni-xmr-20-port-1g-copper
>
> module 2 ni-xmr-20-port-1g-copper
>
> !
>
> !
>
> !
>
> !
>
>
>
> !
>
> no spanning-tree
>
> !
>
> !
>
> vlan 1 name DEFAULT-VLAN
>
> !
>
> vlan 50 name interconnect
>
> untagged ethe 1/8
>
> router-interface ve 50
>
> !
>
> vlan 133 name test
>
> untagged ethe 1/20
>
> router-interface ve 133
>
> vsrp vrid 133
>
> backup
>
> track-port ethe 1/11
>
> enable
>
>
>
> <snip>
>
> router ospf
>
> area 0.0.0.0
>
> redistribute connected
>
> !
>
> !
>
> router vsrp
>
> !
>
> !
>
> !
>
> !
>
> !
>
> !
>
> !
>
> interface ethernet 1/8
>
> enable
>
> !
>
> interface ethernet 1/11
>
> enable
>
> !
>
> interface ethernet 1/20
>
> enable
>
> !
>
> interface ve 50
>
> ip ospf area 0.0.0.0
>
> ip address 172.16.1.2/29
>
> !
>
> interface ve 133
>
> ip ospf area 0.0.0.0
>
> ip ospf passive
>
> ip address 216.171.239.1/29
>
>
>
>
>
> *XMR2*
>
> Current configuration:
>
> !
>
> ver V5.5.0eT163
>
> module 1 ni-xmr-20-port-1g-copper
>
> module 2 ni-xmr-20-port-1g-copper
>
> !
>
> !
>
> !
>
> !
>
>
>
> !
>
> no spanning-tree
>
> !
>
> !
>
> vlan 1 name DEFAULT-VLAN
>
> !
>
> vlan 50 name interconnect
>
> untagged ethe 1/8
>
> router-interface ve 50
>
> !
>
> vlan 133 name test
>
> untagged ethe 1/20
>
> router-interface ve 133
>
> vsrp vrid 133
>
> backup priority 150
>
> track-port ethe 1/11 priority 60
>
> enable
>
>
>
> <snip>
>
>
>
> router ospf
>
> area 0.0.0.0
>
> redistribute connected
>
> !
>
> !
>
> router vsrp
>
> !
>
> !
>
> !
>
> !
>
> !
>
> !
>
> !
>
> interface management 1
>
> ip address 192.168.10.106/24
>
> enable
>
> !
>
> interface ethernet 1/1
>
> enable
>
> ip ospf area 0.0.0.0
>
> ip address 216.171.224.237/29
>
> !
>
> interface ethernet 1/2
>
> enable
>
> ip ospf area 0.0.0.0
>
> ip address 216.171.224.131/29
>
> !
>
> interface ethernet 1/8
>
> enable
>
> !
>
> interface ethernet 1/11
>
> enable
>
> spanning-tree protect
>
> cluster-l2protocol-forward disable
>
> !
>
> interface ethernet 1/20
>
> enable
>
> !
>
> interface ve 50
>
> ip ospf area 0.0.0.0
>
> ip address 172.16.1.1/29
>
> !
>
> interface ve 133
>
> ip ospf area 0.0.0.0
>
> ip ospf passive
>
> ip address 216.171.239.1/29
>
>
>
>
>
> Thanks for any and all help, as always.
>
>
>
> Dave Peters
>
> 415 795 2463 | AIM: terabitdave
>
> Terabit Systems LLC, 2565 3rd St #218, San Francisco, CA 94107
>
> [image: Description: TB-logo-new-150x46] <http://www.terabitsystems.com/>[image:
> Description: twitter_centered] <https://twitter.com/TerabitSystems>[image:
> Description: linkedin_centered]
> <http://www.linkedin.com/company/1098784?trk=tyah>
>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
Re: Two VSRP Masters on XMR units [ In reply to ]
Worked!

That explained itself almost before you finished typing it out. Thanks so much. All of you guys are great.

--Dave Peters

From: ekoyle@gmail.com [mailto:ekoyle@gmail.com] On Behalf Of Eldon Koyle
Sent: Saturday, September 19, 2015 11:30 PM
To: Dave Peters - Terabit Systems
Cc: foundry-nsp@puck.nether.net
Subject: Re: [f-nsp] Two VSRP Masters on XMR units


Be sure 'no route-only' is configured on every ethernet interface involved. XMR/MLX default all interfaces to route only (which disables layer 2 forwarding for packets that aren't being routed).

I'm not sure on the default for the bigiron, but I'd check that one first. The default can also be changed globally. This has bit me more than once.

--
Eldon Koyle
--
Please excuse my autocorrect
On Sep 16, 2015 12:16 PM, "Dave Peters - Terabit Systems" <Dave@terabitsystems.com<mailto:Dave@terabitsystems.com>> wrote:
Hi all—

Having a little trouble with VSRP on a couple of XMRs running 5500e with BigIron-RX units in between. After configuration, both units claim to have mastership, which is no good. Hoping someone can scan the below configs and tell me how I’m not worthy. Any help is, as always, appreciated.
XMR1
Current configuration:
!
ver V5.5.0eT163
module 1 ni-xmr-20-port-1g-copper
module 2 ni-xmr-20-port-1g-copper
!
!
!
!

!
no spanning-tree
!
!
vlan 1 name DEFAULT-VLAN
!
vlan 50 name interconnect
untagged ethe 1/8
router-interface ve 50
!
vlan 133 name test
untagged ethe 1/20
router-interface ve 133
vsrp vrid 133
backup
track-port ethe 1/11
enable

<snip>
router ospf
area 0.0.0.0
redistribute connected
!
!
router vsrp
!
!
!
!
!
!
!
interface ethernet 1/8
enable
!
interface ethernet 1/11
enable
!
interface ethernet 1/20
enable
!
interface ve 50
ip ospf area 0.0.0.0
ip address 172.16.1.2/29<http://172.16.1.2/29>
!
interface ve 133
ip ospf area 0.0.0.0
ip ospf passive
ip address 216.171.239.1/29<http://216.171.239.1/29>


XMR2
Current configuration:
!
ver V5.5.0eT163
module 1 ni-xmr-20-port-1g-copper
module 2 ni-xmr-20-port-1g-copper
!
!
!
!

!
no spanning-tree
!
!
vlan 1 name DEFAULT-VLAN
!
vlan 50 name interconnect
untagged ethe 1/8
router-interface ve 50
!
vlan 133 name test
untagged ethe 1/20
router-interface ve 133
vsrp vrid 133
backup priority 150
track-port ethe 1/11 priority 60
enable

<snip>

router ospf
area 0.0.0.0
redistribute connected
!
!
router vsrp
!
!
!
!
!
!
!
interface management 1
ip address 192.168.10.106/24<http://192.168.10.106/24>
enable
!
interface ethernet 1/1
enable
ip ospf area 0.0.0.0
ip address 216.171.224.237/29<http://216.171.224.237/29>
!
interface ethernet 1/2
enable
ip ospf area 0.0.0.0
ip address 216.171.224.131/29<http://216.171.224.131/29>
!
interface ethernet 1/8
enable
!
interface ethernet 1/11
enable
spanning-tree protect
cluster-l2protocol-forward disable
!
interface ethernet 1/20
enable
!
interface ve 50
ip ospf area 0.0.0.0
ip address 172.16.1.1/29<http://172.16.1.1/29>
!
interface ve 133
ip ospf area 0.0.0.0
ip ospf passive
ip address 216.171.239.1/29<http://216.171.239.1/29>


Thanks for any and all help, as always.

Dave Peters
415 795 2463<tel:415%20795%202463> | AIM: terabitdave
Terabit Systems LLC, 2565 3rd St #218, San Francisco, CA 94107
[Description: TB-logo-new-150x46]<http://www.terabitsystems.com/>[Description: twitter_centered]<https://twitter.com/TerabitSystems>[Description: linkedin_centered]<http://www.linkedin.com/company/1098784?trk=tyah>


_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net<mailto:foundry-nsp@puck.nether.net>
http://puck.nether.net/mailman/listinfo/foundry-nsp