Re: 3560 Switch Mac Add Flapping facing NE40(huawei Router) - Page 3

joshualuna12 · ‎01-09-2014

Hi Guys,

Logs seen on switch:

FLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:26:37: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:27:06: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 252 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:28:06: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:28:37: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:29:10: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:31:50: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:32:26: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:32:39: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:33:28: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:34:34: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:35:38: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:36:35: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:37:39: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:38:06: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:38:38: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:39:00: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:40:40: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:41:15: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:41:38: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:42:45: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:43:27: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:43:40: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:43:59: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:46:01: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:46:57: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:47:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to down

Jan 7 17:47:30: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down

Jan 7 17:48:03: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:48:44: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/25 and port Gi0/26

Jan 7 17:49:02: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:49:46: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:50:14: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Jan 7 17:50:49: %SW_MATM-4-MACFLAP_NOTIF: Host 707b.e8b9.5a36 in vlan 250 is flapping between port Gi0/26 and port Gi0/25

Switch Configuration:

!

interface GigabitEthernet0/25

switchport trunk encapsulation dot1q

switchport trunk allowed vlan 250-252

switchport mode trunk

speed nonegotiate

!

interface GigabitEthernet0/26

switchport trunk encapsulation dot1q

switchport trunk allowed vlan 250-252

switchport mode trunk

speed nonegotiate

!

--------------

I believe that NE40(huawei router) is configured with VRRP and Layer 3 Port Channel,

so I tried to configure port channel(but only Layer 2..because of not capable of sub interface port chan/ needed because we have VLANS with IPs) for Gi0/25 & Gi0/26... the flapping is gone but some error appeared in NE40 router.See below.

Jan 3 2014 15:36:26+08:00 CNR-CS-RTR-002 %%01VRRP/4/STATEWARNINGEXTEND(l)[0]:Virtual Router state MASTER changed to BACKUP, because of priority calculation. (Interface=Eth-Trunk11.250, VrId=7, InetType=IPV4)
Jan 3 2014 15:36:26+08:00 CNR-CS-RTR-002 %%01VRRP/4/STATEWARNINGEXTEND(l)[1]:Virtual Router state BACKUP changed to MASTER, because of protocol timer expired. (Interface=Eth-Trunk11.250, VrId=7, InetType=IPV4)
Jan 3 2014 15:36:25+08:00 CNR-CS-RTR-002 %%01VRRP/4/STATEWARNINGEXTEND(l)[2]:Virtual Router state MASTER changed to BACKUP, because of priority calculation. (Interface=Eth-Trunk11.251, VrId=8, InetType=IPV4)
Jan 3 2014 15:36:25+08:00 CNR-CS-RTR-002 %%01VRRP/4/STATEWARNINGEXTEND(l)[3]:Virtual Router state BACKUP changed to MASTER, because of protocol timer expired. (Interface=Eth-Trunk11.251, VrId=8, InetType=IPV4)
Jan 3 2014 15:35:24+08:00 CNR-CS-RTR-002 %%01VRRP/4/STATEWARNINGEXTEND(l)[4]:Virtual Router state MASTER changed to BACKUP, because of priority calculation. (Interface=Eth-Trunk11.252, VrId=9, InetType=IPV4)

FYI. Ne40 is a third party device.

Is it not possible to have Layer 2 and layer 3 portchannel connectivity? if not, based on above info what do you recommend?

Can you please help me guys. Thanks

Jon Marshall · ‎01-15-2014

Josh

I missed these bits from your last post -

Can you tell me why there are hellos From HT router sent going to the switch? Is it for link checking like "track in HSRP?"

It's not tracking as such it is just hello packets ie the hello are sent so each router can keep a check on the other routers state in case one of them needs to take over. Your switch is seeing them because that is the L2 path between the HT routers.

is it supposed to be HT subinterface IP to use?

That's the main question. I think maybe you should talk to the people who setup the HT routers to find out what they think should be happening. It may just be a miscommunication issue.

Jon

joshualuna12 · ‎01-15-2014

Hi Jon

"The question i would have now is if the switches are doing inter vlan routing what are the HT routers for ie. what is their purpose. That's what i was trying to ask before. You don't just connect up devices without knowing why you are doing it. Again no criticism is intended, i am just trying to understand what you are trying to achieve.

My best guess at the moment is that the HT routers are used to give you access to remote networks from the client vlans and for remote networks to get to the client vlans. If that is correct and i need you to confirm this then i am not clear why they are using subinterfaces with VRRP."

First the vlans are for Signalling, Application, OAM and Monitoring Servers .

Devices connected to SW:

Cisco ITP router 7600 - used for sigtran

Monitoring Servers

You are right, HT routers are the core routers

"

Is the idea that the switches only use one of the HT routers (ie the VRRP master) to route to remote networks and then if the active HT router fails it moves over to the other one ?

If so i am not clear on why they are using subinterfaces ie. you only need one L3 interface per HT router for the routing.

"

Yes, it is for HA purposes.

Is it wrong that they configure vrrp per vlan subinterface instead they should have use the L3 int?

Also I missed out to tell you that the two Switches are running in HSRP.

It's not tracking as such it is just hello packets ie the hello are sent so each router can keep a check on the other routers state in case one of them needs to take over. Your switch is seeing them because that is the L2 path between the HT routers.

So HT router 1 and HT router 2 use the switch to send VRRP hellos/heartbeat. Did I get it right?

Is it possible that VRRP hellos/heartbeat are send directly from/to the routers if they have direct connection?

ITP --------SW1 =======HT Router 1

\ ||

\---------SW2 =======HT Router 1

JOsh

Jon Marshall · ‎01-15-2014

Josh

Yes, you did get it right, the routers are using the links to send VRRP hellos and yes if they had a direct connection they could use that but the interface would need to be L2 and that may not be possible on a router (it depends). But that might not solve the problem anyway as really the routers need to see each other via the switch links if you want to run VRRP on the HT routers.

So is it right to say that you want to only use one HT router for the connectivity but if that fails then use the other one ?

Either way, whether you want to use one HT router or both at the same time there are alternatives to the solution you have. It would be better if you could use both HT routers at the same time and then you simply configure both ends as L3 etherchannels and there is no need for VRRP at all because the switches can use both HT routers at the same time.

However this may not be an option so could you answer the question above and we can take it from there.

Jon

joshualuna12 · ‎01-15-2014

Hi Jon

In what manner did the VRRP hellos passing to switch? Are the VRRP hellos in vlan? native/untagged frames..Idk?

I raised the question because the ports facing the HT routers allowed only the said vlan in the previous messages. Just thinking.

So is it right to say that you want to only use one HT router for the connectivity but if that fails then use the other one ?

Yes that's right. Active / Standby for the routers.

Josh

Jon Marshall · ‎01-15-2014

Josh

VRRP hellos will be sent per vlan so if you have multiple vlans on the etherchannel trunk link then the subinterfaces on the HTrouters will send VRRP hellos per subinterface.

Okay, active/standby it is. On the switches can you do the following (you need to have the etherchannels to the HT routers up and running and they need to configured as L2 etherchannel trunks on the switches) -

1) post the output of "sh int trunk"

2) post the output of "sh vlan brief"

for 1) can you indicate which trunk connects to what ie. there will be at least 3 trunks shown using port channel interfaces so i need you to confirm which port channel connects to what eg.

po1 connects to HT1

po2 connects to the other switch

each switch will have a connection to one of the routers and to the other switch.

I need the outputs from both switches.

Jon