Network Management

Reply
Occasional Contributor I
Posts: 7
Registered: ‎06-01-2017

Physical interface state up/down

Hi all, can someone help me. How can I stop this from happening?

 

Under network log I get this:

Jun 15 09:43:01 :208084: <WARN> |im| Physical interface GE2/0/44 (interface in dex 333) operational state down
Jun 15 09:43:03 :208083: <WARN> |im| Physical interface GE2/0/44 (interface in dex 333) operational state up

And on system log I get this:

 

Jun 15 09:45:21 :340001: <WARN> |l2m| changing the instance 0 port GE2/0/44 state from FORWARDING to DISCARDING

 

Will unplugging the cable from the port stop the problem?

 

I've been having issues loading the MAC addresses on the WebGui recently and I've been getting this on the CLI:

 

Jun 15 09:45:17 :340004: <WARN> |l2m| Flushing mac-addresses on GE2/0/10 vlan-id 14 due to STP topology change
Jun 15 09:45:17 :340004: <WARN> |l2m| Flushing mac-addresses on GE2/0/10 vlan-id 25 due to STP topology change
Jun 15 09:45:17 :340004: <WARN> |l2m| Flushing mac-addresses on GE2/0/26 vlan-id 11 due to STP topology change
Jun 15 09:45:17 :340004: <WARN> |l2m| Flushing mac-addresses on GE2/0/27 vlan-id 11 due to STP topology change
Jun 15 09:45:17 :340004: <WARN> |l2m| Flushing mac-addresses on GE2/0/28 vlan-id 11 due to STP topology change
Jun 15 09:45:17 :340004: <WARN> |l2m| Flushing mac-addresses on GE2/0/29 vlan-id 11 due to STP topology change
Jun 15 09:45:17 :340004: <WARN> |l2m| Flushing mac-addresses on GE2/0/40 vlan-id 11 due to STP topology change
Jun 15 09:45:17 :340004: <WARN> |l2m| Flushing mac-addresses on GE2/0/40 vlan-id 14 due to STP topology change

 

I am not sure what is causing all these anomalies but its slowly down some of the projects my office want to carry out. We want to make sure that the stack is stable before we can hook up more equipment to it.

 

So I have 3 issues.

 

1) able to populate MAC address on WebGUI.

2) the GE2/0/44 state up/down + going from forwarding to discarding

3) flushing of mac-addresses on various ports on certain vlans due to topology change.

 

Any help would be much appreciated. There is no network loop or any that I know of that is running.

 

MVP
Posts: 1,011
Registered: ‎04-13-2009

Re: Physical interface state up/down

These are spanning tree events. STP is spanning tree protocol.

There is possibly a loop in the network.
Cheers
James

-------------------------------------------------------
-------------------@whereisjrw-------------------
------------------------blog-------------------------
ACCX #540 | ACMX #353 | ACDX #216
-----------Mobility First Expert #11----------
-------------------------------------------------------

If a reply adequately addresses your issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users via search.
MVP
Posts: 554
Registered: ‎11-04-2011

Re: Physical interface state up/down

Is this the same environment as http://community.arubanetworks.com/t5/Network-Management/Flushing-mac-addresses/m-p/299221#M7051 ?

 

Ports going into discarding are because spanning-tree detected a loop. You now also know that interface 2/0/44 is part of the loop, as that one is disabled. You also know that vlans 11, 14 and 25 are affected.

 

Please consult an engineer who can look with you to your deployment. Honestly, spanning-tree issues can be complex to solve if you are unfamiliar with how the protocol works and the troubleshooting commands.There is a loop in your network for sure, and as it also involves multiple VLANs it can be that it is not so obvious to find it and fix it. It can be as simple as having two interfaces connected to another system, like a firewall if that is running in bridging/L2 mode.

 

You can contact your Aruba partner, or if you have a support contract with direct access to Aruba TAC, you can contact them as well.

--
If you have urgent issues, please contact your Aruba partner or Aruba TAC (click for contact details).
Search Airheads
Showing results for 
Search instead for 
Did you mean: