Status Window Reference

This chapter describes the MAX unit's status windows. This chapter covers these topics:

Using the MAX status windows

Status window reference in alphabetic order

Using the MAX status windows

This section gives an overview of the information contained in the eight windows that are displayed by default, and shows you how to swap out a default window and replace it with status windows of your choice. These are the parameters used to customize the display:

System
      Sys Config
            Status 1=10-100
            Status 2=10-200
            Status 3=50-100
            Status 4=00-200
            Status 5=50-300
            Status 6=50-400
            Status 7=00-100
            Status 8=00-000

|--------------------| |--------------------|
|10-100 1234567890   | |10-200 1234567890   |
| L1/LA nnnnnnnnnn   | | L2/RA ..........   |
|   12345678901234   | |   12345678901234   |
|   nnnnnnnnnnnnnn   | |   ..............   |
|--------------------| l--------------------|
|90-100 Sessions     | |00-200 15:10:34     |
|>  1 Active         | |>M31  Line    Ch    |
| O slc-lab-236      | | LAN session up     |
|                    | | slc-lab-236        |
|--------------------| |--------------------|
|90-300 WAN Stat     | |90-400 Ether Stat   |
|>Rx Pkt:     184318^| |>Rx Pkt:    3486092 |
| Tx Pkt:     159232 | | Tx Pkt:      10056 |
|    CRC:          0v| |    Col:       3530 |
|--------------------| |--------------------|
|00-100 Sys Option   | |Main Status Menu    |
|>Security Prof: 1  ^| |>00-000 System     ^|
| Software +5.0A0+    | | 10-000 Net/T1      |
| S/N: 5210003      v| | 20-000 Net/T1     v|
|--------------------| |--------------------|

Figure 2-1. Status windows

Navigating the status windows

Some of the status windows contain more information than can be displayed in the small window. If a lowercase v appears in the lower-right corner of a window, it means there is more information available. To scroll through additional information in a window, use the TAB key to move to that window.

Default status window displays

Line status windows

|--------------------| |--------------------|
|10-100 1234567890   | |10-200 1234567890   |
| L1/LA nnnnnnnnnn   | | L2/RA ..........   |
|   12345678901234   | |   12345678901234   |
|   nnnnnnnnnnnnnn   | |   ..............   |
|--------------------| l--------------------|

• The first line shows the menu number and column numbers for channels 1-10.

• The second line identifies the line (L1 or L2) and shows a a 2-character link status indicator and 1-character channel status indicator.

  For example:

  LA indicates Link Active (the line is physically connected).

  n means the channel is nailed.

  * indicates a current connection.

  - means the channels is idle but in service.

  s means the channel is an active D channel (ISDN only).

• The third line has column headers for channels 11-24.

  The fourth line shows a 1-character channel status indicator for channels 11-24.

|--------------------| l--------------------|
|90-100 Sessions     | |00-200 15:10:34     |
|>  1 Active         | |>M31  Line    Ch    |
| O slc-lab-236      | | LAN session up     |
|                    | | slc-lab-236        |
|--------------------| |--------------------|

The system message log provides a log of up to 32 of the most recent system events. Use the arrow key to scroll up (previous messages) or down (later ones). The Delete key clears all the messages in the log. The message log window is organized as follows:

• The first line shows the menu number and the time the most recent logged event occurred.

• The second line identifies the log entry number (M00-M31) and, if applicable, the line and channel on which the event occurred.

• The third line contains the text of the message.

  For example:

  Call Terminated means an active call disconnected normally.

  LAN session up means that an incoming connection has been established.

  No Connection means the remote device did not answer the call.

• The fourth line contains a message qualifier, such as a name or phone number that qualifies the message displayed.

|--------------------| |--------------------|
|90-300 WAN Stat     | |90-400 Ether Stat   |
|>Rx Pkt:     184318^| |>Rx Pkt:    3486092 |
| Tx Pkt:     159232 | | Tx Pkt:      10056 |
|    CRC:          0v| |    Col:       3530 |
|--------------------| |--------------------|

The Ether Stat window shows the current count of received frames, transmitted frames, and frames with errors at the Ethernet interface.

Sys Option and Main Status Menu windows

|--------------------| |--------------------|
|00-100 Sys Option   | |Main Status Menu    |
|>Security Prof: 1  ^| |>00-000 System     ^|
| Software +5.0A0+    | | 10-000 Net/T1      |
| S/N: 5210003      v| | 20-000 Net/T1     v|
|--------------------| |--------------------|

Up: 12:17:18:26

The last status window contains the Main Status Menu-a hierarchical menu that contains an entry for each line or installed card in the MAX. The structure of the Main Status Menu exactly follows the Main Edit Menu (the top-level configuration menu).

When the window that displays the Main Status Menu is active, the menu works like the Main Edit Menu. Use the arrow keys to scroll to a particular status menu. Then, press Return to open that menu and ESC to close it.

Customizing which status windows appear

For example, the MAX displays line status windows for the T1 (or E1) lines in Slot 1 in status windows 1 and 2 by default. To instruct it to use status windows 3 and 4 to display line status windows for the T1 (or E1) lines in Slot 2:

1. Open the System profile.

2. Type the number identifying line 1 in slot 2 the Status 3 parameter.

   Status 3=20-100
   

3. Type the number identifying line 2 in slot 2 the Status 4 parameter.

   Status 4=20-200
   

4. Close the System profile.

Status window reference in alphabetic order

BRI/LT window

X0-000 BRI/LT
    XO-100 Line Status
    X0-200 Line Errors	
    X0-300 Block Errors
    X0-400 LB Counters
    X0-500 Net Options

The Line Errors status window displays the errors recorded on all current channels in a channel-by-channel, line-by-line list. See Line Errors window.

The Block Errors status display shows the errors for near-end block errors (NEBE) and far-end block errors (FEBE). The numbers displayed are totals accumulated since the last time the block error buffers were cleared. The FEBE and NEBE error buffers can be cleared per line and per counter (you can clear the FEBE buffer for a line without clearing the NEBE buffer). The totals for each buffer wrap back to zero after they reach 65535. Restarting the MAX clears the buffers.

X0-X00  FEBE      NEBE
  1:      0         0
  2:      0         0
  3:      0         0
  4:      0         0
  5:      0         0
  6:      0         0
  7:      0         0
  8:      0         0

X0-XXX  XMIT      RECV
  1:      0         0
  2:      0         0
  3:      0         0
  4:      0         0
  5:      0         0
  6:      0         0
  7:      0         0
  8:      0         0

Call Status window

A Call Status window exists for each host port. It is the first option listed in the PortN Stat window, and its window number is XN-100, where X is the module number and N is the AIM port number.

71-000 Port1 Stat
>71-100 Call Status
 71-200 Message Log
 71-300 Statistics  
 71-400 Port Opts
 71-500 Session Err
 71-600 Port Leads

71-100 Albuquerque+ C
CALLING/ONLINE
336K      6 channels
 Albq. NM

The second line shows the call status message corresponding to the current state. It can change dynamically as you dial, modify, or receive calls. These are the call status characters and messages that can appear:

Table 2-1. Call status characters and messages

Status indicator	Status message	Description
Blank	IDLE	No calls exist and no other MAX operations are being performed.
A	ANSWERING	An incoming call is being answered.
R	RINGING	An incoming call is on the line, ready to be answered.
C	CALLING	An outgoing call is being dialed.
O	ONLINE	A call is up on the line.
H	CLEARING	The current call is being cleared.
D	LOCAL LOOP	Local loopback diagnostic tests are in progress.
!	HANDSHAK	The MAX is exchanging information with the inverse multiplexer at the remote end and verifying that the call is transmitting reliably.
!	SETUP ADD	The MAX is preparing to add channels while a call is online and passing data.
!	SETUP REM	The MAX is preparing to remove channels while a call is online and passing data.
!	SETUP HND	The MAX is preparing to handshake for resynchronization while a call is online and passing data.
L	LOOP MAST	You have selected DO 6 or Control-D 6 to begin a remote loopback test. While the loopback test is in progress, the remote end displays the status message LOOP SLAV.
T	BERT MAST	The MAX has connected with the remote-end AIM-compatible product and is performing an automatic BERT (byte error test). Or, you are performing a manual BERT from the local MAX.
T	BERT SLAVE	Your MAX has received a call and the calling AIM-compatible product is performing an automatic BERT. Or, someone using the remote MAX is performing a manual BERT test.

For calls other than FT1-B&O, the third line of the Call Status window shows the current data rate in kbps, and how many channels this data rate represents. If the current call type is FT1-B&O, the third line of the Call Status window shows how many channels the online data represents, followed by the number of nailed-up channels the MAX has placed offline because their quality was poor. This screen shows the call status of an FT1-B&O call with six channels online and two channels offline:

21-100 Albuquerque+ C
CALLING
336K  6/2  channels
 Albq. NM

The last line of the Call Status window contains the name of the AIM port of the remote end AIM-compatible product that has been connected. If the remote end Port profile is not named, the MAX uses the remote end module name taken from the host-module profile. If both the module and the port are not named, the MAX uses the remote end system name.

CDR window

You can view CDR status displays in real time through the vt100 interface or Palmtop Controller. This screen shows the four-line CDR display:

00-400 CDR 
 93:05:28:10:33:52
 OR 025 384KR 02-01
 15105551212

The second line displays the time the event occurred in this format:

<year>:<month>:<day>:<hour>:<minute>:<second>

The third line displays describes the CDR event. It shows an event description, event ID, the data service in use, and the slot-port address on which the event occurred, in that order.

• CDR event description

  The event description uses these abbreviations:

  • OR for Originated (outgoing call)

  • AN for Answered (incoming call)

  • AP for Assigned to Port or module (incoming call)

  • CL for Cleared

  • OF for Overflowed

  All events except OF are associated with calls. OF indicates that the CDR buffer overflowed because events occurred faster than the MAX could report them.

• CDR event ID

  The MAX creates a new event ID for every DS0 channel originating a connection. The event ID ranges from 0 to 255; events after 255 start the count again at 0. In addition, CDR creates a new event ID for every change in a channel's status. Because a MAX call can consist of several channels, the MAX can generate multiple CDRs for every change in call status.

• The data service in use

  Indicates the data service, using values nearly identical to those available to the Data Svc parameter in the Call profile. The only difference is that the Data Svc values 384K/H0 and 1536K correspond to the CDR data service values 384K and 1536KR, respectively.

• The slot-port address on which the event occurred

  For example, if the event occurred on the first port of a Host/6 card installed in slot 3, the slot-port address is 03-01.

For related information, see the Data Svc parameter in Chapter 3, MAX Alphabetic Parameter Reference.

Dyn Stat window

90-500 Dyn Stat
 Qual Good 00:02:03
 56K     1 channels
 CLU  12%  ALU  23%

The first line of the Dyn Stat window shows the window number and the name of the current Connection profile. If no connection is currently active, the window name appears instead (Dyn Stat).

The second line lists the quality of the link and the amount of time the link has been active. When a link is online more than 96 hours, the MAX reports the duration in number of days. The link quality can have one of the following values:

• Good (The current rate of CRC errors is less than 1%).

• Fair (The current rate of CRC errors is between 1% and 5%).

• Marg (The current rate of CRC errors is between 5% and 10%).

• Poor (The current rate of CRC errors is more than 10%).

• N/A (The link is not online).

The last line displays these values:

• CLU (Current Line Utilization)

  CLU is the percentage of bandwidth currently being used by the call for transmitted data, divided by the total amount of bandwidth available.

• ALU (Average Line Utilization)

  ALU is the average amount of available bandwidth used by the call for transmitted data during the current history period as specified by the Sec History and Dyn Alg parameters.

90-600 Ether Opt
>I/F: COAX
 Adrs: 00c07b322bd8

Ether Stat window

90-400 Ether Stat
>Rx Pkt:      106
    Col:        0
 Tx Pkt:      118

• Rx Pkt (the number of Ethernet frames received on the Ethernet interface)

• Col (the number of collisions detected at the Ethernet interface)

• Tx Pkt (the number of Ethernet frames transmitted over the Ethernet interface)

Ethernet window

50-000 Ethernet
 50-100 Sessions
 50-200 Routes
 50-300 WAN Stat

The FDL Stats windows are the fourth and fifth options listed in the Net/T1 window:

10-000 Net/T1
 10-300 Line Errors ^
 10-400 FDL1 Stats
>10-500 FDL2 Stats
 10-600 Net Options

10-500 FDL2 Stats
>Error Events...
 Current Period...
 Last 24 Hours...
 00:00...          v

Error-register statistics

Performance-register statistics

If you have a D4 (SF) interface, no carrier performance data is recorded.

The performance registers contain both user and carrier ESF (Extended Superframe Format) The user performance-registers appear in the middle column after the register names, and the carrier performance-registers appear in the last column:

You can reset the user performance registers using Clr Perf1 and Clr Perf2 in the Line Diag menu, but only the carrier can reset the carrier registers. All performance registers are reset upon power-up or software reset.

Table 2-2 shows the FDL performance registers:

Table 2-2. FDL performance registers

Register name	Description
EE	Displays the number of error events accumulated since the last time this register was reset. An ESF error event is counted when the CRC-6 (Cyclic Redundancy Check-6) calculations at the receiving end of the T1 span do not match the CRC-6 calculations at the sending end. This mismatch indicates that the frame had at least one data error. Error events have no meaning for D4 lines. Only ESF lines carry the CRC-6 signature used to check the quality of the PRI line as a whole.
ES	Specifies errored seconds. For ESF lines, this register displays the number of seconds in the 15-minute period in which there was at least one error event, or in which two or more framing errors were detected within a 3-millisecond interval. For D4 lines, this register displays the number of seconds in which one or more framing bit errors (FE) were detected or in which a controlled slip (CS) occurred.
US	Indicates unavailable seconds-the number of seconds in the 15-minute period preceded by at least 10 consecutive severely errored seconds (SS).
SS	Displays severely errored seconds-the number of seconds in the 15-minute period in which there were at least 320 CRC-6 errors as detected by the MAX, or in which the T1 line was out of frame. For D4 lines, this register displays the number of one-second intervals containing eight or more FE events or one or more SEF events.
BS	Specifies bursty errored seconds-the number of seconds in the 15-minute period in which there were at least 2, but not more than 319, CRC-6 errors as detected by the MAX.
LF	Indicates loss of frame seconds- the number of seconds in the 15-minute period in which the T1 line was out of frame.
CS	Displays controlled slip seconds-the number of seconds in the 15-minute period in which a frame was either replicated or deleted.

For related information, see Clr Err1, Clr Err 2, Clr Perf1, and Clr Perf2 in Chapter 3, MAX Alphabetic Parameter Reference.

FR Stat window

B0-500 FR profile
 Rx Pxt:       2560
 Tx Pxt:       3000
    CRC:        003
CprofX           16
 Rx Pxt:       2560
 Tx Pxt:       3000

Host/6 (Host/Dual) window

60-000 Host/Dual
 60-100 Host Config
 60-200 Port1 Menu
 60-300 Port2 Menu

To open the Line Errors window, you can choose Line Errors in the Net/T1 or Net/BRI status window. For example:

10-000 Net/T1
 10-100 Line 1 Stat
 10-200 Line 2 Stat
 10-300 Line Errors

10-300 Ln1  Ln2    
 1:      0    -
 3:     33    -
 4:      0    -    

The second column indicates the number of byte errors the MAX has detected on the channel in line 1 during the current call. The third column displays the number of byte errors the MAX has detected on the channel in line 2 during the current call.

If a channel is not associated with a current call, a dash (-) appears in place of errors. Any channel in the Line Errors display that would show dashes in both columns is omitted.

Line N Stat window (N=1-2)

10-000 Net/T1
 10-100 Line 1 Stat
 10-200 Line 2 Stat
 10-300 Line Errors

The second line begins with the line number, followed by the link status using one of the two-character abbreviations shown in Table 2-3. The link status is followed by a single-character which indicates channel status, shown in Table 2-4. The third line has column headers for the remaining channels. The fourth line continues where the second line left off, showing the status of the remaining channels.

Table 2-3. T1 link status indicators

Link status	Mnemonic	Description
LA	Link active	The line is active and physically connected.
RA	Red Alarm/Loss of Sync	The line is not connected, improperly configured, experiencing a very high error rate, or is not supplying adequate synchronization. When the line is in this state, either the RA LED alone is lit, or both the RA and LS LEDs are lit.
YA	Yellow Alarm	The MAX is receiving a Yellow Alarm pattern. The Yellow Alarm pattern is sent to the MAX to indicate that the other end of the line cannot recognize the signals the MAX is transmitting. When the line is in this state, the YA LED is lit.
DF	D-channel failure	The D channel for a PRI line is not currently communicating.
1S	Keep alive (all ones)	A signal is being sent from the T1 PRI network to the MAX to indicate that the T1 PRI line is currently inoperative. When the line is in this state, the 1S LED is lit.
DS	Disabled link	The line is physically connected, but you have disabled the line in the Line profile.

A single character represents the status of each channel in the line:

Table 2-4. T1 channel status indicators

Channel status	Mnemonic	Description
.	Not available	The channel is not available because the line is disabled, has no physical link, or does not exist, or because the channel is marked Unused in the channel usage parameter of the Line profile.
*	Current	The channel is connected in a current call
-	Idle	The channel is currently idle (but in service).
d	Dialing	The MAX is dialing from this channel for an outgoing call.
r	Ringing	The channel is ringing for an incoming call.
m	Maintenance	The channel is in maintenance/backup (ISDN only).
n	Nailed	The channel is marked Nailed in the Line profile.
o	Out Of Service	The channel is out of service (ISDN only).
s	ISDN D-channel	The channel is an active D channel (ISDN only).

Line Status (BRI) window

40-100 12345678    O
Link   PPP-----   
B1     ***.....     
B2     ***.....     

Table 2-5. BRI line status indicators

The third and fourth lines describe the state of the B1 and B2 channels, respectively, using the indicators shown in Table 2-6.

Table 2-6. B1 and B2 channel status indicators

Channel status	Mnemonic	Description
.	Not available	The channel is not available because the line is disabled, has no physical link, or does not exist, or because the channel is marked Unused in the channel usage parameter of the Line profile.
*	Current	The channel is connected in a current call
-	Idle	The channel is currently idle (but in service).
d	Dialing	The MAX is dialing from this channel for an outgoing call.
r	Ringing	The channel is ringing for an incoming call.

Message Log windows

Each message log displays up to 32 of the most recent system events the MAX has recorded. When you select the Message Log option, the most recent message appears. The message logs update dynamically. Press the Up-arrow key to display the previous entry. Press the Down Arrow key to display the next entry.

AIM port message logs

71-200 12:23:47    O
>M31 Line 1 Ch 13
Moved to primary
 1 secondary chans

00-200 12:23:47    O
>M31 Line 1 Ch 13
 Moved to primary
 1 secondary chans

00-200 11:23:55
>M31 Line 1 Ch 07
 Incoming Call
 MBID 022

Log messages

Table 2-7. Informational log messages

Table 2-8 shows the warning messages that can appear in the Message Log windows:

Table 2-8. Warning log messages

Message	Description
Busy	The phone number was busy when the call was dialed.
Call Disconnected	The call has ended unexpectedly.
Call Refused	An incoming call could not be connected to the specified AIM port, digital modem, packet-handling module, or terminal server because the resource was busy or otherwise unavailable.
Dual Port req'd	The call could not be placed because both ports of the dual-port pair were not available.
Far End Hung Up	The remote end terminated the call normally.
Incoming Glare	The MAX could not place a call because it saw an incoming "glare" signal from the switch. Glare occurs when you attempt to place an outgoing call and answer an incoming call simultaneously. If you receive this error message, you have probably selected incorrect Line profile parameters.
Internal Error	Call setup failed because of a lack of system resources. If this type of error occurs, notify Ascend customer support.
LAN security error	This warning appears after Incoming Call but before Call Terminated if a PPP, MP+, terminal server, or Combinet session has failed authentication, another session by the same name already exists, or the timeout period for RADIUS/TACACS authentication has been exceeded. For details, see the Auth Timeout parameter in Chapter 3, MAX Alphabetic Parameter Reference.
Network Problem	The call setup was faulty because of problems within the WAN or in the Line profile configuration. The D channel might be getting an error message from the switch, or the telco might be experiencing a problem.
No Chan Other End	No channel was available on the remote end to establish the call.
No Channel Avail	No channel was available to dial the initial call.
No Connection	The remote end did not answer when the call was dialed.
No Phone Number	No phone number exists in the Call profile being dialed.
No port DSO Mins	No maximum has been specified for the Max DS0 Mins or Max Call Mins parameter in the Port profile.
No System DSO Mins	No maximum has been specified for the Max DS0 Mins parameter in the System profile.
Not Enough Chans	A request to dial multiple channels or to increase bandwidth could not be completed because there were not enough channels available.
Not FT1-B&O	The local MAX attempted to connect an FT1-B&O call to the remote end, but the call failed because the call type at the remote end was not FT1-B&O.
Remote Mgmt Denied	The MAX rejected a request to run the remote MAX by AIM remote management because the Remote Mgmt parameter in the System profile at the remote end is set to No.
Request Ignored	The MAX denied a request to manually change bandwidth during a call because the Call Mgm parameter in the Call profile has the value Dynamic. With this value, the MAX allows only automatic bandwidth changes.
Wrong Sys Version	The remote-end product version was incompatible with the version of the local MAX. The software version appears on the Sys Options status window.

Table 2-9 shows connection messages that can appear on the fourth line of the Message Log windows:

Table 2-9. Message indicators

Indicator	Description
MBID	The MBID parameter appears with either the Incoming Call or Assigned to Port (line 3) messages. The first message means an incoming call has been received and the second message means it has been routed to a MAX port. If you cannot match the MBID value of an incoming call log to the MBID value in an assigned-to-port log, the call disconnected, often because the intended port was busy. MBID also appears in the System log.
Channels	This parameter specifies the number of channels added to or removed from a call. It appears with the Added Bandwidth, Removed Bandwidth, Moved to Primary, and Moved to Secondary messages. When line 3 is an Outgoing Call, line 4 displays the Phone Number dialed. In multichannel calls, line 4 displays the phone number for the first connection. Only the phone number appears; the parameter name Phone Number does not.
Cause Code	This parameter indicates a signaling error or event. The code number was sent by the ISDN network equipment and received by the MAX.
Name	When the message in line 3 is either LAN session up or LAN session down, line 4 displays the remote end's Name. If the session is a Combinet bridging link, the MAC address is displayed. If the session is a PPP link, either the remote end's system name (as specified by the Name parameter in the System profile) or IP address (as specified by the IP Adrs parameter in the Ethernet profile) is displayed. The IP address is displayed only if the system's name is not known.
CLID	When an incoming call is answered and the calling party number is known, line 4 specifies the CLID (calling line ID). When the CLID appears, the MBID does not.

Modem window

80-000 Modem Stat
12345678
-**-*-**

Table 2-10. Modem status characters

Net T1 and Net BRI windows

10-000 Net/T1
 10-100 Line 1 Stat
>10-200 Line 2 Stat
 10-300 Line Errors 

40-000 Net/BRI
>40-100 Line Status
 40-200 Line Errors

Net Options 
>T1/PRI Network I/F
 2 Network I/F(s)
 Type: CSU/CSU

The second line shows the number of network interfaces associated with the module.

The third line shows whether internal CSUs are installed for the T1 lines. These values can display:

• Type: DSX/DSX

• Type: CSU/DSX

• Type: DSX/CSU

• Type: CSU/CSU

00-300 Port Info
 Avail BW= 128K
 DS0 Mins=12
>71 O G  384K      v

The fourth line and each line that follows it display the AIM host-interface status. It includes these fields, in the order shown:

• Module and port number

• Call status indicator (see Table 2-11)

• Call quality indicator (the quality of the link for an active call)

  This value can be G (good), F (fair), M (marginal), N (not applicable), or P (poor). Not applicable (N) appears before the call is connected end-to-end.

• Bandwidth (the approximate bandwidth given to the codec)

  If the call is an FT1-B&O call, these values specify the offline bandwidth as well as the online bandwidth of the call. This screen shows statistics for an FT1-B&O call on the base system's AIM port 2:

  00-300 Port Info
   Avail BW= 128K
   21 O G 384K
  >22 O G 128K/  64K 
  

  The fourth line shows that AIM port 2 has an FT1-B&O call online. The call is running at 128 kbps, and an additional 64 kbps is available but has been removed from the call. Whenever nailed-up channels in an FT1-B&O call are bad, the MAX removes them from the call and monitors them for possible restoration. In this example, the MAX has removed one 64K channel and is monitoring it.

Table 2-11. Call status characters for AIM ports

Port Leads window

For example, this screen shows the Port Leads window for the serial WAN port:

B0-100 Port Leads  
 DSR+ DCD+ RI + DTR+

The first line of the window shows the slot-port address of the AIM port. The remaining lines show the state of the control leads going into and out of the serial port. The plus symbol (+) indicates an active control lead, while the minus symbol (-) indicates that the lead is inactive. For RS-366 dialing output and input signals, the MAX uses the abbreviations in Table 2-12.

Table 2-12. RS-366 abbreviations

Output	Input
acr (Abandon Call and Retry)	dp (Digit Present)
pnd (Present Next Digit)	crq (Call Request)
dlo (Data Line Occupied)

The digit field in the lower right-hand corner displays the last digit dialed if the port is an RS-366 dialing interface.

Table 2-13 lists the abbreviations for dialing output and input signals at the AIM port. The Clear to Send (CTS) output signal is not monitored in this window. The standard cables supplied with the MAX tie CD and CTS together.

Table 2-13. Serial host port abbreviations

Output	Input
DSR (Data Set Ready)	DTR (Data Terminal Ready)
CD (Carrier Detect)	RTS (Request to Send)
RI (Ring Indicate)

Table 2-14 lists the abbreviations used for dialing output and input signals at the serial WAN port.

Table 2-14. Serial WAN port abbreviations

Output	Input
DSR (Data Set Ready)	DTR (Data Terminal Ready)
CD (Carrier Detect)
RI (Ring Indicate)

Port Opts window

71-400 Port Opts    
>V.35 Host I/F

PortN Stat window

71-000 Port1 Stat
 71-100 Call Status
 71-200 Message Log
 71-300 Statistics
>71-400 Port Opts 
 71-500 Session Err
 71-600 Port Leads  

50-200 Routes
>D: 223.0.100.129
 G: 223.0.100.129
 LOOP Active

The second line in a Routes window contains the destination address. The destination can be a network address or the address of a single station. If this route is the default route, the word Default replaces the address.

The third line shows the address of the router.

The fourth line can have one of the values listed in Table 2-16.

Table 2-16. Routes window values

Value	Description
LAN Active	This active route has a destination on the local subnet.
WAN Active	This active route has a destination off the local subnet.
LOOP Active	This active route has this MAX as a router and destination. No data packets are propagated.
LAN Inactive	This inactive route has a destination on the local subnet.
WAN Inactive	This inactive route has a destination off the local subnet.

A route becomes inactive if taken out of service. Whether a dialed-up link in a route has been connected does not affect the active or inactive status of the route

Serial WAN window

Session Err window

21-500 Errors      O
 1: 1: 1:     0  -
 1: 1: 3:    33  -
 1: 1: 4:     0  -

Column 4 shows the number of byte errors detected during the current call. In an online FT1-B&O call, any channels that the MAX has removed appear in the status window with an asterisk (*) following in the error column.

If a channel is not associated with the current call, its session errors are displayed as a dash (-). Any line in the display that would show dashes in both columns is omitted.

For related information, see the Line Errors window.

Sessions window

50-100 Sessions
>5 Active
 O Headquarters

<status> <remote device>

where <status> is a status indicator and <remote device> is the name, address, or CLID of the remote device. Table 2-17 lists the session status characters that can appear.

Table 2-17. Session status characters

Indicator	Mnemonic	Description
Blank	Nothing	No calls exist and no other MAX operations are being performed
R	Ringing	An incoming call is ringing on the line, ready to be answered.
A	Answering	The MAX is answering an incoming call.
C	Calling	The MAX is dialing an outgoing call.
O	Online	A call is up on the line.
H	Hanging up	The MAX is clearing the call.

Statistics window

71-300 Albuquerqu+ O
 Qual Good 01:23:44 
 Max Rel Delay 10
 CLU  80%  ALU  77%

The second line lists the quality of the call and the call duration. When a call lasts more than 96 hours, the window displays the call duration in number of days. The call quality, or Qual, can be Good, Fair, Marg (Marginal), or Poor.

• Good means that no errors have been detected during the transmission of the call.

• Fair means that some errors have been detected in transmission.

• Marg means that a significant number of errors have been detected; in this case, reliable transmission is not guaranteed and resynchronization is recommended.

• Poor means that the MAX may drop individual channels from the call, or clear the call automatically.

21-300 Albuquerqu+ O
 Qual Good 2=Poor 
 Max Rel Delay 10
 CLU  80%  ALU  77%

The last line displays these values:

• CLU (Current line utilization): The percentage of bandwidth currently being used by the call for transmitted data, divided by the total amount of bandwidth that is available.

• ALU (Average line utilization): The average amount of available bandwidth used by the call for transmitted data during the current history period as specified by the Sec History and Dyn Alg parameters.

For related information, see the Call Mgm, Call Type, Dyn Alg, and Sec History parameters in Chapter 3, MAX Alphabetic Parameter Reference.

Syslog window

• Level 4 (warning) and Level 5 (informational) syslog messages

  The data for level 4 (warning) and level 6 (informational) syslog messages is derived from the Message Log displays. Level 4 and 6 messages are presented in this format:

  ASCEND: slot-n port-n | line-n, channel-n, text-1, text-2

  The device address (slot, port or line, and channel) is followed by two lines of text, which are displayed on lines 3 and 4 of the Message Log window.

  The device address is suppressed when it is not applicable or unknown.

  Text-2 specifies the system name, IP address, or MAC address of the remote end of a session for the "LAN session up" and "LAN session down" messages (text-1).

• Level 5 (notice) syslog messages

  The data for level 5 (notice) syslog messages is derived from the CDR display, lines 3 and 4. Level 5 messages are presented in this format:

  ASCEND: call-event-ID event-description slot-n port-n data-svcK phone-n

  • The call-event-ID specifies the event ID in the CDR display.

  • The event description is a description of the CDR event.

  • The slot-n port-n address indicates the AIM port, which is suppressed when it is not applicable or unknown.

  • Data-svcK indicates the data service in use.

  • Phone-n is the phone number.

  Because the syslog host adds the date, type, and name of all syslog messages from the MAX, that data is not included in the message format. Some example syslog entries follow:

  Oct 21 11:18:07 marcsmax ASCEND: slot 0 port 0, line 1, channel 1, \
  No Connection
  

  Oct 21 11:18:07 marcsmax ASCEND: slot 4 port 1, Call Terminated
  

  Oct 21 11:19:07 marcsmax ASCEND: slot 4 port 1, Outgoing Call, 123
  

  In this example, three messages are displayed for the system "marcsmax." Notice that the back-slash (\) indicates the continuation of a log entry onto the next line.

• Disconnect cause codes and progress codes

  If the syslog option is set, a call-close (CL) message is sent to the syslog daemon whenever a connection is closed. Additional information about the user name, disconnect reason, progress code, and login host is appended to each CL message. The disconnect cause code uses this format:

  [name,]c=xxxx,p=yyyy,[ip-addr]

  Name is the name of a profile. It can contain up to 64 characters. A name containing more than 64 characters is truncated, and '+' is added to the truncated name. The name appears for incoming calls only.

  Xxxx is the disconnect cause code.

  Yyyy is the connection progress code.

  Ip-addr is the login host's IP address for Telnet and raw TCP connections (if applicable).

Table 2-18. Ascend Disconnect Cause codes

Code	Description
0	No reason.
1	The event was not a disconnect.
2	The reason for the disconnect is unknown. This code can appear when the remote connection goes down.
3	The call has disconnected.
4	CLID authentication has failed.
These codes can appear if a disconnect occurs during the initial modem connection.
10	The modem never detected DCD.
11	The modem detected DCD, but became inactive.
12	The result codes could not be parsed.
These codes are related to immediate Telnet and raw TCP disconnects during a terminal server session.
20	The user exited normally from the terminal server.
21	The user exited from the terminal server because the idle timer expired.
22	The user exited normally from a Telnet session.
23	The user could not switch to SLIP or PPP because the remote host had no IP address or because the dynamic pool could not assign one.
24	The user exited normally from a raw TCP session.
25	The login process ended because the user failed to enter a correct password after three attempts.
26	The raw TCP option is not enabled.
27	The login process ended because the user typed Ctrl-C.
28	The terminal server session has ended.
29	The user closed the virtual connection
30	The virtual connection has ended.
31	The user exited normally from an Rlogin session
32	The user selected an invalid Rlogin option.
33	The MAX has insufficient resources for the terminal server session.
These codes concern PPP connections.
40	PPP LCP negotiation timed out while waiting for a response from a peer.
41	There was a failure to converge on PPP LCP negotiations.
42	PPP PAP authentication failed.
43	PPP CHAP authentication failed.
44	Authentication failed from the remote server.
45	The peer sent a PPP Terminate Request.
46	LCP got a close request from the upper layer while LCP was in an open state.
47	LCP closed because no NCPs were open.
48	LCP closed because it could not determine to which MP bundle it should add the user.
49	LCP closed because the MAX could not add any more channels to an MP session.
These codes are related to immediate Telnet and raw TCP disconnects, and contain more specific information that the Telnet and TCP codes listed earlier in this table.
50	The Raw TCP or Telnet internal session tables are full.
51	Internal resources are full.
52	The IP address for the Telnet host is invalid.
53	The MAX could not resolve the hostname.
54	The MAX detected a bad or missing port number.
The TCP stack can return these disconnect codes during an immediate Telnet or raw TCP session.
60	The host reset the TCP connection.
61	The host refused the TCP connection.
62	The TCP connection timed out.
63	A foreign host closed the TCP connection.
64	The TCP network was unreachable.
65	The TCP host was unreachable.
66	The TCP network was administratively unreachable.
67	The TCP host was administratively unreachable.
68	The TCP port was unreachable.
These are additional disconnect codes.
100	The session timed out because there was no activity on a PPP link.
101	The session failed for security reasons.
102	The session ended for callback.
120	One end refused the call because the protocol was disabled or unsupported.
150	RADIUS requested the disconnect.
160	The allowed retries for V.110 synchronization have been exceeded.
170	PPP authentication has timed out.
180	The call disconnected as the result of a local hangup.
185	The call disconnected because the remote end hung up.
190	The call disconnected because the T1 line that carried it was quiesced.
195	The call disconnected because the call duration exceeded the maximum amount of time allowed by the Max Call Mins or Max DS0 Mins parameter on the MAX.

Table 2-19 lists the Ascend Connect codes.

Table 2-19. Ascend Connect codes

Code	Explanation
0	No progress.
1	Not applicable.
2	The progress of the call is unknown.
10	The call is up.
30	The modem is up.
31	The modem is waiting for DCD.
32	The modem is waiting for result codes.
40	The terminal server session has started up.
41	The MAX is establishing the TCP connection.
42	The MAX is establishing the immediate Telnet connection.
43	The MAX has established a raw TCP session with the host. This code does not imply that the user has logged into the host.
44	The MAX has established an immediate Telnet connection with the host. This code does not imply that the user has logged into the host.
45	The MAX is establishing an Rlogin session.
46	The MAX has established an Rlogin session with the host. This code does not imply that the user has logged into the host.
60	The LAN session is up.
61	LCP negotiations are allowed.
62	CCP negotiations are allowed.
63	IPNCP negotiations are allowed.
64	Bridging NCP negotiations are allowed.
65	LCP is in the Open state.
66	CCP is in the Open state.
67	IPNCP is in the Open state.
68	Bridging NCP is in the Open state.
69	LCP is in the Initial state.
70	LCP is in the Starting state.
71	LCP is in the Closed state.
72	LCP is in the Stopped state.
73	LCP is in the Closing state.
74	LCP is in the Stopping state.
75	LCP is in the Request Sent state.
76	LCP is in the ACK Received state.
77	LCP is in the ACK Sent state.
80	IPXNCP is in the Open state.
90	V.110 is up.
91	V.110 is in the Open state.
92	V.110 is in the Carrier state.
93	V.110 is in the Reset state.
94	V.110 is in the Closed state.

• The backoff queue error message in the syslog file

  Accounting records are kept until they are acknowledged by the accounting server. Up to 100 unacknowledged records are stored in the backoff queue. If the unit never receives an acknowledgment to an accounting request, it will eventually run out of memory. In order to keep this situation from the occurring, the unit deletes the accounting records and displays this error message in the syslog file:

  Backoff Q full, discarding user <username>
  

  This error generally occurs for one of the following reasons:

  • You enabled RADIUS accounting on the MAX, but not on the RADIUS server.

  • The Accounting Port or Accounting Key are incorrect. The Accounting Key must match the value assigned in the RADIUS clients file or the TACACS+ configuration file.

  • You are using the Livingston server instead of the Ascend server.

• Syslog messages generated by packets seen by a Secure Access Manger firewall

  Syslog messages may be generated for packets seen by the firewall if specified by SAM. By default, SAM will cause a syslog message to be generated for all packets blocked by a firewall. Syslog messages created by firewalls will use the standard format:

  <date> <time> <router name> ASCEND: <interface> <message>
  

  • <date> indicates the date the message was logged by syslog.

  • <time> indicates the time the message was logged by syslog.

  • <router name> indicates the router this message was sent from.

  • <interface> is the name of the interface (ie0, wan0, and so on) or `call' if the packet is logged by the call filter as it brings up the link.

  • The <message> format has a number of fields, one or more of which may be present.

  The message fields appear in this order:

  <protocol> <local> <direction> <remote> <length> <frag> <log> <tag>
  

  • <protocol> is the 4 hexadecimal digit Ether Type, or one of the following network protocol names: arp, rarp, ipx, appletalk. For IP protocols, it is either the IP protocol number (up to 3 decimal digits) or one of the following names: ip-in-ip, tcp, icmp, udp, esp, ah. In the special case of icmp, it will also include the ICMP Code and Type ([Code]/[Type]/icmp).

  • For non-IP packets, <local> is the source Ethernet MAC address of transmitted packets and the destination Ethernet MAC address of received packets. On a non-bridged WAN connection, the two MAC addresses will be all zeros. For IP protocols, it is the IP source address of transmitted packets and the IP destination address of received packets. In the case of TCP or UDP, it will also include the TCP or UDP port number ([IP-address];[port]).

  • <direction> is an arrow (<- or ->) showing the direction in which the packet was traveling (receive and send, respectively).

  • For non-IP protocols, <remote> has the same format as <local> non-IP packets but shows the destination Ethernet MAC destination address of transmitted packets and the source Ethernet MAC address of received packets. For IP protocols, it has the same format as <local> but shows the IP destination address of transmitted packets and the IP source address of received packets.

  • <length> is the length of the packet in octets (8-bit bytes).

  • <frag> is used to report "frag" if the packet has a non-zero IP offset or the IP More-Fragments bit is set in the IP header.

  • <log> is used to report one or more messages based upon the packet status or packet header flags. The packet status messages include:
    corrupt-the packet is internally inconsistent

    unreach-the packet was generated by an "unreach=" rule in the firewall

    !pass-the packet was blocked by the data firewall

    bringup-the packet matches the call firewall

    !bringup-the packet did not match the call firewall

    TCP flag bits that will be displayed include syn, fin, rst.

    syn is will only be displayed for the initial packet which has the SYN flag and not the ACK flag set.

    <tag> contains any user defined tags specified in the filter template used by SAM.

00-100 Sys Options  
>Security Prof:1   ^
 Software +1.0+
 S/N:42901 

System Status window

The System Status window contains the following selections:

00-000 System
 00-100 Sys Options 
>00-200 Message Log 
 00-300 Port Info  
 00-400 CDR

WAN Stat window

This screen shows WAN statistics:

50-300 WAN Stat
>Rx Pkt:  387112
 Tx Pkt:   22092
    CRC:  0

The second and third lines show the number of frames received and transmitted, respectively. The fourth line indicates the number of CRC errors. An CRC error indicates a frame containing at least one data error.

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