This article provides information on how to access MS-PIC via telnet from the Junos Command Line Interface (CLI).
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.
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@router-re0> start shell pfe network fpc3 RFPC platform (666Mhz MPC 8541 processor, 128MB memory, 512KB flash) RFPC3(router-re0 vty)# pty 0 Connected. sp30(atr0)#
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.
Access PIC via the PFE CLI (refer to step 1).
Type the show ipv4 statistics command; the following output is generated:
show ipv4 statistics
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@router-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
Check for the Routing Instance and Local addr . In this example, they are __juniper_private1__ and 128.0.1.19 , respectively.
Type control + c to exit the PIC.
control + c
From the Junos CLI, telnet to the PIC with the IP address and routing instance:
lab@router-re0> telnet 128.0.1.19 routing-instance __juniper_private1__ Trying 128.0.1.19... Connected to 128.0.1.19. Escape character is '^]'. ABC platform (700Mhz XLR processor, 3968MB memory, 0KB flash) sp30(vty)# For MX platform to obtain the private IP address assigned to a port do following command: SDPC_XLP2(ironman-re0 vty)# show ipv4 address Index Name Address ----- -------------------- -------------------------- 1320678136 .local..1 10.0.0.4 [local] 1320678136 .local..2 20.0.0.1 [local] 1320678136 pc-2/0/0.16384 20.0.0.1 [local] 1320678136 pc-2/1/0.16384 20.0.0.1 [local] 1320678136 pc-2/2/0.16384 20.0.0.1 [local] 1320678136 pc-2/3/0.16384 20.0.0.1 [local] 1320678136 pc-2/0/0.16384 20.0.0.48 1320678136 pc-2/1/0.16384 20.0.0.49
lab@router-re0> telnet 128.0.1.19 routing-instance __juniper_private1__ Trying 128.0.1.19... Connected to 128.0.1.19. Escape character is '^]'. ABC platform (700Mhz XLR processor, 3968MB memory, 0KB flash) sp30(vty)#
SDPC_XLP2(ironman-re0 vty)# show ipv4 address Index Name Address ----- -------------------- -------------------------- 1320678136 .local..1 10.0.0.4 [local] 1320678136 .local..2 20.0.0.1 [local] 1320678136 pc-2/0/0.16384 20.0.0.1 [local] 1320678136 pc-2/1/0.16384 20.0.0.1 [local] 1320678136 pc-2/2/0.16384 20.0.0.1 [local] 1320678136 pc-2/3/0.16384 20.0.0.1 [local] 1320678136 pc-2/0/0.16384 20.0.0.48 1320678136 pc-2/1/0.16384 20.0.0.49
2020-11-17: Updated router name with a generic name; checked article for accuracy; article found relevant and useful
2022-07-07: Updated with MX almost similar command to check the IP private addressing. Article is still valid and relevant.