Example: Configuring Shared Interfaces (SONET)

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

In this configuration example, two Protected System Domains (PSDs) share a single interface on a Flexible PIC Controller (FPC) that is owned by the Root System Domain (RSD).

Requirements

This configuration example requires the following hardware and software components:

JUNOS Release 9.3 or later
JCS 1200 platform with Routing Engines in slots 5, 6, and 7
T640 router with FPCs in slots 1 through 7
Two Tunnel PICs—one installed on the FPC in slot 1 and the other installed on the FPC in slot 7
One SONET PIC installed on the FPC in slot 6

Overview

With this example configuration, Protected System Domain 5 (PSD5) and PSD6 can both transport packets using a single SONET PIC owned by Root System Domain 3 (RSD3).

As illustrated in Figure 8, RSD3 owns the physical interface (so-6/0/0). PSD5 owns the logical interfaces so-6/0/0.0, so-6/0/0.1, and so-6/0/0.2. A cross-connect using the tunnel interface ut-1/0/0 transports packets between the logical interfaces configured on the PSD and the physical SONET interface on RSD3. Similarly, PSD5 owns logical interface so-6/0/0.3 and uses ut-7/0/0 to transport packets between so-6/0/0.3 and the physical interface on RSD3.

Figure 8: Example: Shared Interfaces (SONET)

Image g016951.gif

Configuration

First, configure the Routing Engines on the JCS 1200 platform using the management module command-line interface (CLI). Then, configure each T-series routing platform using the JUNOS CLI.

JCS 1200 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.
Assign the Routing Engines in slots 5 (primary) and 6 (backup) to RSD3 and PSD1. Assign the Routing Engine in slot 7 to RSD3 and PSD2.
system> baydata —b 05 —data “V01–JCS01–SD03–PSD01–REP05–REB06–PRDT640”
system> baydata —b 06 —data “V01–JCS01–SD03–PSD01–REP05–REB06–PRDT640”
system> baydata —b 07 —data “V01–JCS01–SD03–PSD02–REP07–REB00–PRDT640”

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    No blade present
5    Supported         V01–JCS01–SD03–PSD01–REP05–REB06–PRDT640
6    Supported         V01–JCS01–SD03–PSD01–REP05–REB06–PRDT640
7    Supported         V01–JCS01–SD03–PSD02–REP07–REB00–PRDT640
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:

Log in to the T640 router.
At the [edit chassis system-domains] hierarchy level of the JUNOS CLI, include the root-domain-id 3 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:
1. Include the fpcs 1 fpcs 2 fpcs 3 statement to assign the FPCs in slots 1, 2, and 3 to PSD1.
2. Include the control-system-id 1 statement to identify the JCS 1200 platform.
3. 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 PSD1.
4. Include the control-plane-bandwidth-percent 50 statement to allocate 50 percent of the bandwidth on the JCS switch modules and T-series control boards (T-CBs) 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:
1. Include the fpcs 4 fpcs 5 fpcs 6 fpcs 7 statement to assign the FPCs in slots 4, 5, 6, and 7 to PSD2.
2. Include the control-system-id 1 statement to identify the JCS 1200 platform.
3. Include the control-slot-numbers 3 control-slot-numbers 4 statement to assign the Routing Engines in slot 3 and slot 4 in the JCS chassis to PSD2.
4. Include the control-plane-bandwidth-percent 50 statement to allocate 50 percent of the bandwidth on the JCS switch modules and T-CBs to PSD2.
At the [edit interfaces] hierarchy level, include the so-6/0/0 statement to configure the physical SONET interface.
At the [edit interfaces so-6/0/0] hierarchy level, include the encapsulation frame-relay statement to configure Frame Relay encapsulation on the physical interface, and include the unit 0, unit 1, unit 2, and unit 3 statements to configure the logical interfaces.
At the [edit interfaces so-6/0/0 unit n] hierarchy level, include the following statements:
- interface-shared-with psdn—Assign the logical interface to a PSD:
  - For unit 0, the value is 5 (PSD5).
  - For unit 1, the value is 5 (PSD5).
  - For unit 2, the value is 5 (PSD5).
  - For unit 3, the value is 6 (PSD6).
- dlci dlci-identifier—Configure the data-link connection identifier (DLCI) for the point-to-point Frame Relay connection:
  - For unit 0, the value is 16.
  - For unit 1, the value is 17.
  - For unit 2, the value is 18.
  - For unit 3, the value is 100.

Results

Display the results of the configuration:



system-domains {
root-domain-id 3;


protected-system-domains {


psd5 {
description customerA;
fpcs [ 1 2 3 ];
control-system-id 1;
control-slot-numbers [ 5 6 ];
control-plane-bandwidth-percent 50;
}




psd6 {
description customerB;
fpcs [ 4 5 7 ];
control-system-id 1;
control-slot-numbers 7;
control-plane-bandwidth-percent 50;
}


}


}
}
interfaces
so-6/0/0 {
no-keepalives;
encapsulation frame-relay;


unit 0 {
interface-shared-with psd5;
dlci 16;
}




unit 1 {
interface-shared-with psd5;
dlci 17;
}




unit 2 {
interface-shared-with psd5;
dlci 18;
}




unit 3 {
interface-shared-with psd6;
dlci 100;
}


}

PSD5 Configuration

Step-by-Step Procedure

To configure PSD5:

At the [edit interfaces] hierarchy level, include the ut-1/0/0 statement to configure the physical tunnel interface.
At the [edit interfaces ut-1/0/0] hierarchy level, include the unit 0, unit 1, and unit 2 statements to configure the logical tunnel interfaces.
At the [edit interfaces ut-1/0/0 unit n] hierarchy level, include the peer-interface so-6/0/0.logical-unit-number statement to bind the tunnel and SONET interfaces together. Use the following logical-unit-number values:
- For unit 0, the value is 0.
- For unit 1, the value is 1.
- For unit 2, the value is 2.
At the [edit interfaces so-6/0/0] hierarchy level, include the encapsulation frame-relay statement to match the configuration on the RSD, and the shared-interface statement to identify the physical interface as the shared interface.
At the [edit interfaces so-6/0/0] hierarchy level, include unit 0, unit 1, and unit 2 statements to configure logical interfaces.
At the [edit interfaces so-6/0/0 unit n] hierarchy level, include the following statements:
- peer-interface peer-interface—Bind the SONET and tunnel interface interfaces together. Use the following peer-interface values:
  - For unit 0, the value is ut-1/0/0.0.
  - For unit 1, the value is ut-1/0/0.1.
  - For unit 2, the value is ut-1/0/0.2.
- dlci dlci—Configure the DLCI for the point-to-point Frame Relay connection. Use the following dlci values:
  - For unit 0, the value is 16.
  - For unit 1, the value is 17.
  - For unit 2, the value is 18.
- family inet address address—Configure the IP version 4 (IPv4) suite protocol family on the logical SONET interface. Use the following address values:
  - For unit 0, the value is 10.70.0.1/30.
  - For unit 1, the value is 17.17.17.1/30.
  - For unit 2, the value is 18.18.18.1/30.

Results

Display the results of the configuration:



interfaces {


ut-1/0/0 {


unit 0 {
peer-interface so-6/0/0.0;
}




unit 1 {
peer-interface so-6/0/0.1;
}




unit 2 {
peer-interface so-6/0/0.2;
}


}


so-6/0/0 {
encapsulation frame-relay;
shared-interface;


unit 0 {
peer-interface ut-1/0/0.0;
dlci 16;


family inet {
address 10.70.0.1/30;
}


}




unit 1 {
peer-interface ut-1/0/0.1;
dlci 17;


family inet {
address 17.17.17.1/30;
}


}




unit 2 {
peer-interface ut-1/0/0.2;
dlci 18;


family inet {
address 18.18.18.1/30;
}


}


}

PSD6 Configuration

Step-by-Step Procedure

To configure PSD6:

At the [edit interfaces] hierarchy level, include the ut-7/0/0 statement to configure the physical tunnel interface.
At the [edit interfaces ut-7/0/0] hierarchy level, include the unit 0 statement to configure the logical tunnel interface.
At the [edit interfaces ut-1/0/0 unit 0] hierarchy level, include the peer-interface so-6/0/0.logical-unit-number statement to bind the tunnel and the SONET interfaces together.
At the [edit interfaces so-6/0/0] hierarchy level, include the encapsulation frame-relay statement to match the configuration on the RSD, and the shared-interface statement to identify the SONET interface as the shared physical interface.
At the [edit interfaces so-6/0/0] hierarchy level, include the unit 3 statement to configure the logical interface.
At the [edit interfaces so-6/0/0 unit 3] hierarchy level, include the following statements:
- peer-interface ut-7/0/0.0—Bind the SONET and tunnel interfaces together.
- dlci 100—Configure the DLCI for the point-to-point Frame Relay connection.
- family inet address 10.10.10.1/24—Configure the IP version 4 (IPv4) suite protocol family.

Results

Display the results of the configuration:



interfaces {


ut-7/0/0 {


unit 0 {
peer-interface so-6/0/0.3;
}


}




so-6/0/0 {
encapsulation frame-relay;
shared-interface;


unit 3 {
peer-interface ut-7/0/0.0;
dlci 100;


family inet {
address 10.10.10.1/24;
}


}


}

Verification

Verifying Shared Interfaces on RSD3

Purpose

From RSD3, display the status of shared interfaces.

Action

Issue the show interfaces so-6/0/0 command:

user@rsd3> show interfaces so-6/0/0

Physical interface: so-6/0/0, Enabled, Physical link is Up
  Interface index: 128, SNMP ifIndex: 109
  Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, SONET mode,
  Speed: OC192, Loopback: None, FCS: 16, Payload scrambler: Enabled
  Device flags   : Present Running Down
  Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x4000
  Shared-interface  : Owner
  Link flags     : No-Keepalives DTE
  ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
  LMI: Input: 0 (never), Output: 0 (never)
  DTE statistics:
    Enquiries sent                       : 0
    Full enquiries sent                  : 0
    Enquiry responses received           : 0
    Full enquiry responses received      : 0
  DCE statistics:
    Enquiries received                   : 0
    Full enquiries received              : 0
    Enquiry responses sent               : 0
    Full enquiry responses sent          : 0
  Common statistics:
    Unknown messages received            : 0
    Asynchronous updates received        : 0
    Out-of-sequence packets received     : 0
    Keepalive responses timedout         : 0
  CoS queues     : 8 supported, 8 maximum usable queues
  Last flapped   : 2008-08-11 10:51:51 PDT (1w1d 04:47 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  SONET alarms   : LOL, PLL
  SONET defects  : LOL, PLL, LOF, SEF, AIS-L, AIS-P

  Logical interface so-6/0/0.0 (Index 67) (SNMP ifIndex 117) 
    Flags: Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
    Shared interface:
      Shared with: psd5
      Tunnel token: Rx: 2.517, Tx: 1.517
    Input packets : 0 
    Output packets: 0
    DLCI 16
      Flags: Active
      Total down time: 00:01:09 sec, Last down: 264:48:29 ago
        Input packets : 0 
        Output packets: 0
  DLCI statistics:
    Active DLCI  :1  Inactive DLCI  :0

  Logical interface so-6/0/0.1 (Index 68) (SNMP ifIndex 118) 
    Flags: Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
    Shared interface:
      Shared with: psd5
      Tunnel token: Rx: 2.345, Tx: 1.346
    Input packets : 0 
    Output packets: 0
    DLCI 17
      Flags: Active
      Total down time: 00:01:09 sec, Last down: 257:53:11 ago
        Input packets : 0 
        Output packets: 0
  DLCI statistics:
    Active DLCI  :1  Inactive DLCI  :0

  Logical interface so-6/0/0.2 (Index 69) (SNMP ifIndex 119) 
    Flags: Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
    Shared interface:
      Shared with: psd5
      Tunnel token: Rx: 2.333, Tx: 1.334
    Input packets : 0 
    Output packets: 0
    DLCI 18
      Flags: Active
      Total down time: 00:01:09 sec, Last down: 284:58:21 ago
        Input packets : 0 
        Output packets: 0
  DLCI statistics:
    Active DLCI  :1  Inactive DLCI  :0

  Logical interface so-6/0/0.3 (Index 67) (SNMP ifIndex 117) 
    Flags: Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
    Shared interface:
      Shared with: psd5
      Tunnel token: Rx: 2.522, Tx: 1.523
    Input packets : 0 
    Output packets: 0
    DLCI 100
      Flags: Active
      Total down time: 00:01:09 sec, Last down: 278:38:41 ago
        Input packets : 0 
        Output packets: 0
  DLCI statistics:
    Active DLCI  :1  Inactive DLCI  :0

Meaning

Under the Physical interface section of the output, the Shared-interface field displays the value Owner, meaning that RSD owns the physical shared interface so-6/0/0. In the Shared interface fields for each logical interface, you see that so-6/0/0.0, so-6/0/0.1, and so-6/0/0.2 are shared with PSD5, whereas logical interface so-6/0/0.3 is shared with PSD6.

Verifying Shared Interfaces on PSD5

Purpose

From PSD5, display the status of shared interfaces.

Action

Issue the show interfaces so-6/0/0 command:

user@psd5> show interfaces so-6/0/0

Physical interface: so-6/0/0, Enabled, Physical link is Up
  Interface index: 151, SNMP ifIndex: 19353
  Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, Speed: OC192,
  Loopback: None, FCS: 16, Payload scrambler: Enabled
  Device flags   : Present Running
  Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
  Shared-interface  : Non-Owner
  Link flags     : No-Keepalives DTE
  ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
  CoS queues     : 8 supported, 8 maximum usable queues
  Last flapped   : Never
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)

  Logical interface so-6/0/0.0 (Index 68) (SNMP ifIndex 19352)
    Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
    Shared interface:
      Peer interface: ut-1/0/0.0
      Tunnel token: Rx: 2.455, Tx: 1.456
    Input packets : 9
    Output packets: 10
    Protocol inet, MTU: 4470
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 16.16.0.0/30, Local: 16.16.0.1, Broadcast: 16.16.0.3
    DLCI 16
      Flags: Active
      Total down time: 00:00:00 sec, Last down: 00:00:55 ago
        Input packets : 9
        Output packets: 10
  DLCI statistics:
    Active DLCI  :1  Inactive DLCI  :0

  Logical interface so-6/0/0.1 (Index 68) (SNMP ifIndex 19352)
    Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
    Shared interface:
      Peer interface: ut-1/0/0.1
      Tunnel token: Rx: 2.567, Tx: 1.568
    Input packets : 9
    Output packets: 10
    Protocol inet, MTU: 4470
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 16.16.0.0/30, Local: 16.16.0.1, Broadcast: 16.16.0.3
    DLCI 17
      Flags: Active
      Total down time: 00:00:00 sec, Last down: 00:00:55 ago
        Input packets : 9
        Output packets: 10
  DLCI statistics:
    Active DLCI  :1  Inactive DLCI  :0


  Logical interface so-6/0/0.2 (Index 68) (SNMP ifIndex 19352)
    Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
    Shared interface:
      Peer interface: ut-1/0/0.2
      Tunnel token: Rx: 2.567, Tx: 1.568
    Input packets : 9
    Output packets: 10
    Protocol inet, MTU: 4470
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 16.16.0.0/30, Local: 16.16.0.1, Broadcast: 16.16.0.3
    DLCI 18
      Flags: Active
      Total down time: 00:00:00 sec, Last down: 00:00:55 ago
        Input packets : 9
        Output packets: 10
  DLCI statistics:
    Active DLCI  :1  Inactive DLCI  :0

Meaning

Under the Physical interfaces section of the output, the Shared-interface field displays a value of Non-owner, indicating that the shared physical interface so-6/0/0 is not owned by PSD5. The Shared interface field for each logical interface provides the name of its peer uplink tunnel (ut-) interface. For example, for so-6/0/0.0, the peer interface is ut-1/0/0.0.

Verifying Shared Interfaces on PSD6

Purpose

From PSD6, display the status of shared interfaces.

Action

Issue the show interfaces so-6/0/0 command:

user@psd6> show interfaces so-6/0/0

Physical interface: so-6/0/0, Enabled, Physical link is Up
  Interface index: 151, SNMP ifIndex: 19353
  Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, Speed: OC192,
  Loopback: None, FCS: 16, Payload scrambler: Enabled
  Device flags   : Present Running
  Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
  Shared-interface  : Non-Owner
  Link flags     : No-Keepalives DTE
  ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
  CoS queues     : 8 supported, 8 maximum usable queues
  Last flapped   : Never
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)

  Logical interface so-6/0/0.3 (Index 68) (SNMP ifIndex 19352)
    Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
    Shared interface:
      Peer interface: ut-7/0/0.3
      Tunnel token: Rx: 2.455, Tx: 1.456
    Input packets : 9
    Output packets: 10
    Protocol inet, MTU: 4470
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 16.16.0.0/30, Local: 16.16.0.1, Broadcast: 16.16.0.3
    DLCI 100
      Flags: Active
      Total down time: 00:00:00 sec, Last down: 00:00:55 ago
        Input packets : 9
        Output packets: 10
  DLCI statistics:
    Active DLCI  :1  Inactive DLCI  :0

Meaning

Under the Physical interfaces section of the output, the Shared-interface field displays a value of Non-owner, indicating that the shared physical interface so-6/0/0 is not owned by PSD6. The Shared interface field for so-6/0/0.3 indicates that its peer interface is ut-7/0/0.3.