Displaying Stacking Process Information Stored in Log Manager

All background job output is redirected to the internal log manager. Log manager information is displayed from the most recent to the oldest. Each line in the log manager contains the following fields:

  • date and time - Date and time of the entry in the format Jul 04 15:29:31
  • info - The message type, such as debug, info, warning, or error
  • infra - log manager module name
  • stacking - submodule of the infra module specific to stacking

For example:

Jul 04 15:29:31:276736:info:infra:stacking:1:129589836776192: T=3m19.9: Assigned unit 2 to be standby

Enter the show log debug infra stack all command to display the contents of the log manager.

In the following example, the display contains two sets of information. One set is for the current reload, and the other set is for the previous reload. There is no clear visual separator between them. Use the date/time to determine the set boundary. In the example, any information displayed above the date and time Jul 04 15:27:52 belongs to the current life after reload. The remainder is from the previous life before reload. 

ICX7850-48FS Router# show log debug infra stack all
Jul 04 15:29:31:276736:info:infra:stacking:1:129589836776192: T=3m19.9: Assigned unit 2 to be standby
Jul 04 15:27:57:868023:debug:infra:stacking:1:10314228695808: T=1m46.5: Synchronize webauth files to u3
Jul 04 15:27:57:261067:debug:infra:stacking:1:2428668741121: T=1m45.9: Synchronize webauth files to u4
Jul 04 15:27:57:258148:debug:infra:stacking:1:55308377391872: T=1m45.9: Synchronize webauth files to u2
Jul 04 15:27:56:374051:info:infra:stacking:1:9691458437888: T=1m45.0: Election, I d4c1.9e18.83e1 was alone --> active, ID=1, pri=128, 4U(1-4), A=u1, nbr#=3 3,reason: u4: port-up,
Jul 04 15:27:52:429634:debug:infra:stacking:1:6934089433856: T=1m41.1: Unit 1 loses all neighbors.
Jul 02 17:11:48:099456:info:infra:stacking:1:53304364383601408: T=19h52.7: Election, I d4c1.9e18.83e1 was active, no change, ID=1, pri=128, 4U(1-4), A=u1, nbr#=3 3,reason: u2: stk-po-chg,
Jul 02 17:11:44:719352:info:infra:stacking:1:53301851827733248: T=19h49.3: Election, I d4c1.9e18.83e1 was active, no change, ID=1, pri=128, 4U(1-4), A=u1, nbr#=3 3,reason: u2: port-up,
Jul 02 17:09:44:363971:info:infra:stacking:1:0: Suppressed 60 times: prog_stk_p_hw, sw=1/2/4 (d=0 p=95), IEEE HW=1 who=5 dly=1, ini=0: 17/1 ms del->0, ?p_di(1/2/4)=1, enc=3, +pcl, D-1 1/2/4 ->IEEE, acl(1), rv=0, p_en(0) 13ms, fram, pau1, CPU: 0:0 1:0 3:2 6:1 7:0 8:13 9:0 10:0 11:0 16:0 17:1 18:0 sum=34 log=2, err=3 ret=0x4001050, 4U 0P A1S2 I1A
Jul 02 17:09:31:272456:info:infra:stacking:1:53195912164410112: prog_stk_p_hw, sw=1/2/4 (d=0 p=95), IEEE HW=1 who=5 dly=1, ini=0: 17/1 ms del->0, ?p_di(1/2/4)=1, enc=3, +pcl, D-1 1/2/4 ->IEEE, acl(1), rv=0, p_en(0) 13ms, fram, pau1, CPU: 0:0 1:0 3:2 6:1 7:0 8:13 9:0 10:0 11:0 16:0 17:1 18:0 sum=34 log=2, err=3 ret=0x4001050, 4U 0P A1S2 I1A
Jul 02 16:34:37:074456:info:infra:stacking:1:51566470291784448: T=18h23m41.7: Election, I d4c1.9e18.83e1 was active, no change, ID=1, pri=128, 4U(1-4), A=u1, nbr#=3 3,reason: u2: stk-po-chg,
Jul 02 16:34:34:027258:info:infra:stacking:1:51564103764804352: T=18h23m38.6: Election, I d4c1.9e18.83e1 was active, no change, ID=1, pri=128, 4U(1-4), A=u1, nbr#=3 3,reason: u1: stk-po-chg,

Parent topic: Displaying Stack Information