- Download PDFs
-
Example: Consolidating a Layer 2 VPN Network
- Related Topics
- Configuring an RSD and Creating PSDs
Example: Consolidating a Layer 2 VPN Network
In this configuration example, a Layer 2 VPN network topology is reduced and simplified by replacing two M320 routers at the provider edge (PE) of the network with a single platform. The configuration for the consolidated Layer 2 VPN topology is described in the following sections:
Requirements
This example requires the following hardware and software components:
- JUNOS Release 9.1 or later
- One JCS 1200 platform with Routing Engines in slots 4, 5, and 6
- One T640 routing node with FPCs in slots 4 and 5
Overview and Topology
In a typical Layer 2 VPN topology, a customer edge (CE) router is located on each customer site, providing an Ethernet interface between the customer LAN and the provider core network. Provider (P) routers are located in the core of the provider network, and provider edge (PE) routers sit at the edge of the network.
Figure 1 illustrates a typical Layer 2 VPN topology, with T640 routers as P routers, M320 routers as PE routers, and MX-series Ethernet Services routers as CE routers. The service provider uses a separate PE router for each customer.
Figure 1: Typical Layer 2 VPN Network Topology
By replacing the two M320 routers with the JCS 1200 chassis interconnected with the T640 routing node, the service provider simplifies and consolidates the network at the provider edge. One platform supports both customer networks through the creation of PSDs, as shown in Figure 2.
Figure 2: Consolidated Layer 2 VPN Network Topology
Configuration
Table 1 provides the chassis parameters required for the JCS 1200 platform and the T640 routing node for each PSD.
Table 1: Chassis Parameters
The configuration for the consolidated Layer 2 VPN topology is described in the following sections.
JCS 1200 Platform Configuration
Step-by-Step Procedure
To configure the parameters required for the Routing Engines in the JCS chassis:
- Log in to the JCS management module CLI.
- Configure the Routing Engine that is part of PSD1.
The Routing Engine in slot 4 of the JCS chassis is the master
Routing Engine. There is no backup Routing Engine.
To configure the Routine Engine in slot 4, issue the following command:
system> baydata —b 04 —data “V01–JCS01–SD01–PSD01–REP04–REB00–PRDT640”OK
The baydata command specifies the target as a bay blade (-b), identifies the blade (Routing Engine) in slot 04, and specifies the following parameters:
- V01—Product version, which is 01.
- JCS01—JCS platform identifier, which is 01.
- SD01—RSD identifier, which is 01.
- PSD01–PSD identifier, which is 01.
- REP04—Slot in which the primary (or master) Routing Engine resides, which is 04.
- REB00—Slot in which the backup Routing Engine resides. 00 indicates that there is no backup Routing Engine.
- PRDT640—Juniper Networks router product, which is a T640 routing node.
- Configure the baydata command parameters
for the Routing Engines that are part of PSD2. The Routing Engine
in slot 5 is the master, whereas the Routing Engine in slot 6 is the
backup Routing Engine.
- To configure the
Routing Engine in slot 5, issue the following command:
system> baydata —b 05 —data “V01–JCS01–SD01–PSD02–REP05–REB06–PRDT640”OK
The baydata command specifies the target as a bay blade (-b), identifies the blade (Routing Engine) in slot 05, and specifies the following parameters:
- V01—Product version. JUNOS Release 9.1 supports only the value of 01.
- JCS01—JCS platform identifier of 01. JUNOS Release 9.1 supports only the value of 01.
- SD01—RSD identifier, which is 01.
- PSD02–PSD identifier, which is 02.
- REP05—Slot in which the primary (or master) Routing Engine resides, which is 05.
- REB06—Slot in which the backup Routing Engine resides, which is 06.
- PRDT640—Juniper Networks router product, which is a T640 routing node.
- To configure the Routing Engine in slot 6, issue the following
command:
system> baydata —b 06 —data “V01–JCS01–SD01–PSD02–REP05–REB06–PRDT640”OK
The baydata command specifies the target as a bay blade (-b), identifies the blade (Routing Engine) in slot 06, and specifies the following parameters:
- V01—Product version, which is 01.
- JCS01—JCS platform identifier, which is 01.
- SD01—RSD identifier, which is 01.
- PSD02–PSD identifier, which is 02.
- REP05—Slot in which the primary (or master) Routing Engine resides, which is 05.
- REB06—Slot in which the backup Routing Engine resides, which is 06.
- PRDT640—Juniper Networks router product, which is a T640 routing node.
- To configure the
Routing Engine in slot 5, issue the following command:
Results
Display the results of the configuration:
system> baydata
Bay Status Definition 1 No blade present 2 No blade present 3 No blade present 4 Supported V01-JCS01-SD01-PSD01-REP04-REB00-PRDT640 5 Supported V01-JCS01-SD01-PSD02-REP05-REB06-PRDT640 6 Supported V01-JCS01-SD01-PSD02-REP05-REB06-PRDT640 7 No blade present 8 No blade present 9 No blade present 10 No blade present 11 No blade present 12 No blade present
RSD Configuration
Step-by-Step Procedure
To configure the RSD and create the PSDs on the master Routing Engine in the T640 routing node:
- At the [edit chassis system-domains] hierarchy level of the JUNOS CLI, include the root-domain-id 1 statement to identify the RSD.
- At the [edit chassis system-domains] hierarchy level, include the protected-system-domains psd1 statement to create PSD1.
- At the [edit chassis system-domains protected-system-domains
psd1] hierarchy level:
- Include the fpcs 4 statement to assign the FPC in slot 4 to PSD1.
- Include the control-system-id 1 statement to identify the JCS 1200 platform.
- Include the control-slot-numbers 4 statement to assign the Routing Engine in slot 4 in the JCS chassis to PSD1.
- At the [edit chassis system-domains] hierarchy level, include the protected-system-domains psd2 statement to create PSD2.
- At the [edit chassis system-domains protected-system-domains
psd2] hierarchy level:
- Include the fpcs 5 statement to assign the FPC in slot 5 to PSD2.
- Include the control-system-id 1 statement to identify the JCS 1200 platform.
- Include the control-slot-numbers 5 control-slot-numbers 6 statement to assign the Routing Engines in slot 5 and slot 6 in the JCS chassis to PSD2.
Results
Display the results of the configuration:
- chassis {
-
- system-domains {
- root-domain-id 1;
-
- protected-system-domains {
-
- psd1 {
- fpcs 4;
- control-system-id 1;
- control-slot-numbers 4;
- }
-
- psd2 {
- fpcs 5;
- control-system-id 1;
- control-slot-numbers [5 6];
- }
- }
- }
- }
PSD1 Configuration
Step-by-Step Procedure
The configuration for PSD1 is much the same as the configuration that was running on the T640 routing node in the original VPN network topology before the consolidation of two routers into a single platform.
The key difference is the management configuration. To configure the unique parameters for PSD1:
- Configure the following statements at the [edit groups re0 system] hierarchy level:
- Include the host-name customer-a statement to configure the hostname for PSD1,
- Include the backup-router 192.168.71.254 statement to configure a backup router. The backup router should be directly connected to the local routing platform by way of the management interface
- Include the address 192.168.66.240/21 statement at the [edit interfaces fxp0 unit 0 family inet] hierarchy level to configure the management interface.
Results
Display the results of the configuration:
-
- re0 {
-
- system {
- host-name customer-a;
- backup-router 192.168.71.254 destination [ 172.16.0.0/12
192.168.0.0/16 207.17.136.192/32 10.9.0.0/16 10.10.0.0/16 10.13.10.0/23
10.84.0.0/16 10.5.0.0/16 10.6.128.0/17 192.168.102.0/23 207.17.136.0/24
10.209.0.0/16 10.227.0.0/16 10.150.0.0/16 10.157.64.0/19 10.204.0.0/16
];
- }
-
- interfaces {
-
- fxp0 {
-
- unit 0 {
-
- family inet {
- address 192.168.66.240/21;
- }
- }
- }
- }
- }
- interfaces {
-
- fe-0/2/3 {
-
- unit 0 {
-
- family inet {
- address 10.6.1.1/30;
- }
- family iso;
- family mpls;
- }
- }
-
- so-4/0/3 {
- encapsulation frame-relay-ccc;
-
- unit 2 {
- encapsulation frame-relay-ccc;
- dlci 512;
- }
- }
-
- fe-4/3/0 {
-
- unit 0 {
-
- family inet {
- address 10.5.1.2/30;
- }
- family iso;
- family mpls;
- }
- }
- }
-
- routing-options {
- autonomous-system 65299;
- confederation 702 members [ 65299 65235 65240 65269 ];
- }
-
- protocols {
-
- mpls {
- interface all;
- }
-
- bgp {
-
- group ibgp {
- type internal;
- local-address 10.255.171.124;
- import match-all;
-
- family l2vpn {
- signaling;
- }
- export match-all;
- neighbor 10.255.171.125;
- }
- }
-
- isis {
-
- interface fe-4/2/3.0 {
- level 2 metric 10;
- level 1 disable;
- }
-
- interface fe-4/3/0.0 {
- level 2 metric 10;
- level 1 disable;
- }
- interface all;
-
- interface fxp0.0 {
- disable;
- }
-
- interface lo0.0 {
- passive;
- }
- }
-
- ldp {
- interface all;
- interface lo0.0;
- }
- }
-
- policy-options {
-
- policy-statement frame-relay-vpn-export {
-
- term a {
-
- then {
- community add frame-relay-vpn-comm;
- accept;
- }
- }
-
- term b {
- then reject;
- }
- }
-
- policy-statement frame-relay-vpn-import {
-
- term a {
-
- from {
- protocol bgp;
- community frame-relay-vpn-comm;
- }
- then accept;
- }
-
- term b {
- then reject;
- }
- }
-
- policy-statement match-all {
- then accept;
- }
- community frame-relay-vpn-comm members target:65299:400;
- }
-
- routing-instances {
-
- frame-relay-vpn {
- instance-type l2vpn;
- interface so-4/0/3.2;
- route-distinguisher 10.255.171.124:4;
- vrf-import frame-relay-vpn-import;
- vrf-export frame-relay-vpn-export;
-
- protocols {
-
- l2vpn {
- encapsulation-type frame-relay;
-
- site 2 {
- site-identifier 2;
-
- interface so-4/0/3.2 {
- remote-site-id 1;
- }
- }
- }
- }
- }
- }
PSD2 Configuration
Step-by-Step Procedure
The configuration for PSD2 is much the same as the configuration that was running on the T640 routing node in the original VPN network topology before the consolidation of two routers into a single platform.
The key difference is the management configuration. To configure the unique parameters for PSD2:
- Configure the following statements at the [edit system re0] hierarchy level:
- Include the host-name customer-b statement to configure the hostname for the master Routing Engine (re0) on PSD2,
- Include the backup-router 192.168.71.254 statement to configure a backup router. The backup router should be directly connected to the local routing platform by way of the management interface.
- Include the address 192.168.66.240/21 statement at the [edit interfaces fxp0 unit 0 family inet] hierarchy level to configure the fxp0 management interface.
- Configure the backup Routing Engine parameters
by including the following statements at the [edit system re1] hierarchy level:
- Include the host-name customer-b1 statement to configure the hostname for the backup Routing Engine (re1) on PSD2,
- Include the backup-router 192.168.71.254 statement to configure a backup router. The backup router should be directly connected to the local routing platform by way of the management interface.
- Include the address 192.168.66.242/21 statement at the [edit interfaces fxp0 unit 0 family inet] hierarchy level to configure the fxp0 management interface.
Results
Display the results of the configuration:
-
- re0 {
-
- system {
- host-name customer-b;
- backup-router 192.168.71.254 destination [ 172.16.0.0/12
192.168.0.0/16 207.17.136.192/32 10.9.0.0/16 10.10.0.0/16 10.13.10.0/23
10.84.0.0/16 10.5.0.0/16 10.6.128.0/17 192.168.102.0/23 207.17.136.0/24
10.209.0.0/16 10.227.0.0/16 10.150.0.0/16 10.157.64.0/19 10.204.0.0/16
];
- }
-
- interfaces {
-
- fxp0 {
-
- unit 0 {
-
- family inet {
- address 192.168.66.242/21;
- }
- }
- }
- }
- }
-
- re1 {
-
- system {
- host-name customer-b1;
- backup-router 192.168.71.254 destination [ 172.16.0.0/12
192.168.0.0/16 207.17.136.192/32 10.9.0.0/16 10.10.0.0/16 10.13.10.0/23
10.84.0.0/16 10.5.0.0/16 10.6.128.0/17 192.168.102.0/23 207.17.136.0/24
10.209.0.0/16 10.227.0.0/16 10.150.0.0/16 10.157.64.0/19 10.204.0.0/16
];
- }
-
- interfaces {
-
- fxp0 {
-
- unit 0 {
-
- family inet {
- address 192.168.66.241/21;
- }
- }
- }
- }
- }
- interfaces {
-
- fe-5/1/1 {
-
- unit 0 {
-
- family inet {
- address 10.5.1.1/30;
- }
- family iso;
- family mpls;
- }
- }
-
- fe-5/1/2 {
-
- unit 0 {
-
- family inet {
- address 10.8.1.1/30;
- }
- family iso;
- family mpls;
- }
- }
-
- so-5/3/0 {
- encapsulation frame-relay-ccc;
-
- unit 1 {
- encapsulation frame-relay-ccc;
- dlci 512;
- }
- }
- }
-
- routing-options {
- autonomous-system 65299;
- confederation 702 members [ 65299 65235 65240 65269 ];
- }
-
- protocols {
-
- mpls {
- interface all;
- }
-
- bgp {
-
- group ibgp {
- type internal;
- local-address 10.255.171.125;
- import match-all;
-
- family l2vpn {
- signaling;
- }
- export match-all;
- neighbor 10.255.171.124;
- }
- }
-
- isis {
-
- interface fe-5/1/1.0 {
- level 2 metric 10;
- level 1 disable;
- }
-
- interface fe-5/1/2.0 {
- level 2 metric 10;
- level 1 disable;
- }
- interface all;
-
- interface fxp0.0 {
- disable;
- }
-
- interface lo0.0 {
- passive;
- }
- }
-
- ldp {
- interface all;
- interface lo0.0;
- }
- }
-
- policy-options {
-
- policy-statement frame-relay-vpn-export {
-
- term a {
-
- then {
- community add frame-relay-vpn-comm;
- accept;
- }
- }
-
- term b {
- then reject;
- }
- }
-
- policy-statement frame-relay-vpn-import {
-
- term a {
-
- from {
- protocol bgp;
- community frame-relay-vpn-comm;
- }
- then accept;
- }
-
- term b {
- then reject;
- }
- }
-
- policy-statement match-all {
- then accept;
- }
- community frame-relay-vpn-comm members target:65299:400;
- }
-
- routing-instances {
-
- frame-relay-vpn {
- instance-type l2vpn;
- interface so-5/3/0.1;
- route-distinguisher 10.255.171.125:4;
- vrf-import frame-relay-vpn-import;
- vrf-export frame-relay-vpn-export;
-
- protocols {
-
- l2vpn {
- encapsulation-type frame-relay;
-
- site 1 {
- site-identifier 1;
-
- interface so-5/3/0.1 {
- remote-site-id 2;
- }
- }
- }
- }
- }
- }
Verification
Verify that the two PSDs are configured and operating properly:
- Verifying Configured PSDs
- Verifying PSD Hardware
- Verifying PSD Routing Engine Information
- Verifying PSD Ethernet Switch Statistics
Verifying Configured PSDs
Purpose
Verify that PSD1 and PSD2 are configured and online.
Action
On the RSD, issue the show chassis psd command.
{master}
user@host> show chassis psd
PSD Description State Uptime 1 Online 5 days, 19 hours, 16 minutes, 16 seconds 2 Online 5 days, 18 hours, 12 minutes, 11 seconds
Meaning
The example shows that the PSDs are configured and online.
Verifying PSD Hardware
Purpose
Display information about the FPCs and Routing Engines that are part of each PSD.
Action
On each PSD, issue the show chassis hardware command.
The following example displays the hardware components belonging to PSD1:
user@psd1> show chassis hardware
rsd-re0: -------------------------------------------------------------------------- Hardware inventory: Item Version Part number Serial number Description Chassis S19068 T640 Midplane REV 04 710-002726 AX5666 T640 Backplane FPM GBUS REV 02 710-002901 HE3251 T640 FPM Board FPM Display REV 02 710-002897 HE7860 FPM Display CIP REV 05 710-002895 HC0474 T-series CIP PEM 1 Rev 03 740-002595 MH15367 Power Entry Module SCG 0 REV 04 710-003423 HF6042 T640 Sonet Clock Gen. SCG 1 REV 11 710-003423 HW7765 T640 Sonet Clock Gen. Routing Engine 0 REV 04 740-014082 1000660098 RE-A-2000 Routing Engine 1 REV 01 740-005022 210865700324 RE-3.0 CB 0 REV 06 710-007655 WE9377 Control Board (CB-T) CB 1 REV 06 710-007655 WE9379 Control Board (CB-T) FPC 4 REV 02 710-002385 HC0619 FPC Type 2 CPU REV 06 710-001726 HB1916 FPC CPU MMB 1 REV 03 710-004047 HE3195 MMB-288mbit ICBM REV 04 710-003384 HC0377 FPC ICBM PPB 0 REV 02 710-003758 HC0585 PPB Type 2 PPB 1 REV 02 710-003758 HC0574 PPB Type 2 SPMB 0 REV 10 710-003229 WE9582 T-series Switch CPU SPMB 1 REV 10 710-003229 WE9587 T-series Switch CPU SIB 0 REV 05 750-005486 HV8445 SIB-I8-F16 SIB 1 REV 05 750-005486 HW2650 SIB-I8-F16 SIB 2 REV 05 750-005486 HW7041 SIB-I8-F16 SIB 3 REV 05 750-005486 HV4274 SIB-I8-F16 SIB 4 REV 05 750-005486 HV8464 SIB-I8-F16 Fan Tray 0 Front Top Fan Tray Fan Tray 1 Front Bottom Fan Tray Fan Tray 2 Rear Fan Tray psd1-re0: -------------------------------------------------------------------------- Hardware inventory: Item Version Part number Serial number Description Chassis 740-023156 SNJCSJCSAC00 JCS1200 AC Chassis Routing Engine 0 REV 01 740-023157 SNBLJCSAC004 RE-JCS1200-1x2330
The following example displays the hardware components belonging to PSD2:
user@psd2> show chassis hardware
rsd-re0: -------------------------------------------------------------------------- Hardware inventory: Item Version Part number Serial number Description Chassis S19068 T640 Midplane REV 04 710-002726 AX5666 T640 Backplane FPM GBUS REV 02 710-002901 HE3251 T640 FPM Board FPM Display REV 02 710-002897 HE7860 FPM Display CIP REV 05 710-002895 HC0474 T-series CIP PEM 1 Rev 03 740-002595 MH15367 Power Entry Module SCG 0 REV 04 710-003423 HF6042 T640 Sonet Clock Gen. SCG 1 REV 11 710-003423 HW7765 T640 Sonet Clock Gen. Routing Engine 0 REV 04 740-014082 1000660098 RE-A-2000 Routing Engine 1 REV 01 740-005022 210865700324 RE-3.0 CB 0 REV 06 710-007655 WE9377 Control Board (CB-T) CB 1 REV 06 710-007655 WE9379 Control Board (CB-T) FPC 5 REV 01 710-010233 HM4187 E-FPC Type 1 CPU REV 01 710-010169 HS9939 FPC CPU-Enhanced MMB 1 REV 01 710-010171 HR0833 MMB-288mbit SPMB 0 REV 10 710-003229 WE9582 T-series Switch CPU SPMB 1 REV 10 710-003229 WE9587 T-series Switch CPU SIB 0 REV 05 750-005486 HV8445 SIB-I8-F16 SIB 1 REV 05 750-005486 HW2650 SIB-I8-F16 SIB 2 REV 05 750-005486 HW7041 SIB-I8-F16 SIB 3 REV 05 750-005486 HV4274 SIB-I8-F16 SIB 4 REV 05 750-005486 HV8464 SIB-I8-F16 Fan Tray 0 Front Top Fan Tray Fan Tray 1 Front Bottom Fan Tray Fan Tray 2 Rear Fan Tray psd2-re0: -------------------------------------------------------------------------- Hardware inventory: Item Version Part number Serial number Description Chassis 740-023156 SNJCSJCSAC00 JCS1200 AC Chassis Routing Engine 0 REV 01 740-023157 SNBLJCSAC006 RE-JCS1200-1x2330 Routing Engine 1 REV 01 740-023157 SNBLJCSAC005 RE-JCS1200-1x2330
Meaning
In the command output, the FPC that belongs to the PSD is displayed under the rsd-re0: field heading. The Routing Engines on the JCS chassis that belong to the PSD are displayed under the psd2-re0: heading.
Verifying PSD Routing Engine Information
Purpose
Display detailed information about the Routing Engines assigned to each PSD.
Action
On each PSD, issue the show chassis routing-engine command.
The following example displays detailed information about the Routing Engine assigned to PSD1.
user@psd1> show chassis routing-engine
Routing Engine status:
Slot 0:
Physical Slot 4
Current state Master
Election priority Master (default)
DRAM 3328 MB
Memory utilization 10 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 100 percent
Model RE-JCS1200-1x2330
Serial ID SNBLJCSAC004
Start time 2008-03-30 03:19:49 PDT
Uptime 11 hours, 46 minutes, 24 seconds
Load averages: 1 minute 5 minute 15 minute
0.00 0.00 0.00
The following example displays detailed information about the Routing Engines assigned to PSD2.
user@psd2> show chassis routing-engine
Routing Engine status:
Slot 0:
Physical Slot 6
Current state Master
Election priority Master (default)
DRAM 3328 MB
Memory utilization 10 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 100 percent
Model RE-JCS1200-1x2330
Serial ID SNBLJCSAC006
Start time 2008-03-30 03:25:43 PDT
Uptime 11 hours, 49 minutes, 30 seconds
Load averages: 1 minute 5 minute 15 minute
0.00 0.00 0.00
Routing Engine status:
Slot 1:
Physical Slot 5
Current state Backup
Election priority Backup (default)
DRAM 3328 MB
Memory utilization 9 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 100 percent
Model RE-JCS1200-1x2330
Serial ID SNBLJCSAC005
Start time 2008-03-30 03:25:40 PDT
Uptime 11 hours, 49 minutes, 36 seconds
Meaning
The Physical Slot field displays the JCS chassis slot number in which each Routing Engine is installed.
Verifying PSD Ethernet Switch Statistics
Purpose
Display the Ethernet switch statistics for each PSD.
Action
On each PSD, issue the show chassis ethernet-switch statistics command.
The following example displays information about the Ethernet switch statistics for PSD1:
user@psd1> show chassis ethernet-switch
statistics
Statistics for switch[1] port INT4 connected to fpx0: TX Octets 3295346375 TX Unicast Packets 47634559 TX Multicast Packets 1848912 TX Broadcast Packets 28900124 Tx Discards 0 TX Errors 0 RX Octets 1393157883 RX Unicast Packets 25671001 RX Multicast Packets 453 RX Broadcast Packets 1568098 RX Discards 1539 RX Errors 0 RX Unknown Protocol 0 Link State Changes 209 Statistics for switch[1] port EXT1 connected to RSD 1: TX Octets 2205898607 TX Unicast Packets 23928658 TX Multicast Packets 412974 TX Broadcast Packets 4848743 Tx Discards 0 TX Errors 0 RX Octets 2391964542 RX Unicast Packets 26419568 RX Multicast Packets 226 RX Broadcast Packets 6025807 RX Discards 8 RX Errors 4 RX Unknown Protocol 0 Link State Changes 113 Statistics for switch[1] port EXT6 connected to external management: TX Octets 1528646621 TX Unicast Packets 7591565 TX Multicast Packets 112 TX Broadcast Packets 6025 Tx Discards 0 TX Errors 0 RX Octets 509146577 RX Unicast Packets 30206303 RX Multicast Packets 3036487 RX Broadcast Packets 12226460 RX Discards 18650 RX Errors 6 RX Unknown Protocol 0 Link State Changes 1 Statistics for switch[2] port INT4 connected to fpx1: TX Octets 3973176699 TX Unicast Packets 27784685 TX Multicast Packets 90293282 TX Broadcast Packets 35160560 Tx Discards 0 TX Errors 0 RX Octets 2278093260 RX Unicast Packets 10421370 RX Multicast Packets 496 RX Broadcast Packets 1881084 RX Discards 1936 RX Errors 0 RX Unknown Protocol 0 Link State Changes 231 Statistics for switch[2] port EXT1 connected to RSD 1: TX Octets 3175062867 TX Unicast Packets 4961873 TX Multicast Packets 509882 TX Broadcast Packets 5622328 Tx Discards 0 TX Errors 0 RX Octets 478994886 RX Unicast Packets 49004 RX Multicast Packets 251 RX Broadcast Packets 7419709 RX Discards 12 RX Errors 6 RX Unknown Protocol 0 Link State Changes 129 Statistics for switch[2] port EXT6 connected to external management: TX Octets 778154 TX Unicast Packets 4244 TX Multicast Packets 73 TX Broadcast Packets 769 Tx Discards 0 TX Errors 0 RX Octets 723965940 RX Unicast Packets 43991082 RX Multicast Packets 91767677 RX Broadcast Packets 15655861 RX Discards 24442638 RX Errors 3331664 RX Unknown Protocol 0 Link State Changes 1
The following example displays information about the Ethernet switch statistics for PSD2:
user@psd2> show chassis ethernet-switch
statistics
Statistics for switch[1] port INT6 connected to fpx0: TX Octets 2686108265 TX Unicast Packets 45820458 TX Multicast Packets 1849567 TX Broadcast Packets 28901148 Tx Discards 0 TX Errors 0 RX Octets 3814661840 RX Unicast Packets 23875023 RX Multicast Packets 364 RX Broadcast Packets 1578993 RX Discards 1492 RX Errors 0 RX Unknown Protocol 0 Link State Changes 151 Statistics for switch[1] port EXT1 connected to RSD 1: TX Octets 2206358846 TX Unicast Packets 23930762 TX Multicast Packets 413155 TX Broadcast Packets 4850581 Tx Discards 0 TX Errors 0 RX Octets 2392164387 RX Unicast Packets 26421668 RX Multicast Packets 226 RX Broadcast Packets 6026725 RX Discards 8 RX Errors 4 RX Unknown Protocol 0 Link State Changes 113 Statistics for switch[1] port EXT6 connected to external management: TX Octets 1528692454 TX Unicast Packets 7591911 TX Multicast Packets 112 TX Broadcast Packets 6027 Tx Discards 0 TX Errors 0 RX Octets 510609656 RX Unicast Packets 30209066 RX Multicast Packets 3037753 RX Broadcast Packets 12229518 RX Discards 18650 RX Errors 6 RX Unknown Protocol 0 Link State Changes 1 Statistics for switch[2] port INT6 connected to fpx1: TX Octets 3938845805 TX Unicast Packets 27450378 TX Multicast Packets 90293642 TX Broadcast Packets 35156025 Tx Discards 0 TX Errors 0 RX Octets 2016108068 RX Unicast Packets 9832240 RX Multicast Packets 448 RX Broadcast Packets 1897002 RX Discards 1844 RX Errors 0 RX Unknown Protocol 0 Link State Changes 195 Statistics for switch[2] port EXT1 connected to RSD 1: TX Octets 3175192403 TX Unicast Packets 4961873 TX Multicast Packets 510063 TX Broadcast Packets 5624171 Tx Discards 0 TX Errors 0 RX Octets 479053702 RX Unicast Packets 49004 RX Multicast Packets 251 RX Broadcast Packets 7420628 RX Discards 12 RX Errors 6 RX Unknown Protocol 0 Link State Changes 129 Statistics for switch[2] port EXT6 connected to external management: TX Octets 778154 TX Unicast Packets 4244 TX Multicast Packets 73 TX Broadcast Packets 769 Tx Discards 0 TX Errors 0 RX Octets 732481038 RX Unicast Packets 44041821 RX Multicast Packets 91768932 RX Broadcast Packets 15658928 RX Discards 24443758 RX Errors 3331666 RX Unknown Protocol 0 Link State Changes 1
Meaning
In the output for PSD1:
- INT4 provides the internal connection between the Routing Engine in slot 4 and the JCS switch module.
- EXT1 provides the connection between the JCS switch module and the RSD.
- EXT6 provides the connection between the JCS switch module and the management ports on each Routing Engine in the JCS chassis
In the output for PSD2:
- INT6 provides the internal connection between the master Routing Engine in slot 6 and the JCS switch module.
- EXT1 provides the connection between the JCS switch module and the RSD.
- EXT6 provides the connection between the JCS switch module and the management ports on each Routing Engine in the JCS chassis.