VRRP between x670_G2's
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-27-2019 01:40 PM
Good afternoon,
We have a total of 4 x670_G2 switches at one of our customers, connected by backbone (40GB).
2 of them are located in one server room, 2 of them in another (about 200meters).
These switches are operational and can all communicate with eachother.
In order to communicate with the network of our customer, we have a redundant connection, one per server room. We want to use VRRP to create one IP to communicate to/from on our side.
The issue: Both connection switches are Master on the same VRRP.
Our configuration regarding VRRP:
The switches also have this VLAN configured on the backbone ports (tagged).
Question: How do we configure VRRP so that switch A is master until the connection is lost, in which case switch B takes over.
We have a total of 4 x670_G2 switches at one of our customers, connected by backbone (40GB).
2 of them are located in one server room, 2 of them in another (about 200meters).
These switches are operational and can all communicate with eachother.
In order to communicate with the network of our customer, we have a redundant connection, one per server room. We want to use VRRP to create one IP to communicate to/from on our side.
The issue: Both connection switches are Master on the same VRRP.
Our configuration regarding VRRP:
code:
Switch A:
create vlan test tag 99
configure vlan test ipaddress 10.102.99.2/24
enable ipforwarding vlan test
create vrrp vlan test vrid 1
configure vrrp vlan test vrid 1 priority 200
configure vrrp vlan test vrid 1 add 10.102.99.1
enable vrrp
Switch B:
create vlan test tag 99
configure vlan test ipaddress 10.102.99.3/24
enable ipforwarding vlan test
create vrrp vlan test vrid 1
configure vrrp vlan test vrid 1 priority 100
configure vrrp vlan test vrid 1 add 10.102.99.1
enable vrrp
The switches also have this VLAN configured on the backbone ports (tagged).
Question: How do we configure VRRP so that switch A is master until the connection is lost, in which case switch B takes over.
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-27-2019 02:01 PM
Hello Oscar,
In the default log there were no messages other than the setup of neighbours for OSPF.
The configuration to add the ports + some additional config lines for your information:
If the complete configuration is needed to tackle this issue I'll provide it for you.
Niels
In the default log there were no messages other than the setup of neighbours for OSPF.
The configuration to add the ports + some additional config lines for your information:
code:
create vlan "Backbone_1"
configure vlan Backbone_1 tag 101
create vlan "Backbone_2"
configure vlan Backbone_2 tag 102
configure vlan test tag 99
configure vlan test add ports 47,49,53 tagged
configure vlan Backbone_1 add ports 49 tagged
configure vlan Backbone_2 add ports 53 tagged
configure ospf add vlan Backbone_1 area 0.0.0.0
configure ospf add vlan Backbone_2 area 0.0.0.0
configure ospf add vlan test area 0.0.0.0
configure pim add vlan "Backbone_1" sparse
configure pim add vlan "Backbone_2" sparse
enable pim
enable ospf
If the complete configuration is needed to tackle this issue I'll provide it for you.
Niels
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-27-2019 01:55 PM
Hello Niels,
these are used for PIM I think.
Did you add the ports to the vlan ?
Any log messages about multicast ?
these are used for PIM I think.
Did you add the ports to the vlan ?
Any log messages about multicast ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-27-2019 01:52 PM
Hello OscarK,
On all switches are policies active, which contain the following:
And yes I can ping every switch from every other switch, I've not included the complete config since its quite a lot & I would need to blur out customer specific information.
On all switches are policies active, which contain the following:
code:
entry extreme_rp2 {
if match any { }
then {
nlri 239.1.3.0/24 ;
nlri 239.1.4.0/24 ;
nlri 239.249.0.0/24 ;
nlri 239.255.255.0/24 ;
nlri 224.2.127.254/32 ;
}
}
And yes I can ping every switch from every other switch, I've not included the complete config since its quite a lot & I would need to blur out customer specific information.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-27-2019 01:43 PM
In your config there are no ports added to vlan test.
That would make both switches not able to ping eachother.
As you can ping I assume you forgot to add it to this post ?
Are you sure there is no ACL in place to make VRRP active-active ?
That would make both switches not able to ping eachother.
As you can ping I assume you forgot to add it to this post ?
Are you sure there is no ACL in place to make VRRP active-active ?
