Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Example: CTP Interoperability with M Series T1/E1 Circuit Emulation PICs

This example describes how to configure an M Series router and a CTP device to create a T1 SAToP circuit that can interoperate between the router and the CTP device. Topics include:

Requirements

This example uses the following software and hardware components:

  • Juniper Networks CTP150 or CTP2000 Circuit to Packet platform with a T1/E1 interface or a serial interface with a T1/E1 daughter card
  • CTPOS 6.0 or later
  • Juniper Networks M Series Multiservice Edge Router with the following:
    • PB-12T1E1-CE-TELCO 12-port discrete T1/E1 Telco connector
    • PB-TUNNEL-1 PIC

Overview and Topology

The topology used in this example consists of an M Series router used as the provider edge (PE) router and a CTP device at the customer edge (CE).

  • On the router, you configure a Layer 2 circuit that provides a point-to-point Layer 2 connection transported by means of MPLS. It is represented by a logical interface that connects the router (PE) to the CTP device (CE). You configure the Layer 2 circuit as a static Layer 2 circuit pseudowire that has static values for the incoming and outgoing MPLS labels needed to enable the pseudowire connection. You then configure a GRE tunnel that is used to transport the Layer 2 circuit.
  • On the CTP device, you configure a SAToP bundle that has the remote address of the Layer 2 circuit on the router and the incoming and outgoing MPLS labels that correspond to the labels configured on the router. GRE is used as the transport protocol for the SAToP bundle.

Figure 2 shows the topology for this example.

Figure 2: Network Topology for a T1 SAToP Circuit between a CE PIC and a CTP Device

Network Topology
for a T1 SAToP Circuit between a CE PIC and a CTP Device

Table 17 shows the configuration of the SAToP bundle on the CTP device and the configuration of the M Series router.

Table 17: Configuration Components for CTP Interoperability with M Series T1/E1 Circuit Emulation PIC

Device

Property

Setting

CTP Platform SATop Bundle

Interface

te-0/1

Remote address

10.0.0.161

Outgoing MPLS label

1000003

Incoming MPLS label

1000004

Transport protocol

GRE

Router

Controller interface

ct1-0/0/0

T1 interface

t1-2/0/1

GRE tunnel source address

10.0.0.161

GRE tunnel destination network

10.0.0.163

Layer 2 circuit neighbor interface:

IP address

Interface

Outgoing MPLS label

Incoming MPLS label

Virtual circuit ID


10.0.0.163

t1-2/0/1

1000004

1000003

1001

Configuration

In this example, the CTP device is configured using CTP Menu.

To configure the CTP device and the router, perform these tasks:

Configuring the Default Bundle Data Protocol on the CTP Device

Step-by-Step Procedure

The default bundle data protocol is GRE (47). Before you configure SAToP bundles, you should change the default bundle data protocol to a value other than GRE. Doing so prevents conflict between legacy CTP bundles and SAToP bundles that are using GRE for interoperability.

To configure the default data protocol for bundles to a value other than GRE using CTP Menu:

  1. From the Main Menu, select 5) Node Operations.
  2. Select 3) Configure network settings.
  3. Select 6) CTP Bndl Data pkt protocol.

    You are notified that changing this parameter requires a system reboot.

  4. Enter 46 as the protocol for data packets.
  5. Reboot the system.

Results

Please select a number from the following list:
-------------------------------------
 0) Back to Previous Menu
 1) Supported Protocols:        IPv4&IPv6
 2) IPv4 Configuration
 3) IPv6 Configuration
 4) Virtual IP addresses
 5) OAM port (IPv4):            16
 6) CTP Bndl Data pkt protocol: 46
 7) CTP Bndl OAM port (IPv6):   32
 8) VLAN Configuration
 9) Current Configuration (active on reboot)
10) Port operations (PBS/bridge)
11) Config port operational mode (CE/PBS/bridge)
12) Config access ip filtering
13) SNMP Configuration
------------ Your choice [0]: 

Creating a SAToP Bundle on the CTP Device

Step-by-Step Procedure

To create a SAToP bundle:

  1. From the Main Menu, select 1) Bundle Operations.
  2. Select 2) SAToP.
  3. Enter add, and select a T1/E1 interface or select a serial interface that has a T1/E1 daughter card.

    The CTP device creates a new SAToP bundle.

Configuring the Port Settings for the SAToP Bundle on the CTP Device

Step-by-Step Procedure

To configure the port settings:

  1. From the Main Menu, select 3) Port Config.
  2. Select 2) Interface.
  3. Select 1) Type, and set the type to T1 or (for daughter cards) to Optional Interface: T1/E1
  4. Select 2) Option and select B8ZS.
  5. Select 3) Clock Config and select 1) CTP is Clock Source.

Results

==========================================================================
= (g74 04/20/10 18:51:58 GMT) | Config Menu for Port te-0/1
==========================================================================

Please select a number from the following list:
-------------------------------------
 0) Back to Previous Menu
 1) Port descriptor text:
 2) Interface:            T1-B8ZS
 3) Clock Config:         CTP is Clock Source
------------ Your choice [2]:

Configuring the Bundle Settings for the SAToP Bundle on the CTP Device

Step-by-Step Procedure

To configure the bundle settings:

  1. From the Main Menu, select 3) Port Config.
  2. Select 10) Transport and set the transport protocol to GRE.
  3. Select 1) Remote Address and specify the remote circuit IP address 10.0.0.161.
  4. Select 2) Outgoing MPLS Label, and set the outgoing label to 1000003.
  5. Select 3) Incoming MPLS Label, and set the incoming MPLS label to 1000004.
  6. Select 4) Packet Size, and set the packet size. We recommend that you set the packet size to 1024 bytes or higher to reduce the overhead associated with the headers and to reduce the packet size. SAToP requires that both endpoints are configured to use the same packet payload size.

Results

==========================================================================
= (g74 04/20/10 19:01:42 GMT) | Config Menu for Bundle 1
= Bundle type: SAToP | Bundle source is Port te-0/1
= Bundle description:
==========================================================================

Please select a number from the following list:
-------------------------------------
 0) Back to Previous Menu
 1) Remote Address:        10.0.0.1 
 2) Outgoing MPLS Label:   1000003
 3) Incoming MPLS Label:   1000004
 4) Packet Size:           1024
 5) Min Buffer (ms):       8.000
 6) Pkt Buffer Set (ms):   12.000
 7) Max Buffer (ms):       16.000
 8) Service Type:          0
 9) Time to Live:          255
10) Transport:             GRE
11) Advanced Options...
12) Bundle descriptor text:
------------ Your choice [10]: 
8

Configuring the Controller Interface on the Router

CLI Quick Configuration

To quickly configure the controller interface, copy the following commands and paste them into the router terminal window:

[edit]edit interfaces ct1-0/0/0 set clocking internalset no-partition interface-type t1

Step-by-Step Procedure

To configure a controller interface:

  1. Create the controller interface.
    [edit]user@sp-router# edit interfaces ct1-0/0/0
  2. Set the clocking to internal.
    [edit interfaces ct1-0/0/0]user@sp-router# set clocking internal
  3. Specify that the controller interface is unpartitioned, and specify the interface type.
    [edit interfaces ct1-0/0/0]user@sp-router# set no-partition interface-type t1

Configuration Results

Display the results of the configuration.

[edit interfaces]user@sp-router# show
ct1-0/0/0 {clocking internal;no-partition interface-type t1;}

Configuring SAToP Emulation on the T1 interface on the Router

CLI Quick Configuration

To quickly configure SAToP Emulation on the T1 interface, copy the following commands and paste them into the router terminal window:

[edit]edit interfaces t1-2/0/1set encapsulation satop set unit 0set satop-options payload-size 1024set satop-options jitter-buffer-packets 8set clocking internal

Step-by-Step Procedure

To configure the T1 interface:

  1. Create the T1 interface.
    [edit]user@sp-router# edit interfaces t1-2/0/1
  2. Set the encapsulation type to SAToP.
    [edit interfaces t1-2/0/1]user@sp-router# set encapsulation satop
  3. Specify the unit number.
    [edit interfaces t1-2/0/1]user@sp-router# set unit 0
  4. Specify the payload size, in bytes. We recommend that you set the packet payload size to 1024 bytes or higher to reduce the overhead associated with the headers and to reduce the packet size. SAToP requires that both endpoints are configured to use the same packet payload size.
    [edit interfaces t1-2/0/1]user@sp-router# set satop-options payload-size 1024
  5. Specify the number of packets in the jitter buffer.
    [edit interfaces t1-2/0/1]user@sp-router# set satop-options jitter-buffer-packets 8
  6. Set clocking to internal.
    [edit interfaces t1-2/0/1]user@sp-router# set clocking internal

Configuration Results

Display the results of the configuration.

[edit interfaces]user@sp-router# show
ct1-0/0/0 {clocking internal;no-partition interface-type t1;}t1-2/0/1 {satop-options {payload-size 1024;jitter-buffer-packets 8;}clocking internal;encapsulation satop;unit 0;}

Enabling MPLS on the T1 Interface on the Router

CLI Quick Configuration

To quickly enable MPLS on the T1 interface, copy the following commands and paste them into the router terminal window:

[edit]edit protocols set mpls interface t1-2/0/1

Step-by-Step Procedure

To enable MPLS on the T1 interface:

  1. Access the protocol configuration.
    [edit]user@sp-router# edit protocols
  2. Enable MPLS on the T1 interface.
    [edit protocols]user@sp-router# set mpls interface t1-2/0/1

Configuration Results

Display the results of the configuration.

[edit protocols]user@sp-router# show
mpls {interface t1-2/0/0.1;}

Configuring the Static Layer 2 Circuit on the Router

CLI Quick Configuration

To quickly configure the Layer 2 circuit, copy the following commands and paste them into the router terminal window:

[edit]edit protocols l2circuitedit neighbor 10.0.0.163edit interface t1-2/0/1set static incoming-label 1000003set static outgoing-label 1000004set virtual-circuit-id 1001

Step-by-Step Procedure

To configure a static Layer 2 circuit:

  1. Create the Layer 2 circuit.
    [edit]user@sp-router# edit protocols l2circuit
  2. Create the neighbor interface for the Layer 2 circuit.
    [edit protocols l2circuit]user@sp-router# edit neighbor 10.0.0.163user@sp-router# edit interface t1-2/0/1
  3. Configure static values for the in and out labels needed to enable the pseudowire connection.
    [edit protocols l2circuit neighbor 10.0.0.163 interface t1-2/0/0.1]user@sp-router# set static incoming-label 1000003user@sp-router# set static outgoing-label 1000004
  4. Specify the virtual circuit identifier.
    [edit protocols l2circuit neighbor 10.0.0.163 interface t1-2/0/0.1]user@sp-router# set virtual-circuit-id 1001

Configuration Results

Display the results of the configuration.

[edit protocols l2circuit]user@sp-router# show
neighbor 10.0.0.163 {interface t1-2/0/1.0 {static {incoming-label 1000003;outgoing-label 1000004;}virtual-circuit-id 1001;}}

Configuring the GRE Tunnel on the Router

CLI Quick Configuration

To quickly configure the GRE tunnel, copy the following commands and paste them into the router terminal window:

[edit]edit routing-optionsedit dynamic-tunnels gre-ctpset gre set source-address 10.0.0.161set destination-networks 10.0.0.163/32

Step-by-Step Procedure

To configure a GRE tunnel:

  1. Create a dynamic tunnel.
    [edit]user@host# edit routing-optionsuser@host# edit dynamic-tunnels gre-ctp
  2. Specify the type of tunnel.
    [edit routing-options dynamic-tunnels gre-ctp]user@host# set gre
  3. Specify the source address for the GRE tunnel. The source address is used as the source for the local tunnel endpoint.
    [edit routing-options dynamic-tunnels gre-ctp]user@host# set source-address 10.0.0.161
  4. Specify the IPv4 prefix range for the destination network. Only tunnels within the specified IPv4 prefix range can be created.
    [edit routing-options dynamic-tunnels gre-ctp]user@host# set destination-networks 10.0.0.163/32

Configuration Results

Display the results of the configuration.

[edit routing-options]user@sp-router# show
dynamic-tunnels {gre-ctp {source-address 10.0.0.161;gre;destination-networks {10.0.0.163/32;}}}

Activating the SAToP Bundle on the CTP Device

Step-by-Step Procedure

To activate the SAToP bundle

  1. From the Main Menu, select 1) Bundle Operations.
  2. Select 2) SAToP.
  3. Select the SAToP bundle from the list.
  4. Select 4) Activate .
  5. Verify that you want to activate the bundle.

Verification

To confirm that the configuration is working properly, perform these tasks:

Verifying the SAToP Circuit Using a Node Summary on the CTP Device

Purpose

Verify that the circuit is running.

Action

From the Main Menu of CTP Menu, select 3) Node Summary

CTP Code version     : 6.0R1 100325 (Compile Time 09:18:24 AM)

>>>>> Circuit Emulation Bundles <<<<<
Bndl BndlTyp    Port      TS         RemAddr     CID    LCID RunState RCtr
==========================================================================
   0   SAToP  te-0/0     N/A      10.0.0.161 1000003 1000004  RUNNING    0
==========================================================================
Checked out PPS - All Bundles: 376, System Maximum: 12500
   (1 PPS = full duplex packet transfer, Bundle <---> IP network)

Meaning

The display shows that the SAToP bundle is in the RUNNING state.

Verifying the SAToP Circuit Using a Bundle Query on the CTP Device

Purpose

Verify that the circuit is running.

Action

From the Main Menu of CTP Menu, select 1) Query

########### Bundle 0 type    SAToP ############
##### Bundle 0 is transporting Port te-0/0 ####

--------- Bundle 0 Config ---------
DBase State:         ACTIVE
Remote Addr:         10.0.0.161
Outgoing MPLS Label: 1000003
Incoming MPLS Label: 1000004
Using Virtual IP:    10.0.0.163
Packet size:         512
Buf Max/Set/Min(ms): 24.000/16.000/8.000
IP Hdr TOS:          0 (decimal)
Port(s) in bundle:   te-0/0
Bndl Config Flags:   TunGRE

---------- Port te-0/0 Config ----------
Interface type:      T1-B8ZS
Framing type:        N/A
Line Buildout:       ~133 ft
Clock Config:        CTP is Clock Source (Adaptive End)

Hit Carriage Return to Continue...

--------- Bundle 0 State ----------
Run State:           RUNNING
T1E1 flags:          No_Alarm
Adaptive State:      Maintain   (20 us)
Adap Recovered Freq: 1544.009918 kHz
Checked out PPS:     Bndl: 376, All Bndl: 376, Sys Max: 12500

--------- Bundle 0 Counters -------
I/F bound packets:   358288
NET bound packets:   358288
Late pkts:           0
Missing pkts:        0
Buffer restarts:     0
Buffer underflows:   0
Buffer overflows:    0
Buffer starves:      0
Buffer max samples:  377
Buff Max/Avg/Min:    16.25/16.24/15.54
Buff Last Minute:    16.25/16.24/15.56
Last counter clear:  0wk, 0d, 0h, 15m, 51s

Meaning

The display shows that the SAToP bundle is in the ACTIVE state and that the run state is RUNNING.

Verifying That the GRE Route is Added to Routing Table on Router

Purpose

Verify that the GRE route has been added to the inet.3 routing table.

Action

user@host> show route 10.0.0.163
inet.3: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.0.163/32      *[Tunnel/300] 05:35:04
                    > via gr-2/3/0.32769
                    [Tunnel/300] 7w0d 03:12:32
                      Tunnel

Meaning

The display shows that

Verifying the Layer 2 Circuit Connections on Router

Purpose

Verifying that the Layer 2 circuit connections are running on the router.

Action

user@host> show l2circuit connections
Layer-2 Circuit Connections:

Legend for connection status (St)
EI -- encapsulation invalid      NP -- interface h/w not present
MM -- mtu mismatch               Dn -- down
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down
CM -- control-word mismatch      Up -- operational
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          IB -- TDM incompatible bitrate
NC -- intf encaps not CCC/TCC    TM -- TDM misconfiguration
BK -- Backup Connection          ST -- Standby Connection
CB -- rcvd cell-bundle size bad  SP -- Static Pseudowire
LD -- local site signaled down   RS -- remote site standby
RD -- remote site signaled down  XX -- unknown

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 10.0.0.163
    Interface                 Type  St     Time last up          # Up trans
    t1-2/0/1.0(vc 1001)(SP)   rmt   Up     Apr 20 14:06:12 2010           1
      Remote PE: 10.0.0.163, Negotiated control-word: Yes (Non-null)
      Incoming label: 1000003, Outgoing label: 1000004
      Negotiated PW status TLV: No
      Local interface: t1-2/0/1.0, Status: Up, Encapsulation: SATOP-T1


Meaning

The display shows that the Layer 2 circuit connection to neighbor 10.0.0.163 is up.

Related Documentation

Modified: 2015-11-17