06-16-2015 06:55 AM - edited 03-01-2019 07:56 AM
Anyone know about xbar log ? I found xbar status powered-dn on Nexus7710 after turn-on this log below.
switch# 2015 Jun 16 00:44:34 switch %$ VDC-1 %$ %XBAR-2-XBM_EEM_FABRIC_ACTION: Fabric slot 3 has been reloaded by xbar-manager because of an eem-policy triggered action xbm_eem_err_mgmt_fn 864
2015 Jun 16 00:44:37 switch %$ VDC-1 %$ %PLATFORM-2-XBAR_DETECT: Xbar 3 detected (Serial number JAE1919081K)
2015 Jun 16 00:44:55 switch %$ VDC-1 %$ %PLATFORM-2-XBAR_DETECT: Xbar 3 detected (Serial number JAE1919081K)
switch#
switch# 2015 Jun 16 00:45:54 switch %$ VDC-1 %$ %XBAR-2-XBM_EEM_FABRIC_ACTION: Fabric slot 3 has been reloaded by xbar-manager because of an eem-policy triggered action xbm_eem_err_mgmt_fn 864
2015 Jun 16 00:45:57 switch %$ VDC-1 %$ %MODULE-2-XBAR_FAIL: Initialization of xbar 3 (Serial number: JAE1919081K) failed
switch# sh mod
Mod Ports Module-Type Model Status
--- ----- ----------------------------------- ------------------ ----------
1 24 10/40 Gbps Ethernet Module N77-F324FQ-25 ok
5 0 Supervisor Module-2 N77-SUP2E active *
6 0 Supervisor Module-2 N77-SUP2E ha-standby
Mod Sw Hw
--- -------------- ------
1 6.2(12) 1.1
5 6.2(12) 1.2
6 6.2(12) 1.2
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 b0-7d-47-db-c1-02 to b0-7d-47-db-c1-73 JAE192102N1
5 d8-b1-90-85-f2-0a to d8-b1-90-85-f2-1c JAE191708LV
6 78-ba-f9-c4-66-ef to 78-ba-f9-c4-67-01 JAE19150FCP
Mod Online Diag Status
--- ------------------
1 Pass
5 Pass
6 Pass
Xbar Ports Module-Type Model Status
--- ----- ----------------------------------- ------------------ ----------
1 0 Fabric Module 2 N77-C7710-FAB-2 ok
3 0 Fabric Module 2 N77-C7710-FAB-2 powered-dn
5 0 Fabric Module 2 N77-C7710-FAB-2 ok
Xbar Power-Status Reason
--- ------------ ---------------------------
3 powered-dn Reset (powered-down) because module does not boot
Xbar Sw Hw
--- -------------- ------
1 NA 1.2
5 NA 1.2
Xbar MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 NA JAE1920008N
3 NA JAE1919081K
5 NA JAE1921073B
JK.
06-21-2015 09:00 PM
could you try reseating the Xbar module?
08-08-2016 12:34 AM
Hi,
Did you resolved this problem ?
01-04-2018 11:49 PM
XBM EEM (xbar manager Embedded Event Manager) policy takes care of bringing down (power cycled) the appropriate card (linecard or fabric card). The policy is that if there 5 sync losses in 1 hour, then a card is power cycled. If there are less than this rate no action is taken.
a) If the LC loses sync with more than one fabric, then the LC is power cycled
b) If multiple LC loose sync with one fabric, then the fabric is power cycled (Only if there are more than one fabric in the system)
c) If a line card loosing sync continuously with a fabric card and reaches EEM threshold, the fabric card is power cycled (unless if there is only one fabric card in the system).
Note: In all the above cases, the software takes the least disruptive procedure to diagnose the failure, i.e. power cycling the fabric card (if there are more than one fabric card in the system) is the least disruptive procedure and then moves forward with the next least disruptive approach.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide