|
|
Follow the procedures in this chapter to configure the access server manually or if you want to change the configuration after you have run the setup script (described in "First-Time Configuration."
This chapter does not describe every configuration possible--only the most commonly used configuration procedures. For advanced configuration topics and procedures, go to "Advanced Configuration."
You can also view these publications on the Documentation CD-ROM that arrived with your access server, or you can order printed copies separately.
If you are experienced using the Cisco IOS software, you might find the "Where to Go Next" section at the end of this chapter a useful reference for configuration.
![]() |
Note If you skipped ""Using Cisco IOS Software," and you have never configured a Cisco access server, return to this chapter and read it now. |
One of the first configuration tasks you might want to do is configure the host name and set an encrypted password. Configuring a host name allows you to distinguish multiple Cisco access servers from each other. Setting an encrypted password allows you to prevent unauthorized configuration changes.
To verify that you configured the right host name and passwords:
5400(config)# show config Using 1888 out of 512000 bytes ! version XX.X . . ! hostname 5400 ! enable secret 5 $1$60L4$X2JYOwoDc0.kqa1loO/w8/ .
5400# exit 5400 con0 is now available Press RETURN to get started. 5400> enable Password: guessme 5400#
![]() |
Tips If you are having trouble: |
Facility alarms currently monitor the following failure events:
Cisco IOS software polls every second to detect the failure events that you have configured and will turn on the alarm when any one of the failure events is detected. By default, facility alarm is off. Users have to configure one of the following commands to enable monitoring of the failure conditions.
Enter [no] before the full command to disable any of the alarm commands.
5400# no facility-alarm detect rps
Command | Purpose | |
|---|---|---|
| 5400>enable Password: password 5400# |
|
|
|
|
| 5400(config)#facility-alarm detect interface |
|
| 5400(config)#facility-alarm detect controller [t1 | e1 | t3] |
|
| 5400(config)#facility-alarm detect modem-board |
|
| 5400(config)#facility-alarm detect rps |
|
| 5400(config)# facility-alarm detect temperature |
|
| 5400(config)# facility-alarm detect fan |
|
|
|
|
To see the status of the alarms, enter the show facility-alarm command:
5400# show facility-alarm
Device State
------ -----
FastEthernet0/0 UP
Modem Card 4 UP
Facility Alarm is ON
![]() |
Tips If you are having trouble: |
Assign an IP address to the FastEthernet interface of your access server so that it can be recognized as a device on the Ethernet LAN. The FastEthernet interface supports 10- and 100-Mbps speeds with the 100BaseT and 10BaseT routers, hubs, and switches.
Command | Purpose | |||
|---|---|---|---|---|
| 5400>enable Password: password 5400# |
| ||
|
|
| ||
| 5400(config)#interface fastethernet 0/0 5400(config-if)# |
| ||
|
|
| ||
| 5400(config-if)# |
| ||
| 5400(config-if)# |
| ||
| 5400(config-if)#no shutdown |
| ||
|
|
|
| Duplex Mode | Speed Mode | Action |
|---|---|---|
auto | auto | Auto negotiates speed and duplex modes. |
auto | 100/10 | Auto negotiates duplex mode. |
half/full | auto | Auto negotiates speed mode. |
half | 10 | Sets 10 Mbps for speed and half-duplex for duplex. |
full | 10 | Sets 10 Mbps for speed and full-duplex for duplex. |
half | 100 | Sets 100 Mbps for speed and half-duplex for duplex. |
full | 100 | Sets 100 Mbps for speed and full-duplex for duplex. |
To verify the IP address, configured speed and duplex mode operations:
5400# show arp Protocol Address Age (min) Hardware Addr Type Interface Internet 172.21.101.21 - 0050.3eff.5f4c ARPA FastEthernet0/0 Internet 172.21.101.1 180 0050.0b00.141e ARPA FastEthernet0/0
5400# show interface fastethernet 0/0
FastEthernet0/0 is up, line protocol is up
Hardware is amd79c971, address is 0050.3eff.5f4c (bia 0050.3eff.5f4c)
Internet address is 172.21.101.21/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s, 100BaseTX/FX
ARP type:ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy:fifo
Output queue 0/40, 0 drops; input queue 0/512, 0 drops
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
8607 packets input, 2015947 bytes
Received 5318 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast
0 input packets with dribble condition detected
11957 packets output, 1289542 bytes, 0 underruns(0/0/0)
0 output errors, 0 collisions, 12 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
![]() |
Tips If you are having trouble: |
Configure the synchronous serial interfaces on the motherboard to connect to a WAN through a CSU/DSU.
This section describes how to enable the serial interface, specify IP routing, and set up external clock timing on a DCE or DTE interface. To use a port as a DTE interface, you need only connect a DTE adapter cable to the port. When the system detects the DTE mode cable, it automatically uses the external timing signal. To use a port in DCE mode, you must connect a DCE interface cable and set the clock speed with the clock rate configuration command. You must also set the clock rate to perform a loopback test.
Command | Purpose | |
|---|---|---|
| 5400>enable Password: |
|
| 5400#configure terminal Enter configuration commands, one per line. End with CNTL/Z. 5400(config)# |
|
| 5400(config)# interface serial 0/0 |
|
| 5400(config-int)# ip address |
|
| 5400(config-int)# clock rate 2015232 |
|
| 5400(config-int)# no shutdown |
|
| 5400(config-controller)#Ctrl-Z 5400# |
|
To verify you have configured the interfaces correctly:
5400# show interfaces serial 0/0
Serial0/0 is up, line protocol is up
Hardware is 4T
Internet address is 120.0.0.1/8
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliablility 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, crc 16, loopback not set, keepalive set (10 sec)
Last input 00:00:08, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Queueing strategy:fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
392 packets input, 33312 bytes, 0 no buffer
Received 392 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
358 packets output, 25157 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up
![]() |
Tips If you are having trouble, make sure the network interface is properly connected and terminated. |
On a Cisco AS5400, you can allocate the available channels for channelized E1 and T1 in the following ways:
![]() |
Note For configuration information about leased line or non-dial use, see section "Configuring Synchronous Serial Interfaces for WAN Support" and the Cisco IOS Configuration Fundamentals Configuration Guide publication available online. |
The CT1/E1 controller numbering convention is dfc-slot/port in CLI commands. DFC slot numbering starts from the motherboard and works up from left to right. Slot 0 is reserved for the motherboard. The CT1/E1 DFC slots are numbered sequentially from 1 to 7. Port numbering is from 0 to 7.
Command | Purpose | |
|---|---|---|
| 5400>enable Password: password 5400# |
|
| 5400#configure terminal Enter configuration commands, one per line. End with CNTL/Z. 5400(config)# |
|
| 5400(config)#controller [t1 | e1 |
|
| 5400(config-controller)#framing esf |
|
| 5400(config-controller)#linecode b8zs |
|
| 5400(config-controller)#Ctrl-Z 5400# |
|
To verify your controller is up and running and no alarms have been reported:
5400# show controller t1 1/7
T1 1/7 is up.
No alarms detected.
Framing is ESF, Line Code is AMI, Clock Source is Line Primary.
Version info of slot 2: HW: 2, Firmware: 14, NEAT PLD: 13, NR Bus PLD: 19
Data in current interval (476 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
![]() |
Note For details on the TDM feature, refer to the Cisco IOS software configuration guide and command reference publications. These publications are available on the Documentation CD-ROM that came with your access server, on the World Wide Web from Cisco's home page, or you can order printed copies. |
![]() |
Tips If you are having trouble: |
Your AS54-DFC-CT3 card offers 28 individual T1 channels (bundled in the T3) for serial transmission of data. The CT3 link supports the maintenance data link channel in C-Bit parity mode and also payload and network loopbacks. The T1s multiplexed in the CT3 link supports facilities data link (FDL) in extended super frame (ESF) framing.
Additionally, you can allocate your CT1 channels in the manner that was described in the "Configuring Channelized T1 and E1 Dial Feature Cards" section .
The CT3 controller numbering convention is dfc-slot/port in CLI commands. DFC slot numbering starts from the motherboard and works up from left to right. Slot 0 is reserved for the motherboard. The DFC slots are numbered sequentially from 1 to 7. Port number value is always 0.
Under the CT3, the CT1 controller numbering convention is dfc-slot/port:channel in CLI commands. Port numbering values range from 1 to 28.
Command | Purpose | |||
|---|---|---|---|---|
| 5400>enable Password: password |
| ||
| 5400#configure terminal Enter configuration commands, one per line. End with CNTL/Z. 5400(config)# |
| ||
| 5400(config)#controller t3 1/0 5400(config-controller)# |
| ||
| 5400(config-controller)# framing c-bit |
| ||
| 5400(config-controller)# clock source |
| ||
| 5400(config-controller)# cablelength 450 |
| ||
| 5400(config-controller)# t1 1-28 controller or 5400(config-controller)# t1 1-10,15-20,23 controller |
| ||
| 5400(config-controller)#Ctrl-Z 5400# |
|
To verify your controller is up and running and no alarms have been reported:
5400# show controller t3
T3 1/0 is up.
Applique type is Channelized T3
No alarms detected.
MDL transmission is disabled
FEAC code received: No code is being received Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Line Data in current interval (190 seconds elapsed): 0 Line Code Violations, 0 P-bit Coding Violation 0 C-bit Coding Violation, 0 P-bit Err Secs 0 P-bit Severely Err Secs, 0 Severely Err Framing Secs 0 Unavailable Secs, 0 Line Errored Secs 0 C-bit Errored Secs, 0 C-bit Severely Errored Secs Total Data (last 3 15 minute intervals): 45331 Line Code Violations, 16404 P-bit Coding Violation, 15 C-bit Coding Violation, 1 P-bit Err Secs, 1 P-bit Severely Err Secs, 0 Severely Err Framing Secs, 0 Unavailable Secs, 1 Line Errored Secs, 1 C-bit Errored Secs, 0 C-bit Severely Errored Secs
![]() |
Tips If you are having trouble, make sure the show controller output is not reporting alarms or violations. Also, see Tips under the "Configuring Channelized T1 and E1 Dial Feature Cards" section . |
You can configure up to 24 channel groups for each CT1 on your AS54-DFC-CT1 and AS54-DFC-CT3 cards for backup links or serial backhaul connections.
First, you must define the timeslots that belong with each channel group. Channel groups are numbered 0 to 23, and timeslots are numbered 1 to 24. Defining a channel group creates a serial interface; defining multiple channel groups creates an equal number of serial interfaces that you can configure independently.
The channel group numbers for each CT1 controller can be arbitrarily assigned.
Perform the following task in controller configuration mode to define the channel groups and timeslots:
Command | Purpose | |||
|---|---|---|---|---|
|
|
After you define the T1 channel groups, you can configure each channel group as a serial interface. In other words, you can think of each channel group as a virtual serial interface. Subinterface configuration is also supported on the created serial interface.
Perform the following task in global configuration mode to enter interface configuration mode and configure the serial interface that corresponds to a channel group:
Command | Purpose | |
|---|---|---|
5400(config)# interface serial slot/port:channel-group |
|
The following example shows a channelized T1 controller configured for channel groups and an ISDN PRI group. The pri-group command and the channel-group command cannot have overlapping timeslots; note the correct timeslot configuration.
5400# show running-config
Building configuration...
Current configuration:
!
! Last configuration change at 15:49:30 UTC Mon Apr 3 2000 by admin
! NVRAM config last updated at 01:35:05 UTC Fri Mar 17 2000 by admin
!
version 12.0
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
!
<text omitted>
!
controller t1 0channel-group 0 timeslot 1-6channel-group 1 timeslot 7channel-group 2 timeslot 8channel-group 3 timeslot 9-11pri-group timeslot 12-24
Your AS54-DFC-8CT1, AS54-DFC-8CE1 and AS54-DFC-CT3 cards support ISDN PRI. ISDN, which uses the D channel for signaling and the B channels for user data provides out-of-band signaling.
Channelized T1 ISDN PRI offers 23 B channels and 1 D channel. Channelized E1 ISDN PRI offers 30 B channels and 1 D channel. Channel 24 is the D channel for T1, and channel 16 is the D channel for E1.
For a complete description of the commands mentioned in this chapter, refer to the Dial Solutions Command Reference available online.
This process varies dramatically from provider to provider on a national and international basis. However, some general guidelines follow:
Table 3-2 provides a sample of the CT1 configuration attributes you might request for a PRI switch.
| Attribute | Value |
|---|---|
Line format | Extended Superframe Format (ESF) |
Line coding | Binary 8-zero substitution (B8ZS) |
Call type | 23 incoming channels and 23 outgoing channels |
Speed | 64 kbps |
Call-by-call capability | Enabled |
Channels | 23 B + D |
Trunk selection sequence | Either ascending order (from 1 to 23) or descending order (from 23 to 1) |
B + D glare | Yield |
Directory numbers | Only 1 directory number assigned by service provider |
SPIDs required? | None |
The CT1/E1 controller numbering convention is dfc-slot/port in CLI commands. DFC slot numbering starts from the motherboard and works up from left to right. Slot 0 is reserved for the motherboard. The CT1/E1 DFC slots are numbered sequentially from 1 to 7. Port numbering is from 0 to 7.
The CT3 controller numbering convention is dfc-slot/port in CLI commands. DFC slot numbering starts from the motherboard and works up from left to right. Slot 0 is reserved for the motherboard. The DFC slots are numbered sequentially from 1 to 7. Port number value is always 0.
Under the CT3, the CT1 controller numbering convention is dfc-slot/port:channel in CLI commands. Port numbering values range from 1 to 28.
Command | Purpose | |||
|---|---|---|---|---|
| 5400>enable Password: password |
| ||
| 5400#configure terminal Enter configuration commands, one per line. End with CNTL/Z. 5400(config)# |
| ||
| 5400(config)#isdn switch-type switch-type |
| ||
| 5400(config)# controller t1 1/0:1 or 5400(config)# controller e1 1/0:1 |
| ||
| 5400(config-controller)# framing esf or 5400(config-controller)# framing crc4 |
| ||
| 5400(config-controller)# linecode b8zs |
| ||
| 5400(config-controller)# pri-group [timeslots range]1 |
| ||
| 5400(config-controller)#Ctrl-Z 5400# |
|
| 1On CT1, time slots range 1 to 24. You can specify a range of time slots (for example, pri-group timeslots 12-24) if other time slots are used for non-PRI channel groups. |
For CT1 ISDN PRI--If you do not specify the time slots, the specified controller is configured for 24 B channels and 1 D channel. The B channel numbers range 1 to 24; channel 24 is the D channel for T1. Corresponding serial interfaces numbers range 0 to 23. In commands, the D channel is interface serial controller-number:23. For example, interface serial 0:23.
For CE1 ISDN PRI--If you do not specify the time slots, the specified controller is configured for 30 B channels and 1 D channel. The B channel numbers range 1 to 31; channel 16 is the D channel for E1. Corresponding serial interfaces numbers range 0 to 30. In commands, the D channel is interface serial controller-number:15. For example, interface serial 0:15.
| Keywords by Area | Switch Type |
|---|---|
none | No switch defined. |
| Australia | |
primary-ts014 | Australia PRI switches. |
| Europe | |
primary-net5 | European, New Zealand, and Asia ISDN PRI switches (covers the Euro-ISDN E-DSS1 signaling system and is European Telecommunication Standards Institute or ETSI-compliant). |
| Japan | |
primary-ntt | Japanese ISDN PRI switches. |
| North America | |
primary-4ess | AT&T 4ESS switch type for the United States. |
primary-5ess | AT&T 5ESS switch type for the United States. |
primary-dms100 | NT DMS-100 switch type for the United States. |
primary-ni | National ISDN switch type. |
To verify you have configured the interfaces correctly:
5400# show controller t3 1/0
T3 1/0 is up.
Applique type is Channelized T3
No alarms detected.
MDL transmission is disabled
FEAC code received:No code is being received
Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal
Data in current interval (270 seconds elapsed):
0 Line Code Violations, 0 P-bit Coding Violation
0 C-bit Coding Violation, 0 P-bit Err Secs
0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
0 Unavailable Secs, 0 Line Errored Secs
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Total Data (last 32 15 minute intervals):
0 Line Code Violations, 0 P-bit Coding Violation,
0 C-bit Coding Violation, 0 P-bit Err Secs,
0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,
0 Unavailable Secs, 0 Line Errored Secs,
0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
5400# show controller t1 1/0:1
T1 1/0:1 is up.
Applique type is Channelized T1
Cablelength is short
No alarms detected.
Version info of slot 1: HW: 768, PLD Rev: 4
Framer Version: 0x8
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x01,
Board Hardware Version 3.0, Item Number 73-4089-03,
Board Revision 05, Serial Number JAB99432626,
PLD/ISP Version 0.1, Manufacture Date 11-Nov-1999.
Framing is ESF, Line Code is AMI, Clock Source is Line.
Data in current interval (651 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 1:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
.
.
.
5400# show isdn status
Global ISDN Switchtype = primary-5ess
ISDN Serial1/0:1:23 interface
dsl 0, interface ISDN Switchtype = primary-5ess
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
The Free Channel Mask: 0x807FFFFF
.
.
.
ISDN Serial1/0:28:23 interface
dsl 27, interface ISDN Switchtype = primary-5ess
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 27 CCBs = 0
The Free Channel Mask: 0x807FFFFF
Total Allocated ISDN CCBs = 0
5400# show isdn service PRI Channel Statistics: ISDN Se0:23, Channel (1-31) Activated dsl 0 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 0 0 0 0 3 3 3 3 3 3 3 3 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 ISDN Se1:23, Channel (1-31) Activated dsl 1 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 0 3 3 3 3 3 3 3 3 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 ISDN Se2:23, Channel (1-31) Activated dsl 2 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 0 0 0 0 3 3 3 3 3 3 3 3 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 ISDN Se3:23, Channel (1-31) Activated dsl 3 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 ISDN Se4:23, Channel (1-31) Activated dsl 4 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 ISDN Se5:23, Channel (1-31) Activated dsl 5 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 2 2 2 2 2 2 2 2 2 2 2 2 0 0 0 0 0 0 0 0 0 0 0 3 3 3 3 3 3 3 3 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 ISDN Se6:23, Channel (1-31) Activated dsl 6 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 0 3 3 3 3 3 3 3 3 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2 ISDN Se7:23, Channel (1-31) Activated dsl 7 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 0 3 3 3 3 3 3 3 3 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2
![]() |
Note Your Cisco AS5400 supports a total of 248 ISDN channels. If you are configuring individual T1 channels of your CT3 for backup links or serial backhaul connections, the CT1s must be configured into channel-groups--each channel-group using 24 timeslots or channels. For example, to configure 6 CT1s (6*24), 144 ISDN channels are in use leaving a remainder of 104 (248-144) channels for ISDN use. See "Configuring CT1 Channel Groups" section. |
In the following show running-config example, six CT1s are configured into channel-groups:
5400# show running-config
Building configuration...
Current configuration:
!
! Last configuration change at 15:49:30 UTC Mon Apr 3 2000 by admin
! NVRAM config last updated at 01:35:05 UTC Fri Mar 17 2000 by admin
!
version 12.0
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
!
<text omitted>
!
controller T3 1/0
framing m23
clock source line
t1 1-28 controller
!
controller T1 1/0:11
framing esf
channel-group 20 timeslots 1-24 speed 64
!
controller T1 1/0:12
framing esf
channel-group 20 timeslots 1-24 speed 64
!
controller T1 1/0:13
framing esf
channel-group 20 timeslots 1-24 speed 64
!
controller T1 1/0:14
framing esf
channel-group 20 timeslots 1-24 speed 64
!
controller T1 1/0:15
framing esf
channel-group 20 timeslots 1-24 speed 64
!
controller T1 1/0:16
framing esf
channel-group 20 timeslots 1-24 speed 64
![]() |
Tips If you are having trouble: |
ISDN Non-Facility Associated Signaling (NFAS) allows a single D channel to control multiple PRI interfaces. A backup D channel can also be configured for use when the primary NFAS D channel fails.
When configuring NFAS for channelized T1 controllers configured for ISDN, you use an extended version of the ISDN pri-group command to specify the following :
![]() |
Note Your Cisco AS5400 must connect to a Primary-4ess, Primary-DMS 100 or Primary-NI switch (see Table 3-3). It must also have a channelized T1 controller and, as a result, be ISDN PRI capable. |
To configure ISDN NFAS, complete the following tasks in controller configuration mode:
Command | Purpose |
|---|---|
5400(config-controller)# pri-group timeslots 1-24 nfas_d primary nfas_interface number nfas_group number |
|
5400(config-controller)# pri-group timeslots 1-24 nfas_d backup nfas_interface number nfas_group number |
|
5400(config-controller)# pri-group timeslots 1-24 nfas_d none nfas_interface number nfas_group number |
|
You can take a specified channel or an entire PRI interface out of service or put it into one of the other states that is passed in to the switch.
To do so, complete one of the following tasks in interface configuration mode:
Command | Purpose |
|---|---|
5400(config-controller)# isdn service dsl number b_channel number state state-value |
|
5400(config-controller)# isdn service dsl number b_channel 0 state state-value |
|
These are the supported state values:
5400# show isdn nfas group 0 ISDN NFAS GROUP 0x0 ENTRIES: The primary D is Serial0:23. The backup D is Serial1:23. There are 2 total nfas members. There are 24 total available B channels. The primary D-channel is DSL 0 in state IN SERVICE. The backup D-channel is DSL 1 in state STANDBY. The current active layer 2 DSL is 0.
The ISDN D channels carry the control and signaling information for ISDN calls--for both circuit-switched data calls and analog modem calls. All incoming ISDN analog modem calls that come in on an ISDN PRI receive signaling information from the ISDN D channel.
When you configure ISDN PRI on the CT1 or CE1 controller (see "Configuring ISDN PRI"), in effect you automatically create a serial interface that corresponds to the PRI group time slots. This interface is a logical entity that is associated with the specific controller. After the serial interface is created, you must configure the D channel serial interface. The configuration applies to all the PRI B channels (time slots) for that pri group.
![]() |
Note When you configure your CT1 controller for an NFAS backup D channel, a serial interface is automatically created only when your primary D channel fails. See "Configuring ISDN NFAS on CT1 PRI Groups." |
Command | Purpose | |||
|---|---|---|---|---|
| 5400>enable Password: |
| ||
| 5400#configure terminal Enter configuration commands, one per line. End with CNTL/Z. 5400(config)# |
| ||
| 5400(config)#interface serial 1/0:23 5400(config-if)# |
| ||
| 5400(config-if)#ip address 172.16.254.254 255.255.255.0 | |||
| 5400(config-if)#isdn incoming-voice modem | |||
| 5400(config-if)#dialer-group 1 |
| ||
| 5400(config-if)#encapsulation ppp |
| ||
| 5400(config-if)#ppp multilink |
| ||
| 5400(config-if)#ppp authentication chap pap |
| ||
| 5400(config-if)# peer default ip adress pool default | |||
| 5400(config-if)#Ctrl-Z 5400# |
|
| 1PPP = Point-to-Point Protocol. 2CHAP = Challenge Handshake Authentication Protocol. 3PAP = Password Authentication Protocol. |
To verify your D channel configuration:
5400# show interface serial 2/0:23
Serial2/0:23 is up, line protocol is up (spoofing)
Hardware is DSX1
Internet address is 172.16.254.254/16
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Last input 00:00:03, output never, output hang never
Last clearing of "show interface" counters 00:00:01
Queueing strategy:fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
1 minute input rate 0 bits/sec, 0 packets/sec
1 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Timeslot(s) Used:24, Transmitter delay is 0 flags
5400#
![]() |
Tips If you are having trouble: |
5400# show interface serial 2/0:23
Serial2/0:23 is up, line protocol is up (spoofing)
Hardware is DSX1
Internet address is 172.16.254.254/16
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Last input 00:00:07, output never, output hang never
Last clearing of "show interface" counters 00:00:06
Queueing strategy:fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
1 minute input rate 0 bits/sec, 0 packets/sec
1 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Timeslot(s) Used:24, Transmitter delay is 0 flags
5400#
5400# debug dialer
*Jan 6 06:20:47.980:Serial2/1:23 DDR:rotor dialout [priority]
*Jan 6 06:20:47.980:Serial2/1:23 DDR:Dialing cause ip (s=192.168.2.20, d=70.1.1.1)
*Jan 6 06:20:47.980:Serial2/1:23 DDR:Attempting to dial 5250100000
*Jan 6 06:20:48.128:%LINK-3-UPDOWN:Interface Serial2/1:0, changed state to up
*Jan 6 06:20:48.132:%DIALER-6-BIND:Interface Serial2/1:0 bound to profile Dialer1
*Jan 6 06:20:48.132:isdn_call_connect:Calling lineaction of Serial0:0
*Jan 6 06:20:48.188:Se0:0 DDR:Dialer protocol up
*Jan 6 06:20:48.188:Serial2/1:0 DDR:dialer protocol up
*Jan 6 06:20:48.188:Dialer1:dialer_ckt_swt_client_connect:incoming circuit switched call.
*Jan 6 06:20:49.168:%LINEPROTO-5-UPDOWN:Line protocol on Interface Serial2/1:0, changed state to up..
*Jan 6 06:20:54.132:%ISDN-6-CONNECT:Interface Serial2/1:0 is now connected to 5250100000 5250100000..
5400# no debug dialer
| Message | Description |
|---|---|
| A packet is received that should cause a call to be placed. However, there is no dialer string configured, so dialing cannot occur. This message usually indicates a configuration problem. Re-enter the dialer-group command in step 6 in the "Configure" section. |
| A packet has been received that passes the dial-on-demand access lists. That packet causes dialing of a phone number. The 5250100000 variable is the number being called. |
| The phone call could not be placed. This can be because of a lack of memory, full output queues, or other problems. |
| The Cisco AS5400 attempted to hang up a call. |
| Corresponding dialer timer expires. Messages are mostly informational and are useful when debugging a disconnected call or call failure. |
5400#debug isdn q931 ISDN Se2/0/-1:RX <- SETUP pd = 8 callref = 0x0002 *Jan 5 23:36:36.330: Bearer Capability i = 0x8890 *Jan 5 23:36:36.330: Channel ID i = 0xA98381 *Jan 5 23:36:36.330: Called Party Number i = 0x80, '5250100000', Plan:Unknown, Type:Unknown *Jan 5 23:36:36.334:ISDN Se2/0/-1:TX -> CALL_PROC pd = 8 callref = 0x8002 *Jan 5 23:36:36.334: Channel ID i = 0xA98381 *Jan 5 23:36:36.334:%LINK-3-UPDOWN:Interface Serial2/0:0, changed state to up *Jan 5 23:36:36.334:%ISDN-6-CONNECT:Interface Serial2/0:0 is now connected to 42501 *Jan 5 23:36:36.338:ISDN Se2/0/-1:TX -> CONNECT pd = 8 callref = 0x8002 *Jan 5 23:36:36.338: Channel ID i = 0xA98381 *Jan 5 23:36:36.498:ISDN Se2/0/-1:RX <- CONNECT_ACK pd = 8 callref = 0x0002 *Jan 5 23:36:36.498:ISDN Se2/0/-1:CALL_PROGRESS:CALL_CONNECTED call id 0x5D26, bchan -1, dsl 0 *Jan 5 23:36:37.758:%LINEPROTO-5-UPDOWN:Line protocol on Interface Serial2/0:0, changed state to up *Jan 5 23:36:42.338:%ISDN-6-CONNECT:Interface Serial2/0:0 is now connected to 42501 5300_t1_15400#no debug isdn q931
| Message | Description |
|---|---|
| Indicates this message is being transmitted from the local router (user side) to the network side of the ISDN interface. |
| Indicates this message is being received by the user side of the ISDN interface from the network side. |
| Indicates the SETUP message has been sent to initiate call establishment between peer network layers. The message can be sent from the local router or network. |
| Indicates the protocol discriminator. The protocol discriminator distinguishes messages for call control over the user-network ISDN interface from other ITU-T1-defined messages, including other Q.931 messages. The protocol discriminator is 8 for call control messages such as SETUP. |
| Indicates the call reference number in hexadecimal. The field value indicates the number of calls made from the router (outgoing calls) or the network (incoming calls). Note that the originator of the SETUP message sets the high-order bit of the call reference number to 0. The destination of the connection sets the high-order bit to 1 in subsequent call control messages, such as the CONNECT message. For example, callref = 0x04 in the request becomes callref = 0x84 in the response. |
| Indicates the requested bearer service to be provided by the network. |
| Indicates the Information Element Identifier. The value depends on the field it is associated with. Refer to the ITU-T Q.931 specification for details about the possible values associated with each field for which this identifier is relevant. |
| Indicates the Channel Identifier. The value 83 indicates any channel, 89 indicates the B1 channel, and 8A indicates the B2 channel. For more information about the Channel Identifier, refer to ITU-T Q.931. |
| Identifies the called party. This field is only present in outgoing SETUP messages. It can be replaced by the Keypad facility field. This field uses the IA5 character set. |
| Indicates that the sending equipment will release the channel and call reference. The recipient of this message should prepare to release the call reference and channel. |
| Indicates that the sending equipment has received a RELEASE message and has now released the call reference and channel. |
| 1ITU-T = International Telecommunication Union Telecommunication Standardization Sector. |
R2 signaling is an international signaling standard that is common to channelized E1 networks. You can configure a channelized E1 interface to support different types of R2 signaling, which is used in older analog telephone networks.
![]() |
Note The Cisco implementation of R2 signaling has DNIS support turned on by default. If you enable the ANI option, the collection of DNIS information is still performed. Specifying the ANI option does not disable DNIS collection. DNIS is the number being called. ANI is the caller's number. For example, if you are configuring router A to call router B, then the DNIS number is assigned to router B, the ANI number is assigned to router A. Also, note that ANI is similar to Caller ID. |
Command | Purpose | |||
|---|---|---|---|---|
| 5400>enable Password: |
| ||
| 5400#configure terminal Enter configuration commands, one per line. End |
| ||
| 5400(config)#controller e1 0/0 5400(config-controller)# |
| ||
| 5400(config-controller)#ds0-group 1 timeslots |
| ||
| 5400(config-controller-cas)#cas-custom 1 |
| ||
| 5400(config-ctrl-cas)#country country use-default |
| ||
| 5400(config-ctrl-cas)#answer-signal group-b 6 [or] 5400(config-ctrl-cas)# default answer-signal |
After you configure a country with default settings, the Cisco AS5400 displays a write term, similar to the one displayed here. | ||
| 5400(config-if)#Ctrl-Z 5400# |
|
Table 3-6 lists the country codes supported for R2 signaling.
.
| Country | Code |
|---|---|
Argentina | argentina |
Australia | australia |
Brazil | brazil |
China | china |
Columbia | columbia |
Costa Rica | costarica |
East Europe (includes Croatia, Russia, and Slovak Republic) | easteurope |
Ecuador ITU | ecuador-itu |
Ecuador LME | ecuador-lme |
Greece | greece |
Guatemala | guatemala |
Hong Kong (China variant) | hongkong-china |
Indonesia | indonesia |
Israel | israel |
ITU (default) | itu |
Korea | korea |
Malaysia | malaysia |
New Zealand | newzealand |
Paraguay | paraguay |
Peru | peru |
Philippines | philippines |
Saudi Arabia | saudiarabia |
Singapore | singapore |
South Africa Panafte | southafrica-panaftel l |
Telmex (a telephone corporation in Mexico) | telmex |
Telnor (a telephone corporation in Norway) | telnor |
Thailand | thailand |
Uruguay | uruguay |
Venezuela | venezuela |
Vietnam | vietnam |
To verify your R2 signaling configuration:
5400# show controller e1 0/0
E1 0/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
Version info of Slot 0: HW: 2, Firmware: 4, PLD Rev: 2
Manufacture Cookie is not programmed.
Framing is CRC4, Line Code is HDB3, Clock Source is Line Primary.
Data in current interval (785 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 13 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 12 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 12 Unavail Secs
![]() |
Tips If the connection does not go up, check the following: |
If you see errors on the line or the line is going up and down, check the following:
When the E1 controller comes up, you will see the following message:
%CONTROLLER-3-UPDOWN: Controller E1 0, changed state to up
The Time-Division Multiplexing (TDM) bus on the Cisco AS5400 backplane can receive an input clock from one of four basic sources on the Cisco AS5400:
The TDM bus can be synchronized with any DFC cards. On the 8PRI CT1/CE1 DFC, each port receives clock from the T1/E1 line. The CT3 DFC uses an M13 multiplexer to receive the DS1 clock. Each port on each DFC trunk slot has a default clock priority. Also, clock priority is configurable through the dial-tdm-clock priority CLI command.
The TDM bus can be synchronized with an external clock source that can be used as an additional network reference. If no clocks are configured, the system will use a primary clock through a software-controlled default algorithm. If you want the external clock as the primary clock source, you must configure it using the dial-tdm-clock priority CLI command; the external clock is never selected by default.
If there is no good clocking source from a DFC card or an external clock source, then the free running clock from the local osciallator is used through the dial-tdm-clock priority CLI command.
The following table lists commands to help you configure the clock source and clock source priority used by the TDM bus:
Command | Purpose | |||
|---|---|---|---|---|
|
|
| ||
|
|
| ||
|
| |||
a. |
|
| ||
b. |
|
| ||
|
|
| ||
|
|
|
In the following example, BITS clock is set at priority 1.
5400(config)# dial-tdm-clock priority 1 external 5400(config)# exit 5400#
In the following example, a trunk clock from an 8 PRI CT1 DFC is set at priority 2 and uses slot 4 and ds1 port (controller) 6.
5400(config)# dial-tdm-clock priority 2 4/6 5400(config)# exit
In the following example, a trunk clock from a CT3 DFC is set at priority 2 and uses slot 1, ds3 port 0, and ds1 port 19.
5400(config)# dial-tdm-clock priority 2 1/0/:19 5400(config)# exit
In the following example, free running clock is set at priority 3.
5400(config)# dial-tdm-clock priority 3 free 5400(config)# exit
You can verify the system primary and backup clocks; status of all trunk DFC controller clocks; information and history of last 20 TDM clock changes and the events that caused them.
5400# show tdm clocks Primary Clock: System primary is slot 2 port 0 of priority 204 TDM Bus Master Clock Generator State = NORMAL Backup clocks for primary: Source Slot Port DS3-Port Priority Status State Trunk 2 1 NO 205 Good Default Trunk cards controllers clock health information Slot Type 7 6 5 4 3 2 1 0 2 T1 B B B B G G G G 5400#
5400# sh tdm clock
Primary Clock:
--------------
System primary is slot 7 ds3_port 0 ds1_port 1 of priority 1
TDM Bus Master Clock Generator State = NORMAL
Backup clocks for primary:
Source Slot Port DS3-Port Priority Status State
-------------------------------------------------------------
Trunk 7 8 YES 214 Good Default
Trunk 7 9 YES 215 Good Default
Trunk cards controllers clock health information
------------------------------------------------
CT3 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
Slot Port Type 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1
7 0 T3 G G G G G G G G G G G G G G G G G G G G G G G G G G G G
CLOCK CHANGE HISTORY
--------------------------
CLOCK Event Time
----- ----- ----
7/1 Signal recovered from LOS 00:03:29 UTC Sat Jan 1 2000
7/8 Alarm Indication Signal (AIS) 11:27:48 UTC Fri Feb 25 2000
7/1 Signal recovered from LOS 11:30:22 UTC Fri Feb 25 2000
Verify your user configured trunk clock selection using the show tdm clocks command:
5400# show tdm clocks
Primary Clock:
System primary is slot 2 port 0 of priority 15
TDM Bus Master Clock Generator State = NORMAL
Backup clocks for primary:
Source Slot Port DS3-Port Priority Status State
Trunk 2 1 NO 205 Good Default
Trunk cards controllers clock health information
Slot Type 7 6 5 4 3 2 1 0
2 T1 B B B B G G G G
CLOCK CHANGE HISTORY
CLOCK Event Time
2/1 Controller shutdown 23:23:06 UTC Tue Nov 30 1999
2/0 Change in CLI configuration 23:27:25 UTC Tue Nov 30 1999
5400#
5400# show tdm clocks Primary Clock: System primary is FREE RUNNING with priority 2 TDM Bus Master Clock Generator State = FREERUN Backup clocks for primary: Source Slot Port DS3-Port Priority Status State Trunk 2 0 NO 204 Good Default Trunk 2 1 NO 205 Good Default Trunk cards controllers clock health information Slot Type 7 6 5 4 3 2 1 0 2 T1 B B B B G G G G CLOCK CHANGE HISTORY CLOCK Event Time Freerun Change in CLI configuration 23:27:25 UTC Tue Nov 30 1999 5400#
5400# show tdm clocks Primary Clock: System primary is external with priority 1 TDM Bus Master Clock Generator State = NORMAL Backup clocks for primary: Source Slot Port DS3-Port Priority Status State Trunk 2 0 NO 204 Good Default Trunk 2 1 NO 205 Good Default Trunk cards controllers clock health information Slot Type 7 6 5 4 3 2 1 0 2 T1 B B B B G G G G CLOCK CHANGE HISTORY CLOCK Event Time External Change in CLI configuration 23:27:25 UTC Tue Nov 30 1999 5400#
You can assign the asynchronous interfaces to a group so that you can configure them as a group, instead of individually.
![]() |
TimeSaver Because there are so many asynchronous interfaces on the access server, configuring them as a group will save you time. |
To verify your group interface configuration:
5400# show interface async 6/50
Async6/50 is up, line protocol is up
modem(slot/port)=6/50, state=CONNECTED
dsx1(slot/unit/channel)=3/2/13,
status=VDEV_STATUS_ACTIVE_CALL.VDEV_STATUS_ALL
OCATED.
Hardware is Async Serial
Interface is unnumbered. Using address of FastEthernet0/0 (192.168.10.100)
MTU 1500 bytes, BW 115 Kbit, DLY 100000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Keepalive not set
DTR is pulsed for 5 seconds on reset
LCP Open
Open:IPCP
Last input 00:00:41, output 00:01:27, output hang never
Last clearing of "show interface" counters 00:30:37
Input queue:1/10/0 (size/max/drops); Total output drops:0
Queueing strategy:weighted fair
Output queue:0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/1/32 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
135 packets input, 6621 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
1 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
10 packets output, 250 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
5400# show dialer maps Dynamic dialer map ip 10.2.1.1 name customer1 () on As4/87 Static dialer map ip 21.0.0.2 name customer2 (22222) on Se3/3:23
![]() |
Tips If you are having trouble: |
5400# show async status
Async protocol statistics:
Int Local Remote Qd InPack OutPac Inerr Drops MTU
1/00 42.1.1.1 None 0 0 0 0 0 1500
1/01 192.168.10.100 None 0 0 0 0 0 1500
1/02 192.168.10.100 None 0 0 0 0 0 1500
1/03 192.168.10.100 None 0 0 0 0 0 1500
1/04 192.168.10.100 None 0 0 0 0 0 1500
1/05 192.168.10.100 None 0 0 0 0 0 1500
4/52 192.168.10.100 None 0 0 0 0 0 1500
.
.
.
*6/00 192.168.10.100 34.6.42.1 0 130 50 5 0 1500
*6/01 192.168.10.100 34.6.92.1 0 131 53 5 0 1500
*6/02 192.168.10.100 34.5.92.1 0 130 50 5 0 1500
*6/03 192.168.10.100 34.4.14.1 0 116 40 4 0 1500
.
.
.
*7/102 192.168.10.100 34.1.89.1 0 119 40 4 0 1500
*7/103 192.168.10.100 34.4.34.1 0 118 40 4 0 1500
*7/104 192.168.10.100 34.1.67.1 0 105 40 4 0 1500
7/105 192.168.10.100 None 0 0 0 0 0 1500
*7/106 192.168.10.100 34.4.90.1 0 119 40 4 0 1500
*7/107 192.168.10.100 34.1.42.1 0 119 40 4 0 1500
Rcvd: 25762 packets, 1052214 bytes
0 format errors, 891 checksum errors, 0 overrun
Sent: 8891 packets, 222264 bytes, 0 dropped
5400# debug ppp negotiation PPP protocol negotiation debugging is on 5400# Feb 9 10:25:29.347:%LINK-3-UPDOWN:Interface Async1/00, changed state to up Feb 9 10:25:29.347:As1/00 PPP:Treating connection as a dedicated line Feb 9 10:25:29.347:As1/00 PPP:Phase is ESTABLISHING, Active Open Feb 9 10:25:29.347:As1/00 LCP:O CONFREQ [Closed] id 15 len 25 Feb 9 10:25:29.347:As1/00 LCP: ACCM 0x000A0000 (0x0206000A0000) Feb 9 10:25:29.347:As1/00 LCP: AuthProto CHAP (0x0305C22305) Feb 9 10:25:29.347:As1/00 LCP: MagicNumber 0x34D02CF0 (0x050634D02CF0) Feb 9 10:25:29.347:As1/00 LCP: PFC (0x0702) Feb 9 10:25:29.347:As1/00 LCP: ACFC (0x0802) Feb 9 10:25:29.359:As1/00 LCP:I CONFREQ [REQsent] id 17 len 20 Feb 9 10:25:29.359:As1/00 LCP: ACCM 0x000A0000 (0x0206000A0000) Feb 9 10:25:29.359:As1/00 LCP: MagicNumber 0xD48B83AC (0x0506D48B83AC) . . . Feb 9 10:25:31.787:As1/00 IPCP:State is Open Feb 9 10:25:31.791:As1/00 IPCP:Install route to 160.1.1.1 Feb 9 10:25:32.651:%LINEPROTO-5-UPDOWN:Line protocol on Interface Async1/00, changed state to up 5400# no debug ppp negotiation 5400# debug ppp authentication Feb 9 10:27:58.923:As1/01 PPP:Treating connection as a dedicated line Feb 9 10:27:58.923:%LINK-3-UPDOWN:Interface Async1/01, changed state to up Feb 9 10:27:59.063:As1/01 CHAP:O CHALLENGE id 6 len 32 from "CT3-CAS-UUT" Feb 9 10:27:59.199:As1/01 CHAP:I RESPONSE id 6 len 30 from "ELNINO-N3" Feb 9 10:27:59.203:As1/01 CHAP:O SUCCESS id 6 len 4 Feb 9 10:28:00.203:%LINEPROTO-5-UPDOWN:Line protocol on Interface Async1/01, changed state to up 5400# no debug ppp authentication . . .
Rather than the more traditional line/modem one-to-one correspondence, lines are mapped to a Service Process Element (SPE) that resides on the NextPort DFC (also referred to as the AS54-DFC-108NP). Associated SPE firmware serves a function similar to modem code on a MICA modem.
One SPE provides modem services for six ports, with additional ports per SPE. Busyout and shutdown can be configured at the SPE or port level. The NextPort DFCs available for the Cisco AS5400 provide 18 SPEs for a total of 108 ports per DFC.
The Cisco AS5400 NextPort DFC performs the following functions:
![]() |
Note This release supports modem and digital service types only. For further information in this document, refer to "Managing and Troubleshooting the NextPort Dial Feature Card." For detailed information about NextPort Cisco IOS CLI commands, refer to the NextPort Port Service Management for Cisco AS5400 Universal Access Server. |
SPE firmware is automatically downloaded to a NextPort DFC from the Cisco AS5400 when you boot the system for the first time or when you insert a NextPort DFC while the system is operating. When you insert DFCs while the system is operating, the Cisco IOS image recognizes the cards and downloads the required firmware to the cards.
The SPE firmware image is bundled with the access server Cisco IOS image. The SPE firmware image uses an auto detect mechanism, which enables the NextPort DFC to service multiple call types. An SPE detects the call type and automatically configures itself for that operation. The firmware is upgradeable independent of Cisco IOS upgrades, and different firmware versions can be configured to run on SPEs in the same DFC.
The NextPort DFC supports the modem standards and features listed in Table 3-7.
| Feature | Description |
|---|---|
Carrier protocols | ITU V.23 at 75/1200 bps Telcordia Technologies (formerly Bellcore) 103 at 300 bps ITU V.21 at 300 bps ITU V.22 at 1200 bps Telcordia Technologies (formerly Bellcore) 212A at 1200 bps ITU V.22bis at 2400 bps ITU V.32 up to 9600 bps ITU V.32bis up to 14,400 bps V.32 turbo up to 19,200 bps V.FC up to 28,800 bps V.34 up to 28,800 bps V.34+ up to 33.6 bps TIA/ITU V.90 K56flex |
Error-correcting link-access protocols | V.42 LAPM, MNP 2-4 |
Compression protocols | V.42bis (includes MNP 5) |
Command interface | Superset of the AT command set |
In-band signaling/tone generation and detection | DTMF generation DTMF detection MF generation MF detection |
Other | Out-of-band access for management PPP and SLIP framing |
Configure the lines and ports to allow users to dial in to your network.
Command | Purpose | |||
|---|---|---|---|---|
|
|
| ||
|
|
| ||
|
|
| ||
|
|
| ||
|
| |||
|
|
| ||
|
| |||
|
|
|
![]() |
Note You may optionally use the modem autoconfigure type name line configuration command to configure the attached modem using the entry for name. |
To reset to default settings for country codes, enter the following commands in global configuration mode:
To verify your SPE configuration:
5400# show spe SPE settings: ============== Country code configuration: default T1 (u Law) Polling interval: 12 secs. History log events: 50(per port) SPE# Port Range State Crash Busy Shut 4/00 0000-0005 ACTIVE 0 0 0 4/01 0006-0011 ACTIVE 0 0 0 4/02 0012-0017 ACTIVE 0 0 0 4/03 0018-0023 ACTIVE 0 0 0 4/04 0024-0029 ACTIVE 0 0 0 4/05 0030-0035 ACTIVE 0 0 0 4/06 0036-0041 ACTIVE 0 0 0 4/07 0042-0047 ACTIVE 0 0 0 4/08 0048-0053 ACTIVE 0 0 0 4/09 0054-0059 ACTIVE 0 0 0 4/10 0060-0065 ACTIVE 0 0 0 4/11 0066-0071 ACTIVE 0 0 0 4/12 0072-0077 ACTIVE 0 0 0 4/13 0078-0083 ACTIVE 0 0 0 4/14 0084-0089 ACTIVE 0 0 0 4/15 0090-0095 ACTIVE 0 0 0 4/16 0096-0101 ACTIVE 0 0 0 4/17 0102-0107 ACTIVE 0 0 0
5400# show line 1
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int
1 AUX 9600/9600 - - - - - 0 0 0/0 -
Ready
Line 1, Location: "", Type: ""
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600, no parity, 2 stopbits, 8 databits
Status: Ready
Capabilities: none
Modem state: Ready
Group codes: 0
Modem hardware state: noCTS noDSR DTR RTS
TTY NUMBER 1
Parity Error = 0 Framing Error = 0 Receive Error = 0 Overrun = 0
Outcount = 0 totalout = 39 incount = 0 totalin = 0
Special Chars: Escape Hold Stop Start Disconnect Activation
^^x none - - none
Timeouts: Idle EXEC Idle Session Modem Answer Session Dispatch
00:10:00 never none not set
Idle Session Disconnect Warning
never
Login-sequence User Response
![]() |
Tips If you are having trouble, make sure you turned on the protocols for connecting to the lines (transport input all) and configured for incoming and outgoing calls (modem inout). |
To prevent the loss of the access server configuration, save it to NVRAM.
Command | Purpose | |
|---|---|---|
| 5400>enable Password: password 5400# |
|
| 5400#copy running-config startup-config |
|
| 5400(config-if)#Ctrl-Z 5400# |
|
At this point you can go to:
![]() |
Tips The following publications are available on the Documentation CD-ROM that came with your access server, on the World Wide Web from Cisco's home page, or you can order printed copies. |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Aug 15 10:44:31 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.