Support Support Downloads Knowledge Base Service Request 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

[T/M-series] How to access MS-PIC from the Junos CLI

0

0

Article ID: KB22657 KB Last Updated: 05 Mar 2017Version: 3.0
Summary:
This article provides information on how to access MS-PIC, via telnet, from the Junos CLI.
Symptoms:
  • MS-PC (and MSDPC PIC) can be accessed from the PFE CLI mode, but the connection is very low rate (9.6Kbps).

  • It is not suitable to take information from the PIC.
Cause:
 
Solution:
  1. Access via the PFE CLI is very slow and it takes a few hours to obtain information. For example, flow information in a production network:
    FPC 3 REV 02 710-015839 CY6301 M120 FPC Type 3
    PIC 0 REV 07 750-013423 JY4904 MultiServices 500
    
    
    lab@shokupanman-re0> start shell pfe network fpc3 
    
    
    RFPC platform (666Mhz MPC 8541 processor, 128MB memory, 512KB flash)
    
    RFPC3(shokupanman-re0 vty)# pty 0
    Connected.
    
    sp30(atr0)# 
    

  2. Access from Junos CLI is via telnet and established over the router's internal Ethernet. To do this, you need to first obtain the PIC IP address for telnet access.

    1. Access PIC via the PFE CLI (refer to step 1).

    2. Type the show ipv4 statistics command; the following output is generated:
      sp30(atr0)# show ipv4 statistics 
      Routing Instance: 1 (__juniper_private1__)
      IP ifl index 131078
      Local addr: 128.0.1.19
      address 0.0.0.0/0 type[8] ifl[131078]
      address 127.0.0.1/8 type[8] ifl[131078]
      address 128.0.1.19/32 type[8] ifl[131078]
      
      Traffic Statistics:
      Input Statistics:
      Intercept packets: 0
      Dropped packets : 0
      Fragments : 0
      Up the stack : 465286
      Output Statistics:
      Loopback packets : 0
      Dropped packets : 2
      Output packets : 457984 
        There is another way (optional) to obtain the sp-interface's internal address:
      root@shokupanman-re0% netstat -rn | grep sp- | grep 128
      
      128.0.1.19/32      intf     1 128.0.1.19        ucst   566     2 sp-1/3/0.16383
      
      

    3. Check for the Routing Instance and Local addr. In this example, they are __juniper_private1__ and 128.0.1.19 respectively.

    4. Type control + c to exit PIC.

    5. From the Junos CLI, telnet to the PIC with the IP address and routing instance:
      lab@shokupanman-re0> telnet 128.0.1.19 routing-instance __juniper_private1__ 
      Trying 128.0.1.19...
      Connected to 128.0.1.19.
      Escape character is '^]'.
      
      
      Stargate platform (700Mhz XLR processor, 3968MB memory, 0KB flash)
      
      sp30(vty)#
      
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Security Alerts and Vulnerabilities

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