Ethernet Switches & Routers

Reply
New Contributor
Posts: 4
Registered: ‎08-18-2011

MCT-LAG traffic only on one link.

We have two MLX chassis configured as a cluster to allow MCT.
A Linux Server is connected via LACP to each cluster-unit.


The LAG seems okay, but traffic does only run through one link.

The GbE-interface on the MLX1 nearly peaks, while the other stays low in kilobytes.

Any help how to debug?

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: MCT-LAG traffic only on one link.

Hi krause,

     Is this a test setup or in production?  How many flows are you testing accross the MCT please?

Some extra infor for you.

Use the show cluster client command to display additional State Machine information including thereason for Local CCEP down.

NetIron#show cluster mct client c2

State: Remote Up

Reason for Local CCEP down: "client-interfaces shutdown" command

Number of times Local CCEP down: 2

Number of times Remote CCEP down: 1

Number of times Remote Client undeployed: 1

Total CCRR packets sent: 12

Total CCRR packets received: 13

Syntax: show cluster client

Syslogs and debugging

Syslogs are displayed when remote CCEP is state is changed or remote client is deployed or

undeployed.

SYSLOG: Jun 1 15:43:36:<14>Jun 1 15:43:36 CES, CLUSTER FSM: Cluster mct (Id: 1),

client c2 (RBridge Id: 4) -

Remote client deployed

SYSLOG: Jun 1 16:04:24:<14>Jun 1 16:04:24 CES, CLUSTER FSM: Cluster mct (Id: 1),

client c2 (RBridge Id: 4) -

Remote client CCEP up

Thanks Michael.

New Contributor
Posts: 4
Registered: ‎08-18-2011

Re: MCT-LAG traffic only on one link.

We have a migration from Extreme to Brocade MLX. On Extreme we have load sharing on both links.

The server runs tivoli storage manager, so we should have several flows from clients backup to tivoli server.

show cluster client shows, that both links are up and active. LACP seems okay, but the traffic is mainly hold on one link.

How to debug the LAG traffic distribution and flows?

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: MCT-LAG traffic only on one link.

Hi krause,

Here are the Debug commands for MCT

debug cluster forwarding

Syntax: debug cluster forwarding

This command displays all the MCT forwarding-related events or messages in the MP that can affect traffic forwarding. Some examples include remote CCEP status changes, MCT FID creation, FID updates, and so on.

Command output resembles the following example.

Brocade# debug cluster forwarding

CLUSTER FORWARDING: MCT CCEP control FID 0xa006 for vlan 101 - REMOVE CCEP port

1/1

CLUSTER FORWARDING: Processing remote CCEP UP event for port eth 1/1

CLUSTER FORWARDING: Processed remote CCEP event for port 1/1 for 100 vlans

CLUSTER FORWARDING: MCT CCEP control FID 0xa006 for vlan 101 - ADD CCEP port 1/1

CLUSTER FORWARDING: Processing remote CCEP DOWN event for port eth 1/1

debug cluster actions

Syntax: debug cluster actions

This command displays the debug messages for MCT-related events, such as MCT FID port changes, and so on.

Command output resembles the following example.

Brocade# debug cluster actions

CLUSTER ACTIONS: Mac learning disabled for MAC 0000.2222.0001 on ICL 4/2, vlan

101

CLUSTER ACTIONS: Received remote CCEP UP IPC

debug cluster cam

Syntax: debug cluster cam

This command displays all the CAM- or PRAM-related activities for MCT-related events in the LP. Command output resembles the following example.

Brocade# debug cluster cam

CLUSTER CAM: Added peer interface cam:mac 001b.ed3b.a200, ppcr 0

CLUSTER CAM: Deleted peer interface cam:mac 001b.ed3b.a200, ppcr 0

debug cluster ipc

Syntax: debug cluster ipc

This command is helpful to debug IPC to LP to sync forwarding information in the LP. Command output resembles the following example.

Brocade# debug cluster ipc

CLUSTER IPC: MCT FID 0xa005 received for vlan 101

CLUSTER IPC: cluster 1, vlan mask change

Configuration notes

• ICL ports must not be untagged members of any VLAN. An ICL is preferably a LAG that provides

port level redundancy and higher bandwidth for cluster communication.

• ICL ports can be part of MCT VLANs as well as regular VLANs.

• The ICL VLAN mask must be a superset of the client VLAN mask.

• MAC learning is disabled on ICL ports for the MCT VLANs.

• MAC Database Update Protocol (MDUP) will synchronize all MAC entries for VLANs served by an

ICL link.

• On CCEP ports, MCT does not support MPLS, VLL, VPLS, 802.1ah, 802.1ad, and routing

protocols.

Thanks

Michael.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

Download FREE NVMe eBook