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


Using Administrative Profiles


This chapter covers the following topics:
Overview
How the MAX TNT creates administrative profiles
Using the Admin-State profile
Using the Slot-Info profile
Using the Slot-State profile
Using the Device-State profile
Using the T1-Stat profile
Using SWAN-Stat profiles
Using ADSL profiles
Using the IDSL-Stat profile
Using SDSL profiles

Overview

The MAX TNT provides a number of profiles that either monitor administration information or enable the administrator to change the state of a slot, line, or device. (For discussion of profiles not directly related to system administration, for example, profiles related to configuring lines, connections, or calls, see the MAX TNT Network Guide or the MAX TNT Hardware Installation Guide.)

Following are the MAX TNT administrative profiles:

Profile

Description

Admin-State

SNMP Administrative State

ADSL-CAP-Stat

ADSL-CAP line status

ADSL-CAP-Statistics

ADSL-CAP interface statistics

ADSL-CAP-Status

ADSL-CAP interface status

Base

System version and enabled features

Call-Info

Active call information

Call-Logging

RADIUS-accounting based feature for logging call information from the MAX TNT

Device-State

Device Operational State

Error

Fatal Error Log

IDSL-Stat

ISDL interface status

LAN-Modem

LAN modem disable state

Log

System event logging configuration

RADIUS-Stat

RADIUS status

SDSL-CAP-Stat

SDSL line status

SDSL-CAP-Statistics

SDSL interface statistics

SDSL-CAP-Status

SDSL interface status

Slot-State

Slot Operational State

Slot-Type

Slot Type profile

SNMP

SNMP profiles

SNMP Trap

SNMP trap destinations

SWAN-Stat

Serial WAN interface status

System

System-level parameters

T1-Stat

T1 line status

T3-Stat

T3 line status

Timedate

Current system time and date

User

Administrative user accounts

For information about the parameters contained within each of these profiles, see the MAX TNT Reference Guide.

An administrative profile uses the same set of commands as does any configuration profile in the MAX TNT. For example:

How the MAX TNT creates administrative profiles

The MAX TNT allocates SNMP interfaces when a card comes up for the first time. For example, the initial installation of a T1 card creates eight SNMP interfaces, one for each T1 line. An SNMP interface is associated with a physical address and is maintained across system resets.

Each object in the system has in an Admin-State profile, which stores the object's desired state and SNMP interface number. Admin-State profiles are stored in NVRAM to keep state information over system resets, so a physical device keeps the same interface number across system reset or power failures.

At system startup, the MAX TNT reads the Admin-State profiles. If the addressed device is not present in the system and has been replaced by a device of another type, the MAX TNT deletes that profile and creates a new one, with a new SNMP interface number. The next time the system is reset or power cycles, the old device's SNMP interface number becomes available for reassignment. This means that pulling a slot card does not free up interface numbers. When you reinstall the slot card, the same interface number is assigned. Also, pulling a slot card and replacing it with a slot card of another type does not free up the old interface numbers until the next power cycle or system reset.

For example, each T1 line has an Admin-State profile, and each of the 48 modems on a modem card has a profile. To read the Admin-State profile for the first T1 line in Slot 3, use the Read and List commands, as in the following example:

ADMIN-STATE/{ shelf-1 slot-3 1 } read
device-address* = { shelf-1 slot-3 1 }
slot-type = slot-card-8t1
snmp-interface = 2
desired-state = admin-state-up

Using the Admin-State profile

If you use an Admin-State profile to change the state of a device, the actual state of the device can differ from the desired state, as, for example, when a device is powering up or when the desired state is changed from up to down on a running slot.

To use the Admin-State profile to bring down a T1 line, use the Desired-State parameter, as in the following example:

To bring the device back up:

ADMIN-STATE/{ shelf-1 slot-3 1 } read
ADMIN-STATE/{ shelf-1 slot-3 1 } written

Using the Slot-Info profile

The read-only Slot-Info profile stores information about each slot card that has successfully booted. This profile is not stored in NVRAM, so it is not persistent across system resets or power cycles. It is created when the slot card boots, and is deleted when the slot card is removed or when the MAX TNT system is rebooted. It can be read by SNMP managers.

To view the Slot-Info profile, read and list its contents, as in the following example:

For information about the parameters in the Slot-Info profiles, see the MAX TNT Reference Guide .

Using the Slot-State profile

When you set the required operational state of a slot, the MAX TNT initiates a state change. IN terms of settings, Current-State changes to match Reqd-State. This setting is not persistent across system resets or power cycles. At system startup, the MAX TNT reinitializes the required state to match the actual state of the card.

To read a Slot-State profile and display its contents, proceed as in the following example:

The slot address is the physical address of the slot, and cannot be set directly. The Current-State value shows the current operational state of the slot, and can be any of the states described below.

State

Description

Oper-State-Down

The slot is in a nonoperational state.

Oper-State-Up

The slot is in normal operations mode.

Oper-State-Diag

The slot is in diagnostics mode.

Oper-State-Dump

The slot is dumping core.

Oper-State-Pend

The slot is no longer down, but is not yet ready for normal operation. This value denotes a transitional state in which additional shelf-to-slot communications are required to make the slot fully operational.

Oper-State-Post

The slot is running a self-test.

Oper-State-None

The slot is empty.

The Reqd-State parameter indicates the required operational state of the slot, which can be up or down. Changing this value initiates a state change for the device, as explained in the following sections.

To use the Slot-State profile to change slot states, proceed as in the following example.

To bring a slot down:

SLOT-STATE/{ shelf-1 slot-3 6 } read
To bring the slot back up:

Using the Device-State profile

Every host interface (such as an HDLC channel or a digital modem) or network interface (such as T1 or E1 channel) on the MAX TNT has a Device-State profile, which stores the current state of the device and allows you to change it. For example, each eight port T1 card has 192 Device-State profiles (one for each T1 channel). Similarly, each modem card has 48 Device-State profiles (one for each modem).

To open one of the profiles, proceed as in the following example:

DEVICE-STATE/{ { shelf-1 slot-3 1 } 24 } read
device-address* = { { shelf-1 slot-3 1 } 24 }
device-state = down-dev-state
up-status = idle-up-status
reqd-state = up-reqd-state
In the output, the Device-State parameter shows the current operational state of the device, which can be down, up, or none. (None indicates that the device does not exist.)

The Up-Status parameter is ignored unless the device is up (Device-State=Up-Dev-State). If the device is up, Up-Status shows the status of the device, which can be idle, reserved (will not be used until all idle devices of the same type are in use), or assigned (in use).

The Reqd-State parameter indicates the required operational state of the device, which can be up or down. Changing this value initiates a state change for the device. The change is complete when Device-State changes to match Reqd-State. This setting is not persistent across system resets or power cycles. At system startup, the MAX TNT reinitializes the required state to match the actual state of the card.

To change the state of a device by modifying its Device-State profile, proceed as in the following example.

To bring a device down:

DEVICE-STATE/{ { shelf-1 slot-3 6 } 24 } read
DEVICE-STATE/{ { shelf-1 slot-3 6 } 24 } written
To bring the device back up:

DEVICE-STATE/{ { shelf-1 slot-3 6 } 24 } read
DEVICE-STATE/{ { shelf-1 slot-3 6 } 24 } written

Using the T1-Stat profile

The T1-Stat profile displays the status of the T1 lines and their channels. Each T1 line has a separate profile. When the T3 card is operational, it creates a T3-Stat profile and twenty-eight T1-Stat profiles, which store the current status of the DS3 and each component DS1. Similarly, when a FrameLine card is operational, it creates a 10 T1-Stat profiles, which store the current status each component DS1.

To display the status of the T1 line, read and list the T1-Stat profile, as in the following example:

The Line-State parameter shows the overall state of the line which can be any of the following:

State

Description

Does-Not-Exist

Link is not physically on board.

Disabled

Line disabled.

Loss-of-Sync

Red-alarm state, plus or minus.

Yellow-Alarm

Yellow-alarm state.

AIS-Receive

Receiving keep-alive signal.

No-D-Channel

D-Channel failure.

Active

Multipoint established.

The channel-state parameter shows the state of each channel. Possible states are:

State

Description

Unavailable

Not available.

Unused

Not in use.

Out-of-service

Out of service.

Nailed-up

Nailed.

.

The Error-Count parameter shows an error count for each channel.

For complete descriptions of the parameters in the T1-Stat profile, see to the MAX TNT Reference Guide.

Using SWAN-Stat profiles

A SWAN-Stat profile displays the status of a serial WAN line. Each line on the SWAN card has a separate profile.

To display the status of a serial WAN line, use the command, as in the following example:

For descriptions of the parameters in the SWAN-Stat profile, see to the MAX TNT Reference Guide.

Using ADSL profiles

The ADSL-CAP-Stat, ADSL-CAP-Statistics, and ADSL-CAP-Status profiles facilitate the administration of Asymmetic Digital Subsriber Line (ADSL) connections.

Using the ADSL-CAP-Stat profile

The ADSL-CAP-Stat profile displays the status of the RADSL connection. Each port on the RADSL card has a separate profile.

To display the status of the RADSL lines, read and list in the ADSL-CAP-Stat profile, as in the following example:

For descriptions of the parameters in the ADSL-CAP-Stat profile, see the MAX TNT Reference Guide.

Using the ADSL-CAP-Statistics profile

The ADSL-CAP-Statistics profile indicates the status of the RADSL interface. To display RADSL line statistics, read and list the ADSL-CAP-Statistics profile, as in the following example:

Following are brief descriptions of the parameters in the ADSL-CAP-Statistics profile. (For complete descriptions, see the MAX TNT Reference Guide.)

Parameter

Indicates

Physical-Address

Identifies the physical address of the RADSL card, in the format {shelf slot item}, where item is the port number of the card.

Line-Up-Timer

Indicates the period of time the line has been in the up state, in the format {dd hh mm} where dd is the number of days, hh the number of hours, and mm the number of minutes.

RX-Signal-Present

Indicates whether this node is receiving a signal from the remote node.

Line-Quality

Indicates the line quality in decibels. For an RADSL interface, a reading of 18 dB or greater is required for reliable data transfer.

Up-Down-Cntr

Indicates the number of times the link has transitioned from an up state to a down state since the card was last reset.

Self-Test

Indicates whether the card has passed Power On Self Test (POST). Possible values are:

  • Passed

  • Failed

RS-Errors

Indicates the Reed Solomon errors that have not been corrected. This value is only used by the CPE unit. If the CPE unit detects a very high rate of RS Errors (255 every 50ms) for 8 consecutive seconds, it disconnects the line.

RS-Corrected-Errors

Indicates the number of Reed Solomon corrected errors.

Transmit-Power

Indicates the transmission power level in dB.

RX-Attenuation

Indicates the attentuation level of the receive signal from the far end.

Connection-SQ

Indicates the signal quality (SQ) in dB. When the line is active, the MAX TNT compares Connection-SQ to Line-Quality. If the difference between the Line-Quality and the Connection-SQ readings is greater than 6dB for 22 seconds, the MAX TNT disconnects the line. This typically occurs when a line becomes open or the remote unit loses power.

HDSL-RX-CRC-Error-Cnt

Indicates the number of HDLC receive CRC errors.

BERT-Enable

Enables or disables the Bit Error Rate (BER) test. The BER test counts data errors that occur on each channel, to check the data integrity of the connection. If the two ends of the RADSL connection are physically connected, the BER test is run between the two units. If the two ends are not connected, the BER test is run within the card itself. Note that both ends of the connection must enable the BER test.

A BER test interrupts normal data transmission.

BERT-Timer

Specifies the BER test timer. If the two ends or the connection are not connected, the BERT-Timer does not apply. In this case, you must set BERT-Enabled to No to end the BER test.

BERT-Operation-State

Indicates the state of the BER test. Possible values, and the status the indicate, are:

  • Waiting-for-511-sync-The node is waiting for the other node before starting its BER test.

  • Local-Loop-Active-The interface is in local analog loopback and is running the BER test. During an analog loopback, the card itself is looped back. No remote device is involved.

  • Active-The node is connected to the remote node and the BER test is running.

  • Stopped-The BER test is not enabled.

  • Loop-Back-Setup-The interface is being placed into analog loopback. During an analog loopback, the card itself is looped back. No remote device is involved.

  • Start-Up-The BER test is starting up.

  • Data-Overflow-During the test, a sudden surge of errors was received, causing the RADSL buffers to overflow. This could occur if the remote end stopped the test.

  • 511-Sync-Loss-The BER test went out of snyc.

BERT-Error-Counter

Indicates the number of errors received during the BER test.

Using the ADSL-CAP Status profile

The ADSL-CAP-Status profile indicates the status of the RADSL interface. To display RADSL line status, read and list the ADSL-CAP-Status profile, as in the following example:

Following are the parameters in the ADSL-CAP-Status profile, with descriptions of that they indicate. (For complete descriptions, see the MAX TNT Reference Guide.)

Parameter

Indicates

Physical-Address

Identifies the physical address of the RADSL card in the format {shelf slot item} where item is the port number of the card.

IF-Group-Index

SNMP interface group index assigned to this port.

Unit-Type

Operating mode of the card. The values can be either of the following:

  • COE (Central Office Equipment)

  • CPE (Customer Premise Equipment)

Dev-Line-State

Interface status, as one of the following values:

  • Port-Up-The RADSL connection is operating normally and data can be transferred between nodes.

  • Test-The unit is undergoing power-on self-testing.

  • Startup-Handshake-The RADSL units are trying to establish a connection. This node is waiting for the remote node's connection request. If this condition persists, it could indicate that the connection between the units is faulty.

  • Startup-Training-The units are negotiating a connection.

  • Startup-Download-The unit is downloading firmware code into the RADSL card.

  • Idle-The unit has been reset and has not yet downloaded any code.

  • Down-The RADSL port is down. Data cannot be transmitted between nodes. The link goes down if one of the nodes loses power or if line quality degrades. (For an explanation of how the MAX TNT determines line quality, see Connection-SQ.

  • Out-of-Service-The port has been administratively disabled.

Up-Stream-Rate

Upstream data rate. A value of 0 (zero) indicates that the data rate is unknown.

RADSL ensures maximum throughput for any given line conditions. The better the line quality the higher the data rate.

Down-Stream-Rate

Downstream data rate. A value of 0 (zero) indicates that the data rate is unknown.

RADSL ensures maximum throughput for any given line conditions. The better the line quality the higher the data rate. (For information on configuring the maximum downstream rate, see the MAX TNT Hardware Installation Guide.)

Major-Firmware-Ver

Major version number of the card's firmware.

Minor-Firmware-Ver

Minor version number of the card's firmware.

Hardware-Ver

Hardware version of the card.

Up-Stream-Constellation

Operational upstream constellation.This correlates to rate. Constellation is the number of points within the digital spectrum. A value of 0 (zero) indicates that the upstream constellation is unknown. A value of 1 (one) indicates automatic.

Down-Stream-Constellation

Operational downstream constellation.This correlates to rate. Constellation is the number of points within the digital spectrum. A value of 0 (zero) indicates that the downstream constellation is unknown. A value of 1 (one) indicates automatic.

Down-Stream-Operational-Baud

Downstream operational baud rate.

Using the IDSL-Stat profile

Following are the parameters in the IDSL-Stat profile, with brief descriptions of what they indicate. (For complete descriptions, see the MAX TNT Reference Guide.)

Parameter

Indicates

Physical-Address

Physical address of the IDSL card, in the format {shelf slot item} where item is the port number of the card.

Line-State

State of the line, as one of the following values:

  • Does-Not-Exist-The line is not physically connected.

  • Disabled-Line disabled.

  • No-Physical-No physical link.

  • No-Logical-Logical link failure.

  • No-Mgmt-Layer-2 link established but management entities not initialized.

  • Point-to-Point-Point-to-point link established.

  • Multipoint-1-Multipoint link established with one phone number and one SPID.

  • Multipoint-2-Multipoint link established with two phone numbers and two SPIDs.

Channel-State

State of the channels, as one of the following values:

  • Unavailable-Not available.

  • Unused-Not in use.

  • Out-of-Service-Out of service.

  • Nailed-Up-Nailed up.

  • Idle-Idle.

  • Clear-Pending-Clear pending.

  • Dialing-Dialing.

  • Ringing-Ringing.

  • Connected-Connected.

  • Signaling-Channel is a D Channel used for signalling.

  • Cut-through-Channel is a drop-and-insert source or destination.

  • Current-D-Channel is a current D Channel (NFAS signaling only).

  • Backup-D-Channel is a backup D Channel (NFAS signaling only).

  • Maintenance-Maintenance state.

Error-Count

Number of errors per channel that have occurred since the last reset.

Using SDSL profiles

SDSL profiles include SDSL-Stat, SDSL-Statistics, and SDSL Status.

Using the SDSL Stat profile

The SDSL-Stat profile indicates the status of the SDSL connection. Each port on the SDSL card has a separate profile.

To display the status of an SDSL line, read and lists its SDSL-Stat profile, as in the following example:

For descriptions of the parameters in the SDSL-Stat profile, see to the MAX TNT Reference Guide.

Using the SDSL Statistics profile

Following are the parameters in the SDSL Statistics profile, with brief descriptions of what they indicate. (For complete descriptions, see to the MAX TNT Reference Guide.)

Parameter

Indicates

Physical-Address

Physical address of the SDSL card, in the format {shelf slot item} where item is the port number of the card.

Line-Up-Timer

Period of time the line has been in the up state, in the format {dd hh mm} where dd is the number of days, hh the number of hours, and mm the number of minutes.

RX-Signal-Present

The local node is/is not receiving a signal from the remote node.

Line-Quality

Line quality in decibels. For an SDSL interface, a reading of -5dB or better is required for reliable data transfer.

Up-Down-Cntr

Number of times the link has transitioned from an up state to a down state since the card was last reset.

Self-Test

Whether the card has passed or failed Power On Self Test (POST).

Far-End-Db-Attenuation

Attenuation level of the signal received from the far end.

Firmware-Startup-Stage

Current firmware state.

HDLC-RX-CRC-Error-Cnt

The number of CRC errors that have occurred. A few CRC errors are normal, but the line is disconnected if 1500 errors occur within a 2-second time period.

Using the SDSL Status profile

Following are the parameters in the SDSL Status profile, with brief descriptions of what they indicate. (For complete descriptions, see to the MAX TNT Reference Guide.)

Parameter

Indicates

Physical-Address

Physical address of the SDSL card, in the format {shelf slot item} where item is the port number of the card.

IF-Group-Index

SNMP interface group index assigned to this port.

Unit-Type

Operating mode of the card. The values can be either of the following.

  • COE (Central Office Equipment)

  • CPE (Customer Premise Equipment)

Dev-Line-State

Interface status. as one of the following values:

  • Config-The physical interface is being configured.

  • Deactivate-The interface is transitioning to a port down state.

  • Deactivate-lost-The interface is waiting for the Loss of Signal (LOS) Timer to expire.

  • Inactive-The interface is starting up.

  • Activating-The interface is waiting for the remote side to start up.

  • Active-RX-The interface is waiting for the remote side to start 4 level transmission.

  • Port-Up-The interface is connected to the remote node and data can be transferred.

  • Portup-Pending-Deactive-The interface experienced an LOS or noise-margin error. This occurs when the line detects noise of more than -5dB.

Up-Stream-Rate

Upstream data rate.

Down-Stream-Rate

Downstream data rate.

Major-Firmware-Ver

Major version number of the card's firmware.

Minor-Firmware-Ver

Minor version number of the card's firmware.

Hardware-Ver

Hardware version of the card.



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

techpubs@eng.ascend.com

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