Mailing List Archive: CER-2024 Forwarding Issue's

CER-2024 Forwarding Issue's

Aug 11, 2015, 10:17 PM

Post #1 of 3 (961 views)

Hi,

All this week I've been seeing some strange forwarding issue's and mac-address learning problems.

Currently running a CER-2048C with code version 5.4.0bT183.

I'm not doing any VLL, VPLS or MPLS on it, it's purely just a layer2 switch at this stage.

The symptom's we are seeing;

* Traffic stops forwarding between interfaces

* Unable to learn new mac address's on interfaces

I resolved the issue earlier in the week by performing a reboot of the box as it had been up for 735 days and figured it was just kind of weird bug, but it's started doing it again today.

Any suggestions on where to look on why it can't learn new mac-address's ? theirs currently only 250 mac's in the table. One workaround I have done today and previously was to move traffic into a vlan that's already tagged on the same ports and changing downstream switches to matchup, it's a nasty workaround I know, and I'm surprised it will re-learn the mac's with a different VLAN, if I attempt to create a new VLAN it will not learn mac-address's on the new VLAN either.

Any assistance would be appreciated.

Regards,

Daniel Hooper | Network Manager | Goldnet | ph +61 8 9080 5111 | fax +61 8 9021 0222 | Shop 1, 97 Forrest St, Kalgoorlie WA 6430 | PO Box 1043, Kalgoorlie WA 6430 | dhooper@gold.net.au<mailto:dhooper@gold.net.au>

Re: CER-2024 Forwarding Issue's [ In reply to ]

nick at foobar

Aug 12, 2015, 2:03 AM

Post #2 of 3 (941 views)

Permalink

On 12/08/2015 06:17, Daniel Hooper wrote:
> · Traffic stops forwarding between interfaces
> · Unable to learn new mac address’s on interfaces

i've seen similar issues on the ces2k platform after stp topology changes
where l2 forwarding was basically hosed and the unit needed to be rebooted.
It looked at the time like the problem was caused by a temporary
microloop, but it was only a problem on ports which had port security enabled.

The problem went away after we upgraded from 5.4 to 5.6.0c, made the
affected unit singly-homed (i.e. no possibility of loops) and migrated all
the ports to layer 2 acls.

Nick

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Re: CER-2024 Forwarding Issue's [ In reply to ]

dhooper at gold

Aug 12, 2015, 3:35 AM

Post #3 of 3 (942 views)

Permalink

Thanks Nick,

We have STP disabled on this particular switch for "historic" reasons.

On advice from a Brocade rep I'm upgrading the box to 5.6.0ff

We don't run with port-security either, but probably something I should look at rolling out.

As we are connecting a dozen or so customer networks into the chassis that we have no control over I suspect some type of loop in the network is the root cause of the problem.

Regards,

Daniel

-----Original Message-----
From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf Of Nick Hilliard
Sent: Wednesday, 12 August 2015 5:04 PM
To: foundry-nsp@puck.nether.net
Subject: Re: [f-nsp] CER-2024 Forwarding Issue's

On 12/08/2015 06:17, Daniel Hooper wrote:
> * Traffic stops forwarding between interfaces
> * Unable to learn new mac address's on interfaces

i've seen similar issues on the ces2k platform after stp topology changes where l2 forwarding was basically hosed and the unit needed to be rebooted.
It looked at the time like the problem was caused by a temporary microloop, but it was only a problem on ports which had port security enabled.

The problem went away after we upgraded from 5.4 to 5.6.0c, made the affected unit singly-homed (i.e. no possibility of loops) and migrated all the ports to layer 2 acls.

Nick

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp