Troubleshooting NextGen Port Extender
General Troubleshooting
This document provides various troubleshooting commands to assist you in monitoring and maintaining your NextGen Port Extender (NGPE) topology.
Base Verification Commands
Use these commands to confirm the base operation of your NGPE topology.
-
show chassis jnu role: displays whether a device is a controller or satellite.
If run from the AD: show chassis jnu role controller If run from a satellite: show chassis jnu role satellite
-
show chassis jnu satellites: displays the status of a single satellite or all satellites.
user@ad> show chassis jnu satellites Satellite Alive Model Version ----------------------------------------------------- sd1 up qfx5120-48y-8c 25.4R1
-
show chassis port-extender: displays each virtual SD slot number, along with its IP address, MAC address, and cascade port number.
user@ad> show chassis port-extender Target MAC-address MAC Slot Description IP-address mode Base count Cascade-ports 100 sd1 10.100.100.1 N 80:63:7c:0e:af:39 1280 ae4001 -
show interfaces terse: displays the up/down status of interfaces; useful for confirming the NGPE fabric is up.
user@ad> show interfaces terse Interface Admin Link Proto Local Remote et-0/0/0 up up et-0/0/0.0 up up aenet --> ae4001.0 et-0/0/0.16384 up up aenet --> ae4001.16384 et-0/0/0.32767 up up aenet --> ae4001.32767 ... ae4001 up up ae4001.0 up up inet 10.0.1.0/31 multiservice ae4001.16384 up up inet 10.1.1.0/31 multiservice ae4001.32767 up up multiservice ... ge-100/0/0 up up ge-100/0/0.16386 up up ge-100/0/1 up up ge-100/0/1.16386 up up ge-100/0/2 up up ge-100/0/2.16386 up up ge-100/0/3 up up ge-100/0/3.16386 up up ge-100/0/4 up up ge-100/0/4.16386 up up ge-100/0/5 up up ge-100/0/5.16386 up up ge-100/0/6 up up ge-100/0/6.16386 up up ge-100/0/7 up up ge-100/0/7.16386 up up ge-100/0/8 up up ge-100/0/8.16386 up up ge-100/0/9 up up ge-100/0/9.16386 up up -
show lacp interfaces: check the status of aex participating in LACP
user@ad> show lacp interfaces Aggregated interface: ae4001 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity et-0/0/0 Actor No No Yes Yes Yes Yes Fast Active et-0/0/0 Partner No No Yes Yes Yes Yes Fast Active et-0/0/1 Actor No No Yes Yes Yes Yes Fast Active et-0/0/1 Partner No No Yes Yes Yes Yes Fast Active LACP protocol: Receive State Transmit State Mux State et-0/0/0 Current Fast periodic Collecting distributing et-0/0/1 Current Fast periodic Collecting distributing Aggregated interface: ae4002 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity et-0/0/2 Actor No No Yes Yes Yes Yes Fast Active et-0/0/2 Partner No No Yes Yes Yes Yes Fast Active et-0/0/3 Actor No No Yes Yes Yes Yes Fast Active et-0/0/3 Partner No No Yes Yes Yes Yes Fast Active LACP protocol: Receive State Transmit State Mux State et-0/0/2 Current Fast periodic Collecting distributing et-0/0/3 Current Fast periodic Collecting distributing -
show interfaces vtep: check the status of VTEP interfaces.
user@ad> show interfaces vtep Physical interface: vtep, Enabled, Physical link is Up Interface index: 136, SNMP ifIndex: 521 Type: Software-Pseudo, Link-level type: VxLAN-Tunnel-Endpoint, MTU: Unlimited, Speed: Unlimited Device flags : Present Running Interface Specific flags: Internal: 0x200 Link type : Full-Duplex Link flags : None Last flapped : Never Input packets : 0 Output packets: 0 Logical interface vtep.32768 (Index 387) (SNMP ifIndex 546) Flags: Up SNMP-Traps 0x4000 Encapsulation: ENET2 Ethernet segment value: 00:00:00:00:00:00:00:00:00:00, Mode: single-homed, Multi-homed status: Forwarding VXLAN Endpoint Type: Source, VXLAN Endpoint Address: 10.101.100.0, L2 Routing Instance: ngpe/ngpe-ad, L3 Routing Instance: ngpe/default Input packets : 0 Output packets: 0 Logical interface vtep.32769 (Index 432) (SNMP ifIndex 726) Flags: Up SNMP-Traps Encapsulation: ENET2 VXLAN Endpoint Type: Remote, VXLAN Endpoint Address: 10.101.100.1, L2 Routing Instance: ngpe/ngpe-ad, L3 Routing Instance: ngpe/default Input packets : 0 Output packets: 0 Protocol bridge, MTU: Unlimited Flags: Is-Primary, Trunk-Mode, 0xc000000 -
show l2-learning vxlan-tunnel-endpoint remote: check the status of remote VTEP interfaces
user@ad> show l2-learning vxlan-tunnel-endpoint remote Logical System Name Id SVTEP-IP IFL L3-Idx SVTEP-Mode ELP-SVTEP-IP ngpe 1 10.101.100.0 lo0.16000 9
-
show bfd session device-list [satellite-name(s)]: check the status of BFD sessions
user@ad> show bfd session device-list [sd1 sd2] sd1 -------------------------------------------------------------------- Detect Transmit Address State Interface Time Interval Multiplier 10.1.1.0 Up ae0.1 3.000 1.000 3 10.101.100.0 Up 5.000 1.000 5 2 sessions, 2 clients Cumulative transmit rate 2.0 pps, cumulative receive rate 2.0 pps sd2 -------------------------------------------------------------------- Detect Transmit Address State Interface Time Interval Multiplier 10.1.2.0 Up ae0.1 3.000 1.000 3 10.101.100.0 Up 5.000 1.000 5 2 sessions, 2 clients Cumulative transmit rate 2.0 pps, cumulative receive rate 2.0 pps -
show configuration | display set: displays the active configuration on the device
-
show log jnud: use this command to either monitor the progress of a satellite onboarding, or use after onboarding to check for any errors.
user@ad> show log jnud Nov 25 05:18:39 jnud_open_netconf_session : Host name : 10.100.100.0 - User name : jnuadmin Nov 25 05:18:39 jnud_send_request_to_node - Node : 10.100.100.0 RPC : <mgd-jnu-get-lock/> Nov 25 05:18:39 jnud_send_request_to_node - Node : 10.100.100.0 RPC : <mgd-jnu-get-lock/> successfull Nov 25 05:18:39 jnud_receive_response_from_node : 10.100.100.0 Nov 25 05:18:40 jnud_get_release_lock: rpc <mgd-jnu-get-lock/> passed Nov 25 05:18:40 jnud_get_release_lock: rpc <mgd-jnu-get-lock/> passed Nov 25 05:18:40 jnud_send_file_remote_scp: Copying the files with scp -O -o StrictHostKeychecking=no -i /var/db/jnu/.ssh/id_rsa /var/tmp/jnu_initial_sync jnuuser@10.100.100.0:/var/tmp/jnu_initial_sync Nov 25 05:18:41 jnud_send_request_to_node - Node : 10.100.100.0 RPC : <mgd-jnu-schema-add> <model>qfx5120-48y-8c</model> <version>25.4R1</version> <filename>/var/tmp/sd1-schema-258.tar.gz</filename> <model-id>169</model-id> </mgd-jnu-schema-add> Nov 25 05:18:41 jnud_send_request_to_node - Node : 10.100.100.0 RPC : <mgd-jnu-schema-add> <model>qfx5120-48y-8c</model> <version>25.4R1</version> <filename>/var/tmp/sd1-schema-258.tar.gz</filename> <model-id>169</model-id> </mgd-jnu-schema-add> successfull Nov 25 05:18:41 jnud_receive_response_from_node : 10.100.100.0 Nov 25 05:18:42 jnud_sync_dual_controller: schema create rpc passed
Sync a Satellite Device with the Aggregation Device
You may find a satellite device which is fully operational, yet isn't associated with the aggregate device. The following command will re-associate the satellite device with the aggregate device.
-
request jnu satellite sync: needed if the SD goes out of sync with the AD.
user@sd1> request jnu satellite sync Junos node unifier process started, pid 99442
Configure Traceoptions
-
set system scripts commit traceoptions: traceoptions may be enabled for the commit scripts. Traceoptions are system intensive and should only be applied as directed by support.
user@ad> set system scripts commit traceoptions file commit-script.log set system scripts commit traceoptions file size 1g set system scripts commit traceoptions flag all
-
set system services netconf traceoptions: traceoptions may be enabled for netconf to assist in jnud commit issues. Traceoptions are system intensive and should only be applied as directed by support.
user@ad> set system services netconf traceoptions file netconf.log set system services netconf traceoptions file size 1g set system services netconf traceoptions file files 10 set system services netconf traceoptions flag all
Check for Core Files
-
show system core-dumps device-list [satellite name(s)]: check for any core files, as directed by support. In this example, we see a core file for the LACP process in the /var/tmp/ directory on SD1, while SD2 has no cores.
user@ad> show system core-dumps device-list [sd1 sd2] sd1 -------------------------------------------------------------------- /var/crash/*core*: No such file or directory -rw-r--r-- 1 root wheel 20250624 Feb 24 14:03 /var/tmp/lacpd.core.0 /var/tmp/pics/*core*: No such file or directory /var/crash/kernel.*: No such file or directory /var/jails/rest-api/tmp/*core*: No such file or directory /tftpboot/corefiles/*core*: No such file or directory total files: 1 sd2 -------------------------------------------------------------------- /var/crash/*core*: No such file or directory /var/tmp/*core*: No such file or directory /var/tmp/pics/*core*: No such file or directory /var/crash/kernel.*: No such file or directory /var/jails/rest-api/tmp/*core*: No such file or directory /tftpboot/corefiles/*core*: No such file or directory
Offboard a Satellite Device
You can offboard an existing SD from your NGPE topology by following this process:
Capture a baseline output of the existing fabric state.
user@ad# run show ospf neighbor logical-system ngpe Address Interface State ID Pri Dead 10.1.1.1 ae4001.16384 Full 128.54.176.96 128 34 10.1.2.1 ae4002.16384 Full 128.54.176.91 128 34
This output shows the fabric configuration on the SD.
user@ad# show chassis satellite sd1 | display set | match fabric set groups ngpe-satellite-fabric apply-flags omit set groups ngpe-satellite-fabric interfaces lo0 unit 0 family inet address 10.101.100.1/32 primary set groups ngpe-satellite-fabric interfaces ae0 unit 1 vlan-id 101 set groups ngpe-satellite-fabric interfaces ae0 unit 1 family inet address 10.1.1.1/31 set groups ngpe-satellite-fabric interfaces ge-0/0/0 mtu 1522 set groups ngpe-satellite-fabric interfaces ge-0/0/0 encapsulation ethernet-bridge set groups ngpe-satellite-fabric interfaces ge-0/0/0 network-isolation-profile test-core-isolation set groups ngpe-satellite-fabric interfaces ge-0/0/0 gigether-options asynchronous-notification set groups ngpe-satellite-fabric interfaces ge-0/0/0 unit 0 set groups ngpe-satellite-fabric interfaces ge-0/0/1 mtu 1522 set groups ngpe-satellite-fabric interfaces ge-0/0/1 encapsulation ethernet-bridge set groups ngpe-satellite-fabric interfaces ge-0/0/1 network-isolation-profile test-core-isolation set groups ngpe-satellite-fabric interfaces ge-0/0/1 gigether-options asynchronous-notification set groups ngpe-satellite-fabric interfaces ge-0/0/1 unit 0 <remaining output truncated>
Disable the fabric on the SD.
user@ad# set services port-extender satellite <satellite-name> fabric-disable
Commit the change.
user@ad# commit synchronize re0: configuration check succeeds re1: commit complete re0: warning: Clear Sat change bits terminated abnormally commit complete
Confirm the new fabric state. The aex fabric interface for the SD is absent.
user@ad# run show ospf neighbor logical-system ngpe Address Interface State ID Pri Dead 10.1.2.1 ae4002.16384 Full 128.54.176.91 128 32
The fabric configuration for the SD is also absent.
user@ad# show chassis satellite sd1 | display set | match fabric [edit] user@ad#
Capture the current
port-extenderconfiguration for the SD.user@ad# show services port-extender satellite sd1 | display set set services port-extender satellite sd1 device-model qfx5120-48y set services port-extender satellite sd1 connectivity-interface-ad et-0/0/0 set services port-extender satellite sd1 connectivity-interface-ad et-0/0/1 set services port-extender satellite sd1 connectivity-interface-sd et-0/0/1 set services port-extender satellite sd1 connectivity-interface-sd et-0/0/2 set services port-extender satellite sd1 ssh-key "ssh-key"
Remove the SD from the topology with the
deactivateoption. Ensure that you have disabled the fabric. Otherwise, the system will not allow you to perform this step.user@ad# deactivate services port-extender satellite <satellite-name>
Commit the change.
user@ad# commit synchronize re0: warning: Port extender configuration is not detected in the candidate configuration.. warning: Checking for any pending satellites to deboard.. warning: Attempting to delete sd1 warning: Commit script clean up is successful... warning: No configuration to be done with script as port-extender is disabled re0: configuration check succeeds re1: [edit chassis] 'satellite sd1' warning: statement does not exist commit complete re0: commit completeThe device should not appear in the NGPE topology. Confirm with this command:
user@ad# run show chassis jnu satellites Satellite Alive Model Version ------------------------------------------------------------- sd2 up qfx5120-48y-8c 26.2R1
Re-onboard a Satellite Device
You can re-onboard an SD to your NGPE topology by following this process:
Activate the satellite.
user@ad# activate services port-extender satellite <satellite-name>
Commit the change.
user@ad# commit synchronize
Remove the
fabric-disablestatement.user@ad# delete services port-extender satellite <satellite-name> fabric-disable user@ad# commit synchronize
If the satellite does not come back online, confirm that the SD is in the satellite role.
user@sd> show chassis jnu role
If the satellite is not in the satellite role, then re-initiate it. If the satellite is in the satellite role, then skip to step 6.
user@sd> request jnu role satellite
Sync the satellite with the AD and wait for the SD to appear in the NGPE topology.
user@sd> request jnu satellite sync
Disable or Enable an Extended Port
You can disable or enable an extended port (EP) for troubleshooting purposes. This applies to a single EP, or an aggregated Ethernet interface (aex) containing EP's. The ability to disable and enable an EP is available in Junos OS Release 26.2R1 and later.
user@ad# set interfaces <interface name> disable user@ad# commit synchronize
Confirm that the interface is down.
user@ad# run show interfaces <interface name> terse user@ad# run show interfaces ge-100/0/0 terse Interface Admin Link Proto Local Remote ge-100/0/0 down down
When you are ready to bring the port up, you can remove the disable option.
user@ad# delete interfaces ge-100/0/0 disable user@ad# commit synchronize
Confirm the port status.
user@ad# run show interfaces ge-100/0/0 terse Interface Admin Link Proto Local Remote ge-100/0/0 up up
Bounce an Extended Port
You can bounce an EP for troubleshooting purposes. The request interface bounce
<interface-name> interval <value> operation temporarily disables and
re-enables the interface automatically. You may either specifiy an interval, in seconds, or omit
the interval statement. Omitting the interval causes the interface to go down and come back up
immediately. The ability to bounce an EP is available in Junos OS Release 26.2R1 and later.
user@ad> request interface bounce ge-100/0/0 interval 5 Bounce operation on interface ge-100/0/0 started with interval 5 secs.