Unit 1

Basic Circuit Aggregation Configuration

Basic Circuit Aggregation Rev 3.2 Page 1- 1

Configuration
 Basic Circuit Aggregation Unit
Objectives
• Describe basic CT3 components
• Configure a CT3 or CE1/CT1 controller
• Describe basic CE1 components
• Configure a serial interface on a CT3/CE1/CT1 controller
using PPP and IP
• Compare and contrast POS and ATM
• Configure a POS interface
• Describe basic IP routing concepts
• Configure static IP routes
• Use show commands to verify network operation
• Describe ERX logging capabilities
• Configure pppPacket logging on the ERX

Basic Circuit Aggregation Rev 3.2 Page 1- 2

Configuration
 ISP1’s Current Network…

EDGE LAN EDGE WAN CORE EDGE WAN EDGE LAN

IP IP
75xx
PPP 75xx FR/PPP
T1/FT1/T3
C I S C O SY S TE M S

E1/E3
C I S C O SY S T E M S

OC3, DS3
100’s of
100’s of Customers
Customers POS

IP FR
T1/FT1/T3 9000
ATM
75xx 75xx
C I S C O SY S T E M S

C I S C O SY S T E M S

IP
FR/PPP
E1/E3

100’s of
100’s of Customers
Customers

Our ISP’s current network looks something like this:

Customer’s access rates vary from 56 kbps to T1 using a combination of PPP and Frame
Relay.
This ISP uses a combination of Cisco 75xx;s for dedicated, high speed links, and uses
9000’s to aggregate slower speed links onto higher speed links which then are fed into the
75xx’s.
This network design has worked fairly well from the mid-1990’s until today.

Basic Circuit Aggregation Rev 3.2 Page 1- 3

Configuration
 Life is Full of Choices...

EDGE LAN EDGE WAN CORE EDGE WAN EDGE LAN

75xx IP
C I S C O SY S T E M S

IP 75xx
PPP FR/PPP
E1/E3
C I S C O SY S T E M S

T1/FT1/T3
C I S C O SY S T E M S

C I S C O SY S T E M S

OC3, DS3 C I S C O SY S T E M S

1000’s of 1000’sof
C I S C O SY S T E M S

C I S C O SY S T E M S

Customers Customers
POS
C I S C O SY S T E M S

75xx
C I S C O SY S T E M S

IP FR 9000
T1/FT1/T3
C I S C O SY S T E M S
ATM
C I S C O SY S T E M S

75xx
IP
C I S C O SY S T E M S

C I S C O SY S T E M S

FR/PPP
C I S C O SY S T E M S
C I S C O SY S T E M S

E1/E3
C I S C O SY S T E M S

1000’s of 1000’s of
Customers Customers

But now our ISP is experiencing tremendous growth and expansion. Instead of
supporting hundreds of customers at each location, the ISP is planning on supporting
thousands of customers! And these customers are demanding faster access speeds and
guaranteed throughput.
Life is full of choices!
Our ISP could continue on building his network using yesterday’s equipment….

Basic Circuit Aggregation Rev 3.2 Page 1- 4

Configuration
 Circuit Aggregation… Using the ERX

EDGE LAN EDGE WAN CORE EDGE WAN EDGE LAN

IP IP
75xx
PPP 75xx FR/PPP
T1/FT1/T3
C I S C O SY S T E M S

E1/E3
C I S C O SY S T E M S

OC3, DS3
1000’s of
1000’s of Customers
U

Customers POS U

ERX
IP FR
T1/FT1/T3 9000
ATM
75xx ERX
C I S C O SY S T E M S

75xx IP
C I S C O SY S T E M S

FR/PPP
U
E1/E3
U

ERX 1000’s of
ERX Customers
1000’s of
Customers

Instead of installing a Cisco 75xx for every 100 customers or a combination of a 7500 and
a 9000, simply install one ERX that will support 1,000’s of customers in one box. In
addition, the ERX will support additional services, such as B-RAS and Quality of Service,
so that the ISP is ready to offer additional services without purchasing additional
equipment!
We will be focusing on Basic Circuit Aggregation in this course.

Basic Circuit Aggregation Rev 3.2 Page 1- 5

Configuration
 A Simple Example...

ERX ERX
U U

IP/PPP IP/PPP
POS
CT3 CE1
4 DS0’s 4 DS0’s

We’ll be configuring the ERX to initially support PPP access links to the customers and
Packet over Sonet (POS) uplinks.

Basic Circuit Aggregation Rev 3.2 Page 1- 6

Configuration
 Start Thinking in Layers!
ERX ERX
U U

IP/PPP
IP/PPP POS
CT3 CE1
4 DS0’s 4 DS0’s

Network
IP IP IP
Layer

Data Link
PPP PPP PPP
Layer

T1 #1
SONET/SDH DS0 1-4
Physical DS0 1-4
Layer

CT3 Port OC3 Port E1 Port

When designing and configuring networks using the ERX, start thinking in layers! We will
focus on what needs to be configured at each layer. Next, we’ll focus on how to
troubleshoot problems, using the same layers.

Basic Circuit Aggregation Rev 3.2 Page 1- 7

Configuration
 IP/PPP/CT3

ERX ERX
U U

192.168.2.1/24
IP/PPP IP/PPP
POS
CT3 4/0 CE1
4 DS0’s 4 DS0’s

Network IP Address
IP
Layer Mask

Encapsulation
Data Link
PPP KeepAlive
Layer
Authentication

T1
T1 #1 Assign Subchannel
Physical DS0 1-4 Timeslots
Layer Speed
Slot/Port
CT3 Port Clocking
Shutdown
Line Build Out

PPP is used on dedicated, point to point links. In this example, we are using PPP on
access links between the customer and the ISP’s network.
We will configure PPP initially over a CT3 or CE1 interface.
The ERX is configured like this diagram, working from the bottom layer up. First configure
the physical layer attributes, then layer on the data link protocol or encapsulation method,
and finally add the IP addressing information.
Note that controllers (T3/T1/E3/E1) are disabled or shutdown by default. It will be
necessary to turn on the controller using a no shutdown command.

Basic Circuit Aggregation Rev 3.2 Page 1- 8

Configuration
 CT3 Review
28 T1 Channels 24 DS0’s or
Timeslots

T1 #1
• DS0

...
- Individual 56 or 64 kbps
timeslots
T1 #2
T3 • DS1/T1
- 24 DS0 circuits or
Slot 4 timeslots
Port 0
T1 #3 • FT1
…. - 1 or more DS0’s bundled
together as one circuit
....

• DS3/T3
T1 #28
- 28 Individual T1’s

Basic Circuit Aggregation Rev 3.2 Page 1- 9

Configuration
 ERX CT3 Configuration Concepts
28 T1 Channels 24 DS0’s or
Timeslots
Subchannel 1
T1 #1 Subchannel 2

...
• Configure CT3 Controller / M13 Mux
T1 #2 - Slot/Port 4/0
- Clocking
Slot 4 - Shutdown
Port 0 - Line Build Out
• Configure FT1 Parameters
T1 #3 - T1 and Subchannel 1/1 1/2
- Timeslots 1-4 5-8
- Speed 64K
64K
….
....

• Configure Serial Interface

- Assigns HDLC Controller
- Specify Combination of
T1 #28 CT3 Slot/Port:T1/Subchannel
- 4/0:1/1
• 128 HDLC Controllers per port

Basic Circuit Aggregation Rev 3.2 Page 1- 10

Configuration
 ERX Configuration Tree
Config

Controller Interface Router IP Log

T1 FastEthernet RIP Static Routes Destination

E1 ATM OSPF

T3 POS BGP

E3 Loopback ISIS

Sonet Serial

gigabitEthernet • Novice Users

- Traverse the Tree
• exit takes you back a level
- The ‘?’ is your friend!
• Experienced Users
- No need to traverse the tree

The ERX Configuration Tree at 30,000 feet. Not all branches are listed at this point in
time.
Remember to use the ‘?’ at any level in the tree or use the tab key to complete
commands.
Traverse the tree using the exit command to go back a level.
To exit global configuration mode, use control Z or the end command.
Once one is familiar with the configuration tree, there is no need to traverse the
configuration tree. Top level configuration branches, such as the interface branch or the
router branch, can be accessed anywhere within configuration mode. However, tab
replacement or the ‘?’ only works within a branch of a tree or ‘context’.

Basic Circuit Aggregation Rev 3.2 Page 1- 11

Configuration
 ERX CT3 Configuration
Config

Controller

E1 T1 E3 T3

Interface Interface
Slot/Port Slot/Port
4/0 4/1

Clocking Clocking
Shutdown Shutdown
Framing Framing
Cable length Cable length
Loopback Loopback
T1 T1

Bert Bert
Loopback Loopback
Remote Loopback Remote Loopback
Shutdown Shutdown

Channel/Subchannel Channel/Subchannel Channel/Subchannel Channel/Subchannel

1/1 1/2 1/1 1/2

Timeslot 1-4 Timeslot 5-8 Timeslot 1-12 Timeslot 13-24

Speed 64K Speed 64K Speed 56K Speed 56K
Shutdown Shutdown Shutdown Shutdown

RX-0-9-D0(config)#controller ?
RX-0-9-D0(config-controll)#t1 ?
e1 Configure a channelized E1 controller
<1 - 28> The T1 channel number
e3 Configure a E3 controller
CHANNEL/SUBCHANNEL The FT1 interface
sonet Configure a Sonet controller
t1 Configure a channelized T1 controller
RX-0-9-D0(config-controll)#t1 1 ?
t3 Configure a T3 controller
bert Initiate sending of BERT test patterns
clock Configure the DS1 transmit clock source
RX-0-9-D0(config)#controller t3 ?
framing Configure DS1 line framing
INTERFACE The T3 interface identifier
lineCoding Configure DS1 line coding
loopback Configure DS1 loopback
RX-0-9-D0(config)#controller t3 4/0
remote-loopback Enable remote ability to configure interface loopback
RX-0-9-D0(config-controll)#?
shutdown Disable the interface
cablelength Configure the cable length
snmp Configure SNMP parameters
clock Configure the transmit clock source
exit Exit from the current command mode
RX-0-9-D0(config-controll)#t1 1/1 ?
framing Configure DS3 line framing
shutdown Disable the interface
help Describe the interactive help system
snmp Configure SNMP parameters
loopback Configure loopback
timeslots Specify time slot configuration
no Negate a command or restore its default(s)
shutdown Disable a interface
RX-0-9-D0(config-controll)#t1 1/1 timeslot 1-4 ?
sleep Make the Command Interface pause for a
speed Specify DS0 mode
snmp Configure SNMP parameters
<cr>
support Enter Support mode
t1 Configure T1 parameters
RX-0-9-D0(config-controll)#t1 1/1 timeslot 1-4 speed 64 ?
<cr>
RX-0-9-D0(config-controll)#no shutdown
RX-0-9-D0(config-controll)#clock source internal chassis
RX-0-9-D0(config-controll)#t1 1/1 timeslot 1-4 speed 64
RX-0-9-D0(config-controll)#exit
RX-0-9-D0(config)#

Basic Circuit Aggregation Rev 3.2 Page 1- 12

Configuration
 ERX Serial Interface / PPP / IP Configuration

Config

Interface

FastEthernet ATM Loopback Serial POS

Interface Interface
Slot/Port:Channel/Subchannel Slot/Port:Channel/Subchannel
4/0:1/1 4/0:1/2

Encapsulation Encapsulation

PPP PPP
PPP PPP

Authentication Authentication
Keep Alive Keep Alive
Shutdown Shutdown
IP IP

Address Address
Shutdown Shutdown
Unnumbered Unnumbered

RX-0-9-D0(config-controll)#t1 1/1 timeslot 1-4 speed 64 peer Identify the location of a virtual interface peer
RX-0-9-D0(config-controll)#exit
ppp Configure PPP parameters
RX-0-9-D0(config)#interface ?
FastEthernet IEEE 802.3 FastEthernet interface pppoe Configure pppoe parameters
atm ATM interface sleep Make the Command Interface pause for a specified
loopback Loopback interface duration
pos Packet over SONET interface
support Enter Support mode
serial serial interface
template Specify a template
RX-0-9-D0(config)#interface serial ?
INTERFACE The interface specifier to configure RX-0-9-D0(config-if)#encap ppp
RX-0-9-D0(config)#interface serial 4/0:1/1 RX-0-9-D0(config-if)#ppp ?
RX-0-9-D0(config-if)#? authentication Set authentication type for an interface
atm Configure ATM parameters keepalive Set the PPP keepalive interval
crc Configure CRC
max-bad-auth Maximum number of authentication retries
encapsulation Configure interface encapsulation
exit Exit from the current command mode peer Configure the peer to take precedence
frame-relay Configure frame relay parameters shutdown Change PPP interface administrative state
help Describe the interactive help system
invert Configure data inversion
ip Configure IP characteristics RX-0-9-D0(config-if)#ip address 192.168.2.1 255.255.255.0
isis Configure IS-IS RX-0-9-D0(config-if)#
mru Configure Maximum Receive Unit
mtu Configure Maximum Transmission Unit
no Negate a command or restore its default(s)
...

Basic Circuit Aggregation Rev 3.2 Page 1- 13

Configuration
 IP/PPP/CE1
ERX ERX
U U

192.168.2.1/24
IP/PPP
IP/PPP POS
FT1 4/0 CE1
4 DS0’s 4 DS0’s

Network IP Address
IP
Layer Mask

Encapsulation
Data Link
PPP KeepAlive
Layer
Authentication

Create Channel Group

DS0 1-4 Timeslots
Physical
Speed
Layer

E1 Port Slot/Port
Clocking
Shutdown

PPP is used on dedicated, point to point links. In this example, we are using PPP on
access links between the customer and the ISP’s network.
We will also configure PPP over a CE1 interface.
The ERX is configured like this diagram, working from the bottom layer up. First configure
the physical layer attributes, then layer on the data link protocol or encapsulation method,
and finally add the IP addressing information.

Basic Circuit Aggregation Rev 3.2 Page 1- 14

Configuration
 ERX CE1 Configuration
31 DS0’s or
Timeslots
20 E1 Ports
Channel Group 1
E1 Port 0 Channel Group 2

...
Channel Group 1
E1 Port 1 Channel Group 2
• Configure CE1 Controller

...
- Slot/Port 3/0
Slot 3 - Clocking
E1 Port 2 - Shutdown
• Configure CE1 Channel Parameters
- Channel Group (1-31) 1
2
…
....

- Timeslots 1-4 5-8

- Speed 64K 64K
• Configure Serial Interface
E1 Port 19 - Assigns HDLC Controller
- Specify Combination of
E1 Slot/ Port : Channel Group
3/0:1, 3/0:2, 3/1:1, 3/1:2

As of System Release 1.3.1, the CE1 line module supports clear channel or unframed
mode. To configure clear channel, specify unframed at the CE1 controller level. All DS0’s
or timeslots are automatically assigned to channel group 1.

Basic Circuit Aggregation Rev 3.2 Page 1- 15

Configuration
 ERX CE1 Configuration
Config

Controller

T3 T1 E3 E1

Interface Interface
Slot/Port Slot/Port
3/0 3/1

Clocking Clocking
Shutdown Shutdown
Framing Framing
Line Coding Line Coding
Shutdown Shutdown
Loopback Loopback
Channel Group (1-31) Channel Group (1-31)

Channel Group 1 Channel Group 2 Channel Group 3 Channel Group 1 Channel Group 2

Timeslot 1-4 Timeslot 5-8 Timeslot 9-12 Timeslot 1-12 Timeslot 13-31
Shutdown Shutdown Shutdown Shutdown Shutdown

RX-0-4-B0(config)#controller e1 13/0
RX-0-4-B0(config-controll)#?
channel-group Configure fractional channel group
clock Configure the transmit clock source exit
Exit from the current command mode
framing Configure E1 line framing
help Describe the interactive help system
lineCoding Configure E1 line coding
loopback Configure interface loopback
no Negate a command or restore its default(s)
shutDown Disable a interface
…
RX-0-4-B0(config-controll)#no shutdown
RX-0-4-B0(config-controll)#channel-group ?
<1 - 31> The fractional interface
RX-0-4-B0(config-controll)#channel-group 1 ?
shutDown Disable the interface
snmp Configure SNMP parameters
timeslots Specify time slot configuration
RX-0-4-B0(config-controll)#channel-group 1 timeslot ?
RANGE The DS0 time slot(s) allocation (1-31)
RX-0-4-B0(config-controll)#channel-group 1 timeslot 1-12 ?
speed Specify DS0 mode <cr>
RX-0-4-B0(config-controll)#channel-group 1 timeslot 1-12 speed ?
56 Specify Nx56 mode
64 Specify Nx64 mode
RX-0-4-B0(config-controll)#channel-group 1 timeslot 1-12 speed 64

Basic Circuit Aggregation Rev 3.2 Page 1- 16

Configuration
 ERX Serial Interface / PPP / IP Configuration
Config

Interface

FastEthernet ATM Loopback Serial POS

Interface Interface
Slot/Port:Channel Group Slot/Port:Channel Group
3/0:1 3/0:2

Encapsulation Encapsulation

PPP PPP
PPP PPP

Authentication Authentication
Keep Alive Keep Alive
Shutdown Shutdown
IP IP

Address Address
Shutdown Shutdown
Unnumbered Unnumbered

RX-0-4-B0(config)#interface serial ?
INTERFACE The interface specifier to configure
RX-0-4-B0(config)#interface serial 3/0:1
RX-0-4-B0(config-if)#encapsulation ppp
RX-0-4-B0(config-if)#ip address 192.168.8.1 255.255.255.0
RX-0-4-B0(config-if)#exit
RX-0-4-B0:vr2#show interface serial 3/0:1
Serial Interface at 3/0:1
ifOperStatus = ifOperUp
snmp trap link-status = disabled
Crc type checking - CRC16
Hdlc mru = 1600
Hdlc mtu = 1600
Hdlc interface speed = 768000
Invert data disabled,
Ds0 time slot map = 0xfff
Ds0 mode = Nx64
Interface statistics
Packets received 7
Bytes received 106
Errored packets received 0
Packets sent 7
Bytes send 88
Errored packets sent 0

Basic Circuit Aggregation Rev 3.2 Page 1- 17

Configuration
 PPP Multilink Protocol

U 192.168.2.0
.1 .2
T1 1
T1 2
T1 3

•Require More Bandwidth than T1 but not T3

•An Alternative to ECMP
•Up to 8 T1 links in a bundle

Some users need more bandwidth than a T1 or E1 can provide, however, the bandwidth
difference and the expense of a full T3 is cost prohibitive. Generally the aggregation of up
to eight (8) T1 links is the particle limit within a bundle as opposed to the cost of a full T3.
The goal of multilink is to coordinate multiple independent links between two systems
thereby providing a virtual link that is greater than the contributing links. The aggregate
link is known as a bundle and is given a name during configuration.
Within the ERX a maximum of eight (8) T1 links can be aggregated in a bundle. With a T3
port on a CT3 line module there is no limit to the number of PPP multilink bundles you
could have. In other words twenty eight (28) bundles could be present.
PPP multilink is supported on the CT3, CT1, and CE1 line cards. Currently, bundles must
be fully contained within one line module.

Basic Circuit Aggregation Rev 3.2 Page 1- 18

Configuration
 PPP Multilink Configuration

IP

MLPPP

PPP PPP PPP

HDLC HDLC HDLC

ERX5(config)#int serial 4/0:3/1

ERX5(config-if)#encap mlppp
ERX5(config-if)#exit
ERX5(config)#int serial 4/0:4/1
ERX5(config-if)#encap mlppp
ERX5(config-if)#exit
ERX5(config)#interface mlppp group1
ERX5(config-if)#member-interface serial 4/0:3/1
ERX5(config-if)#member-interface serial 4/0:4/1
ERX5(config-if)#ip address 192.168.3.1 255.255.255.0
ERX5(config-if)#end

ERX5#show ppp interface mlppp group1

PPP interface mlppp group1 is up
1 mlppp interfaces found

ERX5#show ppp interface mlppp members

PPP interface mlppp group1 is up
PPP multilink member-interface serial 4/0:3/1 is up
PPP multilink member-interface serial 4/0:4/1 is up

Basic Circuit Aggregation Rev 3.2 Page 1- 19

Configuration
 ERX Packet Over SONET/SDH (POS)

ERX ERX
U U

IP/PPP
IP/PPP POS
CT3 CE1
4 DS0’s 4 DS0’s

• Needed: Single, high

Network
IP
speed connection
Layer
• Choices:
- ATM
Data Link
Layer
PPP • High Overhead
• Complex
- POS
SONET/SDH
Physical • Low Overhead
Layer
• Easy
OC3 Port • PPP over SONET/SDH

Our ISP needs a single, high speed connection between two ERXs or other network node.
We usually think of ATM for high speed connections. ATM is an option and meets a
specific need as we will see later in the course. But there is another option: POS.
Why not use ATM?
•High Overhead (5 bytes of every 48 byte ATM cell go to overhead. Therefore, 60 Mbit/s
of bandwidth is spent on overhead for every OC12 (622 Mbit/s) installed.
•Complex.
•Challenging to design, implement and manage.
So use SONET, but skip the ATM part!
POS leaves LAN traffic in its native format. In simple terms, POS is simply a serial link
like any other point to point link, only much more reliable and a whole lot faster!
Makes better use of SONET’s capacity since there is no ATM overhead.
POS is simply PPP over Sonet/SDH.
Sonet is typically used in North America where as SDH is used elsewhere in the world.
The basic Sonet Transmission unit is 51.84 Mbps and is referred to as an STS1 or an OC.
We typically start using Sonet rates of OC3-c or 155 Mbps. SDH starts at speeds of 155
Mbps which is referred to as STM-1.

Basic Circuit Aggregation Rev 3.2 Page 1- 20

Configuration
 ERX POS Configuration

ERX ERX
U
192.168.18.0/24 U

.1 .2 IP/PPP
IP/PPP
POS
FT1 Slot 2 CE1
4 DS0’s Port 0 4 DS0’s

Network IP Address
IP
Layer Mask

Encapsulation
Data Link KeepAlive PPP
Layer
Authentication

Framing
Payload Scrambling SONET/SDH
Physical
Layer
Slot/Port
OC3 Port

Basic Circuit Aggregation Rev 3.2 Page 1- 21

Configuration
 ERX OC3 / POS / PPP / IP Configuration
Config

Interface

FastEthernet ATM Loopback Serial POS

Interface Interface
Slot/Port Slot/Port
2/0 2/1

Encapsulation Encapsulation

PPP PPP
PPP PPP

Authentication Authentication
Keep Alive Keep Alive
Shutdown Shutdown
POS POS

Framing Framing
SONET/SDH SONET/SDH
Scramble-atm Scramble-atm
IP IP

Address Address
Shutdown Shutdown
Unnumbered Unnumbered

RX-0-9-D0(config-if)#exit RX-0-9-D0(config-if)#pos ?
RX-0-9-D0(config)#int ? framing Configure framing for Packet Over SONET
FastEthernet IEEE 802.3 FastEthernet interface scramble-atm Specify SONET payload scrambling
atm ATM interface
loopback Loopback interface RX-0-9-D0(config-if)#pos framing ?
pos Packet over SONET interface sdh Specify SDH framing
serial serial interface sonet Specify SONET framing
RX-0-9-D0(config)#int pos ? RX-0-9-D0(config-if)#encap ppp
INTERFACE The interface specifier to configure RX-0-9-D0(config-if)#ip address 192.168.18.1 255.255.255.0
RX-0-9-D0(config)#int pos 2/0 ? RX-0-9-D0(config-if)#exit
<cr> RX-0-9-D0(config)#exit
RX-0-9-D0(config)#int pos 2/0 SHOW CONFIG:
RX-0-9-D0(config-if)#? interface pos 2/0
atm Configure ATM parameters pos framing sonet
clock Specify Packet Over SONET transmit clock source clock source line
crc Configure CRC crc 16
encapsulation Configure interface encapsulation mtu 4470
exit Exit from the current command mode mru 4470
frame-relay Configure frame relay parameters !
help Describe the interactive help system interface pos 2/0
invert Configure data inversion encapsulation ppp
ip Configure IP characteristics !
isis Configure IS-IS ppp max-bad-auth 0
loopback Configure loopback on an ATM interface !
mru Configure Maximum Receive Unit ppp keepalive 30
... !
ip address 192.168.18.1 255.255.255.0

Basic Circuit Aggregation Rev 3.2 Page 1- 22

Configuration
 ERX Management

ERX ERX
U U

IP/PPP IP/PPP
POS
CT3 CE1
4 DS0’s Loopback
4 DS0’s
192.168.0.1
Fast Ethernet
10.3.202.1

• SNMP

Up to 8 SNMP trap receivers can be configured on the ERX. We will see later that SNMP
is configured per virtual router.

Basic Circuit Aggregation Rev 3.2 Page 1- 23

Configuration
 ERX Bulkstatistics

ERX ERX
U U

IP/PPP IP/PPP
POS
CT3 CE1
4 DS0’s Loopback
4 DS0’s
192.168.0.1
Fast Ethernet
10.3.202.1

• Bulkstatisitics

Since SNMP is not well suited for gathering large volumes of data over short time intervals,
the ERX can take advantage of a feature called bulk statistics. Bulk statistics is based on
RFCs 2512 and 2513. It is a method of collecting statistical information for a group of
interfaces in a file on the ERX and then transferring this single file using FTP to a
management station at regular time intervals. The bulk statistics feature avoids the overhead
associated with SNMP data retrieval for each and every interface. The bulk statistics can be
automatically transferred to a management station configured as a bulk statistics receiver or it
can manually transferred. A time interval is specified for automatic transfer as well as a
primary and secondary management station or bulk statistics receiver. The secondary
receiver is only used if the primary receiver is not available. Bulk statistics can be configured
for the following interfaces: PPP, Frame Relay, and ATM. The interface configuration is all or
nothing, meaning all PPP interfaces on the ERX will participate in the bulk statistics collection
or no PPP interfaces will participate in bulk statistics. Here is an example of the contents of a
bulk statistics file:
System Name: ERX1
Description: bulkstatistics
Start Time: WED JAN 12 2000 11:35:36 UTC
Schema: ifDescr {slot/ifIndex} : {ifInOctets; ifInUcastPkts; ifInDiscards; ifInErrors; ifInUnknownProtos,
ifOutOctets; ifOutUcastPkts; ifOutDiscards; ifOutErrors}
FrameRelaySub xface{4/268435521} : { 57987294; 432741; 0; 0; 0; 56256460; 432742; 0;
0}
Redstone Atm xface{2/150994945} : {22275440; 163790; 0; 0; 0; 2934240; 163816; 0; 0}
Redstone Atm1483 xface{2/184549377} : { 22371320; 164495; 0; 0; 0; 23032940; 164521;
0; 0}

Basic Circuit Aggregation Rev 3.2 Page 1- 24

Configuration
 IP Routing Basics

ISP A Static
Static U

Routes
U

Routes
IGP

• Routing Tables
• Static Routes EGP U

• Routing Protocols ISP B

• Autonomous System
• Interior Gateway Protocol
(IGP)
- RIP
- OSPF
- ISIS
• Exterior Gateway Protocols
(EGP)
- BGP4

Routers use routing tables to determine which way to send IP packets through the
network. Routing tables only indicate the next hop to take to get to a destination network.
They do not indicate the entire path an IP datagram will use.
There are two ways entries can be included in an IP routing table: Statically and
dynamically.
Static entries or static routes are configured or hardcoded by the administrator of the
router. Static routes never change. They are useful when there is only one possible route
or path to take to get to a destination network. In our example network, ISP A may
configure static routes for their customers that have only one connection into their
network.
Routes can also be added dynamically to the routing table by using a routing protocol.
Routers use routing protocols to advertise their available routes to other routers. Routers
will then use this information to choose the best path to take to get to a destination
network. Routing protocols are useful when multiple paths exists to get to a destination
network. If one path goes away, they can learn about an alternate route automatically via
the routing protocol.
An Autonomous System is a group of routers that is administered by a single organization.
In this example, there are 2 autonomous systems: ISPA and ISPB.
There are 2 different kinds of routing protocols. Interior gateway protocols or IGPs are
used to advertise detailed information within an Autonomous System. Examples include
the Routing Information Protocol (RIP), Open Shortest Path First (OSPF) and Intermediate
System to Intermediate System (ISIS). We will be discussing each of these protocols
during this course. Exterior Gateway Protocols (EGPs) are used to exchange routing
information between Autonomous Systems. The Border Gateway Protocol Version 4
(BGP4) is an example of an EGP.

Basic Circuit Aggregation Rev 3.2 Page 1- 25

Configuration
 Routing Tables
ISP A
Customer X
192.168.16.0
RIP Router A 192.168.32.0

.1 192.168.1.0 .2 192.168.5.0
U
U

192.168.4.0
.1 .2
.2 .1
19 .0
.3
2.1 68 .2
.1 68
.2 2 .1
.0 U
19
Router A’s Routing Table
.2
• Directly Connected Networks .1
Destination Next Hop Metric Protocol
192.168.1.0 192.168.1.2 1 Connected
• Static Routing 192.168.3.0 192.168.3.2 1 Connected
- Use when no alternate routes 192.168.5.0 192.168.5.1 1 Connected
192.168.32.0 192.168.5.1 2 Static
exist 192.168.2.0 192.168.3.1 2 RIP
- Customers with a single 192.168.4.0 192.168.1.1 2 RIP
192.168.16.0 192.168.1.1 3 RIP
connection 192.168.48.0 192.168.48.0 192.168.3.1 2 RIP
• Dynamic Routing
- Use when redundant links exist
• RIP
- Updates sent every 30 seconds
- Best route = shortest hop count

Routing tables are built dynamically when the router boots. Initially, the router will install
routes for directly connected interfaces and static routes. If the router is running a
dynamic routing protocol, it will begin advertising networks to other routers.
In our example, Router A has configured a specific static route for the customer located off
the 192.168.5.0 interface.
In this example, ISPA is using the routing protocol RIP. Every 30 seconds, the router will
advertise the contents of its routing table, whether or not anything has changed. The
router is also receiving RIP advertisements from other routers. If a router learns about the
same route from multiple routers, it must pick one to use and install in its IP routing table.
Using RIP, the router will always choose the route with the shortest or lowest hop count.
This hop count is shown in the routing table as a metric.

Basic Circuit Aggregation Rev 3.2 Page 1- 26

Configuration
 Default Routes
ISP A
Customer X
192.168.16.0
RIP Router A 192.168.32.0

.1 192.168.1.0 .2 192.168.5.0
U
U

192.168.4.0
.1 .2
.2 .1
19 .0
.3
2.1 68 .2
.1 68
.2 2 .1
.0 U
19

• Customer has a single .2 .1

connection into the Customer X’s Routing Table

Internet Destination
192.168.5.0
Next Hop Metric
192.168.5.2 1
Protocol
Connected
• No alternate paths exist 192.168.32.0 192.168.32.1 1 Connected
192.168.48.0
0.0.0.0 192.168.5.1 2 Static
• Default route
- 0.0.0.0
- Match anything
- *.*.*.*
- Wildcard route

There is a special route called the Default Route (0.0.0.0). This special static route is
useful when no alternate path exists or for basic Internet connectivity. A default route
always points to a router that knows more detailed routing information.
In this example, Customer X has a single connection into the Internet. If this connection
fails, the customer loses Internet connectivity.
When a router receives an IP packet, it will look in its routing table for a match. If a match
exists, the router will forward the IP packet to the next hop listed in the routing table. If no
match exists, the IP packet will be dropped.
In this example, if a default route is not used, Customer X’s router connected to the
Internet would need a routing table entry for each and every route in the Internet. At this
point in time, Customer X’s router would need to know about 60,000+ routes.
An alternate approach would be to use the default route. In this case, Customer X has
entries for its local networks plus a default route pointing to Router A. When the router
receives an IP packet, it will look in its routing table for a match. If an exact match exists,
the router will forward the IP packet to the next hop listed in the routing table. If no exact
match exists but there is a default route, the IP packet will be forwarded to the next hop
specified by the default route.
The default route is similar to a wildcard route. The default route, 0.0.0.0, is similar to
*.*.*.*, which implies match anything.
Using the default route saves memory and CPU processing power.

Basic Circuit Aggregation Rev 3.2 Page 1- 27

Configuration
 ERX Routing Protocol Configuration

Config

Controller Interface Router IP Log

T1 FastEthernet RIP Static Routes Destination

E1 ATM OSPF

T3 POS BGP

E3 Loopback ISIS

Serial
• Static Routes
• Routing Protocols
- Define Routing Process
- Define Network Range

In our example, Router A has configured a specific static route for the customer located off
the serial interface, 4/0:1/1:
ERX2(config)#ip route ?
A.B.C.D The IP network
ERX2(config)#ip route 192.168.32.0 ?
A.B.C.D The IP network mask
ERX2(config)#ip route 192.168.5.0 255.255.255.0 ?
A.B.C.D The next hop IP address
FastEthernet IEEE 802.3 FastEthernet interface
atm ATM interface
loopback Loopback interface
null Null interface
pos Packet over SONET interface
serial serial interface
ERX2(config)#ip route 192.168.1.0 255.255.255.0 serial 4/0:1/1

Basic Circuit Aggregation Rev 3.2 Page 1- 28

Configuration
 LOOPBACK and BERT TESTING

U
Data pattern U

Data pattern

ERX6(config-controll)#t1 1 loopback remote line fdl ansi

ERX6(config-controll)#t1 1 bert pattern 1s interval 1

ERX6#show controller t3 4/0:1 ERX5(config-controll)#t1 1 remote-loopback

One can perform remote loopback and BERT testing on a T1. There are two primary
methods to accomplish this. One method is to enable one end to be commanded by the
other router to loop traffic sent to it. This is accomplished by the
remote-loopback command which enables this router to be invoked by the loopback
remote command. This is followed by injecting a BERT test pattern for examination
purposes.
The below show controller command examples show the output of these during a remote
BERT testing scenario.
ERX5#show cont t3 4/0:1 (on the remote looped router)
DS1 4/0:1
ifOperStatus = ifOperTesting
ERX6#show controllers t3 4/0:1 (on the router performing the BERT test)
S1 4/0:1
ifOperStatus = ifOperUp
snmp trap link-status = disabled
Framing is Esf, Line Code is B8ZS,
Clock Source is Line
Allocated Ds0 time slot map = 0xffffff
Loopback Disabled
Last Remote Loopback Request Sent - LineActivate
BERT test - All ones
Test Interval 10 minute(s), Running - Status is Sync
8 minute(s), 0 second(s) left in test interval
Sync count =1
Received bit count = 183792474
Error bit count =0

Basic Circuit Aggregation Rev 3.2 Page 1- 29

Configuration
 LOOPBACK and BERT TESTING (Cont)

U
Data pattern

Data pattern

ERX5(config-controll)#t1 1 loopback network line

ERX6#(config-controll)#t1 1 bert pattern 1s interval 1

ERX6#show controller t3 4/0:1

The other method is for the looped router end to perform the loopback network
command to loop the data. This process is perhaps more relevant for testing with a
remote customer’s router. This is followed by the other router (ERX) injecting the BERT
test pattern. The following are example displays from each router with the show
controller command.
ERX5#show controllers t3 4/0:1 (Command from looped router)
DS1 4/0:1
ifOperStatus = ifOperUp
snmp trap link-status = disabled
Framing is Esf, Line Code is B8ZS, Clock Source is Line
Allocated Ds0 time slot map = 0xffffff
Loopback Enabled - Line
ERX6#show controllers t3 4/0:1 (Command from router performing BERT test)
DS1 4/0:1
ifOperStatus = ifOperUp
snmp trap link-status = disabled
Framing is Esf, Line Code is B8ZS, Clock Source is Line
Allocated Ds0 time slot map = 0xffffff
Loopback Disabled
Last Remote Loopback Request Sent - LineActivate

BERT test - All ones

Test Interval 10 minute(s), Running - Status is Sync
8 minute(s), 0 second(s) left in test interval
Sync count = 1
Received bit count = 183792474
Error bit count = 0

Basic Circuit Aggregation Rev 3.2 Page 1- 30

Configuration
 How can I tell if it is working?
Think Layers!
Network
• ping, traceroute
• show ip int brief IP IP
• show ip int brief | include 192.168.2.1
• show ip int serial 4/0:1/1
• show ip int pos 2/0
PPP PPP
• show ip route
• show ip route | include 10.1.0.0
Data Link
•show ppp interface
T1 #1
•show ppp interface state up DS0 1-4
Sonet/SDH
•show ppp int statistics serial 4/0:1/1
•show ppp int status
Physical
•show controller t3 4/0 CT3 Port OC3 Port
•show controller t3 serial
•show interface serial 4/0:1/1
•show interface pos 2/0
•baseline interface pos 2/0
•show int pos 2/0 delta

Basic Circuit Aggregation Rev 3.2 Page 1- 31

Configuration
 ERX Logging Overview

• ERX logging must be explicitly configured

• ERX Log Messages
- Categories
• Examples include snmp, telnet, ipInterface, pppPacket,
ospfPktsSent/Rcvd, bgpConnection
- Filters
• Per interface, connection, router, slot
- Severity
• emergency 0
• alert 1
• critical 2
• error 3
• warning 4
• notice 5
• info 6
• debug 7

It is possible to configure the ERX to provide detailed log messages.

ERX log messages are broken into categories. A few category examples include snmp,
telnet, pppPacket, which is a PPP packet trace capability, ospfPktsSent and
ospfPktsRcvd, and bgpConnections. There are over 80 different categories of log
messages.
Categories can also have filters configured to limit and control the amount of logging
information. For example, some categories can have filters configured that apply to a
specific interface, such as pppPacket or ipInterface. Other categories may have filters
that apply to a specific connection, such a bgpConnections. Some categories do not
support any filters, such as snmp or telnet. By default, category filters are not enabled
and must be explicitly configured.
Within a category, ERX log messages are assigned a severity level from 0-7. The lower
the number, the higher the severity of the message. We will see that the severity level can
be configured to determine the amount and type of log messages sent to the various log
destinations.
Log messages also have 3 different verbosity levels: low, medium, and high, though this
feature has not been widely implemented. Low verbosity level will be sufficient in most
situations.
The logging process resides on the SRP. The logging facility, specifically debug logging, is
a very powerful troubleshooting tool. However, it does use CPU and memory on the SRP.
Debug logging should be used sparingly, and only for the duration of a test or while trying
to capture data in a particular scenario. Setting all logs to DEBUG should only be done at
the instruction of customer support and only on specified categories for a specified
duration.

Basic Circuit Aggregation Rev 3.2 Page 1- 32

Configuration
 Where do the log messages go?
Volatile Memory
DEBUG pppPacket (interface serial 4/0:1/1):,
tx lcp echoResp
DEBUG pppPacket (interface serial 4/0:1/1):
• Volatile Memory on SRP
U
- Max Size = 750 entries
tx lcp echoReq
DEBUG pppPacket (interface serial 4/0:1/1):,
rx lcp echoResp,

• Flash
Flash
- system.log
1-3-0.rel
system.log - 64 K maximum size
reboot.hty
- Severity Critical or higher
- ASCII file
• ERX Console
- Real-time
• Telnet/SSH Session
- Real-time

Console • Syslog
Telnet Syslog - Multiple Hosts
- Facility (0-7) per Host

ERX log messages can be sent to a variety of locations.

By default, due to the low severity level and low verbosity level, a very limited number of
log messages are stored in volatile memory on the SRP. A sophisticated algorithm is
used by the logging process so that no one category can monopolize the logging process
and starve other categories from inserting log messages into volatile memory. As of
release 3.2 persistent logging has been implemented between system reloads. This
means that log messages in the SRP volatile memory will be retained through a system
reload unless the ERX is power cycled or the system detects any problems.
Log messages will also be stored in non-volatile memory in a file on the flash called
system.log. Only severity levels 0-2 or EMERGENCY, ALERT and CRITICAL log
messages will be stored in system.log. This ASCII file can have a maximum size of
approximately 64K. When the maximum size is reached, the file is circular in nature and
operates in a FIFO manner. The file can be copied to a PC and read by any text editor.
The log messages can also be sent to the console in real-time. The console also has a
severity level associated with it. By default, only messages that have a severity level of
WARNING or higher are sent to the console. These same messages can also be directed
to a Telnet/SSH session. By default, if NOTICE, INFO OR DEBUG log messages occur,
they are not directed to the console. This behavior is configurable.
Finally, ERX log messages can also be directed to syslog. By default, the severity level for
syslog is DEBUG. Multiple syslog hosts can be configured. For each syslog host, it is
possible to configure which facility (0-7) syslog messages are sent.

Basic Circuit Aggregation Rev 3.2 Page 1- 33

Configuration
 Default ERX Logging Configuration
ERX1#show log config
log destination console severity WARNING
log destination nv-file severity CRITICAL
no log engineering
log fields timestamp instance no-calling-task
log here
no log severity

category severity verbosity filters notes

------------------------- -------- --------- ------- -----
NameResolverLog ERROR low
aaaAtm1483Cfg ERROR low
aaaEngineGeneral ERROR low
aaaServerGeneral ERROR low
aaaUserAccess ERROR low
addressServerGeneral ERROR low
atm ERROR low
atm1483 ERROR low
.....
ppp ERROR low
pppPacket --- low
pppStateMachine --- low
pppoe ERROR low
pppoeControlPacket --- low
profileMgr ERROR low
radiusAttributes ERROR low
radiusClient ERROR low

Use the show log configuration CLI command to view the current ERX logging
configuration. This example is the default log configuration and only shows a subset of the
categories.
Notice the three log destinations:
•console - Currently, only log messages that have severity levels 0-4 will be sent to the
console.
•nv-file - This destination refers to the the file system.log found on the flash card. Only
severity levels 0-2 or EMERGENCY, ALERT and CRITICAL log messages will be stored
in system.log. It is not possible to store ERROR, WARNING, NOTICE, INFO or DEBUG
messages in the file system.log.
•syslog - The IP address of the syslog host is configured as well as a severity level of
DEBUG.
By default, all log categories are assigned a severity of ERROR or 3 and a verbosity level
of low. An exception to this rule is the category os which has a severity of NOTICE. In
addition, no interfaces or connections have logging associated with them. One must
explicitly configure ERX logging on specific interfaces or connections.

Basic Circuit Aggregation Rev 3.2 Page 1- 34

Configuration
 Configuring DEBUG Logging
on a PPP Interface
ERX1(config)#log severity debug pppPacket serial 4/0:1/1
ERX1(config)#end
ERX1#show log config
log destination console severity WARNING
log destination nv-file severity CRITICAL
no log engineering
log fields timestamp instance no-calling-task
log here
no log severity

category severity verbosity filters notes

------------------------- -------- --------- ------- -----
NameResolverLog ERROR low
aaaAtm1483Cfg ERROR low
.....
policyMgrPacketLog ERROR low
ppp ERROR low
pppPacket --- low 1
pppStateMachine --- low
pppoe ERROR low
pppoeControlPacket --- low

log severity DEBUG pppPacket serial 4/0:1/1

In this example, we are going to configure the ERX to log PPP packets on a specific PPP interface,
4/0:1/1. We are going to configure the pppPacket category, specify a severity of DEBUG and
specify the PPP interface, 4/0:1/1. All logging configuration is done in global configuration mode.
When a specific interface or connection is specified for logging, the ERX considers it a log filter.
Specific log filters are always listed at the bottom of the log configuration display. As of release 3.2
the Notes column has been added. This column will indicate a note number next to the categories
where the severity has been modified from its default value. The associated note and number will
be displayed at the end of the command just as the filter is.
ERX1(config)#log ?
destination Configure logging destinations
engineering Enable engineering logs
fields Select optional log fields to display
here Enable this terminal as a log console
severity Configure log severities and/or filters
verbosity Configure the verbosity level
ERX1(config)#log severity debug ?
aaaServerGeneral AAA Server General logs
addressServerGeneral Address Server General logs
atm ATM
…….
ppp Point-to-Point Protocol Layer
pppPacket PPP packet capture
pppStateMachine PPP state machine trace
pppoe Point-to-Point Over Ethernet Layer
ERX1(config)#log severity debug pppPacket ?
atm Specify an ATM PPP interface
pos Specify a POS PPP interface
serial Specify a serial PPP interface
<cr>
ERX1(config)#log severity debug pppPacket serial ?
INTERFACE The PPP interface identifier
ERX1(config)#log severity debug pppPacket serial 4/0:1/1

Basic Circuit Aggregation Rev 3.2 Page 1- 35

Configuration
 Viewing the ERX Log
ERX1(config)#cont t3 4/0
ERX1(config-controll)#no shut
ERX1(config-controll)#end
ERX1#show log data category pppPacket severity debug
*** stored log messages ***
*** log: pppPacket
*** severity: DEBUG and higher
*** no baseline

DEBUG 11/26/2001 16:35:48 pppPacket (interface serial 4/0:1/1): time: 5275.20,

tx lcp confReq, id = 226, length = 14, mru = 1596, magicNumber = 0x2af24653

DEBUG 11/26/2001 16:35:48 pppPacket (interface serial 4/0:1/1): time: 5275.20,

rx lcp confReq, id = 16, length = 14, mru = 1596, magicNumber = 0x7a2c5bbe

DEBUG 11/26/2001 16:35:48 pppPacket (interface serial 4/0:1/1): time: 5275.20,

tx lcp confAck, id = 16, length = 14, mru = 1596, magicNumber = 0x7a2c5bbe

DEBUG 11/26/2001 16:35:48 pppPacket (interface serial 4/0:1/1): time: 5275.20,

rx lcp confAck, id = 226, length = 14, mru = 1596, magicNumber = 0x2af24653

DEBUG 11/26/2001 16:35:48 pppPacket (interface serial 4/0:1/1): time: 5275.20,

tx ipNcp confReq, id = 18, length = 10, ipAddress = 192.168.2.1

DEBUG 11/26/2001 16:35:48 pppPacket (interface serial 4/0:1/1): time: 5275.20,

rx ipNcp confReq, id = 69, length = 10, ipAddress = 192.168.2.2

DEBUG 11/26/2001 16:35:48 pppPacket (interface serial 4/0:1/1): time: 5275.20,

tx ipNcp confAck, id = 69, length = 10, ipAddress = 192.168.2.2

DEBUG 11/26/2001 16:35:48 pppPacket (interface serial 4/0:1/1): time: 5275.20,

rx ipNcp confAck, id = 18, length = 10, ipAddress = 192.168.2.1

In this example, the PPP interface is ‘bounced’. By default, these pppPacket log
messages will go to volatile memory as well as syslog. They will not be directed to the
console since the console’s severity level is still set to WARNING and these messages
are DEBUG.
To view the log messages stored in volatile memory, use the show log data command.
There are several options that can be used to view the log data stored in volatile memory,
including severity levels and categories.
erx1#show log data
erx1#show log data ?
category Limit the display to a specific log category
nv-file Display the nv-file log
severity Specify the minimum severity to display
| Filter output using the CLI Filtering feature
<cr>
erx1#show log data category pppPacket ?
severity Specify the minimum severity to display
| Filter output using the CLI Filtering feature
<cr>
erx1#show log data category pppPacket severity ?
<0 - 7> The minimum severity to display
alert immediate action needed (1)
critical critical conditions exist (2)
debug debug messages (7)
emergency system unusable (0)
error error conditions (3)
info informational messages (6)
notice normal but significant conditions (5)
warning warning conditions (4)
erx1#show log data category pppPacket severity debug ?
| Filter output using the CLI Filtering feature
<cr>

Basic Circuit Aggregation Rev 3.2 Page 1- 36

Configuration
 Additional ERX Log Configuration Options
• To view the log file on the flash
- erx1#show log data nv-file
• To view pppPacket DEBUG log messages real-time on the console
- erx1(config)#log destination console severity debug
• To direct log messages to a Telnet/SSH session
- erx1(config)#log here
• To turn off log messages to a Telnet/SSH session
- erx1(config)#no log here
OR
• erx1(config)#log destination console off
OR
- erx1(config)#log destination console severity warning
• To turn off all logging filters:
- erx1(config)#no log filters
• With release 3.2 the baseline log and delta functions are available
erx1(config)#baseline log
erx1(config)#show log data category pppPacket severity debug delta

To view the pppPacket DEBUG log messages in real-time on the console, use the
configuration command log destination console severity debug. DEBUG messages
will only be sent to the console session directly attached to the ERX.
By default, log messages are not directed to Telnet/SSH sessions. Once the console is
configured to support debug messages, use the log here configuration command from the
Telnet/SSH session to direct log messages to the Telnet/SSH session. At this point,
pppPacket trace log messages will be directed to both the Telnet/SSH session as well as
the directly connected console session.
To stop directing log messages to a specific console or Telnet/SSH session, use the no
log here configuration command. In a troubleshooting situation, log messages could be
directed to a Telnet/SSH session using the log here option and the directly attached
console session could be used for other troubleshooting commands using the no log here
option.
To turn off logging to all console sessions, use the log destination console off
configuration command. This command disables logging to both Telnet/SSH and directly
attached console sessions.
To scale down the amount of log messages being sent to the console or Telnet/SSH
session, use the log destination console severity warning configuration command.
As of release 3.2 you can baseline log data using the baseline log command. Use the
optional delta keyword with the show log data command to specify that baselined
messages are to be shown.

Basic Circuit Aggregation Rev 3.2 Page 1- 37

Configuration
 IP/PPP/CHOCx

SONET SDH
IP/PPP ERX ERX
IP/PPP
COCx U U

COCx
POS
IP/PPP IP/PPP
COCx COCx

Network IP Address
• Common SONET
Layer
IP
Mask Configurations
Encapsulation - T1/FT1 over SONET Virtual
Data Link
Layer
PPP KeepAlive
Authentication
Tributaries
- Clear Channel DS3
T1/FT1 Paths, Virtual Tributaries
E1 Clock Source - Channelized DS3
Physical DS1/DS3 Timeslots
Layer Shutdown
• Common SDH Configurations
CHOCx
Controller
Shutdown
Clock Source
- Clear Channel E1 SDH
SDH Tributaries
- FE1 SDH Tributaries

PPP is used on dedicated, point to point links. In this example, we are using PPP on
access links between the customer and the ISP’s network.
In this example, we will be configuring PPP over Channelized OC3 and OC12 interfaces.
We will configure both SONET and SDH flavors.
We will cover the 3 most common SONET configurations:
T1/FT1 over SONET Virtual Tributaries
Clear Channel DS3
Channelized DS3
We will also cover the 2 most common SDH:
Clear Channel E1 SDH Tributaries
FE1 SDH Tributaries
As before, the ERX is configured like this diagram, working from the bottom layer up. First
configure the physical layer attributes, then layer on the data link protocol or encapsulation
method, and finally add the IP addressing information.

Basic Circuit Aggregation Rev 3.2 Page 1- 38

Configuration
 SONET Hierarchy
STS3/OC3 Virtual Tributary Group
Range = 1-7
VTG-1
VTG-2
Path VT2.0-1 (E1)

...
VTG-3
STS1-1 VT2.0-2 (E1)
VTG-4
VT2.0-3 (E1)
VTG-5
Virtual Tributary
STS3 VTG-6 Range = 1-3
Path Channel
(OC3)
Range = 1-3 VTG-7
155 Mbps Virtual Tributary
STS1-2 Range = 1-4
VTG-1
VTG-2 VT1.5-1 (T1)

VTG-3 VT1.5-2 (T1)

...
STS1-3 VTG-4 VT1.5-3 (T1)

VTG-5 VT1.5-4 (T1)

VTG-6
VTG-7

A Sonet OC3 or STS3 supports 3 STS1’s. Each STS1 is referred to as a Path Channel in
the range of 1-3.
Each Path Channel supports 7 Virtual Tributary Groups or VTG’s.
In theory, each VTG supports either 3 Virtual Tributary 2.0’s (E1’s) or 4 Virtual Tributary
1.5’s (T1’s). Both the CHOC3 and CHOC12 line modules do NOT support VT-2.0 AND
VT1.5 tributaries mapped into an STS-3 at the same time. The line modules will support
either VT-2.0 OR VT1.5 tributaries. Thus, this picture is technically inaccurate for the ERX
line modules.

Basic Circuit Aggregation Rev 3.2 Page 1- 39

Configuration
 How do I reference this group of DS0’s
on a CHOC3 SONET Virtual Tributary?
Slot/Port:Path Channel/path payload**/ VTG /VT Number/Channel Group

4 / 0 : 3 * / 1 ** / 4 / 1 / 2

Special Note:
** In SONET, the Path Payload is ALWAYS 1!

Virtual
Slot 4 Tributary Group
VT Number
Port 0 1-7 Channel Group 1
1-4 Timeslot 1-12
VTG-1
STS3 VT1.5-1 (T1)

...
(OC3) Path Channel VTG-2 Channel Group 2
155 Mbps 1- 3 VT1.5-2 (T1) Timeslot 13-24
VTG-3
STS1-3 VT1.5-3 (T1)
VTG-4
VT1.5-4 (T1)
VTG-5
VTG-6
VTG-7

Basic Circuit Aggregation Rev 3.2 Page 1- 40

Configuration
 How do I configure this group of DS0’s
on a CHOC3 SONET VT?
• Configure the controller, specify clock source and SONET mode
- controller sonet 4/0
- clock source internal module
- no sdh
• Specify which path is being used and assign a logical path name or label
- path logical-path oc1 path-channel
- path 3 oc1 3
• Associate the logical path with a specific VTG & VT and specify VT Type
- path logical-path ds1 path-payload/vt-group/vt-number vt-type
- path 3 ds1 1/4/1 vt15
- * Remember that the path-payload in SONET is always 1!
VT Group
Slot 4 1-7 VT Number
Port 0 VTG-1 1-4 Channel Group 1
Timeslot 1-12
STS3 VTG-2 VT1.5-1 (T1)

...
Path Channel
(OC3) 3 VTG-3 VT1.5-2 (T1) Channel Group 2
155 Timeslot 13-24
STS1-3 VTG-4 VT1.5-3 (T1)
Mbps
VTG-5 VT1.5-4 (T1)
VTG-6
VTG-7

erx3:di1(config)#cont sonet 4/0 erx3:di1(config-controll)#path 3 ds1 ?

erx3:di1(config-controll)#no sdh
erx3:di1(config-controll)#clock source int mod
erx3:di1(config-controll)#path ?
<1 - 2147483647> The path logical channel
erx3:di1(config-controll)#path 3 ?
ds1 Configure a ds1 interface
ds3 Configure a ds3 interface
e1 Configure an e1 interface
oc1 The Sonet path speed oc1
oc12 The Sonet path speed oc12
oc3 The Sonet path speed oc3
oc48 The Sonet path speed oc48
erx3:di1(config-controll)#path 3 oc1 3
D/D/D The tributary specification
erx3:di1(config-controll)#path 3 ds1 1/4/1 ?
bert Initiate sending of BERT test patterns
channel-group Configure fractional channel
group, unavailable unframed mode
clock Configure the transmit clock source
framing Configure ds1 line framing,
unavailable in unframed mode
loopback Configure interface loopback
remote-loopback Enable remote ability to
configure interface loopback
shutdown Disable the interface
snmp Configure SNMP parameters
vt15 The Sonet tributary type vt1.5
vt20 The Sonet tributary type vt2.0
erx3:di1(config-controll)#path 3 ds1 1/4/1 vt15 ?
<cr>
erx3:di1(config-controll)#path 3 ds1 1/4/1 vt15

Basic Circuit Aggregation Rev 3.2 Page 1- 41

Configuration
 How do I configure this group of DS0’s
on a CHOC3 SONET VT?
• Configure the clocking for the DS1
- path logical-path ds1 path-payload/vt-group/vt-number clock source
internal/line
- path 3 ds1 1/4/1 clock source internal module
• Assign a channel group number and specify the appropriate timeslots and speed
- path logical-path ds1 path-payload/vt-group/vt-number
channel-group 1-24 timeslots 1-24 speed 64/56
- path 3 ds1 1/4/1 channel-group 1 timeslot 1-12 speed 64
- path 3 ds1 1/4/1 channel-group 2 timeslot 13-24 speed 64
Tributary Group
1-7 Tributary Number
Channel Group 1
VTG-1 1-4 Timeslot 1-12
STS3 VTG-2 VT1.5-1 (T1)

...
Path Channel
(OC3) Channel Group 2
3 VTG-3 VT1.5-2 (T1)
155 Timeslot 13-24
STS1-3 VTG-4 VT1.5-3 (T1)
Mbps
VTG-5 VT1.5-4 (T1)
Slot 4 VTG-6
Port 0
VTG-7

erx3:di1(config-controll)#path 3 ds1 1/4/1 clock ? erx3:di1(config-controll)#path 3 ds1 1/4/1 clock ?

source Specify the clock source source Specify the clock source
erx3:di1(config-controll)#path 3 ds1 1/4/1 clock source ?
internal Specify the internally generated transmit clock
line Specify the line clock source
erx3:di1(config-controll)#path 3 ds1 1/4/1 clock source int ?
chassis Specify the chassis clock source
module Specify the module clock source
erx3:di1(config-controll)#path 3 ds1 1/4/1 clock source int module
erx3:di1(config-controll)#path 3 ds1 1/4/1 channel-group ?
<1 - 24> The fractional interface
erx3:di1(config-controll)#path 3 ds1 1/4/1 channel-group 1 time 1-12
erx3:di1(config-controll)#path 3 ds1 1/4/1 channel-group 2 time 13-24

Basic Circuit Aggregation Rev 3.2 Page 1- 42

Configuration
 Configuring PPP over a CHOC3
SONET VT
• Create the serial interface
interface serial 4/0:3/1/4/1/2
-
• Specify the encapsulation method
- encapsulation ppp
• Configure the IP address, subnet mask and IP description
- ip address 192.168.13.1 255.255.255.0
- description path 3 vtg 4 vt 1 ch 2

Tributary Group
1-7 Tributary Number Channel Group
VTG-1 1-4 1
STS3 VTG-2 VT1.5-1 (T1) Timeslot 1-12

...
Path Channel
(OC3) Channel Group
3 VTG-3 VT1.5-2 (T1) 2
155
STS1-3 VTG-4 VT1.5-3 (T1) Timeslot 13-24
Mbps
VTG-5 VT1.5-4 (T1)
Slot 4 VTG-6
Port 0
VTG-7

erx3:di1(config)#int ser 4/0:3/1/4/1/1

erx3:di1(config-if)#encap ppp
erx3:di1(config-if)#ip address 192.168.12.1 255.255.255.0
erx3:di1(config-if)#desc path 3 vtg 4 vt 1 ch 1
erx3:di1(config)#int ser 4/0:3/1/4/1/2
erx3:di1(config-if)#encap ppp
erx3:di1(config-if)#ip address 192.168.13.1 255.255.255.0
erx3:di1(config-if)#desc path 3 vtg 4 vt 1 ch 2
erx3:di1(config-if)#^Z
erx3:di1#show config inc | beg sonet 4/0
controller sonet 4/0
no sdh
no loopback
clock source internal module
no shutdown
path 3 oc1 3
path 3 ds1 1/4/1 vt15
no path 3 ds1 1/4/1 shutdown
no path 3 ds1 1/4/1 snmp trap link-status
path 3 ds1 1/4/1 framing esf
path 3 ds1 1/4/1 clock source internal module
no path 3 ds1 1/4/1 loopback
path 3 ds1 1/4/1 channel-group 1 timeslots 1-12 speed 64
no path 3 ds1 1/4/1 channel-group 1 shutdown
no path 3 ds1 1/4/1 channel-group 1 snmp trap link-status
path 3 ds1 1/4/1 channel-group 2 timeslots 13-24 speed 64
no path 3 ds1 1/4/1 channel-group 2 shutdown
no path 3 ds1 1/4/1 channel-group 2 snmp trap link-status

Basic Circuit Aggregation Rev 3.2 Page 1- 43

Configuration
 How do I reference this Clear Channel
DS3 on a SONET CHOC3?
Slot/Port:Path Channel/ Path Payload Number**

DS3 = 4 / 0 : 2 / 1

In SONET, the Path Payload is ALWAYS 1!

Path Channel
Slot 4 1-3
Port 0 Tributary Group
STS1-2 1-7
STS3 Tributary Number Channel
VTG-1
(OC3) 1-4 Group
155 Mbps VTG-2 VT1.5-1 (T1) 2

...
Path Channel Timeslot
1-3 VTG-3 VT1.5-2 (T1) 13-24

STS1-3 VTG-4 VT1.5-3 (T1)

VTG-5
VT1.5-4 (T1)
VTG-6
VTG-7

Basic Circuit Aggregation Rev 3.2 Page 1- 44

Configuration
 Clear Channel DS3 Configuration

• Specify which path is being used and assign a logical path name or label
-path logical-path oc1 path-channel
-path 2 oc1 2
• Identify the path-channel and the mode (channelized or unchannelized)
- path path-channel ds3 Path-Payload-Number unchannelized
- path 2 ds3 1 unchannelized
- * Remember that in SONET, the Path-Payload-Number is always 1
• Configure the clock source for the DS3
- path 2 ds3 1 clock source internal module
• Complete the interface configuration:
- interface serial 4/0:2/1
- encapsulation ppp
Path Channel 2
- ip address 192.168.14.1 255.255.255.0
STS1-2
STS3
(OC3)
155 Mbps

Slot 4
Port 0

erx3:di1(config)#cont sonet 4/0

erx3:di1(config-controll)#no sdh
erx3:di1(config-controll)#clock source int mod
erx3:di1(config-controll)#path 2 oc1 2
erx3:di1(config-controll)#path 2 ds3 ?
<1 - 3> The ds3 channel
erx3:di1(config-controll)#path 2 ds3 1 ?
channelized Configure channelized ds3 interface
clock Configure the transmit clock source
framing Configure ds3 line framing
loopback Configure interface loopback
shutdown Disable the interface
snmp Configure SNMP parameters
t1 Configure T1 parameters
unchannelized Configure unchannelized ds3 interface
<cr>
erx3:di1(config-controll)#path 2 ds3 1 unchannelized ?
<cr>
erx3:di1(config-controll)#path 2 ds3 1 unchannelized
erx3:di1(config-controll)#path 2 ds3 1 clock source internal module
erx3:di1(config)#int ser 4/0:2/1
erx3:di1(config-if)#encap ppp
erx3:di1(config-if)#ip address 192.168.14.1 255.255.255.0
erx3:di1(config-if)#desc path 2 unchannelized DS3

Basic Circuit Aggregation Rev 3.2 Page 1- 45

Configuration
 How do I reference this Channelized
DS3 on a SONET CHOC3?
Slot/Port:Path Channel/ Path Payload Number**/Channel/Subchannel

Channelized DS3 = 4 / 0 : 1 / 1 / 2 / 1

In SONET, the Path Payload is ALWAYS 1!

28 T1 Channels

T1 #1

Subchannel 1
T1 #2 Subchannel 2
Slot 4 Path Channel

...
Port 0 1-1
STS1-1 T1 #3
STS3

....
(OC3)

….
155 Mbps

T1 #28

Basic Circuit Aggregation Rev 3.2 Page 1- 46

Configuration
 Channelized DS3 on a SONET CHOC3
• Identify the path-channel and the mode (channelized or unchannelized)
- path path-channel ds3 Path-Payload-Number channelized
- path 1 ds3 1 channelized
- * Remember that in SONET, the Path-Payload-Number is always 1
• Configure the T1 and T1 Subchannels on the channelized DS-3
- path path-channel ds3 path-payload-number t1 channel/subchannel timeslots
- path 1 ds3 1 t1 2
- path 1 ds3 1 t1 2/1 timeslots 1-4
- path 1 ds3 1 t1 2/2 timeslots 5-8
• Complete the interface configuration
- interface serial 4/0:1/1/2/1
T1 #1
- encapsulation ppp
- ip add 192.168.15.1 255.255.255.0
Subchannel 1
T1 #2 Subchannel 2
Slot 4 Path Channel

...
Port 0 1-1
STS1-1 T1 #3
STS3

....
(OC3)

….
155 Mbps

T1 #28

erx3:di1(config-controll)#path 1 ds3 1 ?
erx3:di1(config)#cont sonet 4/0
channelized Configure channelized ds3 interface
erx3:di1(config-controll)#path 1 oc1 1 clock Configure the transmit clock source
erx3:di1(config-controll)#path 1 ds3 ? framing Configure ds3 line framing
<1 - 3> The ds3 channel loopback Configure interface loopback
erx3:di1(config-controll)#path 1 ds3 1 ? shutdown Disable the interface
channelized Configure channelized ds3 snmp Configure SNMP parameters
interface t1 Configure T1 parameters
clock Configure the transmit clock source unchannelized Configure unchannelized ds3 interface
framing Configure ds3 line framing <cr>
loopback Configure interface loopback erx3:di1(config-controll)#path 1 ds3 1 t1 ?
shutdown Disable the interface <1 - 28> The T1 channel number
snmp Configure SNMP parameters CHANNEL/SUBCHANNEL The fractional interface
t1 Configure T1 parameters erx3:di1(config-controll)#path 1 ds3 1 t1 2 ?
unchannelized Configure unchannelized ds3 bert Initiate sending of BERT test patterns
interface clock Configure the transmit clock source
<cr> framing Configure ds3 line framing
erx3:di1(config-controll)#path 1 ds3 1 loopback Configure interface loopback
channelized remote-loopback Enable remote ability to configure interface
loopback
erx3:di1(config-controll)#path 1 ds3 1 clock
source int module shutdown Disable the interface
snmp Configure SNMP parameters
<cr>
erx3:di1(config-controll)#path 1 ds3 1 t1 2
erx3:di1(config-controll)#path 1 ds3 1 t1 2/1 time 1-4
erx3:di1(config-controll)#path 1 ds3 1 t1 2/2 time 5-8

Basic Circuit Aggregation Rev 3.2 Page 1- 47

Configuration
 SONET Hierarchy
OC12
STS3-1
(OC3)
155 Mbps
Tributary Group
1-7
STS3-2 VTG-1
(OC3) Tributary Number
Path Channel VTG-2
155 Mbps 1-4
1-3
STS12 VTG-3 VT1.5-1 (T1)
(OC12) STS1-1 VT1.5-2 (T1)
VTG-4
622 Mbps
STS3-3 VT1.5-3 (T1)
VTG-5
(OC3) STS1-2 VT1.5-4 (T1)
155 Mbps VTG-6
VTG-7
STS1-3
STS3-4
(OC3)
155 Mbps

A Sonet OC12 or STS12 supports 4 STS3s or OC3’s. Each STS3 supports 3 STS1’s.
Each STS1 is referred to as a Path Channel in the range of 1-3.
Each Path Channel supports 7 Virtual Tributary Groups or VTG’s.
In theory, each VTG supports either 3 Virtual Tributary 2.0’s (E1’s) or 4 Virtual Tributary
1.5’s (T1’s). Both the CHOC3 and CHOC12 line modules do NOT support VT-2.0 AND
VT1.5 tributaries mapped into an STS-3 at the same time. The line modules will support
either VT-2.0 OR VT1.5 tributaries. Thus, this picture is technically inaccurate for the ERX
line modules.

Basic Circuit Aggregation Rev 3.2 Page 1- 48

Configuration
 What is different for a OC12
configuration?
• Specify which path is being used and assign a logical path name or label
- path logical-path oc1 path-channel
- path 30 oc1 3/1
- * This is the big difference!
• Associate the logical path with a specific VTG & VT and specify VT Type
- path logical-path ds1 path-payload/vt-group/vt-number vt-type
- path 30 ds1 1/6/4 vt15
- * Remember that the path-payload in SONET is always 1!
• Configure L2 & L3 as before Tributary Group
1-7
VTG-1
Tributary Number
Path Channel VTG-2 1-4
1-3
STS12 Path Channel VTG-3 VT1.5-1 (T1)
(OC12) 1-4 STS1-1 VT1.5-2 (T1)
VTG-4
622 Mbps
STS3-3 VT1.5-3 (T1)
VTG-5
(OC3) STS1-2 VT1.5-4 (T1)
155 Mbps VTG-6
STS1-3 VTG-7

Basic Circuit Aggregation Rev 3.2 Page 1- 49

Configuration
 SDH Hierarchy
STM1 Tributary Unit Group
Level 2
TUG2-1
Tributary Unit Group TU-11-1 (T1)
TUG2-2
Level 3
TU-11-2 (T1)

...
TUG2-3
TUG3-1 TU-11-3 (T1)
TUG2-4
Path TU-11-3 (T1)
Path Payload TUG2-5
SDH = 1 - 3 Tributary Number
STM1 TUG2-6 1-4
155 Mbps TUG3-2 Tributary Group TUG2-7
1-7
Tributary Number
TUG2-1
1-3
TUG2-2 Tributary Unit Channel
Group
TUG2-3 TU-12-1 (E1) 1-31

...
TUG3-3 TUG2-4 TU-12-2 (E1)
TUG2-5 TU-12-3 (E1)
TUG2-6
TUG2-7

STM1 supports 3 Tributary Unit Group 3’s (TUG-3s) or Path Payloads per STM1. These
Path payloads have the range 1-3.
Each TUG-3 supports 7 Tributary Unit Group 2’s (TUG-2’s) or Tributary Groups.
In theory, each TUG-2 supports either 3 Tributary Unit 12’s (E1’s) or 4 Tributary Unit 11’s
(T1’s). Both the CHOC3 and CHOC12 line modules do NOT support TU-11 AND TU-12
tributaries mapped into an STM-1 at the same time. The line modules will support either
TU-11 OR TU-12 tributaries. Thus, this picture is technically inaccurate for the ERX line
modules.

Basic Circuit Aggregation Rev 3.2 Page 1- 50

Configuration
 How do I reference this Unframed E1
on a CHOC3 SDH Tributary?
Slot/Port:Path Channel**/Path Payload/ Tributary Group /Tributary Number/Channel Group

3 / 0 : 1 ** / 3 / 5 / 1 / 1 ***

Special Note:
** In SDH STM1, there is a single Path
*** The last ‘1’ indicates the group of DS0’s

Path = 1 Path Payload

SDH = 1 - 3 Tributary Group
STM1 1-7
TUG3-2 Tributary Number
155 Mbps
TUG2-1 1-3
TUG2-2 TU-12-1 (E1)

...
TUG2-3 TU-12-2 (E1)
TUG2-4
TUG3-3 TU-13-3 (E1)
TUG2-5
TUG2-6
TUG2-7

In SDH mode, the CHOC3 interface will always have a single STM-1 path. The Path
Channel will always be set to 1. The Path payload will range from 1-3.

Basic Circuit Aggregation Rev 3.2 Page 1- 51

Configuration
 How do I configure an unframed E1
on a CHOC3 SDH Tributary?
• Configure the controller, specify clock source and SDH mode
- controller sonet 3/0
- clock source internal module
- sdh
• Specify the logical path identifier
- path logical-path stm1
- path 1 stm1
- * Remember that there is only 1 path in STM1
Tributary Group Tributary Number
1-7 1-3
Path = 1 Path Payload TU-12-1 (E1)
TUG2-1

...
STM1 1-3
155 Mbps TUG2-2 TU-12-2 (E1)
TUG3-3
Slot 3 TUG2-3 TU-13-3 (E1)
Port 0 TUG2-4
TUG2-5
TUG2-6
TUG2-7

erx1:di1(config-controll)#path ?
erx1:di1(config)#cont sonet 3/0
<1 - 2147483647> The path logical channel
erx1:di1(config-controll)#?
clock Configure the Sonet transmit clock source
erx1:di1(config-controll)#path 1 ?
exit Exit from the current command mode ds1 Configure a ds1 interface
help Describe the interactive help system ds3 Configure a ds3 interface
log Configure logging settings e1 Configure an e1 interface
loopback Configure for loopback mode stm0 The SDH path speed stm0
macro Run a CLI macro stm1 The SDH path speed stm1
no Negate a command or set its default(s) stm16 The SDH path speed stm16
path Configure a path stm4 The SDH path speed stm4
sdh Configure for Synchronous Digital Hierarchy mode <cr>

shutdown Disable the interface

erx1:di1(config-controll)#path 1 stm1 ?
sleep Make the Command Interface pause for a
D[/D[/D]] The path hierarchy
specified duration
<cr>
support Enter Support mode

erx1:di1(config-controll)#path 1 stm1
erx1:di1(config-controll)#sdh
erx1:di1(config-controll)#clock source int mod

Basic Circuit Aggregation Rev 3.2 Page 1- 52

Configuration
 Unframed E1 on a CHOC3 SDH
Tributary (cont.)
• Specify the Path Payload (TUG-3), Tributary group (TUG-2), Tributary Number
(TU) and specify TU Type (TU-12 or TU-11)
- path stm-path e1 path-payload/Tributary group/Tributary number TU-type
- path 1 e1 3/5/1 tu12
• Configure the E1 for unframed mode and configure the clock source
- path 1 e1 3/5/1 unframed
- path 1 e1 3/5/1 clock source internal module
Tributary Group
1-7
Tributary Number
TUG2-1 1-3
Path = 1 TUG2-2 TU-12-1 (E1)

...
STM1 Path Payload
155 Mbps TUG2-3 TU-12-2 (E1)
1-3
Slot 3 TUG3-3 TUG2-4 TU-13-3 (E1)
Port 0
TUG2-5
TUG2-6
TUG2-7

erx1:di1(config-controll)#path 1 ? erx1:di1(config-controll)#path 1 e1 3/5/1 tu12 ?

ds1 Configure a ds1 interface <cr>
ds3 Configure a ds3 interface erx1:di1(config-controll)#path 1 e1 3/5/1 tu12
e1 Configure an e1 interface
erx1:di1(config-controll)#path 1 e1 3/5/1 unframed
stm0 The SDH path speed stm0
stm1 The SDH path speed stm1 erx1:di1(config-controll)#path 1 e1 3/5/1 clock source int mod
stm16 The SDH path speed stm16
stm4 The SDH path speed stm4
<cr>
erx1:di1(config-controll)#path 1 e1 ?
D/D/D The tributary specification

erx1:di1(config-controll)#path 1 e1 3/5/1 ?

bert Initiate sending of BERT test patterns

channel-group Configure fractional channel group, unavailable in unframmed mode
clock Configure the transmit clock source
framing Configure e1 line framing, unavailable in unframed mode
loopback Configure interface loopback
shutdown Disable the interface
snmp Configure SNMP parameters
tu11 The SDH tributary type tu11
tu12 The SDH tributary type tu12
unframed Set e1 line into unframed mode
<cr>

Basic Circuit Aggregation Rev 3.2 Page 1- 53

Configuration
 Configuring PPP over a CHOC3 SDH
Tributary
• Create the serial interface
- interface serial 3/0:1/3/5/1/1
- Note the extra ‘1’ at the end of the interface identifier! The ‘1’ refers to the
bundle of DS0’s in unframed mode.
• Specify the encapsulation method
- encapsulation ppp
• Configure the IP address, subnet mask and IP description
- ip address 192.168.21.1 255.255.255.0 Tributary Group
- description unframed E1 1-7
Tributary Number
TUG2-1
1-3
Path = 1 TUG2-2 TU-12-1 (E1)

...
STM1 Path Payload TUG2-3
155 Mbps 1-3 TU-12-2 (E1)
TUG3-3 TUG2-4
Slot 3 TU-13-3 (E1)
Port 0 TUG2-5
TUG2-6
TUG2-7

erx1:di2(config)#int ser 3/1:1/3/5/1/1

erx1:di2(config-if)#encap ppp
erx1:di2(config-if)#ip add 192.168.21.1 255.255.255.0
erx1:di2(config-if)#exit
erx1:di2#show config inc | beg sonet 3/0
controller sonet 3/0
sdh
no loopback
clock source internal module
no shutdown
path 1 stm1
path 1 e1 3/5/1 tu12
no path 1 e1 3/5/1 shutdown
no path 1 e1 3/5/1 snmp trap link-status
path 1 e1 3/5/1 unframed
path 1 e1 3/5/1 clock source internal module
no path 1 e1 3/5/1 loopback

Basic Circuit Aggregation Rev 3.2 Page 1- 54

Configuration
 How do I reference this FE1 on a
CHOC3 SDH Tributary?
Slot/Port:Path Channel**/Path Payload/ Tributary Group /Tributary Number/Channel Group

4 / 1 : 1** / 3 / 5 / 1

Special Note:
** In SDH STM1, there is a single Path

Path = 1 Path Payload

SDH = 1 - 3
STM1 Tributary Group
155 Mbps TUG3-2 1-7 Tributary Number
Slot 0 TUG2-1 1-3
Port 3 TUG2-2 TU-12-1 (E1)
TUG2-3 TU-12-2 (E1)
TUG3-3 TUG2-4
TU-13-3 (E1)

...
TUG2-5 Channel group 1
Timeslot 1-4
TUG2-6 Channel group 2
Timeslots 5-8
TUG2-7

In SDH mode, the CHOC3 interface will always have a single STM-1 path.

Basic Circuit Aggregation Rev 3.2 Page 1- 55

Configuration
 Configuring a FE1 on a CHOC3 SDH
Tributary
• Specify the logical path identifier
path logical-path stm1
path 1 stm1
* Remember that there is only 1 path in STM1
• Specify the Path Payload (TUG-3), Tributary group (TUG-2), Tributary Number (TU) and
specify TU Type (TU-12 or TU-11)
path stm-path e1 path-payload/Tributary group/Tributary number TU-type
path 1 e1 3/5/3 tu12
• Configure the E1timeslots and configure the clock source
path 1 e1 3/5/3 channel-group 1 timeslot 1-4
path 1 e1 3/5/3 channel-group 2 timeslot 5-8
path 1 e1 3/5/3 clock source internal module Tributary Group 1-7
TUG2-1
Tributary Number 1-3
Path = 1 Path Payload 1-3 TUG2-2 Channel group 1
STM1 TU-12-1 (E1) Timeslot 1-4
TUG3-3 TUG2-3 Channel group 2
155 Mbps TU-12-2 (E1) Timeslots 5-8
TUG2-4
Slot 3
Port 0 TUG2-5 TU-13-3 (E1)

...
TUG2-6
TUG2-7

erx1:di1(config-controll)#path 1 stm1 erx1:di1(config-controll)#path 1 e1 3/5/3 channel-

group 1 ?
erx1:di1(config-controll)#path 1 e1 3/5/3 ?
bert Initiate sending of BERT test patterns shutdown Disable the interface
channel-group Configure fractional channel snmp Configure SNMP parameters
group, timeslots Specify time slot configuration
unavailable in unframed mode erx1:di1(config-controll)#path 1 e1 3/5/3 channel-
clock Configure the transmit clock source group 1 time ?
framing Configure e1 line framing, unavailableRANGE The DS0 time slot(s) allocation (1-31)
in unframed mode
erx1:di1(config-controll)#path 1 e1 3/5/3 channel-
loopback Configure interface loopback
group 1 time 1-4 ?
shutdown Disable the interface
speed Specify DS0 mode
snmp Configure SNMP parameters
tu11 The SDH tributary type tu11 <cr>
tu12 The SDH tributary type tu12 erx1:di1(config-controll)#path 1 e1 3/5/3 channel
unframed Set e1 line into unframed mode -group 1 time 1-4
<cr> erx1:di1(config-controll)#path 1 e1 3/5/3 channel-
erx1:di1(config-controll)#path 1 e1 3/5/3 tu12 group 2 time 5-8
erx1:di1(config-controll)#path 1 e1 3/5/3 channel-erx1:di1(config-controll)#exit
group ?
<1 - 31> The fractional interface

Basic Circuit Aggregation Rev 3.2 Page 1- 56

Configuration
 Configuring PPP over a SDH FE1
Tributary
• Create the serial interface
- interface serial 3/0:1/3/5/3/1
• Specify the encapsulation method
- encapsulation ppp
• Configure the IP address, subnet mask and IP description
- ip address 192.168.22.1 255.255.255.0
- description FE1 Tributary Group
1-7
Tributary Number
TUG2-1 1-3
Path = 1 TUG2-2 TU-12-1 (E1)
STM1 Path Payload
155 Mbps TUG2-3 TU-12-2 (E1)
1-3
Slot 3 TUG3-3 TUG2-4 TU-13-3 (E1)

...
Port 0
TUG2-5
TUG2-6
TUG2-7

erx1:di1(config)#int ser 3/0:1/3/5/3/1

erx1:di1(config-if)#encap ppp
erx1:di1(config-if)#ip add 192.168.22.1 255.255.255.0
erx1:di1(config-if)#int ser 3/0:1/3/5/3/2
erx1:di1(config-if)#encap ppp
erx1:di1(config-if)#ip add 192.168.23.1 255.255.255.0
erx1:di1(config-if)#desc FE1
erx1:di2#show config inc | beg sonet 3/0
controller sonet 3/0
sdh
no loopback
clock source internal module
no shutdown
path 1 stm1
path 1 e1 3/5/3 tu12
no path 1 e1 3/5/3 shutdown
no path 1 e1 3/5/3 snmp trap link-status
path 1 e1 3/5/3 framing crc4
path 1 e1 3/5/3 clock source line
no path 1 e1 3/5/3 loopback
path 1 e1 3/5/3 channel-group 1 timeslots 1-4 speed 64
no path 1 e1 3/5/3 channel-group 1 shutdown
no path 1 e1 3/5/3 channel-group 1 snmp trap link-status
path 1 e1 3/5/3 channel-group 2 timeslots 5-8 speed 64
no path 1 e1 3/5/3 channel-group 2 shutdown
no path 1 e1 3/5/3 channel-group 2 snmp trap link-status !

Basic Circuit Aggregation Rev 3.2 Page 1- 57

Configuration
 SDH Hierarchy
STM4
STM1
155 Mbps

Tributary Group Tributary Number

TUG2-1 TU-12-1 (E1)

STM2
155 Mbps TUG2-2 TU-12-2 (E1)
Path Payload TUG2-3 TU-13-3 (E1)
STM4 TUG3-1
622 Mbps Path TUG2-4

STM3 TUG2-5
155 Mbps TUG3-2
TUG2-6
TUG2-7
TUG3-3

STM4
155 Mbps

A Sonet OC12 or STS12 supports 4 STS3s or OC3’s. Each STS3 supports 3 STS1’s.
Each STS1 is referred to as a Path Channel in the range of 1-3.
Each Path Channel supports 7 Virtual Tributary Groups or VTG’s.
In theory, each VTG supports either 3 Virtual Tributary 2.0’s (E1’s) or 4 Virtual Tributary
1.5’s (T1’s). Both the CHOC3 and CHOC12 line modules do NOT support VT-2.0 AND
VT1.5 tributaries mapped into an STS-3 at the same time. The line modules will support
either VT-2.0 OR VT1.5 tributaries. Thus, this picture is technically inaccurate for the ERX
line modules.

Basic Circuit Aggregation Rev 3.2 Page 1- 58

Configuration
 What is different about a STM4
Configuration?
• Specify the logical path identifiers - An STM4 has 4 paths to configure
- path logical-path stm1 path-number
- path 10 stm1 1
- path 20 stm1 2
- path 30 stm1 3
- path 40 stm1 4
• Specify the Path Payload (TUG-3), Tributary group (TUG-2), Tributary Number (TU) and
specify TU Type (TU-12 or TU-11)
- path stm-path e1 path-payload/Tributary group/Tributary number TU-type
- path 20 e1 3/5/1 tu12
• Configure the tributary for either Unframed or FE1 Tributary Group Tributary Number
- Same as the STM1 configuration TUG2-1 TU-12-1 (E1)
• Configure the L2 and L3 parameters
- Same as the STM1 configuration TUG2-2 TU-12-2 (E1)
Path Payload
TUG2-3 TU-13-3 (E1)
Path 20
TUG3-1
TUG2-4
STM2
STM4
155 Mbps TUG2-5
622 Mbps TUG3-2
TUG2-6
TUG3-3 TUG2-7

Notice that the Path Logical Identifiers can be any unique number for the interface. In the
previous examples, we made the Logical path identifier the same as the STS or SDH path
number. This does not have to be the case. It is simply a locally assigned label.

Basic Circuit Aggregation Rev 3.2 Page 1- 59

Configuration