Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Apstra] Incorrect port breakouts / speeds on Cumulus Linux

0

0

Article ID: KB36679 KB Last Updated: 01 Apr 2021Version: 1.0
Summary:

AIS configuration deployments on Cumulus Linux will fail when using a device profile containing port breakouts or speeds not supported by Cumulus on that specific device.

Symptoms:

The AIS Dashboard will show a deployment failure. The root cause may not be immediately obvious as errors similar to the below are returned from Cumulus:

Errors occurred processing config: section 'portattributes, index 0: Warning: Unit file of switchd.service changed on disk, 'systemctl daemon-reload' recommended. A dependency job for switchd.service failed. See 'journalctl -xn' for details."
Errors occurred processing config: section 'portattributes, index 0: A dependency job for switch
Cause:

This problem is caused by the use of port breakouts and / or Speeds that are not supported on that particular hardware.

Solution:

There are two main scenarios:

  • Unsupported Port Speeds
  • Unsupported Port Breakouts

For both scenario's, the steps to troubleshoot are very similar. The objective is to identify the process that is failing and retrieve the log messages that can tell you why they are failing.

Both errors point to switchd so that's where we need to start.

Note: These commands require root access. While it is possible to run them with 'sudo', we recommend running them as root after using 'sudo su -' for better-formatted results:

root@cumulus:mgmt-vrf:~# systemctl status switchd.service
● switchd.service - Cumulus Linux Switch Daemon
Loaded: loaded (/lib/systemd/system/switchd.service; enabled)
Drop-In: /etc/systemd/system/switchd.service.d
└─override.conf
Active: inactive (dead) since Fri 2019-05-24 12:39:09 UTC; 43min ago
Main PID: 21245 (code=exited, status=0/SUCCESS)
May 24 12:31:32 cumulus switchd[21245]: hal_bcm_console.c:66 bcm-dcmd: multicast show
May 24 12:31:32 cumulus switchd[21245]: hal_bcm_console.c:66 bcm-dcmd: echo bcmshell
May 24 12:31:32 cumulus switchd[21245]: hal_bcm_console.c:66 bcm-dcmd: ipmc table show
May 24 12:31:32 cumulus switchd[21245]: hal_bcm_console.c:66 bcm-dcmd: echo bcmshell
May 24 12:31:32 cumulus switchd[21245]: hal_bcm_console.c:66 bcm-dcmd: show portmap
May 24 12:31:37 cumulus switchd[21245]: hal_bcm_console.c:66 bcm-dcmd: echo bcmshell
May 24 12:31:37 cumulus switchd[21245]: hal_bcm_console.c:66 bcm-dcmd: show portmap
May 24 12:31:38 cumulus switchd[21245]: switchd.c:938 /ctrl/debug triggered
May 24 12:39:09 cumulus systemd[1]: Stopping Cumulus Linux Switch Daemon...
May 24 12:39:09 cumulus switchd[21245]: switchd.c:1254 SIGTERM received. Switchd terminating.
May 24 12:39:15 cumulus systemd[1]: Dependency failed for Cumulus Linux Switch Daemon.
May 24 12:39:15 cumulus systemd[1]: Triggering OnFailure= dependencies of switchd.service.

It shows there is a dependency process that has failed, so let's find out what dependencies we have:

root@cumulus:mgmt-vrf:~# systemctl list-dependencies switchd.service
switchd.service
● ├─-.mount
● ├─acltool.service
● ├─portwd.service
● ├─system.slice
● ├─update-ports.service
● ├─update-ports.service
● └─wd_keepalive.service

Failed dependencies will appear in red. Check the status of one of the failed dependencies:

root@cumulus:mgmt-vrf:~# systemctl status update-ports.service
● update-ports.service - Cumulus Linux switch port setup
Loaded: loaded (/lib/systemd/system/update-ports.service; enabled)
Active: failed (Result: exit-code) since Fri 2019-05-24 12:39:15 UTC; 46min ago
Main PID: 1172 (code=exited, status=255)
May 24 12:39:15 cumulus update-ports[1172]: Error: 1 invalid lines found in /etc/cumulus/ports.conf:
May 24 12:39:15 cumulus update-ports[1172]: [Line 15]:'15=4x10G'
May 24 12:39:15 cumulus update-ports[1172]: Invalid because: Maximum of 52 logical ports exceeded for Trident2 X pipeline (ports 1-16)
May 24 12:39:15 cumulus systemd[1]: update-ports.service: main process exited, code=exited, status=255/n/a
May 24 12:39:15 cumulus systemd[1]: Failed to start Cumulus Linux switch port setup.
May 24 12:39:15 cumulus systemd[1]: Unit update-ports.service entered failed state.

If the full logs are required these can be obtained using the following command:

root@cumulus:mgmt-vrf:~# journalctl -u update-ports.service

In this example the full logs also included the following errors:

May 24 12:39:15 cumulus update-ports[1172]: Error: 1 invalid lines found in /etc/cumulus/ports.conf:
May 24 12:39:15 cumulus update-ports[1172]: [Line 15]:'15=4x10G'

In this example, the switch does not support a 4x10G breakout on port 15. Troubleshooting port speed errors are done in the same way as described above.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search