|
|
With the optional BRI voice module (BVM) installed, the Cisco MC3810 multiservice access concentrator provides four ISDN Basic Rate Interface (BRI) ports for connection to ISDN PBXs (private integrated services network exchanges, or PINXs). The BVM has four ISDN BRI ports for voice traffic. Each BRI port supports two voice channels (ISDN B channels) and one signaling channel (ISDN D channel). The BRI voice ports have the following features:
Figure 1 shows an example of an ISDN BRI voice network. In the example, PINX A is the master PBX for the system and supplies clock for the BRI voice functions.
The ISDN BRI voice capability in the Cisco MC3810 provides the following benefits:
NT---Network termination; the network side of an ISDN BRI interface.
PINX---Private integrated services network exchange; a PBX or key system which, in this BRI voice application, uses QSIG signaling.
POTS---Plain Old Telephone Service. Basic telephone service supplying standard single-line telephones, telephone lines, and access to the public switched telephone network.
QSIG---Common channel signaling protocol based on ISDN Q.931 standards and used by many digital PBXs.
S/T interface---BRI 4-wire interface that can be configured to terminate a subscriber line (S) or a trunk (T).
TE---Terminal equipment; the user side of an ISDN BRI interface.
The standard Cisco IOS ISDN implementation is supported with the following exceptions:
For more information about standard Cisco ISDN BRI configuration, see the Dial Solutions Configuration Guide.
This feature is supported only on the Cisco MC3810 multiservice access concentrator.
None.
To configure a Cisco MC3810 multiservice access concentrator to support ISDN BRI voice traffic, perform the following tasks:
To configure the ISDN BRI voice ports, follow these steps:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| configure terminal | Enter global configuration mode. | ||
| isdn switch-type basic-qsig | (Optional; see note.) Configure the global ISDN switch type as basic-qsig for the BRI voice ports. Note You can configure the ISDN switch type in either global or interface configuration mode. If you configure it here in Step 2, it specifies the switch type for all four BVM ports. If you configure it in Step 4, it specifies the switch type for a single interface. The switch type specified in Step 4 for any individual interface will override the globally specified switch type. | ||
| interface bri number | Enter interface configuration mode to configure parameters for the specified BRI voice port. The number can be from 1 to 4. | ||
| isdn switch-type basic-qsig | (Optional; see note in Step 2.) If the service provider switch type for this BRI port is different from the global ISDN switch type, configure the interface ISDN switch type to match the service provider switch type. The interface ISDN switch type overrides the global ISDN switch type on this interface. | ||
| isdn protocol-emulate {user | network} | Configure the layer 2 and layer 3 port protocol emulation:
| ||
| isdn layer1-emulate {user | network} | Configure the layer 1 port mode emulation and the clock settings:
| ||
| [no] line-power | Turn on or off the power supplied from an NT-configured port to a TE device. The default is no line-power. | ||
| network-clock-priority {low | high} | If this BRI voice port is configured as TE, and you want it to be the first-priority BRI voice port for recovering clock from the network NT device, enter high. If this BRI voice port is configured as TE, and you want it to be a lower-priority BRI voice port for recovering clock from the network NT device, enter low. This command is not used if this port was configured as NT in Step 6 with the command isdn layer1-emulate network. | ||
| isdn overlap-receiving | |||
| isdn network-failure-cause cause code | Specify the cause code to pass to the PINX (PBX) when a call cannot be placed or completed because of internal network failures. Possible values are from 1 to 127. | ||
| isdn sending-complete | (Optional) Configure the BRI voice port to include the Sending Complete information element in the outgoing call setup message. This command is used in some geographic locations, such as Hong Kong and Taiwan, where the sending complete information element is required in the outgoing call setup message. | ||
| Exit from interface configuration mode and repeat Steps 3 through 11 for each remaining BRI voice port. | |||
router# show interfaces bri 1
BRI1 is up (spoofing), line protocol is up (spoofing)
Hardware is BVM
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
Last input 1w0d, output 1w0d, 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/1000/64/0 (size/max total/threshold/drops)
Conversations 0/1/256 (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
70 packets input, 278 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
70 packets output, 278 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions
router# show controllers bri 1 BRI unit 1: Layer 1 is DEACTIVATED. (ISDN L1 State F3) S2084 registers: Configuration register=0x1 . . . QMC Timeslot Assignment Entries (Rx == Tx): . . . D Channel Information: . . . B1 Channel Information: . . . B2 Channel Information: . . .
router# show voice-port summary IN OUT ECHO PORT SIG-TYPE ADMIN OPER IN-STATUS OUT-STATUS CODEC VAD GAIN ATTN CANCEL 1/1 fxo-null up up idle on-hook 729ar8 n 0 0 y 1/2 fxo-null up up idle on-hook 729ar8 n 0 0 y 2/1 fxo-null up up idle on-hook 729ar8 n 0 0 y 2/2 fxo-null up up idle on-hook 729ar8 n 0 0 y 3/1 fxo-null up up idle on-hook 729ar8 n 0 0 y 3/2 fxo-null up up idle on-hook 729ar8 n 0 0 y 4/1 fxo-null up up idle on-hook 729ar8 n 0 0 y 4/2 fxo-null up up idle on-hook 729ar8 n 0 0 y
router# show isdn status
Global ISDN Switchtype = basic-qsig
ISDN BRI1 interface
dsl 1, interface ISDN Switchtype = basic-qsig
**** Slave side configuration ****
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
Layer 3 Status:
NLCB:callid=0x0, callref=0x0, state=31, ces=0 event=0x0
0 Active Layer 3 Call(s)
Activated dsl 1 CCBs = 0
ISDN BRI2 interface
.
.
.
Total Allocated ISDN CCBs = 0
Configuring POTS dial peers for ISDN BRI voice ports is similar to the POTS dial peer configuration for analog and digital voice ports. This section describes how to configure POTS dial peers specifically for ISDN BRI voice ports.
For more information about dial plan strategies, see the "Voice Dial Plan Considerations" chapter of the Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide.
To configure POTS dial peers, follow these steps:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| configure terminal | Enter global configuration mode. | ||
| dial-peer voice tag pots |
The tag value identifies the dial peer and must be unique on the Cisco MC3810. Do not duplicate a specific tag number. | ||
| destination-pattern string | Configure the dial peer's destination pattern. The string variable is a series of digits that specify the E.164 or private dialing plan telephone number. Valid values are digits from 0 to 9 and letters from A to D. The following special characters can be entered in the string:
| ||
| port slot/port | Associate this voice-telephony dial peer with a specific logical dial interface. Enter the slot/port number of the voice port connected to the POTS dial peer. Note The slot/port syntax for BRI voice ports is different than for standard analog or digital voice ports on the Cisco MC3810. For a BRI voice port, the slot number is 1, 2, 3, or 4 to match the BRI voice port being configured, and the port number is always 1. | ||
| num-exp extension-number extension-string | (Optional) If using the number expansion feature, define how to expand an extension number into a particular destination pattern. | ||
| prefix string | (Optional) Assign the dialed digits prefix for the dial peer. | ||
| preference value |
For more information about hunt groups and preferences, see the "Hunt Groups and Preference Configuration" section of the Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide. | ||
| Exit from dial-peer configuration mode and repeat Steps 2 through 7 for the next dial peer. | |||
Make sure the voice port, serial port and/or the T1/E1 controller are set to no shutdown.
Verify the POTS dial peer configuration by using the show dial-peer voice number or the
show dial-peer voice summary command.
router# show dial-peer voice 1 VoiceEncapPeer1 tag = 1, destination-pattern = \Q2...',preference = 0, Admin state is up, Operation state is down DTMF Relay = disabled type = pots, prefix = \Q', fwd-digits = 0, session-target = \Q', voice-port =
router# show dial-peer voice summary
TAG TYPE ADMIN OPER PREFIX DEST-PATTERN FWD PREF SESS-TARGET PORT
1 pots up down 2... 0 0
3 pots up down 3... 0 0
2 pots up down 1... 0 0
100 vofr up down 0 0
To configure network-side dial peers, see the next section "Configuring Network-Side Dial Peers for ISDN BRI Voice Ports."
The procedure for configuring the network-side dial peers depends on the type of WAN transport between this Cisco MC3810 and the far-end Cisco MC3810. See the appropriate procedure in the Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide as follows:
Make sure the voice port, serial port and/or the T1/E1 controller are set to no shutdown.
Verify the network-side dial peer configuration by following the verify procedure that accompanies the configuration procedure you used.
This section contains the following configuration examples:
To view configuration examples for network-side dial peers, see the configuration procedure you used (VoFR, VoATM, or VoHDLC).
The following example shows typical ISDN BRI voice port configurations for BRI ports 1 and 2. In this example, both ports are set to emulate TE (user, or QSIG slave). Port 2 is configured to recover clock from the network NT device, and port 1 does not recover clock.
Router# Router#conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#isdn switch-type basic-qsig Router(config)#interface bri 1 Router(config-if)#isdn protocol-emulate user Router(config-if)#isdn layer1-emulate user Router(config-if)#network-clock-priority low Router(config-if)#no shut Router(config-if)#end Router#s run interface bri 1w0d: %SYS-5-CONFIG_I: Configured from console by console1 Building configuration... Current configuration: ! interface BRI1 no ip address no ip directed-broadcast network-clock-priority low isdn switch-type basic-qsig isdn protocol-emulate user isdn layer1-emulate user isdn incoming-voice voice isdn static-tei 0 no cdp enable end Router# Router#conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#isdn switch-type basic-qsig Router(config)#interface bri 2 Router(config-if)#isdn protocol-emulate user Router(config-if)#isdn layer1-emulate user Router(config-if)#network-clock-priority high Router(config-if)#no shut Router(config-if)#end Router#s run interface bri 1w0d: %SYS-5-CONFIG_I: Configured from console by console1 Building configuration... Current configuration: ! interface BRI2 no ip address no ip directed-broadcast network-clock-priority high isdn switch-type basic-qsig isdn protocol-emulate user isdn layer1-emulate user isdn incoming-voice voice isdn static-tei 0 no cdp enable end Router#
The following example shows POTS dial-peer configurations for BRI ports 1, 2. and 3.
Router#
Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#dial-peer voice 1 pots
Router(config-dial-peer)#destination-pattern 2
Router(config-dial-peer)#port 1/1
Router(config-dial-peer)#prefix 12
Router(config-dial-peer)#preference 1
Router(config-dial-peer)#exit
Router(config)#
Router(config)#dial-peer voice 2 pots
Router(config-dial-peer)#destination-pattern 3...
Router(config-dial-peer)#port 2/1
Router(config-dial-peer)#prefix 12
Router(config-dial-peer)#preference 0
Router(config-dial-peer)#exit
Router(config)#
Router(config)#dial-peer voice 3 pots
Router(config-dial-peer)#destination-pattern 1...
Router(config-dial-peer)#port 3/1
Router(config-dial-peer)#prefix 12
Router(config-dial-peer)#preference 0
Router(config-dial-peer)#end
Router#
Router#s dial-peer voice summary
TAG TYPE ADMIN OPER PREFIX DEST-PATTERN FWD PREF SESS-TARGET PORT
1 pots up up 12 2 0 1 1/1
2 pots up down 12 3... 0 0 2/1
3 pots up down 12 1... 0 0 3/1
100 vofr up down 0 0
Router#
This section documents new or modified commands. All other commands used with the ISDN BRI voice feature are documented in the Cisco IOS Release 12.0 command references.
To configure the layer 1 operation of a BRI voice port as clock master (NT) or slave (TE), use the isdn layer1-emulate interface configuration command. Use the no form of this command to restore the default (user).
isdn layer1-emulate {user | network}
user | Physical interface operation in clock slave mode (as TE). |
network | Physical interface operation in clock master mode (as NT). |
Layer 1 port operation is as user (TE functionality as clock slave).
Interface configuration
This command first appeared in Cisco IOS Release 12.0(3)XG.
If you enter the no isdn layer1-emulate network command, the physical layer port operation defaults to user.
The following example configures the layer 1 operation of a BRI voice port as QSIG clock slave (TE):
configure terminalinterface bri 1
isdn layer1-emulate user
To configure the layer 2 and layer 3 port protocol of a BRI voice port or a PRI interface to emulate NT (network) or TE (user) functionality, use the isdn protocol-emulate interface configuration command. Use the no form of this command to restore the default (user).
isdn protocol-emulate {user | network}
user | Layer 2 and layer 3 port protocol operation as TE (port functions as QSIG slave). |
network | Layer 2 and layer 3 port protocol operation as NT (port functions as QSIG master). |
Layer 2 and layer 3 port protocol emulates user (TE functionality).
Interface configuration
This command first appeared in Cisco IOS Release 12.0(3)XG.
If you enter the no isdn protocol-emulate command, the layer 2 and layer 3 protocol emulation defaults to user.
The following example configures the layer 2 and layer 3 function of a BRI voice port to operate as TE:
interface bri 1isdn protocol-emulate user
The following example configures the layer 2 and layer 3 function of an E1 PRI interface to operate as TE:
interface serial 1:15isdn protocol-emulate user
The following example configures the layer 2 and layer 3 function of a T1 PRI interface to operate as TE:
interface serial 1:23isdn protocol-emulate user
To specify the central office switch type on the ISDN interface, use the isdn switch-type command in global or interface configuration mode. To remove an ISDN switch type, use the no form of this command.
isdn switch-type switch-type
switch-type | ISDN service provider switch type. Table 1 in the "Usage Guidelines" section lists the supported switch types. |
No isdn switch type is specified.
Global configuration or interface configuration
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.3 T.
The basic-qsig switch type option to support QSIG BRI voice signaling was added in Cisco IOS Release 12.0(3)XG.
To remove an ISDN switch type from an ISDN interface, specify no isdn switch-type switch-type.
Table 1 lists supported BRI switch types by geographic area.
If different Cisco MC3810 BRI ports interface with different ISDN switch types, you can use global and interface commands in any combination, as long as you remember that interface commands always override a global command. For example, if you have a BRI QSIG switch interface on BRI voice ports 1, 2, 3 and 4, but a BRI 5ess switch interface on BRI backup port 0, you can configure the ISDN switch types in any of the following combinations:
If you enter the no isdn switch-type command in global configuration mode, any switch type that was originally entered in global configuration mode is cancelled; however, any switch type originally entered on an interface is not affected. If you enter the no isdn switch-type command in interface configuration mode, any switch type configuration on the interface is cancelled.
| Keywords by Area | Switch Type |
|---|---|
none | No switch defined |
| Australia |
|
basic-ts013 | Australian TS013 switches |
| Europe |
|
basic-1tr6 | German 1TR6 ISDN switches |
basic-net3 | NET3 ISDN, Norway NET3, and New Zealand NET3 switches (covers the Euro-ISDN E-DSS1 signaling system and is ETSI-compliant) |
basic-qsig | PINX (PBX) switches with QSIG signaling per Q.931 |
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 |
isdn switch-type basic-qsig
interface bri 1isdn switch-type basic-qsig
isdn switch-type basic-niinterface bri 1
!isdn switch-type basic-qsig
To configure the Cisco MC3810 BRI port to supply line power to the TE, use the line-power interface configuration command. To disable the line power supply, use the no form of this command.
line-powerThis command has no arguments or keywords.
The BRI port does not supply line-power.
Interface configuration
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810.
This command is used only on a BRI port operating in NT mode. A BRI port operating in TE mode is automatically disabled as a source of line power.
When you enter the line-power command, the line power provision is activated on a BRI port. When you enter no line-power, the line power provision is deactivated on a BRI port.
The following example configures a BRI port to supply power to an attached TE device:
interface bri 1line-power
Use the network-clock-priority interface configuration command to specify the clock-recovery priority for the BRI voice ports in a BRI voice module (BVM). Use the no form of this command to restore the default (low) clock-recovery priority.
network-clock-priority {low | high}
low | The BRI port is second priority to recover clock. |
high | The BRI port is first priority to recover clock. |
Each BRI voice port has low clock-recovery priority.
Interface configuration
This command first appeared in Cisco IOS Release 12.0(3)XG.
This command is supported only on the Cisco MC3810.
This command is only valid for BRI ports configured as TE. It allows you to select which PINX (PBX) is the first-priority clock source.
This command becomes effective only when the BVM is the clock source for the Cisco MC3810; this happens in three ways:
The BRI voice port supplying clock operates as a line source; if there are other BRI voice ports configured as TE, they operate in loop-timed mode.
Regardless of the network-clock-priority setting, the first TE-configured BRI voice port that becomes active is automatically chosen to supply clock. The clock source does not change if another BRI voice port configured for network-clock-priority high becomes active.
If the chosen clocking port becomes inactive, the system searches for clock on the active TE-configured ports in the following order:
1. Ports configured as network-clock-priority high in order from lowest (1) to highest (4).
2. Ports configured as network-clock-priority low in order from lowest (1) to highest (4).
If the originally chosen port then reactivates, it resumes its role as clock source regardless of its network-clock-priority setting.
If you enter either the no network-clock-priority low or the no network-clock-priority high command, the network clock priority defaults to low.
The following example configures BRI voice port 1 as a first priority clock source:
interface bri 1network-clock-priority high
Use the network-clock-select global configuration command to specify a clock-source selection priority. Use the no form of this command to cancel the network clock selection.
network-clock-select priority {serial 0 | system | bvm | controller}
priority | Selection priority for the clock source from 1 (highest) to 4 (lowest). |
serial 0 | Clocking priority for serial interface 0. |
system | Clocking priority for the system clock. |
bvm | Clocking priority for the BRI voice module (BVM). |
controller | Clocking priority for either the trunk controller (T1/E1 0) or the digital voice module (T1/E1/ 1). |
No network clock source is specified.
Global configuration
This command first appeared in Cisco IOS Release 11.3 MA.
The BVM as a possible network clock source was added in Cisco IOS Release 12.0(3)XG.
When an active clock source fails, the system chooses the next lower priority clock source specified by this command. When a higher-priority clock becomes available, the system automatically reselects the higher-priority clock source.
Enter the network-clock-select command to establish the clock-selection priority when there are multiple sources of line (network) clocking in a Cisco MC3810. Possible sources of line clocking for the Cisco MC3810 are the BRI voice module (BVM), the multiflex trunk module (MFT), and a serial port configured for clock rate line.
The following example sets a possible clock selection priority in a Cisco MC3810 with a digital voice module (DVM) installed.
network-clock-select 1 T1 0
network-clock-select 2 T1 1
network-clock-select 3 serial 0
network-clock-select 4 system
The following example sets a possible clock selection priority in a Cisco MC3810 with a BRI voice module (BVM) installed.
network-clock-select 1 T1 0
network-clock-select 2 bvm
network-clock-select 3 serial 0
network-clock-select 4 system
network-clock-switch
network-clock-priority
Use the show interfaces bri EXEC command to display statistics for ISDN BRI interfaces configured on the Cisco MC3810.
show interfaces bri [number]
number | Specifies the BRI port number. Valid numbers are from 1 to 4. |
EXEC
This command first appeared in Cisco IOS Release 12.0(3)XG.
If you use the show interfaces bri command in the Cisco MC3810 without the slot-number keywords, information for all of the configured ISDN BRI interfaces will be shown.
The BRI port numbers match the physical ports numbers on the BRI voice module (BVM).
The following example shows interface statistics for interface BRI 1:
Router# Router#show interfaces bri 1 BRI1 is up (spoofing), line protocol is up (spoofing) Hardware is BVM MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Last input 1w0d, output 1w0d, 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/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (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 70 packets input, 278 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 70 packets output, 278 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 2 carrier transitions Router#
Use the show controllers bri command to display statistics for ISDN BRI controllers configured on the Cisco MC3810:
show controllers bri number
number | Specifies the BRI controller number. Valid numbers are from 1 to 4. |
EXEC
This command first appeared in Cisco IOS Release 12.0(3)XG.
If you use the show controllers bri command in the Cisco MC3810 without the slot-number keywords, information for all of the configured ISDN BRI controllers will be shown.
The BRI controller numbers match the physical ports numbers on the BRI voice module (BVM).
The following example shows controller statistics for interface BRI 1:
Router# Router#show controllers bri 1 BRI unit 1: Layer 1 is DEACTIVATED. (ISDN L1 State F3) S2084 registers: Configuration register=0x1 QMC GLOBAL MULTICHANNEL PARAMETERS (at 0x30003C00) [MCBASE]=0x1C4AE38, [QMCSTATE]=0x0, [MRBLR]=0x5F4 [TXSPTR]=0x1C20, [RXPTR]=0x1C24, [GRFTHR]=0x1 [GRFCNT]=0x1, [INTBASE]=0x1B04124, [INTPTR]=0x1B0413C [RXSPTR]=0x1C20, [TXPTR]=0x1C3E, [CMASK32]=0xDEBB20E3 [TSATRX]=0x30003C20, [TSATTX]=0x30003C60, [CMASK16]=0xF0B8 QMC Timeslot Assignment Entries (Rx == Tx): [ 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x540 0x8503 0x84C3 0x8483 0x0 0x400 0x400 0xC400 0xC000 ] D Channel Information: BVM unit 1, qmc_channel: 18 timeslot: 26 idb at 0x1199FC8, driver data structure at 0x11D06D8 SCC Registers: General [GSMR]=0x780:0x0000003A, Protocol-specific [PSMR]=0x80 Events [SCCE]=0x0000, Mask [SCCM]=0x000F, Status [SCCS]=0x0002 Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E Interrupt Registers: Config [CICR]=0x001B9981, Pending [CIPR]=0x00000240 Mask [CIMR]=0x7A000400, In-srv [CISR]=0x00000000 Command register [CR]=0x640 Port A [PADIR]=0x00F0, [PAPAR]=0xFFFF [PAODR]=0x00E0, [PADAT]=0x1AEF Port B [PBDIR]=0x01333F, [PBPAR]=0x01033E [PBODR]=0x000030, [PBDAT]=0x00DFFC Port C [PCDIR]=0x0C0C, [PCPAR]=0x0000 [PCSO]=0x03F3, [PCDAT]=0x00FF, [PCINT]=0x0000 Port D [PDDIR]=0x000760, [PDPAR]=0x00013F [PDDAT]=0x000CB0 SI [SIMODE]=0x00480048, [SIGMR]=0x0E, [SISTR]=0x00 [SICR]=0x6D372E49 BRGC [BRGC1]=0x00000000, [BRGC2]=0x00000000 [BRGC3]=0x00000000, [BRGC4]=0x00000000 QMC CHANNEL PARAMETERS (at 0x30002480) [TBASE]=0xBC0, [CHAMR]=0xB000, [TSTATE]=0x300C0FDE [TBPTR]=0xBD0, [ZISTATE]=0xE1FF0FFF, [INTMSK]=0x3F [RBASE]=0xB40, [MFLR]=0x5F4, [RSTATE]=0x31021C00 [RBPTR]=0xB70, [ZDSTATE]=0x25FFFFAE buffer size 1524 RX ring with 16 entries at 0x1C4B978, Buffer size 1524 Rxhead = 0x1C4B9A8 (6), Rxp = 0x11D070C (6) 00 pak=0x145FDD0 buf=0x1CCE138 status=9000 pak_size=0 01 pak=0x145FBBC buf=0x1CCDA78 status=9000 pak_size=0 02 pak=0x145F9A8 buf=0x1CCD3B8 status=9000 pak_size=0 03 pak=0x145F794 buf=0x1CCCCF8 status=9000 pak_size=0 04 pak=0x14618D4 buf=0x1CD38F8 status=9000 pak_size=0 05 pak=0x14616C0 buf=0x1CD3238 status=9000 pak_size=0 06 pak=0x1461298 buf=0x1CD24B8 status=9000 pak_size=0 07 pak=0x1461084 buf=0x1CD1DF8 status=9000 pak_size=0 08 pak=0x1460E70 buf=0x1CD1738 status=9000 pak_size=0 09 pak=0x1460C5C buf=0x1CD1078 status=9000 pak_size=0 10 pak=0x1460A48 buf=0x1CD09B8 status=9000 pak_size=0 11 pak=0x1460834 buf=0x1CD02F8 status=9000 pak_size=0 12 pak=0x1460620 buf=0x1CCFC38 status=9000 pak_size=0 13 pak=0x146040C buf=0x1CCF578 status=9000 pak_size=0 14 pak=0x14601F8 buf=0x1CCEEB8 status=9000 pak_size=0 15 pak=0x145FFE4 buf=0x1CCE7F8 status=B000 pak_size=0 TX ring with 4 entries at 0x1C4B9F8, tx_count = 0 tx_head = 0x1C4BA08 (2), head_txp = 0x11D0818 (2) tx_tail = 0x1C4BA08 (2), tail_txp = 0x11D0818 (2) 00 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 01 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 02 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 03 pak=0x0000000 buf=0x0000000 status=2000 pak_size=0 0 throttles, 0 enables 0 input aborts on receiving flag sequence 0 missed datagrams, 0 overruns 0 bad datagram encapsulations, 0 memory errors 0 transmitter underruns B1 Channel Information: BVM unit 1, qmc_channel: 0 timeslot: 0 idb at 0x119FEB0, driver data structure at 0x11D0B54 SCC Registers: General [GSMR]=0x0:0x00000000, Protocol-specific [PSMR]=0x0 Events [SCCE]=0x0000, Mask [SCCM]=0x0000, Status [SCCS]=0x0000 Transmit on Demand [TODR]=0x9080, Data Sync [DSR]=0xA4 QMC CHANNEL PARAMETERS (at 0x0) [TBASE]=0x0, [CHAMR]=0x0, [TSTATE]=0x7C6802A6 [TBPTR]=0x9080, [ZISTATE]=0x906000AC, [INTMSK]=0x9060 [RBASE]=0x4800, [MFLR]=0x5, [RSTATE]=0x7C8000A6 [RBPTR]=0x7C9B, [ZDSTATE]=0x3864FFDC buffer size 1524 RX ring with 0 entries at 0x0, Buffer size 1524 Rxhead = 0x0 (0), Rxp = 0x0 (-4670172) TX ring with 0 entries at 0x0, tx_count = 0 tx_head = 0x0 (0), head_txp = 0x0 (-4670243) tx_tail = 0x0 (0), tail_txp = 0x0 (-4670243) 0 throttles, 0 enables 0 input aborts on receiving flag sequence 0 missed datagrams, 0 overruns 0 bad datagram encapsulations, 0 memory errors 0 transmitter underruns B2 Channel Information: BVM unit 1, qmc_channel: 0 timeslot: 0 idb at 0x11A5D98, driver data structure at 0x11D0F8C SCC Registers: General [GSMR]=0x0:0x00000000, Protocol-specific [PSMR]=0x0 Events [SCCE]=0x0000, Mask [SCCM]=0x0000, Status [SCCS]=0x0000 Transmit on Demand [TODR]=0x9080, Data Sync [DSR]=0xA4 QMC CHANNEL PARAMETERS (at 0x0) [TBASE]=0x0, [CHAMR]=0x0, [TSTATE]=0x7C6802A6 [TBPTR]=0x9080, [ZISTATE]=0x906000AC, [INTMSK]=0x9060 [RBASE]=0x4800, [MFLR]=0x5, [RSTATE]=0x7C8000A6 [RBPTR]=0x7C9B, [ZDSTATE]=0x3864FFDC buffer size 1524 RX ring with 0 entries at 0x0, Buffer size 1524 Rxhead = 0x0 (0), Rxp = 0x0 (-4670442) TX ring with 0 entries at 0x0, tx_count = 0 tx_head = 0x0 (0), head_txp = 0x0 (-4670513) tx_tail = 0x0 (0), tail_txp = 0x0 (-4670513) 0 throttles, 0 enables 0 input aborts on receiving flag sequence 0 missed datagrams, 0 overruns --More-- 0 bad datagram encapsulations, 0 memory >errors 0 transmitter underruns Router#
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Mar 25 06:52:15 PST 1999
Copyright 1989-1999©Cisco Systems Inc.