Oracle Fabric Interconnect (Formerly Xsigo) Cannot Add or Remove Ports from LAG, L2D in Bad State

Asset ID:	1-72-1517706.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 1517706.1 : Oracle Fabric Interconnect (Formerly Xsigo) Cannot Add or Remove Ports from LAG, L2D in Bad State

Applies to:

Oracle Fabric Interconnect F1-15 - Version All Versions and later
Oracle Fabric Interconnect F1-4 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Unable to add or remove ports to a LAG group.

Cause

The L2D may be in a bad state, the below test will confirm or rule this out.

Solution

To Confirm L2D is in bad state:

Follow one of the 2 methods:

Method-1:
Log into the IO Director as 'admin'

admin@karnataka[xsigo] set cli mode d

ProcessMonitor> connect <process of VN2_CP>

Run the command:

VN2_CP> show all-lags

// If the above command doesn't give any output - this confirms that the L2D is in a bad state.
// If output like below is received, - this confirms that L2D agent is good:

*********** LACP information ***********

lag id = 1 num ports = 1 lacp key = 0x00

is lacp = false is oper = true

** local information **

pri = 0x0001

MAC = 00:13:97:00:0B:33

id1 = 0x0002 id2 = 0x0000 id3 = 0x0000

** ports information **

local pri = 0x0001 port = 1 status = 0x2

VN2_CP>

Method-2:

In xvnd.log you will see the below message:

Apr 21 15:40:19 iop-11 vn2_agent_cp[608]: [ERR] VN2_CP Failed to send sync

message: timeout: expected 30000, real: 29980

Apr 21 15:40:19 iop-11 vn2_agent_cp[608]: [ERR] l2m::L2M eth10g-11 HW Error:

ERROR Cookie 5491 end (Command timeout)

Apr 21 15:40:19 iop-11 vn2_agent_cp[608]: [ERR] l2m::L2M eth10g-11 HW Error:

reported from:

Apr 21 15:41:09 iop-11 vn2_agent_cp[608]: [ERR] VN2_CP Failed to send sync

message: timeout: expected 30000, real: 29920

Apr 21 15:41:09 iop-11 vn2_agent_cp[608]: [ERR] l2m::L2M eth10g-11 HW Error:

ERROR Cookie 5492 end (Command timeout)

SOLUTION:

Follow either one of 2 solutions
1) Follow internal KB - https://na1.salesforce.com/articles/Knowledge_Article/1283?popup=true
2) Reboot the IO Card

Attachments

This solution has no attachment