Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Mac registration with L2FM failed

My Logfile on Nexus 6K is fiilled with Logs like below:

Nexus Version is: 7.0(3)N1(1)

2014 Sep 12 14:49:11 Nexus-6K %ADJMGR-3-MAC_REG_FAILED:  adjmgr [3727]  Mac registration with L2FM failed for mac xxxx.xxxx.xxxx, iod Vlan191, phy iod: port-channel169
2014 Sep 12 14:49:24 Nexus-6K %ADJMGR-3-MAC_REG_FAILED:  adjmgr [3727]  Mac registration with L2FM failed for mac xxxx.xxxx.xxxx, iod Vlan108, phy iod: port-channel91
2014 Sep 12 14:49:36 Nexus-6K %ADJMGR-3-MAC_REG_FAILED:  adjmgr [3727]  Mac registration with L2FM failed for mac xxxx.xxxx.xxxx, iod Vlan108, phy iod: port-channel91
2014 Sep 12 14:49:58 Nexus-6K %ADJMGR-3-MAC_REG_FAILED:  adjmgr [3727]  Mac registration with L2FM failed for mac xxxx.xxxx.xxxx, iod Vlan191, phy iod: port-channel169

Cisco's document does not explain what is causing this:

Error Message:     AM-3-MAC_REG_FAILED Format: Mac registration with L2FM failed for mac %s, iod %s, phy iod: %s
Explanation    MAC registration with L2FM failed.
Recommended Action    No action is required.

Here is my Logging Configuration:


logging level aaa 5
logging level cdp 6
logging level copp 6
logging level flogi 5
logging level hsrp 6
logging level interface-vlan 5
logging level lldp 5
logging level monitor 6
logging level radius 5
logging level session-mgr 6
logging level spanning-tree 6
logging level track 6
logging level virtual-service 2
logging level igmp 3
logging event link-status default
logging logfile messages 6
logging server x.x.x.x use-vrf x facility syslog
logging monitor 6

Can anyone tell me what are these and how to stop them from occurring. Also would appreciate suggestions on how can I improve logging configuration.

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Hi Saurabh,The L2FM is Layer2

Hi Saurabh,


The L2FM is Layer2 Feature Manager which manages the mac-address table and mac-address
registrations and deletions from the hardware table. The L2FM component exists on Nexus
7K. In case of Nexus 5500 and Nexus 6K, there is an equivalent component called FWM. Since
most of the code is re-used in Nexus 6K platform, the references to L2FM need to be
removed/resolved on Nexus 6K code. There is a software bug to fix these L2FM references in
the code. Still the bug is in assigned state, hence the fix for this bug is not yet
available. You can safely ignore these messages, they have no impact. The mac-addresses
are registered with FWM and since there is no L2FM these messages have no impact.

========================================
CSCum82485    Nexus 5500/6000: L2FM messages seen

Symptom:

In a Nexus 6000 switch running NX-OS 7.0(0)N1(1), messages such as following can be seen

%ADJMGR-3-MAC_REG_FAILED:  adjmgr [3745]  Mac registration with L2FM failed for mac
002a.6a35.b341, iod Vlan250, phy iod: Gateway Port-Channel1:186
%ADJMGR-3-MAC_REG_FAILED:  adjmgr [3745]  Mac registration with L2FM failed for mac
00d0.03eb.2000, iod Vlan60, phy iod: Ethernet131/1/15


Conditions:

Usually seen when a host comes online.

Workaround:

L2FM is not a valid component on Nexus 6000. These are cosmetic messages and can be
ignored.

HTH

Inayath

***Plz rate the post and mark the thread as closed******

2 REPLIES
Cisco Employee

Hi Saurabh,The L2FM is Layer2

Hi Saurabh,


The L2FM is Layer2 Feature Manager which manages the mac-address table and mac-address
registrations and deletions from the hardware table. The L2FM component exists on Nexus
7K. In case of Nexus 5500 and Nexus 6K, there is an equivalent component called FWM. Since
most of the code is re-used in Nexus 6K platform, the references to L2FM need to be
removed/resolved on Nexus 6K code. There is a software bug to fix these L2FM references in
the code. Still the bug is in assigned state, hence the fix for this bug is not yet
available. You can safely ignore these messages, they have no impact. The mac-addresses
are registered with FWM and since there is no L2FM these messages have no impact.

========================================
CSCum82485    Nexus 5500/6000: L2FM messages seen

Symptom:

In a Nexus 6000 switch running NX-OS 7.0(0)N1(1), messages such as following can be seen

%ADJMGR-3-MAC_REG_FAILED:  adjmgr [3745]  Mac registration with L2FM failed for mac
002a.6a35.b341, iod Vlan250, phy iod: Gateway Port-Channel1:186
%ADJMGR-3-MAC_REG_FAILED:  adjmgr [3745]  Mac registration with L2FM failed for mac
00d0.03eb.2000, iod Vlan60, phy iod: Ethernet131/1/15


Conditions:

Usually seen when a host comes online.

Workaround:

L2FM is not a valid component on Nexus 6000. These are cosmetic messages and can be
ignored.

HTH

Inayath

***Plz rate the post and mark the thread as closed******

New Member

I have also found that whilst

I have also found that whilst this is only cosmetic in nature it can easily swamp your logs depending on your vlan setup.  I have stopped this from showing up in the logs with the following command:-

!

logging level adjmgr 0

!

1535
Views
10
Helpful
2
Replies
CreatePlease login to create content