cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3314
Views
0
Helpful
1
Replies

Nexus7000 L2FMC error

MARY MARINILLI
Level 1
Level 1

Trying to find meaning/cause of the following Nexus errors:

Nexus7000

version 4.2(4)

%L2FMC-SLOT12-2-L2PD_HWIDX_TO_IF_FAILED: Failed to get Interface for index                  

%L2FMC-SLOT12-1-L2PD_L2_USD_REQ_FAILED: Failed to send request to the L2 ASIC driver.

1 Accepted Solution

Accepted Solutions

Arumugam Muthaiah
Cisco Employee
Cisco Employee

Hi Mary,

L2FM = Layer2 Feature Manager. Runs on Supervisor. Manages distributed MAC tables across various forwarding engines (FE's) on the modules

L2FMC = Layer2 Feature manager client component. This runs on the line card.


MTM = MAC Table Manager. Runs on all modules as of 5.0 NXOS. Interacts with L2FM on supervisor & the ASIC drivers on the modules. Replaces L2FMC in older code

Log:

%L2FMC-SLOT12-2-L2PD_HWIDX_TO_IF_FAILED: Failed to get Interface for index 

Description:

This msg means corresponding MAC address entry could not be mapped to interface most likely due to interface being removed from VDC. The entry could be being aged when you saw this msg.

Log:

%L2FMC-SLOT12-1-L2PD_L2_USD_REQ_FAILED: Failed to send request to the L2 ASIC driver.

Description:

L2FM (supervisor) & L2FMC (line card) talk with each other. In this case the request came from L2FM to L2FMC which was then supposed to be sent to the ASIC driver. The L2FMC component for some reason did not so. This could be as simple as a new MAC that was learnt by the supervisor and being updated on other DFC's. This output does not mean that the MAC table did not get updated, it just means that it did not get updated at that instance of time. Maybe during the next update it would have gone successfully w/o this error message being printed out.

Some time it will be difficult to point to the source of the problem and what exactly we should do to fix this.

One of the possibilities is that you may have been running in to the bug


CSCtf88219 - L2fm timing out due to frequent Mac aging on Nexus

Symptom:

1. When bringing up a vlan, the vlan does not come up and the cli is hung for couple of seconds

Following error message is displayed:
'interaction with l2fm timed out' error occurs.

2. Sometimes L2FM process can reset

3. Packet forwarding for newly added SVIs may not happen, and you may not be able to ping the SVI

4. You may also observe that the MAC address table stops responding to corresponding "show" commands. Here is an example:

N7k# show mac address-table dynamic
Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link
VLAN MAC Address Type age Secure NTFY Ports
---------+-----------------+--------+---------+------+----+-------------
---------+-----------------+--------+---------+------+----+-----

Service not responding

Condition:
Shut / Unshut a vlan interface

Workaround:
1. Increase the mac-aging to 86400 secs
2. A reset of all the linecards might be required under some conditions to fully recover.

Regards,

Aru

*** Please rate if the post is useful ***

Regards, Aru *** Please rate if the post useful ***

View solution in original post

1 Reply 1

Arumugam Muthaiah
Cisco Employee
Cisco Employee

Hi Mary,

L2FM = Layer2 Feature Manager. Runs on Supervisor. Manages distributed MAC tables across various forwarding engines (FE's) on the modules

L2FMC = Layer2 Feature manager client component. This runs on the line card.


MTM = MAC Table Manager. Runs on all modules as of 5.0 NXOS. Interacts with L2FM on supervisor & the ASIC drivers on the modules. Replaces L2FMC in older code

Log:

%L2FMC-SLOT12-2-L2PD_HWIDX_TO_IF_FAILED: Failed to get Interface for index 

Description:

This msg means corresponding MAC address entry could not be mapped to interface most likely due to interface being removed from VDC. The entry could be being aged when you saw this msg.

Log:

%L2FMC-SLOT12-1-L2PD_L2_USD_REQ_FAILED: Failed to send request to the L2 ASIC driver.

Description:

L2FM (supervisor) & L2FMC (line card) talk with each other. In this case the request came from L2FM to L2FMC which was then supposed to be sent to the ASIC driver. The L2FMC component for some reason did not so. This could be as simple as a new MAC that was learnt by the supervisor and being updated on other DFC's. This output does not mean that the MAC table did not get updated, it just means that it did not get updated at that instance of time. Maybe during the next update it would have gone successfully w/o this error message being printed out.

Some time it will be difficult to point to the source of the problem and what exactly we should do to fix this.

One of the possibilities is that you may have been running in to the bug


CSCtf88219 - L2fm timing out due to frequent Mac aging on Nexus

Symptom:

1. When bringing up a vlan, the vlan does not come up and the cli is hung for couple of seconds

Following error message is displayed:
'interaction with l2fm timed out' error occurs.

2. Sometimes L2FM process can reset

3. Packet forwarding for newly added SVIs may not happen, and you may not be able to ping the SVI

4. You may also observe that the MAC address table stops responding to corresponding "show" commands. Here is an example:

N7k# show mac address-table dynamic
Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link
VLAN MAC Address Type age Secure NTFY Ports
---------+-----------------+--------+---------+------+----+-------------
---------+-----------------+--------+---------+------+----+-----

Service not responding

Condition:
Shut / Unshut a vlan interface

Workaround:
1. Increase the mac-aging to 86400 secs
2. A reset of all the linecards might be required under some conditions to fully recover.

Regards,

Aru

*** Please rate if the post is useful ***

Regards, Aru *** Please rate if the post useful ***
Review Cisco Networking for a $25 gift card