conf vrrp vlan VLAN-Name add backup vrid
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-17-2016 09:02 PM
Surprisingly I could not find any explanation anywhere in Extreme documentation about the below configuration line;
conf vrrp vlan VLAN-Name add backup vrid
--------------------
I know the backup keyword is being used to define vrrp when we have two physical or VLAN IP addresses (one on each switch) and different VIP. or in other words when we are not using the VLAN IP on one of the switches as VIP (means no vrrp priority 255). Priority 255 is the default for vrrp configuration with keyword master.
--------------------
I need advice if the below configuraration has any problem or what exactly the purpose of keyword backup here if my above explanation is not true?
My switches configuration: Both switches have unique IP addresses for VLAN1 from the same IP subnet.
Switch-1
configure vrrp vlan "VLAN1" add backup vrid 1 10.136.225.177
configure vrrp vlan "VLAN1" vrid 1 advertisement-interval 1
configure vrrp vlan "VLAN1" vrid 1 priority 100
configure vrrp vlan "VLAN1" vrid 1 preempt
configure vrrp add vlan "VLAN1"
enable vrrp
Switch-2
configure vrrp vlan "VLAN1" add backup vrid 1 10.136.225.177
configure vrrp vlan "VLAN1" vrid 1 advertisement-interval 1
configure vrrp vlan "VLAN1" vrid 1 priority 60
configure vrrp vlan "VLAN1" vrid 1 dont-preempt
configure vrrp add vlan "VLAN1"
enable vrrp
--------------------------------------------------------
What is the difference between the above and below config.
configure vrrp vlan "VLAN1" vrid 1 priority 100
configure vrrp vlan "VLAN1" vrid 1 add 10.136.225.177
enable vrrp
We have 50-60 pairs of switches where similar configuration (as above Switch-1 &2) is running fine since many years and only one pair is giving problems where vrrp is master-master on both switches. Our support team is rejecting the above configuration stating that there is no definition of keyword backup in extreme manuals so they will not work on it for resolution.
Thanks
Harkanwaljeet Singh
conf vrrp vlan VLAN-Name add backup vrid
--------------------
I know the backup keyword is being used to define vrrp when we have two physical or VLAN IP addresses (one on each switch) and different VIP. or in other words when we are not using the VLAN IP on one of the switches as VIP (means no vrrp priority 255). Priority 255 is the default for vrrp configuration with keyword master.
--------------------
I need advice if the below configuraration has any problem or what exactly the purpose of keyword backup here if my above explanation is not true?
My switches configuration: Both switches have unique IP addresses for VLAN1 from the same IP subnet.
Switch-1
configure vrrp vlan "VLAN1" add backup vrid 1 10.136.225.177
configure vrrp vlan "VLAN1" vrid 1 advertisement-interval 1
configure vrrp vlan "VLAN1" vrid 1 priority 100
configure vrrp vlan "VLAN1" vrid 1 preempt
configure vrrp add vlan "VLAN1"
enable vrrp
Switch-2
configure vrrp vlan "VLAN1" add backup vrid 1 10.136.225.177
configure vrrp vlan "VLAN1" vrid 1 advertisement-interval 1
configure vrrp vlan "VLAN1" vrid 1 priority 60
configure vrrp vlan "VLAN1" vrid 1 dont-preempt
configure vrrp add vlan "VLAN1"
enable vrrp
--------------------------------------------------------
What is the difference between the above and below config.
configure vrrp vlan "VLAN1" vrid 1 priority 100
configure vrrp vlan "VLAN1" vrid 1 add 10.136.225.177
enable vrrp
We have 50-60 pairs of switches where similar configuration (as above Switch-1 &2) is running fine since many years and only one pair is giving problems where vrrp is master-master on both switches. Our support team is rejecting the above configuration stating that there is no definition of keyword backup in extreme manuals so they will not work on it for resolution.
Thanks
Harkanwaljeet Singh
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-18-2016 03:49 AM
Thanks Kevin. Yes we have summit400-48t and 48si switches which are running since long and due to EoS, these are slowly getting replaced with new hardware.
