[Top][Contents][Prev][Next][Last]Search


Administering MAX TNT Slot Cards


This chapter covers the following topics:
Overview
Viewing installed slot cards
Viewing information about a particular slot card
Opening a session with a slot card
Changing a slot state
Changing a device state
Removing a slot card and its configuration
Viewing the clock source for a slot card
Recovering from a failed slot-card installation
Administering Ethernet cards
Administering T1, T3, and FrameLine cards
Administering E1 cards
Administering HDLC cards
Administering IDSL cards
Administering SDSL cards
Administering RADSL cards
Administering SWAN cards
Administering modems

Overview

Typical system administration tasks for the MAX TNT slot cards include viewing status information, removing a slot card configuration, and disabling lines. For information about managing the MAX TNT system, see Chapter 2, "MAX TNT System Administration."

Viewing installed slot cards

The Show command displays information about the slot cards installed in the MAX TNT and the status of each card. In a multishelf system, the Show command displays cards in all shelves the system. You can also use the Show command for a particular slot card. For an example, see Viewing information about a particular slot card.

The following example illustrates use of the Show command to display a list of slot cards installed in a multishelf system:

The output lists the physical address of each slot in which an expansion card is installed. The address is in the form {shelf slot item}. Each listing also shows the status of the card and the type of card installed.

The status can be reported as follows:

Status

Signifies

UP

Normal operational mode.

DOWN

Not in an operational mode.

POST

The card is running power-on self tests.

LOAD

The card is loading code as part of booting up.

OCCUPIED

The slot is occupied by a two-slot card (such as the 48 modem card in shelf 1, slot 4, in the example above).

RESET

The card is being reset.

NONE

The card has been swapped out, but its configuration remains in NVRAM.

The Show command can report the following types of slot cards:

Status

Signifies

unknown

Current software does not recognize the card in the slot.

analog-modem-card

The analog modem card.

10-unchan-t1-card

FrameLine card.

192hdlc-card

192-channel HDLC card.

4ether-card

4-port Ethernet card.

4swan-card

4-interface serial WAN card.

48modem-card

48-modem slot card.

48modem-56k-card

Series56 digital modem card.

8e1-card

8-line E1 slot card.

8t1-card

8-line T1 slot card.

capadsl-card

RADSL CAP card.

32idsl-card

32-port IDSL card.

shelf-controller

Shelf-controller card.

sdsl-card

SDSL card.

T3 card

DS3 card.

Viewing information about a particular slot card

To use the Show command for information about a particular command, add the shelf and slot-card numbers as arguments. For example:

Opening a session with a slot card

To open a session with a slot card, use the Open command as in the following example:

where 1 is the shelf number and 7 is the slot number.

On the master shelf of a multishelf system, you can open a session with a slave shelf. For example:

You cannot use the Open command from the slave shelf.

After you have established a session with the card, the prompt changes to indicate the type of card, its slot number, and its shelf number. To list the commands available on the card, enter a ? or help, as in the following example:

For information about the card-level commands, see the MAX TNT Reference Guide.

To exit the session with the card, enter quit, as in the following example:

Changing a slot state

To force a change in the state of a slot, use the Slot command, as shown in the following examples.

To bring a slot down:

To bring a slot up:

You cannot change the state of a slave shelf controller by using the Slot -u or Slot -d commands.

Changing a device state

To force a change in the state of a device, use the Device command, as shown in the following examples.

To bring a device down:

To bring a device back up:

Removing a slot card and its configuration

MAX TNT slot cards are hot swapable. When you remove a card, the system retains its configuration. This enables you to re-install the card or install another of the same type in the same slot, without reconfiguring the system or uploading a backup configuration. One side-effect of this feature is that the NVRAM used to store configuration information is not cleared when a card is removed, until you explicitly clear the configuration.

When a card has been removed, it shows up with a status of NONE in the Show command output. For example:

The NONE status indicates that the card was removed but its profiles have been saved. The MAX TNT remembers that a card was in that slot and saves its profiles until a card of a different type is installed in the same slot, or until the administrator enters the Slot -r command, as in the following example:

In either case, all the old profiles associated with the slot are deleted. If a different type of card is inserted, appropriate new profiles are created.

Viewing the clock source for a slot card

The Clock-Source command can be run on the shelf controller or on an individual card, as in the following example on a T1 card:

Sources with layer 2 up, which are preferred, are marked with an asterisk. For information about configuring the clock source see the MAX TNT Hardware Installation Guide.

Recovering from a failed slot-card installation

If you installed a new slot card before upgrading the system software, and the slot card does not come up properly, there are two ways to recover:

Using the NVRAM command

Warning: Using the NVRAM command resets the entire system. This method cannot be done remotely because the NVRAM command clears the MAX TNT configuration, including its IP address. Before performing this procedure make sure you have access to the MAX TNT serial port.

To recover from a failed slot-card installation by this method:

  1. Save the current system configuration. For example:

    This saves the configuration to a file named 971001 in the TFTP home directory on a host named bonzo.

  2. Clear the system configuration and restart the MAX TNT by executing the NVRAM command:

  3. Restore the saved system configuration.

    You can either restore it through the serial port, or you can reassign an IP address and default gateway through the serial port, then use the Load command to load the rest of the configuration as in the following example:

    This restores the configuration from a file named 971001 in the TFTP home directory on a host named bonzo.

For a complete description of saving and restoring configurations, see the Backing up and restoring a configuration.

Removing the slot card

To recover from a failed slot-card installation by removing the slot card:

  1. Save the current configuration of any profiles on the card. For example:

    This saves the configuration of all the T1 profiles to a file named 971001 in the TFTP home directory on a host named bonzo.

  2. Bring down the card, as in the following example:

    This disables the slot card in shelf 1, slot 1.

  3. Remove the card profile:

  4. Bring the card back up:

  5. Restore the configuration of any profiles on the card. For the T1 card in this example, you would enter the following command:

    This restores the configuration from a file named 971001 in the TFTP home directory on a host named bonzo.

Displaying line status

To display the activity of the MAX TNT WAN lines, enter the Line command:

where

Figure 3-1 shows an example of a line-status window for the T3 card.

Figure 3-1. Example of a T3 card line-status window

The first entry in the right-hand area of the screen shows the overall status of the DS3 line and each of its seven component DS2 channels. One DS2 includes 4 DS1s. The other entries represent each of the component DS1s.

The Line commands put the window in line-status mode, in which the following message appears below the status window:

[Next/Last Conn:<dn/up arw>, Next/Last Page:<pg dn/up>,Exit: <esc>]
The message indicates the key sequences you can use for displaying additional information in the line status area. The Down Arrow and Up Arrow keys display the next and previous T1 line in the list, respectively. The Page Down and Page Up keys display the list a screen at a time.

When the line-status mode message is displayed, the system prompt does not appear at the bottom of the window. Press the Escape key to exit this mode and return to the system prompt.

Line status information includes the following identifiers and codes:

Following are the link-status codes:

Code

Description

LA (link active)

The line is active and physically connected

NT

The E1 line is active and configured as network-side equipment.

TE

The E1 line is active and configured as user-side equipment.

RA (red alarm)

The line is unconnected, improperly configured, experiencing a very high error rate, experiencing a loss-of-receive-signal, or is not supplying adequate synchronization.

YA (yellow alarm)

The MAX TNT is receiving a Yellow Alarm pattern, an indication that the other end of the line cannot recognize the signals the MAX TNT is transmitting.

DF (d-channel fail)

The D channel for a PRI line is not currently communicating.

1S (all ones)

A keep-alive (also known as a Blue Alarm) signal is being sent from the PRI network to the MAX TNT to indicate that the line is currently inoperative.

DS (disabled)

The line might be physically connected, but the T1 or E1 profile specifies that it is inactive.

ID (idle-DS3 only)

The DS3 interface has detected an Idle Signal transmitted from the other side. This generally indicates that the line is provisioned but is not in use.

WF (wrong framing-DS3 only)

The DS3 interface has detected that the other side is using a framing format that differs from the one the local DS3 interface is configured for (C-bit-parity or M13).

Following are the channel-status codes:

Code:

Description

. (period)

The channel is not available because the line is disabled, has no physical link, or does not exist, or because the channel configuration specifies that it is unused.

* (asterisk)

The channel is connected in a current call.

- (hyphen)

The channel is currently idle (but in service).

b

The channel is a backup NFAS D channel (T1 PRI only).

c

The channel is currently not available because it is in the process of clearing the most recent call, or because it is in the process of sending echo cancellation tones to receive a call (inband signaling on T1 only).

d

The MAX TNT is dialing from this channel for an outgoing call.

r

The channel is ringing for an incoming call.

m

The channel is in maintenance/backup mode (ISDN only).

n

The channel is nailed.

o

The channel is out of service (ISDN only).

s

The channel is an active D channel (ISDN only).

Following are the channel-type codes:

Code

Description

E

E1 line

I

T1 PRI signaling

N

All other NFAS types

P

NFAS Primary

S

NFAS Secondary

T

T1 inband signaling

Administering Ethernet cards

For all Ethernet interfaces except the shelf controller, the MAX TNT detects and flags changes in the interface link-state. You can enable a feature in the Ethernet profile that causes automatic routing table updates based on physical link-state changes. Routes to a disabled (down) interface are deleted from the IP routing table, so alternative configured routes can be used instead, and the routes are added again when the interface comes back up. You can also choose to administratively down a LAN interface by disabling its Ethernet profile.

The following parameters, shown with their default settings, are related to LAN-interface link-state changes:

Enabling or disabling an Ethernet interface

The Enabled parameter in an Ethernet profile specifies whether a LAN interface is enabled (the default) or disabled. If Enabled is set to No, packets routed to and received on the interface are discarded. Note that the user-specified state is preserved across system resets.

An interface may also be disabled by using the Ifmgr command, or it may be marked as down by the Ethernet driver when Link-State-Enabled is Yes and Link-State is Down.

To enable an interface, set the Enabled parameter to Yes (the default), or use the Ifmgr Up option. Note, however, that if there are physical problems with the interface, specifying the interface as up might not enable it.

To disable an interface with the Ifmgr command, proceed as in the following example:

  1. Open a session with an Ethernet card:

  2. View the interface table:

  3. Mark the interface as down by specifying its name:

    The Ifmgr display indicates that the interface is disabled by displaying a dash instead of an asterisk in the Up column (u):


Note: A disabled Ethernet interface is also shown with a dash in Netstat command output.

To mark an interface as up, enter a command similar to the following:

Specifying how the link state affects the IP routing table

The Link-State-Enabled parameter signifies whether the value of the Link-State parameter affects the IP routing tables. If it is set to Yes, routes to an interface are deleted when the link state is down, and added back when the interface comes back up again. If the parameter is set to No (the default), packets are routed to the interface regardless of its link-state. If the interface is down, packets are discarded rather than transmitted over using an alternative route.

A read-only indication of physical link-state

The Link-State parameter shows the physical state of the LAN interface: up or down. The parameter can only be set by the Ethernet driver. A LAN interface is down if it cannot transmit or receive network traffic (for example, if the Ethernet cable is unplugged or the Ethernet hub on that interface is down). For the shelf-controller Ethernet interface, the value of the Link-State parameter is set to Unknown.

Checking multiple IP interfaces on an Ethernet port

In the following Ifmgr command output, the physical interface 1-12-1 has two IP-Interface profiles associated with it. The first is named ie1-12-1 (the default profile), and the second is named ie1-12-1-1:

admin> ifmgr -d
bif slot sif u m p ifname     host-name  remote-addr       local-addr
---------------------------------------------------------------------------
000 1:17 000 * ie0 - 0.0.0.0/32 200.168.6.188/32
001 1:17 001 * lo0 - 0.0.0.0/32 128.0.0.1/32
002 0:00 000 * rj0 - 0.0.0.0/32 128.0.0.2/32
003 0:00 000 * bh0 - 0.0.0.0/32 128.0.0.3/32
004 0:00 000 * local - 0.0.0.0/32 128.0.0.1/32
005 0:00 000 * mcast - 0.0.0.0/32 225.0.0.0/32
006 1:12 001 * ie1-12-1 - 0.0.0.0/32
10.5.6.7/32
007 1:12 002 * ie1-12-2 - 0.0.0.0/32 0.0.0.0/32
008 1:12 003 * ie1-12-3 - 0.0.0.0/32 0.0.0.0/32
009 1:12 004 * ie1-12-4 - 0.0.0.0/32 0.0.0.0/32
010 1:12 005 * ie1-12-1-1 - 0.0.0.0/32
10.9.1.212./24

Administering T1, T3, and FrameLine cards

MAX TNT T1, T3, an FrameLine cards are all administered in much the same way. In most cases, administration of the individual T1 lines on the three cards is identical. Table 3-1 briefly describes the different methods you can use to manage the T1, T3, or FrameLine cards, and shows where each method is discussed in this manual.

Table 3-1. T1-line maintenance tasks

Task/section of this manual

Description

Associated parameter or command

Quiescing a PRI line or T1 channels.

Quiescing a PRI line allows you to gradually take a line or channels out of service.

Maintenance-State parameter

Quiesce command

Specifying FDL.

Your T1 service provider can use Facilities Data Link (FDL) to monitor the status of your line.

FDL parameter

Checking the status of T1 channels.

Display the administrative state and nailed-group assignment of the T1 channels.

T1channel command

Displaying DS1-level diagnostics for T1 cards.

Display T1 channel errors.

T1-Stats command

The FE-Loop command.

Loopback the T1 line.

FE-Loop

Quiescing a PRI line or T1 channels

Quiescing a PRI line takes the line out of service by removing channels from service as active calls disconnect. The switch used by the carrier affects whether the line is taken out of service or busied out. For details, see the Quiesce command description in the MAX TNT Reference Guide.

You can quiesce a line by using either of the following methods:

Restoring a line or channel that has been quiesced can take up to 10 minutes.


Note: You cannot quiesce a T1 line on the FrameLine card.

Using the Maintenance-State parameter

To quiesce a line with the Maintenance-State parameter, proceed as in the following example:

Using the Quiesce command

You can enter the Quiesce command to quiesce a PRI line, port, or channel. The command uses the following syntax:

where

For example, to quiesce a T1 PRI line at port 4 of a card installed in slot 2:

Restoring a line or channel that has been quiesced can take up to 3.5 minutes, because only 1 service message per channel is sent to the switch, at a rate of one per second.

To restore the line quiesced in the preceding example:

Following is an example of quiescing a single channel:

Specifying FDL

The facilities data link (FDL) is used by the telephone company to monitor the quality and performance of T1 lines. If your carrier's maintenance devices require regular data-link reports, and if the line is not configured for D4 framing, you can specify the type of protocol to use (AT&T, ANSI, or Sprint).

You cannot use FDL reporting on a line configured for D4 framing. However, you can obtain D4 and ESF performance statistics in the FDL Stats windows or the DSX MIB, even if you do not choose an FDL protocol. (For further information, see the Frame-Type parameter description in the MAX TNT Reference Guide).


Note: FDL is not supported on the FrameLine card. Also, DS3-level FDL capabilities such as the Far-End Alarm and Control Channel (FEAC) and Path Maintenance Data Link are currently unsupported.

To specify the type of FDL, proceed as in the following example:

Checking the status of T1 channels

To show T1-channel information, enter the T1Channels command. Use the following syntax:

where

For example, to display all T1 channels available, use the -a option:

To display information about which T1 channels are in use:

Displaying DS1-level diagnostics for T1 cards

The T1-Stats command reports DS1-level line errors. Before entering the command, use the Open command to open a session with the installed card. For example, to open a session with a card in shelf 1, slot 13:

Then enter the T1-Stats command. The following example shows the command's syntax:

To view DS1-level statistics on the first line on the card:

Table 3-2 explains the T1-Stats fields.

Table 3-2. T1-Stats command fields

Field

Event that increments the field

CRC Errors

Indicates that a CRC-6 checksum shows data corruption in the signal.

Frame Slips

The MAX TNT receives T1 data at a frequency higher or lower than the internal line clock. In the process of realigning itself to the transmitter, the MAX TNT can skip or repeat a frame.

Framing Bit Errors

Framing bit errors occur when the MAX TNT receives T1 data at a frequency higher or lower than that of the internal line clock. In the process of realigning itself to the transmitter, the MAX TNT can skip or repeat a frame.

Out of Frame Events

The MAX TNT no longer detects a framing pattern in the receiving signal, or it detects a pattern at a different relative offset than expected.

Line Code Violations

The MAX TNT detected either a Bipolar Violation or Excessive Zeros, which means that one of the low-level T1 rules for encoding data was violated in the received signal.

The following example shows how to view and reset the statistics to zero on line 2:

The Statistics cleared message at the end of the display indicates that the statistics have been reset to 0 (zero), because the command included the -c option.

The FE-Loop command

When a T1 line is looped back to the network, either as a result of the FE-Loop diagnostic command issued from the T1 card command line interface or as a result of loopback requests received from the network, the T1 line status display on the shelf controller shows the LB (loopback) status for the line.

The following examples demonstrate the use of the FE-Loop command:

To loop the CSU towards the network for the first DS1 in slot 1:

In this example, the receive side of the T1 is not bridged to the MAX TNT.

To turn the loopback off:

To send a remote loopback request to the remote CSU:

In this example, the receive side of the T1 is bridged to the MAX TNT.

To turn the remote loopback off:

Using DS3 diagnostics

The DS3Link command is a low-level management tool for use during diagnostic sessions with the T3 card. To open a session with the installed DS3 card, use the Open command.

For example, to manage a DS3 card on the shelf 1 in slot 15, first enter the Open command as follows:

Then, enter the DS3Link command:

where -option is one of the following:

Option

Effect

-a

Displays current DS3 line alarms.

-b on

Transmits a DS3 Alarm Indication Signal (Blue Alarm).

-b off

Stops transmitting a DS3 Alarm Indication Signal (Blue Alarm).

-c

Displays and clears line error statistics.

-d 1 - 7

Displays current DS2 line state.

-i on

Internally loops back the DS3 payload.

-i off

Halt internal loop back.

-l on

Externally loops back the DS3 payload.

-l off

Halt external loop back.

-s

Displays line error statistics without clearing.

-t

Toggles debug output.

-?

Displays this summary.

To display alarms on the line:

A display of true for C-bit parity framing would not indicate an alarm state, but that the far end is using C-bit parity.

To display and clear line error statistics:

To display the line state of the third DS2:

Performing an external loopback

To perform an external loopback test, use the -l option as follows:

Performing an internal loopback

An internal DS3 loopback connects the DS3 receive path to the DS3 transmit path at the D3. The transmitted DS3 signal is still sent to the network.

To perform an internal loopback test, use the -i option as follows:


Note: DS1 external loopbacks can be invoked manually with the FE-Loop command on the DS3 card. In addition, you can display DS1 error statistics with the T1-Stats command. To use these commands, first use the Open command to open a session with the card, as described at the beginning of this section.

Administering E1 cards

The E1-Stats command reports DS1-level line errors on E1 cards. Before entering it, use the Open command to open a session with the installed card. For example, to open a session with a card in shelf 1, slot 13:

Then enter the E1-stats command. The following example shows the command's syntax:

To view DS1-level statistics on the first line on the card:

To view and reset the statistics to 0 (zero) on line 2:

The Statistics cleared message at the end of the display indicates that the statistics have been reset to 0 (zero), because the command included the -c option. Table 3-2 explains the E1-Stats fields.

Table 3-3. E1-Stats command fields

Field

Event that increments the field

CRC Errors

A CRC-6 checksum shows data corruption in the signal.

Frame Slips

The MAX TNT receives E1 data at a frequency higher or lower than the internal line clock. In the process of realigning itself to the transmitter, the MAX TNT can skip or repeat a frame.

Framing Bit Errors

Framing bit errors occur when the MAX TNT receives E1 data at a frequency higher or lower than that of the internal line clock. In the process of realigning itself to the transmitter, the MAX TNT can skip or repeat a frame.

Out of Frame Events

The MAX TNT no longer detects a framing pattern in the receiving signal, or it detects a pattern at a different relative offset than expected.

Line Code Violations

The MAX TNT detected either a Bipolar Violation or Excessive Zeros, which means that one of the low-level E1 rules for encoding data was violated in the received signal.

Far end block errors

The far end reported an error in an E1 frame transmitted by the MAX TNT.

Administering HDLC cards

The HDLC command displays information about HDLC channels. You can also use it to display information about the Serial Communications Adapters (SCAs) on the FrameLine card, which are responsible for receiving and transmitting HDLC frames.

This command uses the following syntax:

where -option may be one of the following:

Option

Effect

-a

Displays all available HDLC channels.

-d

Displays disabled HDLC channels.

-f

Displays failed/non-existent HDLC channels.

-i

Displays in-use HDLC channels.

-p

Displays all possible HDLC channels.

This output shows the interface address of each HDLC channel in the slot, followed by the operational status, up-state, required-state, and admin-state of the channel.

For more information about the HDLC command, see the MAX TNT Reference Guide.

Administering IDSL cards

The BRIchannels and BRIdisplay commands display information about IDSL cards in the MAX TNT. You can use the IDSLcmd command to perform line loopbacks and test for block errors.

Using the BRIchannels command

To show IDSL channel information, enter the BRIchannels command:

where

For example:

Regardless of which option you enter, the BRIchannels command displays the following information:

Column Name

Description

dvOp

The operational state of the BRI channel. Values can be:

  • Down

  • Up

dvUpSt

The up status of the BRI channel. Values can be:

  • Idle

  • Reserved

  • Assigned

dvRq

The required state of the BRI channels. Values can be:

  • Down

  • Up

SAdm

The desired state of the device. Values can be:

  • Down

  • Up

Using the BRIdisplay command

The BRIdisplay command is a card-level command that displays actual bytes of the traffic on an IDSL card or its channels. The system monitors the traffic for the number of bytes you specify in the following syntax:

where count is the number of bytes to display in the command's output and channel is a number in the range of 0-31, specifying one of the 32 D channels on the card. If you do not specify a channel, the display includes all traffic on all the card's D channels.

To use the BRIdisplay command, first open a session with the IDSL card. Then specify the number of bytes and (optionally) the D channel to monitor. The following example displays up to 12 bytes of every packet on every D channel on the card:

To turn off the display, set count to zero, as in the following example:

Using the IDSLcmd command

Use the IDSLcmd command to loop back the IDSL line and test for near-end block errors (NEBE) and far-end block errors (FEBE). For more information about IDSL loopbacks, see Line loopbacks. For more information about block errors, see Block-error counters.

The IDSLcmd command has the following syntax:

where option is one of the following:

Option:

Effect

-1

Loops back the first B channel.

-2

Loops back the second B channel.

-a

Starts an analog loopback to test the IDSL hardware.

-f

Fetches block-error counters.

-z

Clears block-error counters.

-c

Starts sending corrupt CRCs.

-u

Cancels corrupt CRCs.

-r

Requests corrupt CRCs.

-n

Cancels the request for corrupt CRCs.

-?

Displays this summary.

The other syntax elements are:

Option:

Effect

channel

Enters the number of the channel to test (0-31). If you do not enter a channel number, the command applies to all channels.

EOC address

For a loopback, specifies the Embedded Operations Channel (EOC) address from which the MAX TNT rolls back the signal.

The default of 0 (zero) specifies the remote ISDN TA device.

A number from 1 to 6 specifies the number of an ISDN repeater between the MAX TNT and the remote TA. The repeater nearest the MAX TNT is number 1.

The number 7 specifies that the EOC command should be broadcast to all the nodes on the IDSL connection.

count

For a loopback, specifies the number of frames to send in the loopback. The default is 10.

buffer size

For a loopback, specifies the size of the frames sent in the EOC loopback. The default is 128 bytes.

Performing IDSL diagnostics

The diagnostic functions of the IDSL line card do not use either the D or B channels to transmit diagnostic function or signaling information. These diagnostic commands are sent in the M1, M2, and M3 bits of the U-superframe. For more information about the M1, M2, and M3 bits of the superframe, refer to ANSI T1-601, from ANSI 1991.

The MAX TNT provides the following diagnostic capabilities:

Line loopbacks

During a line loopback, the MAX TNT continuously sends out test frames over the D channel to the remote end. The frames transmitted differ in content in order to cover every possible bit pattern. Note that loopback occurs at the remote end of the connection, where the remote device loops back all the frames it receives on the BRI interface.


Note: Normal data traffic is disrupted when the line is in loopback mode.

When the MAX TNT is in loopback mode:

Note that you cannot request that the remote end stop sending corrupt CRCs while the MAX TNT is in loopback mode.

To put the line into loopback mode:

  1. Open a session with the IDSL card. For example, to connect to an IDSL card on shelf 1, slot 4:

  2. Start the loopback. For example, to loop back the first B channel on the first IDSL line:

The numbers displayed are cumulative totals, starting when the Line loopback command is issued. Each time the loopback command is started or restarted, the loopback counters are reset to 0.


Note: Only one loopback can be issued at a time on the same line.

Block-error counters

The block-errors counters displays the far-end block errors (FEBE) and near-end block errors (NEBE) that have occurred since the error buffers were cleared. The totals for each buffer return to zero after they reach 65535. The block-error totals are obtained from the remote device.

A near-end block error (NEBE) indicates that the MAX TNT has detected an error in a packet it has received. A far-end block error (FEBE) indicates that the remote device has detected an error in a packet it has received. In either case, the block errors shown in this display are stored in the far-end device's registers.

You can test the NEBE and FEBE counters by simulating transmission errors with artificially corrupted CRCs.

You can use the block error counters to monitor transmission quality at the U-interface. A block error is detected each time the calculated checksum of the received data does not correspond to the control checksum transmitted in the successive superframe. One block error indicates that one U-superframe has not been transmitted correctly. The block error count does not provide information regarding the number of bit errors in the U-superframe, but only indicates that the CRC failed in that superframe.

Testing the far-end block error counters
To test the FEBE counters:

  1. Open a session with the IDSL card. For example, to connect to an IDSL card on shelf 1, slot 4:

  2. Send corrupt CRCs over the B channel. For example, to test the first IDSL line's FEBE counter:

  3. Display the FEBE counter. For example, to display the FEBE for channel 1:

  4. To cancel the transmission of corrupt CRCs, use the -u option. For example:

Testing the near-end block error counters
To test the NEBE counters:

  1. Open a session with the IDSL card. For example, to connect to an IDSL card on shelf 1, slot 4:

  2. Request corrupt CRCs over the B channel. For example, to test the first IDSL line's NEBE counter:

  3. Display the FEBE counter. For example, to display the NEBE for channel 1:

  4. To cancel the reception of corrupt CRCs, use the -n option. For example:

Clearing the error registers
To clear the NEBE registers, use the -z option. For example:

The error register totals are also reset when the totals reach 65535.

Administering SDSL cards

You can use the MAX TNT SDSL diagnostic commands to display information about SDSL channels and to initiate loopbacks. You can also obtain SDSL inforamtion with the Read and List commands.

Using the SDSLlines command

To show SDSL channel information, enter the SDSLlines command:

where

Example: sdsllines -a

All SDSL lines:
(dvOp dvUpSt dvRq sAdm nailg)
Line { 1 3 1 } (Up Idle UP UP 00001)
Line { 1 3 2 } (Up Assigned UP UP 00002)
Line { 1 3 3 } (Up Assigned UP UP 00003)
Line { 1 3 4 } (Up Idle UP UP 00004)
Line { 1 3 5 } (Up Idle UP UP 00005)
Line { 1 3 6 } (Up Assigned UP UP 00006)
Line { 1 3 7 } (Up Idle UP UP 00007)
Line { 1 3 8 } (Up Assigned UP UP 00008)
Line { 1 3 9 } (Up Assigned UP UP 00009)
Line { 1 3 10 } (Up Assigned UP UP 00010)
Line { 1 3 11 } (Up Assigned UP UP 00011)
Line { 1 3 12 } (Up Assigned UP UP 00012)
Line { 1 3 13 } (Up Assigned UP UP 00013)
Line { 1 3 14 } (Up Assigned UP UP 00014)
Line { 1 3 15 } (Up Assigned UP UP 00015)
Line { 1 3 16 } (Up Idle UP UP 00016)

In addition to identifying SDSL channels, SDSLlines output includes the following fields:

Column Name

Description

dvOp

The operational state of the SDSL channel. Values can be:

  • Down

  • Up

  • None

dvUpSt

The up status of the SDSL channel. Values can be:

  • Idle

  • Reserved

  • Assigned

dvRq

The required state of the SDSL channels. Values can be:

  • Down

  • Up

SAdm

The desired state of the device. Values can be:

  • Down

  • Up

nailg

The nailed group that this line is assigned to.

Using the XDSLcmd command

During POST, the SDSL card performs a loopback on all channels. But also, you can use the XDSLcmd command to manually loop back the channels on the SDSL card.

The XDSLcmd command uses the following syntax:

where

The following example shows how to run a loopback test on channel 8 of an SDSL card in shelf 1, slot 6:

The loopback terminates when the count is reached.

Troubleshooting SDSL connections

If the SDSL link between the MAX TNT and the remote end does not come up after a few seconds, try the troubleshooting steps described in Table 3-4.

Table 3-4. troubleshooting SDSL connections

Action

Example

Verify that the card is active.

admin> read sdsl-statistics {1 11 1}
admin> list

Check the list to verify that Active=yes.

Verify that the card passed POST.

admin> read sdsl-statistics {1 11 1}

admin> list

Check the list to verify that Self Test=passed.

Check the data transfer rates.

admin> read sdsl-status {1 11 1}

admin> list

Verify that Up-Stream-Rate=784000 and Down-Stream-Rate=784000.

Administering RADSL cards

For RADSL-card administration, you can use MAX TNT diagnostic commands to perform BER tests and loopbacks.

Performing a RADSL BER test

When you perform a RADSL BER test, the remote end must also activate a BER test. If the remote end is not connected, an analog loopback is performed. During an analog loopback, the card itself is looped back. No remote device is involved.


Note: A BER test interrupts normal data transmission.

To perform a BER test:

  1. Read in the ADSL-CAP-Statistics profile. For example, to test the RADSL line in shelf 1, slot 11, port 1:

  2. List the contents of the profile. For example:

  3. Specify the duration of the BER test. For example:

  4. Start the BER test:

    The BERT-Error-Counter displays the BER test errors.

    The BERT-Operation-State displays the state of the connection.

  5. To end the BER test:

Performing loopbacks

During POST, the ADSL card performs a loopback on all channels. But also, you can use the XDSLcmd command to manually loop back the channels on the ADSL card.

The XDSLcmd command uses the following syntax:

where

The following example shows how to run a loopback test on channel 8 of an SDSL card in shelf 1, slot 6:

The loopback terminates when the count is reached.

Administering SWAN cards

To show serial WAN line information, enter the SWANlines command:

where

Although SWAN cards do not yet support compression, additional POST tests have been added to test the compression hardware on the cards. If a SWAN card fails POST after you upgrade to 2.0.0, the new tests have probably detected a problem with the compression chip, which requires that you return the card.

Administering modems

The MAX TNT provides diagnostic commands to display modem status, bring modems or channels up or down, or quiesce modems.

Using the Modem command to display modem status

To show modem information, enter the Modem command:

where

For example, to see which modems are in use:

For more information about the Modem command refer to the MAX TNT Reference Guide.

Bringing a modem or channel up or down

To administratively up or down a device, you can use the Device command or a Device-State profile. (For discussion of Device-State profiles, see Using the Device-State profile.)

For example, to administratively down modem 24 in slot 3 on shelf 1:

To bring the modem back up:

Disabling a modem

To disable a modem:

  1. Read in the LAN Modem profile. For example:

  2. Disable the modem:

  3. Write the profile to commit your changes:

Quiescing digital modems

The system creates a LAN-Modem profile for each installed modem card. Removing or downing a modem card does not delete this profile or change its contents. You can use the LAN-Modem profile to quiesce digital modems. Quiescing a modem makes it available for maintenance in a graceful way, not by tearing down the current connection, but by taking the channel out of service as soon as the connection is dropped.

To use a LAN-Modem profile, first open it and list its contents. For example:

Then, to quiesce a modem, list its Modem-Disable-Mode setting and change it to disable. For example:

To bring the modem back up:


Note: When you quiesce a modem, you can also quiesce an arbitrary idle T1 channel at the same time by using the Dis-Channel setting. For details, see the MAX TNT Reference Guide.



[Top][Contents][Prev][Next][Last]Search

techpubs@eng.ascend.com

Copyright © 1997, Ascend Communications, Inc. All rights reserved.