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

[Junos Fusion] How to check port mode in Satellite device and convert default uplink ports mode from clustering to extended

0

0

Article ID: KB36238 KB Last Updated: 29 Sep 2020Version: 1.0
Summary:

This article explains how to check the port mode in Satellite device and provides the steps to convert port mode from clustering to extended.

Symptoms:
  • Servers connected in satellite device is not working as expected while they connect via uplink interface.
  • Uplink mode should be in extended mode while connecting to the server. However, it detects as clustering.
Cause:

By default, default uplink ports act as aclustering port. Refer to Understanding Satellite Device Clustering in a Junos Fusion.

If the devices are part of a satellite device cluster, the default uplink ports cannot be configured as extended ports to pass network traffic.

Solution:
  • They should have a direct connection to the aggregation device

OR

  • If there is an uplink port policy configured that excludes them from acting as uplink ports.

‚ÄčTopology:

EX9204 (AD) – Cluster – xe-132/2/2 – server

Use this command to verify the cluster output from the AD:

root# run show chassis satellite-cluster
 
Cluster Name: IDF3
    Number of devices provisioned: 2
    Number of devices present: 2
    Number of devices unprovisioned: 1
    Number of devices misconfig/miwired: 0
    Number of devices online: 2
    Number of devices offline: 1
 
         Device                      Local        Remote       Interface
  Slot   State         Distance      Interface    Interface    State
  132    Online        1   [via 131] xe-132/2/0   xe-131/2/0   present
                                     xe-132/2/1   xe-131/2/1   present
  131    Online        0             et-131/1/0   et-0/0/0     online
                                     xe-131/2/0   xe-132/2/0   present
                                     xe-131/2/1   xe-132/2/1   present
 

From the above output, xe-132/2/0 and xe-132/2/1 are participating in cluster connectivity.

Verify the interface status in satellite device:

root@sd132:~# vty
connect to 127.0.0.1:33000
spfe# show ifd
Index  Name              PEX-Mode   PCID  Flags               State
-----  ----------------- ---------  ----  ------------------  ------
40961  agg-stk-mb1       Clustering      0  0x0000000000000100   Up
40960  agg-ups           Clustering      0  0x0000000000000100   Up
8239  et-0/1/1          Extended     188  0x0000000000000101   Harddown
   31  ge-0/0/0          Extended     147  0x0000000000000101   Harddown
   47  ge-0/0/1          Extended     146  0x0000000000000101   Harddown
  143  ge-0/0/7          Extended     152  0x0000000000000101   Harddown
  159  ge-0/0/8          Extended     143  0x0000000000000101   Harddown
 175  ge-0/0/9          Extended     142  0x0000000000000101   Harddown
40993  lo-prv            None           0  0x0000000000000000   Up
40994  lo-pub            None           0  0x0000000000000000   Up
16415  xe-0/2/0          Clustering    183  0x0000000000000100   Up
16431  xe-0/2/1          Clustering    184  0x0000000000000100   Up
16447  xe-0/2/2          Clustering    185  0x0000000000000100   Up
 

However, xe-132/2/2 is also in clustering mode which is connected to the server.

Note: Interface name will be xe-0/2/2 while you are verifying the output in that specific SD

Steps to convert the port mode from clustering to extended using uplink port policy:

This uplink port policy is applied in the FPC level. For more details, refer to Configuring an Uplink Port Policy for a Satellite Device Cluster  

set chassis satellite-management cluster IDF3 fpc 132 cluster-policy New
set policy-options satellite-policies port-group-alias Grp1 pic 2 port 0
set policy-options satellite-policies port-group-alias Grp1 pic 2 port 1
set policy-options satellite-policies candidate-uplink-port-policy New uplink-port-group Grp1
 
Note: The above set of command used to specify the clustering ports, remaining port (not specified ports) will act as extended port.

The interface mode changed from clustering to Extended in SD device.

root@sd132:~# vty
connect to 127.0.0.1:33000
spfe# show ifd
Index  Name              PEX-Mode   PCID  Flags               State
-----  ----------------- ---------  ----  ------------------  ------
40961  agg-stk-mb1       Clustering     0  0x0000000000000100   Up
40960  agg-ups           Clustering     0  0x0000000000000100   Up
8239  et-0/1/1           Extended     188  0x0000000000000101   Harddown
   31  ge-0/0/0          Extended     147  0x0000000000000101   Harddown
   47  ge-0/0/1          Extended     146  0x0000000000000101   Harddown
  143  ge-0/0/7          Extended     152  0x0000000000000101   Harddown
  159  ge-0/0/8          Extended     143  0x0000000000000101   Harddown
 175  ge-0/0/9           Extended     142  0x0000000000000101   Harddown
40993  lo-prv            None           0  0x0000000000000000   Up
40994  lo-pub            None           0  0x0000000000000000   Up
16415  xe-0/2/0          Clustering   183  0x0000000000000100   Up
16431  xe-0/2/1          Clustering   184  0x0000000000000100   Up
16447  xe-0/2/2          Extended     185  0x0000000000000100   Up
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