Table Of Contents
ISDN Basic Rate Service Setup Commands
interface bri
Syntax Description
Default
Command Mode
Usage Guidelines
Example
Related Commands
isdn answer1, isdn answer2
Syntax Description
Default
Command Mode
Usage Guidelines
Examples
isdn caller
Syntax Description
Default
Command Mode
Usage Guidelines
Examples
Related Commands
isdn calling-number
Syntax Description
Default
Command Mode
Usage Guidelines
Example
Related Commands
isdn fast-rollover-delay
Syntax Description
Default
Command Mode
Usage Guidelines
Example
Related Commands
isdn incoming-voice data
Syntax Description
Default
Command Mode
Usage Guidelines
Example
isdn negotiate-bchan
Syntax Description
Default
Command Mode
Usage Guidelines
Example
Related Commands
isdn not-end-to-end
Syntax Description
Default
Command Mode
Usage Guidelines
Example
isdn sending-complete
Syntax Description
Default
Command Mode
Usage Guidelines
Example
isdn spid1
Syntax Description
Default
Command Mode
Usage Guidelines
Example
isdn spid2
Syntax Description
Default
Command Mode
Usage Guidelines
Example
isdn switch-type
Syntax Description
Default
Command Mode
Usage Guidelines
Examples
isdn tei
Syntax Description
Default
Command Mode
Usage Guidelines
Example
isdn twait-disable
Syntax Description
Default
Command Mode
Usage Guidelines
Example
show controllers bri
Syntax Description
Command Mode
Usage Guidelines
Sample Display
show dialer interface bri
Syntax Description
Command Mode
Usage Guidelines
Sample Displays
show interfaces bri
Syntax Description
Command Mode
Usage Guidelines
Sample Displays
show isdn
Syntax Description
Command Mode
Sample Displays
ISDN Basic Rate Service Setup Commands
This chapter describes the commands available to configure ISDN basic rate interfaces for dial-up solutions on your router.
For configuration tasks and examples to get the ISDN line up and running, see the "Setting Up ISDN Basic Rate Service" chapter of the Dial Solutions Configuration Guide. To complete the configuration for dial-in or dial-out routing or bridging, see the relevant chapters in the "Dial-on-Demand Routing" part of the Dial Solutions Configuration Guide.
interface bri
To configure a Basic Rate Interface (BRI) interface and enter interface configuration mode, use the interface bri global configuration command.
interface bri number
interface bri slot/port (Cisco 7200 series)
To configure a BRI subinterface only, use the following form of the interface bri global configuration command:
interface bri number.subinterface-number [multipoint | point-to-point]
interface bri slot/port.subinterface-number [multipoint | point-to-point] (Cisco 7200 series)
Syntax Description
number
|
Port, connector, or interface card number. The numbers are assigned at the factory at the time of installation or when added to a system, and can be displayed with the show interfaces command.
|
slot/port
|
Backplane slot number and port number on the interface. See your hardware installation manual for the specific slot and port numbers.
|
.subinterface-number
|
Subinterface number in the range 1 to 4294967293. The number or slot/port that precedes the period (.) must match that of the interface this subinterface belongs to.
|
multipoint | point-to-point
|
(Optional) Specifies a multipoint or point-to-point subinterface. The default is multipoint.
|
Default
The default mode for subinterfaces is multipoint.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command was modified in Cisco IOS Release 11.2 P to include slot/port syntax for the PA-8B-ST and PA-4B-U port adapters on Cisco 7200 series routers.
Subinterfaces can be configured to support partially meshed Frame Relay networks. (Refer to the "Configuring Frame Relay" chapter in the Wide-Area Networking Configuration Guide.)
Example
The following example configures BRI 0 to call and receive calls from two sites, use Point-to-Point Protocol (PPP) encapsulation on outgoing calls, and use Challenge Handshake Authentication Protocol (CHAP) authentication on incoming calls:
dialer map ip 131.108.36.10 name EB1 234
dialer map ip 131.108 36.9 name EB2 456
isdn spid1 41346334600101 4633460
isdn spid2 41346334610101 4633461
Related Commands
You can use the master indexes or search online to find documentation of related commands.
dialer map
dialer-group
encapsulation ppp
isdn spid1
isdn spid2
ppp authentication chap
ppp authentication pap
show interfaces bri
isdn answer1, isdn answer2
To have the router verify a called-party number or subaddress number in the incoming setup message for ISDN BRI calls, if the number is delivered by the switch, use the isdn answer1 interface configuration command. To remove the verification request, use the no form of this command.
isdn answer1 [called-party-number][:subaddress]
no isdn answer1 [called-party-number][:subaddress]
To have the router verify an additional called-party number or subaddress number in the incoming setup message for ISDN BRI calls, if the number is delivered by the switch, use the isdn answer2 interface configuration command. To remove this second verification request, use the no form of this command.
isdn answer2 [called-party-number][:subaddress]
no isdn answer2 [called-party-number][:subaddress]
Syntax Description
called-party-number
|
(Optional) Telephone number of the called party. At least one value—called-party-number or subaddress—must be specified.
|
:
|
Identifies the number that follows as a subaddress. Use the colon (:) when you configure both the called party number and the subaddress, or when you configure only the subaddress.
|
subaddress
|
(Optional) Subaddress number, 20 or fewer characters long, used for ISDN multipoint connections. At least one value—called-party-number or subaddress—must be specified.
|
Default
The router does not verify the called-party or subaddress number.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
If you do not specify the isdn answer1 or isdn answer2 command, all calls are processed and/or accepted. If you specify the isdn answer1 or isdn answer2 command, the router must verify the incoming called-party number and the subaddress before processing and/or accepting the call. The verification proceeds from right to left for the called-party number; it also proceeds from right to left for the subaddress number.
You can configure just the called-party number or just the subaddress. In such a case, only that part is verified. To configure a subaddress only, include the colon (:) before the subaddress number.
You can declare a digit a "don't care" digit by configuring it as an x or X. In such a case, any incoming digit is allowed.
Examples
In the following example, 5552222 is the called-party number and 1234 is the subaddress:
isdn answer1 5552222:1234
In the following example, only the subaddress is configured:
isdn caller
To configure ISDN caller ID screening, use the isdn caller interface configuration command. To disable ISDN caller ID screening, use the no form of this command.
isdn caller number
no isdn caller number
Syntax Description
number
|
Telephone number for which to screen. Specify an x to represent a single "don't-care" character. The maximum length of each number is 25 characters.
|
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command configures the router to accept calls from the specified number.
Caller ID screening is available on Cisco platforms that have one or more BRIs.
Note
Caller ID screening requires a local switch that is capable of delivering the caller ID to the router. If you enable caller ID screening but do not have such a switch, no calls are allowed in.
Examples
The following example configures the router to accept a call with a delivered caller ID equal to 4155551234:
The following example configures the router to accept a call with a delivered caller ID having 41555512 and any numbers in the last two positions:
Related Commands
You can use the master indexes or search online to find documentation of related commands.
show dialer
isdn calling-number
To configure an ISDN BRI interface to present the calling number of the device making the outgoing call, use the isdn calling-number interface configuration command. To remove a previously configured calling number, use the no form of this command.
isdn calling-number calling-number
no isdn calling number
Syntax Description
calling-number
|
Number of the device making the outgoing call; only one entry is allowed, and it is limited to 16 digits.
|
Default
No calling number is presented.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
An interface can have only one ISDN calling-number entry.
This command is intended for use when the ISDN network offers TS014 tariffing, in which devices present the calling (billing) number.
Note
This command cannot be used with German 1TR6 ISDN BRI switches. It can be used with all other switches.
Example
In the following example, the ISDN BRI interface is configured to present the number 5551212 when it makes outgoing calls:
isdn calling-number 5551212
Related Commands
You can use the master indexes or search online to find documentation of related commands.
interface bri
isdn fast-rollover-delay
To control the timing between successive attempts, use the isdn fast-rollover-delay interface configuration command. Use the no form of this command to remove or change a value.
isdn fast-rollover-delay seconds
no isdn fast-rollover-delay
Syntax Description
seconds
|
Number of seconds between dial attempts.
|
Default
No default timer.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
This command provides a timer separate from the dialer wait-for-carrier timer to control the amount of time that elapses before calls are redialed. This delay is provided to allow the old call to be torn down completely before the new call is attempted.
This command is necessary on some ISDN switches because the new call may be attempted before the old call is completely torn down. This causes the second call or the call back to fail.
Use this command when all the following conditions are true:
•
A BRI has two phone numbers configured, one for each B-channel.
•
You are dialing into this BRI.
•
You have a dialer map or dialer string for each phone number.
•
The first call succeeds but the second call continuously fails.
If this has occurred, set isdn fast-rollover-delay to 5 seconds and try again.
When these conditions occur, set the isdn fast-rollover-delay command to 5 seconds and try again. A delay of 5 seconds should cover most cases. Configure sufficient delay to make sure the ISDN RELEASE_COMPLETE message has been sent or received before making the fast rollover call. Use the debug isdn q931 command to display this information.
When the isdn fast-rollover-delay command is configured on a client requesting callback, the callback client first confirms whether or not the callback server has placed a call back to the callback client before dialing any subsequent numbers.
Example
The following partial example sets the fast-rollover delay that is suggested when all the conditions specified above are true.
isdn fast-rollover-delay 5
Related Commands
You can use the master indexes or search online to find documentation of related commands.
dialer map
dialer wait-for-carrier
ppp callback
isdn incoming-voice data
To answer incoming voice calls at a configured rate (overriding the incoming data rate in the call), use the isdn incoming-voice data interface configuration command. Use the no form of this command to remove the configured incoming data rate.
isdn incoming-voice data [56 | 64]
no isdn incoming-voice data
Syntax Description
56
|
(Optional) Answers all voice calls at 56 kbps.
|
64
|
(Optional) Answers all voice calls at 64 kbps.
|
Default
Isdn incoming-voice data is not applied.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
When used without a keyword, this command checks the bearer capacity.
If this command is used, the dialing side must dial at 56 kbps.
Ordinarily, a data device ignores incoming voice calls, but the tariff structure for data and voice calls might make "data over voice" calls less expensive.
Example
The following example configures BRI interface 0 to answer all incoming voice calls at 56 kbps:
isdn incoming-voice data 56
isdn negotiate-bchan
To enable the router to accept a B channel that is different from the B channel requested in the outgoing call setup message, use the isdn negotiate-bchan interface configuration command. To restore the default condition, use the no form of this command.
isdn negotiate-bchan
no isdn negotiate-bchan
Syntax Description
This command has no arguments or keywords.
Default
B-channel negotiation is not enabled. Most PRI switch types set the default channel ID to Exclusive in the setup message.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3.
The isdn negotiate-bchan command enables the router to negotiate the B channel by setting the channel ID information element to Preferred in the setup message. If this command is not configured, the channel ID is set to the default of the switch, which is usually Exclusive. Exclusive means that only the requested B channel is accepted; if the requested B channel is not available, the call is cleared.
The isdn negotiate-bchan command is supported for all PRI switch types.
Example
The following example enables an alternate B channel for serial interface 0:23:
Related Commands
isdn bchan-number-order
isdn switch-type (PRI)
isdn not-end-to-end
For incoming calls, to override the speed that the network reports it will use to deliver the call data, use the isdn not-end-to-end interface configuration command. Use the no form of this command to disable the configured end-to-end speed.
isdn not-end-to-end {56 | 64}
no isdn not-end-to-end
Syntax Description
56
|
Answers all voice calls at 56 kbps.
|
64
|
Answers all voice calls at 64 kbps.
|
Default
The default line speed is 64 kbps.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command might be needed to handle incoming calls properly. Although a call might originate at a speed of 56 kbps, the network or internetworking networks might improperly deliver the call to the user at a speed of 64 kbps. This creates a speed mismatch and causes the data to be garbled. Enabling this command makes the router look more closely at the information elements of the incoming call to determine a speed.
A speed mismatch can occur when the source and destination ISDN ports do not belong to the same network.
Example
The following example sets the line speed for incoming calls to 56 kbps:
isdn sending-complete
To specify that the Sending Complete information element (IE) is included in the outgoing Setup message, use the isdn sending-complete interface configuration command. Use the no form of this command to disable the Sending Complete information element.
isdn sending-complete
no isdn sending-complete
Syntax Description
This command has no arguments and keywords.
Default
This command is disabled by default.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
Some switches in some countries want a Sending Complete information element to be included in the outgoing Setup message to indicate that the entire number is included. The Sending Complete IE is required in Hong Kong and Taiwan, and the isdn sending-complete command forces it to be sent.
Example
In the following example, the isdn sending-complete command applies to an ISDN BRI interface:
description connected to PBX 61886
ip address 172.1.1.1 255.255.255.0
dialer map ip 172.1.1.2 name rudder 61884
dialer map ip 172.1.1.3 name bosun 61885
isdn spid1
Use the isdn spid1 interface configuration command on the router to define the service profile identifier (SPID) number that has been assigned by the ISDN service provider for the B1 channel. Use the no form of this command to disable the specified SPID, thereby preventing access to the switch.
isdn spid1 spid-number [ldn]
no isdn spid1 spid-number [ldn]
Syntax Description
spid-number
|
Number identifying the service to which you have subscribed. This value is assigned by the ISDN service provider and is usually a 10-digit telephone number with additional digits.
|
ldn
|
(Optional) Local directory number (LDN), which is a 7-digit number assigned by the service provider. This information is delivered by the switch in the incoming setup message.
If you include the local directory number in the no form of this command, access to the switch is permitted, but the other B channel may not be able to receive incoming calls.
|
Default
No SPID number is defined.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command is required for DMS-100 and National ISDN switches only.
Typically, DMS-100 and National ISDN switch implementations using BRI interfaces with SPIDS require two two TEIs, two SPIDS, and two phone numbers. If you want to take advantage of both B channels, it is advised you configure the router with the LDN value after the SPID.
The ISDN switch checks for the LDN to determine whether both channels can be used to transmit and receive data. If there isn't an LDN present, then only the B1 channel can be used for full-duplex communication. However, the B2 channel can still be used to make outgoing calls.
Note
Some DMS-100 and National ISDN switch installations may be configured as a "hunt group" whereby all calls are initially forwarded to the primary number. Under these circumstances, you should not configure the LDN. You can determine this by enabling the debug isdn q931 command. If the end point identifier (EID) information element is delivered in the incoming setup message, then the switch is addressing the TEIs with the EID, instead of the LDN.
Example
The following example defines, on the router, a SPID and LDN for the B1 channel:
isdn spid1 41555512130101 5551213
isdn spid2
Use the isdn spid2 interface configuration command on the router to define the service profile identifier (SPID) number that has been assigned by the ISDN service provider for the B1 channel. Use the no form of this command to disable the specified SPID, thereby preventing access to the switch.
isdn spid2 spid-number [ldn]
no isdn spid2 spid-number [ldn]
Syntax Description
spid-number
|
Number identifying the service to which you have subscribed. This value is assigned by the ISDN service provider and is usually a 10-digit telephone number with additional digits.
|
ldn
|
(Optional) Local directory number (LDN), which is a 7-digit number assigned by the service provider. This information is delivered by the switch in the incoming setup message.
If you include the local directory number in the no form of this command, access to the switch is permitted, but the other B channel may not be able to receive incoming calls.
|
Default
No SPID number is defined.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command is required DMS-100 and National ISDN switches only.
Typically, DMS-100 and National ISDN switch implementations using BRI interfaces with SPIDS require two two TEIs, two SPIDS, and two phone numbers. If you want to take advantage of both B channels, it is advised you configure the router with the LDN value after the SPID.
The ISDN switch checks for the LDN to determine whether both channels can be used to transmit and receive data. If there isn't an LDN present, then only the B1 channel can be used for full-duplex communication. However, the B2 channel can still be used to make outgoing calls.
Note
Some DMS-100 and National ISDN switch installations may be configured as a "hunt group" whereby all calls are initially forwarded to the primary number. Under these circumstances, you should not configure the LDN. You can determine this by enabling the debug isdn q931 command. If the end point identifier (EID) information element is delivered in the incoming setup message, then the switch is addressing the TEIs with the EID, instead of the LDN.
Example
The following example defines, on the router, a SPID and LDN for the B2 channel:
isdn spid2 41555512140101 5551214
isdn switch-type
To specify the central office switch type on the ISDN interface, use the isdn switch-type global and interface configuration command.
isdn switch-type switch-type
Syntax Description
switch-type
|
Service provider switch type; see Table 35 for a list of supported switches.
|
Default
The switch type defaults to none, which disables the switch on the ISDN interface.
Command Mode
Global and interface configuration
Usage Guidelines
This command first appeared as a global command in Cisco IOS Release 9.21
This command first appeared as an interface command in Cisco IOS Release 11.3T.
To disable the switch on the ISDN interface, specify isdn switch-type none.
lists supported BRI switch types by geographic area.
Note
If you are using the Multiple ISDN Switch Types feature to apply ISDN switch types to different interfaces, refer to the "Setting Up ISDN Basic Rate Service" chapter in the Dial Solutions Configuration Guide for additional details
Table 35 ISDN Service Provider BRI Switch Types
Keywords by Area
|
Switch Type
|
none
|
No switch defined
|
Australia and Europe
|
|
basic-1tr6
|
German 1TR6 ISDN switches
|
basic-net3
|
NET3 ISDN, Norway NET3, Australia NET3, and New Zealand NET3 switches (covers the Euro-ISDN E-DSS1 signaling system and is ETSI-compliant)
|
vn3
|
French VN3 and VN4 ISDN BRI switches
|
Japan
|
|
ntt
|
Japanese NTT ISDN switches
|
North America
|
|
basic-5ess
|
AT&T basic rate switches
|
basic-dms100
|
Northern Telecom DMS-100 basic rate switches
|
basic-ni
|
National ISDN switches
|
Note
Cisco IOS Release 11.3T introduced ISDN switch type changes. The command parser will still accept the following switch types: basic-nwnet3, vn2, and basic-net3; however, when viewing the NVRAM configuration, the basic-net3 or vn3 switch types are displayed respectively.
Examples
The first example configures the French VN3 ISDN switch type:
The following example uses the Multiple ISDN Switch Types feature and shows the global ISDN switch type of basic-ni (formerly basic-ni1) and an interface level switch type of basic-net3. ISDN switch type basic-net3 is applied to BRI interface 0 and overrides the global switch setting.
isdn switch-type basic-ni
!
interface BRI0
isdn switch-type basic-net3
isdn tei
To configure when Layer 2 becomes active and ISDN terminal endpoint identifier (TEI) negotiation occurs, use the isdn tei interface configuration and global configuration command. To remove TEI negotiation from an interface, use the no form of this command.
isdn tei [first-call | powerup]
no isdn tei
Syntax Description
first-call
|
(Optional) ISDN TEI negotiation should occur when the first ISDN call is placed or received.
|
powerup
|
(Optional) ISDN TEI negotiation should occur when the router is powered on.
|
Default
powerup
Command Mode
Interface configuration and global configuration
Usage Guidelines
This command first appeared as a global configuration command in Cisco IOS Release 9.21.
This command first appeared as an interface level configuration command in Cisco IOS Release 11.3 T.
This command is for BRI configuration only.
This command is useful for switches that may deactivate Layers 1 and 2 when there are no active calls or primary-dms100 switches which activate TEI when the first ISDN call is placed or received.
Example
The following example applies isdn tei first-call to BRI interface 0. BRI interface 1 will use isdn tei negotiation powerup, which is the default setting. Default settings do not appear in the router configuration.
isdn switch-type basic-net
!
interface bri0
! Configure the ISDN switch type on this interface and set TEI negotiation to
! first-call
isdn switch-type basic-ni
isdn tei first-call
! BRI interface 1 uses the default TEI negotiation value
interface bri1
isdn twait-disable
To delay a National ISDN BRI switch a random time before activating the Layer 2 interface when the switch starts up, use the isdn twait-disable interface configuration command.
isdn twait-disable
Syntax Description
This command has no arguments and keywords.
Default
This command is enabled by default.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared as a global configuration command in Cisco IOS Release 11.3.
This random-length delay prevents mass power failures from causing the network ISDN switches to be overwhelmed when power returns and all the devices startup at the same time.
The random delay is in the range 1 to 300 seconds.
Example
The following example configures a random wait period after a power failure:
show controllers bri
To display information about the ISDN Basic Rate Interface (BRI), use the show controllers bri privileged EXEC command.
show controllers bri number
show controllers bri slot/port (Cisco 7200 series)
Syntax Description
number
|
Interface number. The value is 0 through 7 if the router has one 8-port BRI network interface module (NIM), or 0 through 15 if the router has two 8-port BRI NIMs. Interface number values will vary, depending on the hardware platform used. The Cisco 3600 series router for example, can have up to 48 interfaces.
|
slot/port
|
Backplane slot number and port number on the interface. See your hardware installation manual for the specific slot and port numbers.
|
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command was modified in Cisco IOS Release 11.2 P to include slot/port syntax for the PA-8B-ST and PA-4B-U port adapters on Cisco 7200 series routers.
Sample Display
The following is sample output from the show controllers bri command:
Router# show controllers bri 0
idb 0x32089C, ds 0x3267D8, reset_mask 0x2
RX ring with 2 entries at 0x2101600 : Rxhead 0
00 pak=0x4122E8 ds=0x412444 status=D000 pak_size=0
01 pak=0x410C20 ds=0x410D7C status=F000 pak_size=0
TX ring with 1 entries at 0x2101640: tx_count = 0, tx_head = 0, tx_tail = 0
00 pak=0x000000 ds=0x000000 status=7C00 pak_size=0
0 missed datagrams, 0 overruns, 0 bad frame addresses
0 bad datagram encapsulations, 0 memory errors
idb 0x3224E8, ds 0x3268C8, reset_mask 0x0
RX ring with 8 entries at 0x2101400 : Rxhead 0
00 pak=0x421FC0 ds=0x42211C status=D000 pak_size=0
01 pak=0x4085E8 ds=0x408744 status=D000 pak_size=0
02 pak=0x422EF0 ds=0x42304C status=D000 pak_size=0
03 pak=0x4148E0 ds=0x414A3C status=D000 pak_size=0
04 pak=0x424D50 ds=0x424EAC status=D000 pak_size=0
05 pak=0x423688 ds=0x4237E4 status=D000 pak_size=0
06 pak=0x41AB98 ds=0x41ACF4 status=D000 pak_size=0
07 pak=0x41A400 ds=0x41A55C status=F000 pak_size=0
TX ring with 4 entries at 0x2101440: tx_count = 0, tx_head = 0, tx_tail = 0
00 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
01 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
02 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
03 pak=0x000000 ds=0x000000 status=7C00 pak_size=0
0 missed datagrams, 0 overruns, 0 bad frame addresses
0 bad datagram encapsulations, 0 memory errors
idb 0x324520, ds 0x3269B8, reset_mask 0x2
RX ring with 8 entries at 0x2101500 : Rxhead 0
00 pak=0x40FCF0 ds=0x40FE4C status=D000 pak_size=0
01 pak=0x40E628 ds=0x40E784 status=D000 pak_size=0
02 pak=0x40F558 ds=0x40F6B4 status=D000 pak_size=0
03 pak=0x413218 ds=0x413374 status=D000 pak_size=0
04 pak=0x40EDC0 ds=0x40EF1C status=D000 pak_size=0
05 pak=0x4113B8 ds=0x411514 status=D000 pak_size=0
06 pak=0x416ED8 ds=0x417034 status=D000 pak_size=0
07 pak=0x416740 ds=0x41689C status=F000 pak_size=0
TX ring with 4 entries at 0x2101540: tx_count = 0, tx_head = 0, tx_tail = 0
00 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
01 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
02 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
03 pak=0x000000 ds=0x000000 status=7C00 pak_size=0
0 missed datagrams, 0 overruns, 0 bad frame addresses
0 bad datagram encapsulations, 0 memory errors
describes the significant fields in the display.
Table 36 Show Controllers BRI Field Descriptions
Field
|
Description
|
BRI unit 0
|
Interface type and unit number.
|
Chan Info
|
D and B channel numbers.
|
Layer 1 is ACTIVATED
|
Status can be DEACTIVATED, PENDING ACTIVATION, or ACTIVATED.
|
idb ds reset_mask
|
Information about internal data structures and parameters.
|
buffer size
|
Number of bytes allocated for buffers.
|
RX ring with - entries at -
|
Information about the Receiver Queue.
|
Rxhead
|
Start of the Receiver Queue.
|
pak ds status pak_size
|
Information about internal data structures and parameters.
|
TX ring with - entries at -
|
Information about the Transmitter Queue.
|
tx_count
|
Number of packets to transmit.
|
tx_head
|
Start of the transmit list.
|
tx_tail
|
End of the transmit list.
|
missed datagrams
|
Incoming packets missed due to internal errors.
|
overruns
|
Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
bad frame addresses
|
Frames received with a cyclic redundancy check (CRC) error and noninteger number of octets.
|
bad datagram encapsulations
|
Packets received with bad encapsulation.
|
memory errors
|
Internal direct memory access (DMA) memory errors.
|
transmitter underruns
|
Number of times that the transmitter has been running faster than the router can handle.
|
The following is a partial sample output from the show controllers bri command on a Cisco 7200 series router:
BRI slot 2 interface 0 with integrated NT1
Layer 1 is ACTIVATED. (ISDN L1 State F7)
Master clock for slot 2 is bri interface 0.
Total chip configuration successes: 193, failures: 0, timeouts: 0
Channel state: UP Channel IDB: 6092AC64
RX ring entries: 5, buffer size 512
RX descriptor ring: head = 165F4D8, tail = 165F508
RX buffer ring: head = 6093A260, tail = 6093A290
00 params=0x2000000 status=0x0 data ptr=0x1650F84 next ptr=0x165F4D8
01 params=0x2000000 status=0xC0080000 data ptr=0x1651884 next ptr=0x165F4E8
02 params=0x2000000 status=0xC0080000 data ptr=0x1651644 next ptr=0x165F4F8
03 params=0x2000000 status=0x0 data ptr=0x1651404 next ptr=0x165F508
04 params=0x42000000 status=0x0 data ptr=0x16511C4 next ptr=0x165F4C8
TX ring entries: 5, in use: 0, buffer size 512
TX descriptor ring: head = 3C2049C0, tail = 3C2049C0
TX buffer ring: head = 608EC0C4, tail = 608EC0C4
00 params=0x80000000 data ptr=0x0000000 next ptr=0x4D0049A8
01 params=0x80000000 data ptr=0x0000000 next ptr=0x4D0049B4
02 params=0x80000000 data ptr=0x0000000 next ptr=0x4D0049C0
03 params=0xC0000000 data ptr=0x0000000 next ptr=0x4D0049CC
04 params=0x0 data ptr=0x0000000 next ptr=0x4D00499C
List of timeslots (sw): 2
describes the significant fields in the display.
Table 37 Show Controllers BRI Field Descriptions
Field
|
Description
|
BRI slot 2 interface 0 with integrated NTI
|
Interface type and slot and port number.
|
Layer 1 is ACTIVATED
|
Status can be DEACTIVATED, PENDING ACTIVATION, or ACTIVATED.
|
Master clock
|
The first interface that comes up on an MBRI port adapter holds the master clock. This clock is used for all interfaces on that port adapter. If the master clock interface goes down, the second interface that came up becomes the master clock interface.
|
Total chip configuration successes
|
Counters of successful chip configuration.
|
failures
|
Counters of bad chip configuration.
|
timeouts
|
Counters of failing to initialize chip.
|
D Channel Information
|
Information related to D-channel status.
|
Channel state
|
Channel state can be UNUSED, IDLE, DOWN, STANDBY, UP, THROTTLED, ILLEGAL.
|
Channel IDB
|
Internal interface channel description.
|
RX (or TX) ring entries
|
Internal receive queue.
|
RX (or TX) descriptor ring
|
Internal receive queue to manage hardware chip
|
RX (or TX) buffer ring
|
Internal receive queue to hold inbound packets.
|
Rxhead
|
Start of the receiver queue.
|
params, status, data ptr, next ptr
|
Information about internal data structures and params.
|
List of timeslots (sw)
|
Timeslots assigned to this channel.
|
show dialer interface bri
To display general diagnostic information for ISDN BRI interfaces configured for DDR, use the show dialer interface bri EXEC command.
show dialer interface bri number
Syntax Description
number
|
BRI interface number.
|
Command Mode
EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 9.21.
Sample Displays
If you enter the show dialer interface bri command for the D channel of an ISDN BRI, the command output also displays the B channels. That is, the command show dialer interface bri 0 displays information of interfaces bri 0, bri 0:1, and bri 0:2. Similarly, use of the related command show dialer interface serial 0:23 (for a channelized T1 line configured for ISDN PRI) displays information for serial interfaces 0:23, 0:0, 0:1, and so forth to 0:22.
If you have defined a dialer group that consists of the interfaces serial 0, serial 1, and bri 2, the command show dialer interface dialer 1 displays information for interfaces bri 0, bri 0:1, bri 0:2, serial 1, and serial 0.
The following is sample output from the show dialer interface bri command for a BRI interface when dialer profiles are configured:
impulse# show dialer interface bri 0
BRI0 - dialer type = ISDN
Dial String Successes Failures Last called Last status
0 incoming call(s) have been screened.
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: ip (s=6.1.1.8, d=6.1.1.1)
Interface bound to profile Dialer0
Time until disconnect 102 secs
Current call connected 00:00:19
Connected to 5773872 (wolfman)
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
describes significant fields shown in the display.
Table 38 Show Dialer Interface BRI Field Descriptions
Field
|
Description
|
BRI0 - dialer type = ISDN
|
ISDN dialer.
|
Dial string
|
Dial strings of logged calls (telephone numbers). On ISDN BRI interfaces, if you have specified a subaddress number in the dialer string, this number is included in the dial string after a colon.
|
Successes
|
Successful connections (even if no data is passed).
|
Failures
|
Failed connections; call not successfully completed.
|
Last called
|
Time that last call occurred to specific dial string.
|
Last status
|
Status of last call to specific dial string (successful or failed).
|
0 incoming call(s) have been screened.
|
Number of calls subjected to Dialer Profiles screening to determine how the call is to be treated.
|
BRI0: B-Channel 1
|
Header indicating the following data is for B channel 1.
|
Idle timer (120 secs), Fast idle timer (20 secs)
|
Settings (in seconds) for the idle timer and the fast idle timer.
|
Wait for carrier (30 secs), Re-enable (15 secs)
|
Settings (in seconds) for the wait for carrier timer and the reenable timer.
|
Dialer state is data link layer up
|
The message "data link layer up" suggests that the dialer came up properly; if it says anything else then dialer did not come up properly. The message "physical layer up" means the line protocol (LCP) came up, but the NCP did not come up. The show interfaces command also provides the similar information.
|
Dial reason: ip (s=6.1.1.8, d=6.1.1.1)
|
What initiated the dial, namely an IP packet, plus source and destination address in the packet.
|
Interface bound to profile Dialer0
|
Dialer profile that is bound to this interface or B channel.
|
Time until disconnect
|
Time until line is configured to disconnect. This field is displayed if the interface is currently connected to a destination.
|
Current call connected
|
Time at which the current call was connected.
|
Connected to
|
Dial string to which line is currently connected.
|
If an interface is connected to a destination, a display is provided that indicates the idle time before the line is disconnected. (The value decrements each second.) Then the duration of the current connection is shown. The following shows an example of this display; it appears after the third line in the show dialer display:
Time until disconnect 596 secs
Current call connected 0:00:25
After a call disconnects, the system displays the time remaining before being it can dial again. The following is an example of this display; it appears after the third line in the show dialer display:
Time until interface enabled 8 secs
If caller ID screening is configured on an ISDN BRI, the show dialer command display includes a line similar to the following:
1 incoming call(s) have been screened.
This line reports the number of calls that have been screened.
show interfaces bri
Use the show interfaces bri privileged EXEC command to display information about the BRI D channel or about one or more B channels.
show interfaces bri number[[:bchannel] | [first] [last]] [accounting]
show interfaces bri slot/port (Cisco 7200 series)
Syntax Description
number
|
Interface number. The value is 0 through 7 if the router has one 8-port BRI NIM, or 0 through 15 if the router has two 8-port BRI NIMs. Interface number values will vary, depending on the hardware platform used. The Cisco 3600 series router for example, can have up to 48 interfaces.
Specifying just the number will display the D channel for that BRI interface.
|
slot/port
|
On the Cisco 7200 series, slot location and port number of the interface.
|
:bchannel
|
(Optional) Colon (:) followed by a specific B channel number.
|
first
|
(Optional) Specifies the first of the B channels; the value can be either 1 or 2.
|
last
|
(Optional) Specifies the last of the B channels; the value can only be 2, indicating B channels 1 and 2.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command was modified in Cisco IOS Release 11.2 P to include slot/port syntax for the PA-8B-ST and PA-4B-U port adapters on Cisco 7200 series routers.
Use either the :bchannel-number argument or the first or last arguments to display information about specified B channels.
Use the show interfaces bri number form of the command (without the optional :bchannel, or first and last arguments) to obtain D channel information.
Use the command syntax sample combinations in to display the associated output.
Table 39 Sample Show Interfaces BRI Combinations
Command Syntax
|
Displays
|
show interfaces
|
All interfaces in the router
|
show interfaces bri 2
|
Channel D for BRI interface 2
|
show interfaces bri 2:1
|
Channel B1 on BRI interface 2
|
show interfaces bri 2:2
|
Channel B2 on BRI interface 2
|
show interfaces bri 4 1
|
Channel B1 on BRI interface 4
|
show interfaces bri 4 2
|
Channel B2 on BRI interface 4
|
show interfaces bri 4 1 2
|
Channels B1 and B2 on BRI interface 4
|
show interfaces bri
|
Error message: "% Incomplete command."
|
Sample Displays
The following is sample output from the show interfaces bri command:
Router# show interfaces bri 0:1
BRI0:1 is down, line protocol is down
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive not set
Last input never, output never, output hang never
Last clearing of "show interface" counters never
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
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
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, 7 interface resets
0 output buffer failures, 0 output buffers swapped out
The following is sample output from the show interfaces bri command on a Cisco 7200 series router:
Router# show interfaces bri 2/0
BRI2/0 is up, line protocol is up (spoofing)
Internet address is 11.1.1.3/27
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set
Last input 00:00:01, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/64/0 (size/threshold/drops)
Conversations 0/1 (active/max active)
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
609 packets input, 2526 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
615 packets output, 2596 bytes, 0 underruns
0 output errors, 0 collisions, 5 interface resets
0 output buffer failures, 0 output buffers swapped out
describes the fields shown in the display.
Table 40 Show Interfaces BRI Field Descriptions
Field
|
Description
|
BRI... is {up | down | administratively down}
|
|