08-25-2020 02:00 AM
Hi community,
I think I missed a configuration line for HSRP. The question is, how the multicast-packets of hsrp v2 are communicated if the hsrp members are configured within a physical subinterface.
Setup:
Fortigate500E Port9 =(like Portchanenl)= Fortigate500E Port10
| |
Eth3/48.27 Eth3/48.27
HSRP27 HSRP27
NX7010-1 -> VPC PEER LINK (with VLAN27) <- NX7010-2
Behavior:
Both Nexus N7K are in a VPC with each other, all vlans are allowed on PEER-Link. On both I have a Vlan20 interface configured with HSRP v2 Group 20. There the HSRP works, so the HSRP multicast-packets have to go over the PEER-Link, in VLAN20 I think. There is no other connection for Vlan 20.
Now I configured Subinterfaces of ETH3/48 with HSRP and a vlan encapsulation 27. But the mutlicast-packets were not received. So I think here is a missing command, that the HSRP for VLAN27 has to be announced over the VPC-PEER.
Could you help?
Configuration:
NX7010-1:
interface Ethernet3/48
description RT-IT-FW-4_CHK
no switchport
no shutdown
interface Ethernet3/48.27
description Transfer_RT-IT-FW-4
encapsulation dot1q 27
no ip redirects
ip address 10.4.5.2/24
ip pim sparse-mode
hsrp version 2
hsrp 27
authentication text DMZ27
preempt delay minimum 300
priority 105
ip 10.4.5.1
no shutdown
show hsrp group 27 brief
Interface Grp Prio P State Active addr Standby addr Group addr
Eth3/48.27 27 105 P Active local unknown 10.4.5.1
NX7010-2:
interface Ethernet3/48
description RT-IT-FW-4_CHK
no switchport
no shutdown
interface Ethernet3/48.27
description Transfer_RT-IT-FW-4
encapsulation dot1q 27
no ip redirects
ip address 10.4.5.3/24
ip pim sparse-mode
hsrp version 2
hsrp 27
authentication text DMZ27
preempt delay minimum 300
priority 95
ip 10.4.5.1
no shutdown
show hsrp group 27 brief
Interface Grp Prio P State Active addr Standby addr Group addr
Eth3/48.27 27 95 P Active local unknown 10.4.5.1
Solved! Go to Solution.
08-25-2020 07:44 AM
Hi
Making a port no switchport, will set that port to "routerport". You can, as You have done, then make subinterfaces. Each subinterface must have it's own encapsulation-number. What encapsulation have you configured for the subinterface ? The number of the subinterface (.27) in your example has nothing to do with vlan27. Whatever encapsulation you configure, it will not sent packet through the vpc link, it will only send packets out of the port. And that packet will be encapsulated with the dot1q tag you have configured. So for your hsrp to work it must be able to communicate with each other outside the nexus.
/Mikael
08-25-2020 11:53 PM
So I found a way that I can connect both physical port without an extra device. The both remote ports on the Fortigate can be connected as a switch, so the Fortigate can have a virtual port there do be addressed and the nexus-switches can see each other over the fortigate - hsrp is working.
Thank you for your help!
08-25-2020 02:48 AM
yes VLAN 27 required to be allowed in vPC link to establish HSRP.
08-25-2020 02:54 AM
08-25-2020 02:59 AM
is VLAN created both the side ?
can you post show spanning-tree for VLAN 27 ?
08-25-2020 04:43 AM
08-25-2020 06:14 AM
I will start with Ping - is the ping working between the IP configured on VLAN 27
can you able to ping .2 to .3 ? (other test, are you able to ping locally - i have seen weird issue some time back, locally not able to ping some times, so i have to delete the interface and re-create to work).
remove authentication and check
Can you post below information : from both the devices ?
show run interface eth 3/48
show hsrp interface Ethernet3/48.27
08-25-2020 06:47 AM
08-25-2020 06:50 AM
08-25-2020 07:44 AM
Hi
Making a port no switchport, will set that port to "routerport". You can, as You have done, then make subinterfaces. Each subinterface must have it's own encapsulation-number. What encapsulation have you configured for the subinterface ? The number of the subinterface (.27) in your example has nothing to do with vlan27. Whatever encapsulation you configure, it will not sent packet through the vpc link, it will only send packets out of the port. And that packet will be encapsulated with the dot1q tag you have configured. So for your hsrp to work it must be able to communicate with each other outside the nexus.
/Mikael
08-25-2020 01:53 PM - edited 08-25-2020 02:06 PM
As shown in one of the first posts I configured "encapsulation dot1q 27" on both interfaces. I was observing, that the firewall is getting VLAN encapsulated packets. So packets really leave the Nexus with flag Vlan 27. Because both subinterfaces are not able to ping each other, I wonder if they can reach each other over vlan 27 via VPC link.
With your last post you confirm that it is not possible that Subinterfaces can put their HSRP multicast traffic into the VPC link.
I hoped I can avoid any scripting/tracking if routes get disabled caused by a port down event. So I would like to have a Layer3 interface which go offline if the port goes down. Also it is the simplest way to configure the Fortigate, if there is only one address / virtual router.
On the other hand in the other VDC there is an almost similar setup, which is working with HSRP. This domain is a little bit more complicated so I cannot say that there aren't links that may transport the hsrp traffic besides the VPC PEER.
Is there a difference of hsrp behavior with portchannel subinterfaces instead of Ethernet subinterfaces?
08-25-2020 08:16 AM
Looks like some information we are missing here ?
Do you have any high level diagram ? where this port connected 3/48 ? 3/48 is connected to FW ?
As per my understand we are doing 2 different task here .
i
08-25-2020 02:22 PM
08-25-2020 11:53 PM
So I found a way that I can connect both physical port without an extra device. The both remote ports on the Fortigate can be connected as a switch, so the Fortigate can have a virtual port there do be addressed and the nexus-switches can see each other over the fortigate - hsrp is working.
Thank you for your help!
08-26-2020 12:58 AM
thanks for th input and glad all working as expected.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide