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:
This example uses the following software and hardware components:
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).
Figure 1 shows the topology for this example.
Figure 1: Network Topology for a T1 SAToP Circuit between a CE PIC and a CTP Device
Table 1 shows the configuration of the SAToP bundle on the CTP device and the configuration of the M Series router.
Table 1: 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 |
In this example, the CTP device is configured using CTP Menu.
To configure the CTP device and the router, perform these tasks:
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:
You are notified that changing this parameter requires a system reboot.
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]:
To create a SAToP bundle:
The CTP device creates a new SAToP bundle.
To configure the port settings:
========================================================================== = (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]:
To configure the bundle settings:
========================================================================== = (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
To quickly configure the controller interface, copy the following commands and paste them into the router terminal window:
To configure a controller interface:
Display the results of the configuration.
To quickly configure SAToP Emulation on the T1 interface, copy the following commands and paste them into the router terminal window:
To configure the T1 interface:
Display the results of the configuration.
To quickly enable MPLS on the T1 interface, copy the following commands and paste them into the router terminal window:
To enable MPLS on the T1 interface:
Display the results of the configuration.
To quickly configure the Layer 2 circuit, copy the following commands and paste them into the router terminal window:
To configure a static Layer 2 circuit:
Display the results of the configuration.
To quickly configure the GRE tunnel, copy the following commands and paste them into the router terminal window:
To configure a GRE tunnel:
Display the results of the configuration.
To activate the SAToP bundle
To confirm that the configuration is working properly, perform these tasks:
Verify that the circuit is running.
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)
The display shows that the SAToP bundle is in the RUNNING state.
Verify that the circuit is running.
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
The display shows that the SAToP bundle is in the ACTIVE state and that the run state is RUNNING.
Verify that the GRE route has been added to the inet.3 routing table.
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
The display shows that
Verifying that the Layer 2 circuit connections are running on the router.
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
The display shows that the Layer 2 circuit connection to neighbor 10.0.0.163 is up.