#

# SNMP and Syslog Configuration

Configuring SNMP
Configuring Syslog
Disconnect codes and progress codes

MAX configurations control which classes of events will generate traps to be sent to an SNMP manager, and which managers have SNMP access to the unit. A configuration includes community strings to prevent unauthorized access. This chapter shows you how to set up the unit to work with SNMP.

## Configuring SNMP

The MAX supports SNMP on a TCP/IP network. An SNMP management station that uses the Ascend Enterprise MIB can query the MAX, set some parameters, sound alarms when certain conditions appear in the MAX, and so forth. An SNMP manager must be running on a host on the local IP network, and the MAX must be able to find that host, through either a static route or RIP.

The MAX supports the Ascend Enterprise MIB, MIB II, and some ancillary SNMP features. The MAX can send management information to an SNMP manager without being polled. SNMP security uses a community name sent with each request. The MAX supports two community names, one with read-only access, and the other with read/write access to the MIB.

SNMP has its own password security, which you should set up to prevent reconfiguration of the MAX from an SNMP station.

### Configuring SNMP access security

There are two levels of SNMP security: community strings, which must be known by a community of SNMP managers to access the box, and address security, which excludes SNMP access unless it is initiated from a specified IP address. Following are the relevant parameters (shown with sample settings):

    Ethernet

          Mod Config

                SNMP options...

                      Read Comm=Ascend

                      R/W Comm Enable=No

                      R/W Comm=Secret

                      Security=Yes

                      RD Mgr1=10.0.0.1

                      RD Mgr2=10.0.0.2

                      RD Mgr3=10.0.0.3

                      RD Mgr4=10.0.0.4

                      RD Mgr5=10.0.0.5

                      WR Mgr1=10.0.0.11

                      WR Mgr2=10.0.0.12

                      WR Mgr3=10.0.0.13

                      WR Mgr4=10.0.0.14

                      WR Mgr5=10.0.0.15

For complete information about each parameter, see the MAX Reference Guide.

#### Enabling SNMP Set commands

The R/W Comm Enable parameter disables SNMP set commands by default. Before you can use an SNMP Set command, you must set R/W Comm Enable to Yes.

Note: Even if you enable R/W Comm, you must still know the read-write community string to use a Set command.

#### Setting community strings

The Read Comm parameter specifies the SNMP community name for read access (up to 32 characters), and the R/W Comm parameter specifies the SNMP community name for read/write access.

#### Setting up and enforcing address security

If the Security parameter is set to No (its default value), any SNMP manager that presents the right community name will be allowed access. If you set this parameter to Yes, the MAX checks the source IP address of the SNMP manager and allows access only to those IP addresses listed in the RD MgrN and WR MgrN parameters, each of which specifies up to five host addresses.

#### Resetting the MAX and verifying reset

You can use SNMP (`sysReset` object) to reset a MAX from an SNMP manager. After the Reset command is issued, a one-minute timeout (not modifiable) permits the MAX to confirm the request before the unit is reset.

Information held in the Ascend Events Group is erased and its values are initialized when the MAX is reset by software or by toggling the power off and on. The SNMP object `sysAbsoluteStartupTime` is the time in seconds since January 1, 1990, and is not modified. To determine whether the MAX has actually reset, you can retrieve `sysAbsoluteStartupTime` and compare its value against the previous poll's value for Ascend Events Group variables.

#### Example of SNMP security configuration

The following procedure sets the community strings, enforces address security, and prevents write access:

1. Open Ethernet > Mod Config > SNMP Options.

2. Set R/W Comm Enable to Yes.

3. Specify the Read Comm and R/W Comm parameter strings.

4. Set Security to Yes.

5. Specify up to five host addresses in the RD MgrN parameters. Leave the WR MgrN parameters set to zero to prevent write access.

6. Close the Ethernet profile.

Following is an example of a profile configured with the preceding procedure.

    Ethernet

          Mod Config

                SNMP options...

                      Read Comm=Secret-1

                      R/W Comm Enable=Yes

                      R/W Comm=Secret-2

                      Security=Yes

                      RD Mgr1=10.0.0.1

                      RD Mgr2=10.0.0.2

                      RD Mgr3=10.0.0.3

                      RD Mgr4=10.0.0.4

                      RD Mgr5=10.0.0.5

                      WR Mgr1=0.0.0.0

                      WR Mgr2=0.0.0.0

                      WR Mgr3=0.0.0.0

                      WR Mgr4=0.0.0.0

                      WR Mgr5=0.0.0.0

### Setting SNMP traps

A trap is a mechanism for reporting system change in real time (for example, reporting an incoming call to a serial host port). When a trap is generated by some condition, a traps-PDU (Protocol Data Unit) is sent across the Ethernet to the SNMP manager.

Following are the parameters related to setting SNMP traps (shown with sample settings):

    Ethernet

          SNMP Traps

                Name=

                Alarm=Yes

                Port=Yes

                Security=Yes

                Comm=

                Dest=10.2.3.4

For complete information about each parameter and the events that generate traps in the various classes, see the MAX Reference Guide.

#### Understanding the SNMP trap parameters

To specify the SNMP trap profile name, set the Name parameter. Use a name of 31 or fewer characters.

To specify the community string for communicating with the SNMP manager, set the Comm parameter to the community name associated with the SNMP PDU.

The Alarm, Port, and Security fields specify whether the MAX traps respectively alarm events, port events, and/or security events, and sends a trap-PDU to the SNMP manager.

The Dest field specifies the destination address for the trap-status report. If DNS or YP/NIS is supported, the Dest field can contain the hostname of a system running an SNMP manager. If the DNS or YP/NIS is not supported, the Dest field must contain the host's address.

Note: To turn off SNMP traps, set Dest to 0.0.0.0 and delete the value for Comm.

#### Example SNMP trap configuration

The following procedure creates a profile that specifies a community name, all the trap types, and the host's IP address in the Dest parameter.

1. Open an SNMP Traps profile and assign it a name.

2. Specify the community name (for example, Ascend).

3. Set the trap types to Yes.

4. Specify the IP address of the host to which the trap-PDUs will be sent.

5. Close the SNMP Traps profile.

Following is an example of a profile configured with this procedure:

    Ethernet

          SNMP Traps

                Name=security-traps

                Alarm=Yes

                Port=Yes

                Security=Yes

                Comm=Ascend

                Dest=10.2.3.4

### Ascend enterprise traps

This section provides a brief summary of the traps generated by alarm, port, and security events. For more details, see the Ascend Enterprise MIB. To obtain the Ascend MIB, see "Supported MIBs" on page 6-7.

#### Alarm events

Alarm events (also called error events) use trap types defined in RFC 1215 and 1315, as well as an Ascend enterprise trap type. The MAX provides the following trap types:

#### Alarm event | #### Signifies that the MAX sending the trap:
--- | ---
coldStart (RFC-1215 trap-type 0) | Is reinitializing itself and that the configuration of the SNMP manager or the unit might be altered.
warmStart (RFC- 1215 trap-type 1) | Is reinitializing itself but neither the configuration of the SNMP manager nor that of the unit will be altered.
linkDown (RFC-1215 trap-type 2) | Recognizes a failure in one of the communication links represented in the SNMP manager's configuration.
linkUp (RFC-1215 trap-type 3) | Recognizes that one of the communication links represented in the SNMP manager's configuration has come up.
frDLCIStatusChange (RFC-1315 trap-type 1) | Recognizes that one of the virtual circuits (to which a DLCI number has been assigned) has changed state. That is, the link has either been created or invalidated, or has toggled between the active and inactive states.
eventTableOverwrite (ascend trap-type 16) | Detected that a new event has overwritten an unread event. This trap is sent only for systems that support Ascend's accounting MIB. Once sent, additional overwrites will not cause another trap to be sent until at least one table's worth of new events has occurred.

#### Port state change events

Port state change event traps are effective on a port-by-port basis for each port pointed to by `ifIndex`. The `hostPort` objects are used to associate a change with `ifIndex` objects.

The following trap types signify a change in the state of the Ascend Inverse Multiplexer (AIM) port associated with the passed index.

#### Trap type | #### Indicates that the indexed AIM port:
--- | ---
portInactive (ascend trap-type 0) | Has become inactive.
portDualDelay (ascend trap-type 1) | Is delaying the dialing of a second to avoid overloading devices that cannot handle two calls in close succession.
portWaitSerial (ascend trap-type 2) | Has detected DTR and is waiting for an HDLC controller to come online. CTS is off (V.25 bis dialing only).
portHaveSerial (ascend trap-type 3) | Is waiting for V.25 bis commands. CTS is on.
portRinging (ascend trap-type 4) | Has been notified of an incoming call.
portCollectDigits (ascend trap-type 5) | Is receiving digits from an RS366 interface (RS-366 dialing only).
portWaiting (ascend trap-type 6) | Is waiting for connect notification from the WAN after dialing or answer notification has been issued.
portConnected (ascend trap-type 7) | Has changed state. This change of state can be from connected to unconnected or vice versa. If connected to the far end, end-to-end data can flow but has not yet been enabled. The following trap report sequence shows that a link is up: portWaiting (6) portConnected (7) portCarrier (8) The following trap report sequence shows that a link is down: portConnected (7) portInactive (0)
portCarrier (ascend trap-type 8) | Has end-to-end data flow enabled
portLoopback (ascend trap-type 9) | Has been placed in local loopback mode.
portAcrPending (ascend trap-type 10) | Has set ACR on the RS366 interface, and is waiting for the host device (RS-366 dialing only).
portDTENotReady (ascend trap-type 11) | Is waiting for DTE to signal a ready condition when performing X.21 dialing.

#### Security events

Security events are used to notify users of security problems and track access to the unit from the console. The MIB-II event authenticationError is a security event. The other security events are Ascend-specific. The include:

#### Security event | #### Signifies
--- | ---
authenticationFailure (RFC-1215 trap-type 4) | The MAX sending the trap is the addressee of a protocol message that is not properly authenticated.
consoleStateChange (ascend trap-type 12) | The console associated with the passed console index has changed state. To read the console's state, get `ConsoleEntry` from the Ascend enterprise MIB.
portUseExceeded (ascend trap-type 13) | The serial host port's use exceeds the maximum set by the Max DS0 Mins Port parameter associated with the passed index (namely, the interface number).
systemUseExceeded (ascend trap-type 14) | The serial host port's use exceeds the maximum set by the Max DS0 Mins System parameter associated with the passed index (namely, the interface number).
maxTelnetAttempts (ascend trap-type 15) | A user has failed in three consecutive attempts to log into this MAX via Telnet.

### Supported MIBs

You can download the most up-to-date version of the Ascend Enterprise MIB by logging in as `anonymous` to`ftp.ascend.com`. (No password is required.) In addition to the Ascend MIB, the MAX also supports objects related to Ascend functionality in the following Internet standard MIBs:

- MIB-II implementation (RFC 1213)

- DS1 MIB implementation (RFC 1406)

- RS232 MIB implementation (RFC-1317)

- Frame Relay MIB implementation (RFC-1315)

- Modem MIB implementation (RFC 1696)

You can download the most recent version of these RFCs by logging in as `anonymous` to `ftp.ds.internic.net`. (No password is required.)

## Configuring Syslog

You can configure the MAX to send messages containing call and system events to an IP host running a `syslog` daemon.

To configure Syslog support, you must set parameters specifying the IP address of the host running the Syslog daemon. In addition, there are optional parameters you can set to customize the way the MAX sends its Syslog messages.

The IP host running the syslog daemon is typically a UNIX host, but can be a Microsoft Windows workstation or server. If the MAX is on a different network than the IP host, you must configure the routers so that the MAX can successfully communicate with the IP host.

Note: Do not configure the MAX to send reports to a IP host that can be reached only by means of a dial-up connection.

### Configuring the MAX to send Syslog messages

To configure the MAX to send messages to a `syslog` daemon:

1. Open the Ethernet > Mod Config > Log menu.

2. Set the Syslog parameter to Yes.

3. Set Log Host to the IP address of the host running the `syslog` daemon.

4. Set Log Port to the port at which the `syslog` daemon listens for Syslog messages from the MAX. The default is 514.

5. Set the Log Facility value to be attached to each Syslog message.

   The `syslog` daemon can receive messages from several devices, and it groups the messages. If the daemon receives messages from devices that specify the same log facility, it stores them in the same file.

6. Exit and save the changes.

To configure the `syslog` daemon on a UNIX host, you need to modify the host's `/etc/syslog.conf` file. This file specifies a specific action the daemon performs when it receives messages with a particular Log Facility number. For example, if you set Log Facility to Local5 in the MAX, and the `syslog` daemon should store messages from the MAX in the file `/var/log/MAX`, add the following line to the `/etc/syslog.conf` file:

    local5.info tab /var/log/MAX

Note: After making changes to the `/etc/syslog.conf` file, you must direct the UNIX host to reread the file.

### Syslog message format

MAX units generate Syslog messages in the following format:

    date time router_name ASCEND: message

where:

- `date` is the date the message was logged by the `syslog` daemon. The MAX does not datestamp the Syslog messages.

- `time` is the time the message was logged by the `syslog` daemon. The MAX does not timestamp the `syslog` messages.

- `router_name` is the name of the MAX sending the message.

- `message``` is the specific activity that caused the MAX to send the Syslog packet.

### Syslog messages and their meanings

Syslog messages are recorded during establishment of a call, during graceful or unexpected disconnection of a call, and during various other events.

In a Syslog message, `slot` x `port` y indicates that action occurred in a session with the module (slot card) located in slot `x`. Because slot cards support multiple simultaneous sessions, the MAX assigns the session to a specific port. For modem calls, port indicates a specific modem on a modem slot card. For digital calls, port typically indicates an HDLC channel on an Ethernet card or Ether-Data card, although port can indicate a port on a slot card supporting inverse multiplexing.

#### Establishment of a call

Following are examples of messages that might be logged during establishment of a call:

slot 0 port 0, line `n`, channel `m`, Incoming Call, `xxxxxxxxxxx`

The MAX has received a call on channel m of line n. The MAX has assigned it an identification number of xxxxxxxxxxx. The MAX has not assigned a slot card to the call.

Note: The internally used identification number might be displayed in the format `MBID` `xxx`.

slot `x` port `y`, Assigned to port, `xxxxxxxxxxx`

The MAX has assigned the incoming call to port y on the module in slot x. The MAX assigns calls on the basis of the bearer service of the call, the configured call routing, or configured answer number routing.

slot `x` port `y`, Call connected, `xxxxxxxxxxx`

The call has connected.

call `n` AN slot `x` port `data service`

Port y on the module in slot x answers the call. The MAX has assigned another identifier (`call` `n`.) to the session. For data service, `56K` indicates that the call is a 56Kbps call, and `VOICE` indicates an analog call.

slot `x` port`y`, LAN session up, `username`

The session has successfully completed authentication, the MAX displays the username, and the connection is complete.

#### Graceful disconnect of a call

To gracefully disconnect a call, the dial-in caller uses the connection software rather than simply turning off the computer or unplugging the modem.

The MAX displays the following messages in the order shown:

slot`x` port `y`, LAN session down, `username`

The MAX has cleared the user's session. If the user gracefully closes down the PPP connection, the MAX indicates a valid slot number and port number.

slot `x` port `y`, Call terminated

The call that was connected to port y on the module in slot x terminated. Typically, the dial-in client has terminated the call. The MAX begins clearing the resources that it had allocated for the call.

call `n` CL OK

The MAX has freed all the remaining internal resources that were used by the call.

#### Unexpected disconnect of a call

When a dial-in user disconnects a session by turning off the computer or unplugging the modem, the call clears before the MAX clears the PPP session. The MAX displays the following messages, which are similar to those shown in "Graceful disconnect of a call" on page 6-9.

call `n` CL OK u= `username` c=`n` p=`m`

The session for `username`, identified by `call` `n`, is disconnecting. The MAX supplies disconnect and progress information about the call. The disconnect code `n` details why the call disconnected. The progress code `m` indicates the last action the MAX logged before the disconnect occurred. For detailed information, see "Disconnect codes and progress codes" on page 6-11.

Note: If the MAX has not successfully authenticated the user before the call disconnects, `u=` `username``` does not appear.

slot `x` port y, line `n`, channel `m`, Call Disconnected

The switch clears the channel on which the call had been active.

slot `x` port `y`, Call Terminated

The call that was connected to port `y` on the module in slot `x` terminated. The dial-in client has terminated the call. The MAX begins clearing the resources that it had allocated for the call.

slot 0 port 0, LAN session down, `username`

The MAX has cleared the user's session. Because the user ended the session ungracefully, the call disconnected before the resources could be completely cleared. The MAX does not require the call to be active while freeing software resources, and records the slot and port as 0 (zero).

call `n` CL OK

The MAX has cleared up all the internal resources that were used for the call.

#### Additional messages

Additional Syslog messages can include the following:

LAN security error, Modem `x`:`y`

The MAX received a call on modem `y` in the module in slot `x`. The call has failed either because authentication failed, or because the IP address of the user did not match the IP address configured in the user's profile.

Busy

The MAX dialed a phone number that was busy.

No connection

There was no response from the far end unit when the MAX dialed.

No Channel Avail

All channels on the MAX are either supporting active calls or are disabled.

Not enough Chans

The outgoing call requested more channels than the MAX has available.

No Chan Other End

The called unit did not have an available channel on which to answer the call.

Network Problem

The telephone network has reported a protocol error.

Far End Hung Up

The telephone network notified the MAX that the calling unit has disconnected the call.

Remote Mgmt Denied

A user attempted to initiate a remote management session, which was denied by the far end unit.

Call Refused

The MAX dialed an outgoing call that was refused by the far end unit, or the MAX answered an incoming call, then immediately disconnected. The latter event might be due to of incorrect line provisioning.

Ethernet Up

The Ethernet interface of the MAX has become active or been reinitialized. This message is logged when the Ethernet interface first comes up, or on the basis of a change to the Ethernet interface.

Callback pending

The MAX received a call configured for callback. The initial call cleared. The MAX is preparing to call back to the user.

IP address 0.0.0.0 not valid for login service

A user attempted to initiate a login service with an invalid IP address.

Backoff Q full, discarding user 10.10.10.1[250725066]

Backoff-queue overflow has resulted in silent discarding of the oldest entry. When a RADIUS accounting event occurs, the MAX (the NAS) sends an Accounting-Request message to the RADIUS Accounting server, which sends back an Accounting-Response message to acknowledge receipt. The NAS is required to buffer the event until it receives an acknowledgment. The NAS employs a simple exponential backoff algorithm between reattempts. The backoff algorithm is:

    backoff_time = 3 * backof_time

where `backoff_time = [1..N]`

Once the NAS sends an accounting request, if no response is received from the Accounting server, the NAS enters backoff mode.

If the backoff queue is not empty when an accounting event occurs (a new user logs in or an existing user logs out), the event goes directly onto the backoff queue.

A maximum of 100 entries is allowed on the backoff queue. If the queue overflows. the oldest entry is silently discarded, and the MAX sends the Syslog message.

The backoff queue can be cleared by setting Acct = None on the MAX or by resetting

the MAX.

When you see this Syslog message, your Accounting Server is not functioning properly. If Acct = RADIUS on the MAX, verify that you are using the correct Port number (e.g. 1646) and that the Acct Key matches the password in the clients file on the RADIUS server. Also, be aware that the default location for your accounting records is `/usr/adm/radacct`. You have to create the `radacct` directory. RADIUS will automatically create a subdirectory with the name or IP address of the MAX (depending on your entry in the clients file) and will then write to the `detail` file. You can redirect your accounting output by starting RADIUS with the `-a` option (for example, `radiusd -a /usr/adm/ascendlog)`.

## Disconnect codes and progress codes

When a call disconnects, the MAX typically sends the following message:

    call n CL OK u= username c=n p=m

where:

- `n` specifies a disconnect code indicating why the call disconnected.

- `m` specifies a progress code indicating how far the call had progressed when it disconnected.

### Disconnect codes and their meanings

Following is a list of disconnect codes and their meanings:

#### Disconnect code | #### Description
--- | ---
1 | Not applied to any call.
2 | Unknown disconnect.
3 | Call disconnected.
4 | CLID authentication failed.
5 | RADIUS timeout during authentication.
6 | Successful authentication. MAX is configured to call the user back.
7 | Pre-T310 Send Disc timer triggered.
9 | No modem is available to accept call.
10 | Modem never detected Data Carrier Detect (DCD).
11 | Modem detected DCD, but modem carrier was lost.
12 | MAX failed to successfully detect modem result codes.
13 | MAX failed to open a modem for outgoing call.
14 | MAX failed to open a modem for outgoing call while `ModemDiag` diagnostic command is enabled.
20 | User exited normally from the terminal server.
21 | Terminal server timed out waiting for user input.
22 | Forced disconnect when exiting Telnet session.
23 | No IP address available when invoking PPP or SLIP command.
24 | Forced disconnect when exiting raw TCP session.
25 | Exceeded maximum login attempts.
26 | Attempted to start a raw TCP session, but raw TCP is disabled on MAX.
27 | Control-C characters received during login.
28 | Terminal-server session cleared ungracefully.
29 | User closed a terminal-server virtual connection normally.
30 | Terminal-server virtual connect cleared ungracefully.
31 | Exit from Rlogin session.
32 | Establishment of rlogin session failed because of bad options.
33 | MAX lacks resources to process terminal-server request.
35 | MP+ session cleared because no null MP packets received. A MAX sends (and should receive) null MP packets throughout an MP+ session.
40 | LCP timed out waiting for a response.
41 | LCP negotiations failed, usually because user is configured to send passwords via PAP, and MAX is configured to only accept passwords via CHAP (or vice versa).
42 | PAP authentication failed.
43 | CHAP authentication failed.
44 | Authentication failed from remote server.
45 | MAX received Terminate Request packet while LCP was in open state.
46 | MAX received Close Request from upper layer, indicating graceful LCP closure.
47 | MAX cleared call because no PPP Network Core Protocols (NCPs) were successfully negotiated. Typically, there is no agreement on the type of routing or bridging that is supported for the session.
48 | Disconnected MP session. The MAX accepted an added channel, but cannot determine the call to which to add the new channel.
49 | Disconnected MP call because no more channels can be added.
50 | Telnet or raw TCP session tables full.
51 | MAX has exhausted Telnet or raw TCP resources.
52 | For Telnet or raw TCP session, IP address is invalid.
53 | For Telnet or raw TCP session, MAX cannot resolve hostname.
54 | For Telnet or raw TCP session, MAX received bad or missing port number.
60 | For Telnet or raw TCP session, host reset.
61 | For Telnet or raw TCP session, connection was refused.
62 | For Telnet or raw TCP session, connection timed out.
63 | For Telnet or raw TCP session, connection closed by foreign host.
64 | For Telnet or raw TCP session, network unreachable.
65 | For Telnet or raw TCP session, host unreachable.
66 | For Telnet or raw TCP session, network admin unreachable.
67 | For Telnet or raw TCP session, host admin unreachable.
68 | For Telnet or raw TCP session, port unreachable.
100 | Session timed out.
101 | Invalid user.
102 | Callback enabled.
105 | Session timeout on the basis of encapsulation negotiations.
106 | MP session timeout.
115 | Instigating call no longer active.
120 | Requested protocol is disabled or unsupported.
150 | Disconnect requested by RADIUS server.
151 | Call disconnected by local administrator.
152 | Call disconnected via SNMP.
160 | Exceeded maximum number of V.110 retries.
170 | Timeout waiting to authenticate far end.
180 | User disconnected by executing Do Hangup from VT100 interface.
181 | Call cleared by MAX.
185 | Signal lost from far end, typically because the far end modem was turned off.
190 | Resource has been quiesced.
195 | Maximum duration time reached for call.
201 | MAX has low memory.
210 | MAX modem card stops working while it has calls outstanding.
220 | MAX requires CBCP, but client does not support it.
230 | MAX deleted Vrouter.
240 | MAX disconnected call on the basis of LQM measurements.
241 | MAX cleared backup call.
250 | IP FAX call cleared normally.
251 | IP FAX call cleared because of low available memory.
252 | MAX detected an error for an incoming IP FAX call.
253 | MAX detected an error for an outgoing IP FAX call.
254 | MAX detected no available modem to support an IP FAX call.
255 | MAX detected problem opening IP FAX session.
256 | MAX detected a problem when performing a TCP function during an IP FAX call.
257 | IP FAX session cleared abnormally.
258 | MAX detected problem when parsing telephone number for IP FAX call.
260 | MAX detected problem when decoding IP FAX variables.
261 | MAX detected problem when decoding IP FAX variables.
262 | MAX has no configured IP FAX server.
300 | MAX detects X.25 error.

### Progress codes and their meanings

Following are the progress codes and their meanings:

#### Progress code | #### Description
--- | ---
1 | Not applied to any call.
2 | Unknown progress.
10 | MAX has detected and accepted call.
30 | MAX has assigned modem to call.
31 | Modem is awaiting DCD from far-end modem.
32 | Modem is awaiting result codes from far-end modem.
40 | Terminal-server session started.
41 | Raw TCP session started.
42 | Immediate Telnet session started.
43 | Connection made to raw TCP host.
44 | Connection made to Telnet host.
45 | Rlogin session started.
46 | Connection made with Rlogin session.
47 | Terminal-server authentication started.
50 | Modem outdial session started.
60 | LAN session is up.
61 | Opening LCP.
62 | Opening CCP.
63 | Opening IPNCP.
64 | Opening BNCP.
65 | LCP opened.
66 | CCP opened.
67 | IPNCP opened.
68 | BNCP opened.
69 | LCP in Initial state.
70 | LCP in Starting state.
71 | LCP in Closed state.
72 | LCP in Stopped state.
73 | LCP in Closing state.
74 | LCP in Stopping state.
75 | LCP in Req-Sent state.
76 | LCP in Ack-Rcvd state.
77 | LCP in Ack-Sent state.
80 | IPX NCP in Open state.
81 | AT NCP in Open state.
82 | BACP being opened.
83 | BACP is now open.
84 | CBCP being opened.
85 | CBCP is now open.
90 | MAX has accepted V.110 call.
91 | V.110 call in Open state.
92 | V.110 call in Carrier state.
93 | V.110 call in Reset state.
94 | V.110 call in Closed state.
100 | MAX determines that call requires callback.
101 | Authentication failed.
102 | Remote authentication server timed out.
120 | Frame Relay link is inactive. Negotiations are in progress.
121 | Frame Relay link is active and has end-to-end connectivity.
200 | Starting Authentication layer.
201 | Authentication layer moving to opening state.
202 | Skipping Authentication layer.
203 | Authentication layer in opened state.

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