Description

On ACX7K routers running Junos EVO, cosd application crash may lead to an error condition that prevents newly configured interfaces from appearing in the CLI upon commit.

Symptoms

  • cosd application crashes, goes offline, and generates core-dumps.
> show system alarms no-forwarding

1 alarms currently active
Alarm time               Class  Description
2024-08-01 19:05:55 UTC  Major  Application cosd fail on node Re0

> show system errors active detail

System Active Errors Detail Information
RE 0
----------------------------------------------------------------
Error Name            : application_major_failure
Identifier            : /re/0/emfd-fpa/0/cosd:0/0/sysman/0/application_major_failure
Description           : application_major_failure
State                 : enabled
Scope                 : board
Category              : processing
Level                 : major
Threshold             : 1
Error limit           : 1
Occur count           : 1
Clear count           : 0
Last occurred(ms ago) : 2024-08-01 19:05:55 UTC (4106629 ms ago)

> show system core-dumps no-forwarding

re0:
--------------------------------------------------------------------------
-rw-------  1 root  root   1546974848 Aug 1  19:07 /var/core/re0/cosd.re.re0.11218.2024_08_01.19_05_41.tar.gz
-rw-------  1 root  root   1547622801 Aug 1  19:09 /var/core/re0/cosd.re.re0.22245.2024_08_01.19_05_49.tar.gz
-rw-------  1 root  root   1547794039 Aug 1  19:11 /var/core/re0/cosd.re.re0.23243.2024_08_01.19_05_52.tar.gz
total files: 3

  • Interfaces configured after the crash do not show up under "show interface terse" and "show interfaces description". In the example below, et-0/0/4 does not appear in the CLI.
> edit
# set interfaces et-0/0/4 speed 1g
# set interfaces et-0/0/4 encapsulation ethernet-vpls
# set interfaces et-0/0/4 unit 0
# commit

> show interfaces terse 
Interface               Admin Link Proto    Local                 Remote
..
et-0/0/1                up    up
et-0/0/1.32767          up    up   aenet    --> ae14.32767
et-0/0/5                up    down
et-0/0/5.16386          up    down multiservice
et-0/0/8                up    down
et-0/0/8.16386          up    down multiservice
et-0/0/9                up    down
et-0/0/9.16386          up    down multiservice
et-0/0/12               up    down
et-0/0/12.16386         up    down multiservice
et-0/0/13               up    down
et-0/0/13.16386         up    down multiservice
<snip/>

Solution

Restart cosd application from CLI.

> restart class-of-service

OR

> request system application app cosd restart node re<0/1>

Modification History

2024-09-01 : Article Created