#

# Network Administration

Administering WAN lines and calls
Managing IP routes and sessions
Monitoring IPX routes and sessions
Managing OSPF routes and sessions
Managing multicast routing
Monitoring Frame Relay connections
Monitoring X.25 and PAD connections
Setting up ISDN D-channel X.25 support

## Administering WAN lines and calls

The MAX allows you to manage WAN lines, ports, and modems. This section describes how to:

- Perform diagnostics on T1, E1, and BRI lines, and ports

- Display call information

- Disable digital modems and modem slots

- Understand how the MAX routes an incoming call

For reference information about each of the commands described in this section, see the MAX Reference Guide.

### T1 line diagnostics

The MAX provides T1 diagnostic commands you can use to test the configuration of your T1 lines. Access the commands from Net/T1 > Line Diag.

The Line Diag menu for T1 includes the following commands, which you execute by selecting the command in the menu and pressing Enter:

#### Command | #### Purpose
--- | ---
`Line LB1` `Line LB2` | Respectively, to test Line 1 or Line 2 in a T1 slot, places a call from the MAX to itself over the WAN to determine the MAX unit's ability to initiate and receive calls and to diagnose the soundness of the digital access line and WAN. Do not activate these commands when a call is active on the line because they disrupt data flow between the codecs connected to either end of the network line.
`Switch D Chan` | Swaps status of the primary and secondary Non-Facility Associated Signaling (NFAS) D channels on T1 lines that use NFAS signaling.
`Clr Err1` `Clr Err2` | Respectively, clears the user error event register of line 1 or line 2.
`Clr Perf1` `Clr Perf2` | Respectively, clears all performance registers for line 1 or line 2, restarts the current time period, and begins accumulating new performance data.

### E1 line diagnostics

The MAX provides E1 diagnostic commands you can use to test the configuration of your E1 lines. Access the commands from Net/E1 > Line Diag.

The Line Diag menu for E1 includes the following commands, which you execute by selecting the command in the menu and pressing Enter:

#### Command | #### Purpose
--- | ---
`Line LB1` `Line LB2` | Respectively, to test Line 1 or Line 2 in an E1 slot, places a call from the MAX to itself over the WAN to determine the MAX unit's ability to initiate and receive calls and to diagnose the soundness of the digital access line and WAN. Do not activate these commands when a call is active on the line because they disrupt data flow between the codecs connected to either end of the network line.

### BRI/LT diagnostics

The MAX provides BRI/LT diagnostic commands you can use to test the configuration of your BRI/LT lines. Access the commands from BRI/LT > Line Diag > Line N where N is the number of the line you want to check.

BRI/LT diagnostic commands use the BRI-U interface's embedded operations channel (EOC). The EOC transfers diagnostic and signaling data from the exchange to the terminal side and vice versa without transmitting on either the B or D channels.

#### Monitoring transmission quality

To monitor transmission quality at the U-interface, the MAX uses internal block-error counters. Block errors encountered in the receive direction are called Near-End Block Errors (NEBE). Block errors encountered in the transmission direction are called Far-End Block Errors (FEBE).

A block error is detected each time the calculated checksum of the received data does not correspond with the control checksum transmitted in the successive superframe. Block error totals are received from the remote TA. Totals are reset when you restart the MAX or use a Line Diag command for clearing counters. You can view Block Error status in the BRI/LT status window while conducting the diagnostic tests.

Before executing diagnostic test commands, you must specify the EOC address to which you want to apply the command. Set the EOC Address Parameter in the Line Diag menu. The values permitted include:

- 0 (the default)-Remote ISDN TA device.

- 1 through 6-Number of an ISDN repeater between the MAX and the remote TA. The number 1 specifies the repeater closest to the MAX.

- 7-Broadcast the command to all nodes on the IDSL connection.

The EOC address reverts to its default value of 0 when you exit from the Line Diag submenu.

The Line Diag menu includes the following commands for running diagnostic tests, which you access by selecting the command and pressing Enter:

#### Command | #### Purpose
--- | ---
`Line LoopBack` | Sends 24-byte-long test frames continuously on the D channel until you cancel the command. When you execute the command, by selecting Line LoopBack and pressing Enter, a submenu appears with `0=Esc` and `1=Line` `N` `LB`. Selecting 1 begins the loopback command. You can examine the LB Counters status screen to see the number of transmitted frames. Selecting 0 cancels the command.
`Corrupt CRC` | BRI-U interface permanently transmits inverted CRCs until the command is canceled. While the test is conducted, view the far-end block error status from the remote TA. This tests NEBE and FEBE signal counters.
`Uncorrupt CRC` | Cancels the `Corrupt CRC` command.
`RQ Corrupt CRC` | Requests that NT1 corrupt the CRC to simulate transmission errors. After issuing the command, you can check the near-end block counter to verify that it is working.
`Rq Uncorrupt CRC` | Requests that the NT1 cancel the `RQ` `Corrupt` `CRC` transmission.
`Clr NEBE` | Clears the Near-End Block Error counter.
`Clr FEBE` | Clears the Far-End Block Error counter.

The Line Diag menu also includes a parameter Sealing Current. This parameter enables sealing, which is the ability of an ISDL card to send 40V current on the line to prevent corrosion caused by inactivity. To enable sealing, specify Yes. The default value is No sealing.

#### Example of performing loopback diagnostics for IDSL

The MAX supports loopback tests from itself to any device on the IDSL connection. For example, you can loop back the signal from the IDSL card to the remote TA or TE, or from the IDSL card to any intermediate repeater.

Figure 5-1. IDSL connection with repeaters

In Figure 5-1, for example, you could set up a loopback test from the MAX to any of the ISDN repeaters, or from the MAX all the way to the remote ISDN at the end of the connection. This ability enables you to isolate trouble anywhere in the connection.

To configure a loopback test on the BRI lines provided by the IDSL slot card:

1. Select BRI/LT > Line Diag > Line N, where N is the number of the line you want to loop back.

2. Specify the EOC Address parameter to specify the device that is the terminating point for the loopback test. Use one of the following values:

   - 0-specifies the remote TA or MAX.

   - 1-6-specifies a repeater between the MAX and the remote TA, with 1 representing that closest to the MAX.

   - 7-specifies all devices.

3. Select Line LoopBack and press Enter.

4. In the confirmation dialog box that appears, select 1=Line N LB.

   While the line loops back, normal data transfer is disrupted.

5. Press Escape to cancel the loopback.

In a local loopback test, data originating at the local site loops back to its originating port without going out over the WAN. It is as though a data mirror were held up to the data at the WAN interface, and the data reflected back to the originator. The WAN interface is the MAX port that connects to a WAN line.

### Performing port diagnostics

After configuring a port, you can perform a loopback test to verify port configuration. You access the loopback command from the Port Diag menu (Host/Dual (or Host/6) > Port N Menu > Port Diag menu.

The loopback test sends data originating at the host (the local application) back to the originating port.

To run a loopback test:

1. Select Local LB and press Enter. The Local LB menu appears:

    31-201 Local LB

    > 	DSR  =  Active
    	RI=Inactive
    	CD=Inactive
    	DLO=Inactive
    	PND=Inactive
    	ACR=Inactive
    	Inc Ch Count
    	Dec Ch Count
    	Rate=64K

2. Use the standard VT100 interface commands to select settings to change. The settings available include the following:

   #### Parameter | #### Description
   --- | ---
   `DSR` | Toggles the host port's Data Set Ready V.25 signal between active and inactive.
   `RI` | Toggles the host port's Ring Indicate V.25 output signal between active and inactive.
   `CD` | Toggles the host port's Carrier Detect output signal between active and inactive.
   `DLO` | Toggles the host port's Data Line Occupied RS-366 output signal between active and inactive.
   `PND` | Toggles the host port's Present Next Digit RS-366 output signal between active and inactive.
   `ACR` | Toggles the host port's Abandon Call and Retry output signal between active and inactive.
   `Inc Ch Count` | Simulates an increase in the number of channels in a call by increasing the clock rate to the host.
   `Dec Ch Count` | Simulates a decrease in the number of channels in a call by decreasing the clock rate to the host.
   `Rate` | Toggles the data rate of the simulated channels between 56 Kbps and 64 Kbps.

3. When you have completed your tests, exit by pressing the Left Arrow key. When you exit, all control signals revert to the state they were in when the test began.

### Disabling digital modems and modem slots

You can temporarily disable digital modems or modem slots without disrupting existing connections. This action is called quiescing, and it prepares a modem for maintenance.

Quiescing a modem or modem slot does not result in active calls being torn down. Instead, when active call drops, that modem or modem slot is added to a disabled list and is unavailable for use. If all modems are disabled, incoming callers receive a busy signal until the modems have been restored for service. A quiesced modem is available for use approximately 20 seconds after it has been re-enabled.

To quiesce a modem or modem slot, access the V.34 (V.42) Modem > Modem Diag menu.

To quiesce a modem, use the Modem #N command, where N is the modem number from 1 to 12. You can set one of the following values:

#### Value | #### Result
--- | ---
`enable modem` | Enables disabled modems. This is the default value.
`disable modem` | Places the modem on the disabled list. When an active connection drops, the card becomes available for maintenance.
`enable modem+chan` | Enables the modem and a disabled B channel.
`disable modem+chan` | Places the modem and an arbitrary B channel on disabled lists.

To quiesce a modem slot, use the ModemSlot command. You can set one of the following values:

#### Value | #### Result
--- | ---
`enable slot` | Enables disabled modems on the slot. This is the default value.
`disable slot` | Places all modems that are not active on the disabled list. When the active connections drop, the card becomes available for maintenance.
`enable slot+chan` | Restores the slot card and channels to use. Modems on the selected slot that appear on the disabled list are enabled. For each modem enabled, an out-of-service B channel returns to service.
`disable slot+chan` | Disables all modems on the slot, along with an equal number of B channels.

### E1 ISDN call information

If the E1/PRI line or BRI line switch-type is German 1TR6 or Japanese NTT, you can display information about ISDN calls by invoking the terminal-server command line and entering the Show Calls command. For example:

    ascend% show calls

The command displays statistics about current calls. For example:

    Call ID  Called Party ID Calling Party ID InOctets OutOctets

    3        5104563434      4191234567        0        0

    4        4197654321      5108888888        888888   99999

The Call ID column contains an index number specific to the call.

Called Party ID and Calling Party ID show the telephone number of the answering device and calling device, respectively.

InOctets and OutOctets show the number of bytes received by the answering device and transmitted by the calling device, respectively.

Note: When an ISDN call disconnects from either a German 1TR6 switch or a Japanese NTT switch, the switch sends call billing information to the call originator as part of the call tear-down process. This information is written to the eventCallCharge (eventEntry 17) SNMP object in the Ascend Enterprise MIB events group (10). An SNMP manager can then read this object to determine the cost of the call. The eventCallCharge object is a read-only integer and is applicable only if eventType is callCleared (3). Otherwise, 0 is returned.

### Incoming call routing state diagram

The following pages show detailed state information about inbound call routing in the MAX. For more information about any of the parameters, see the MAX Reference Guide.

## Managing IP routes and sessions

This section describes how to monitor TCP/IP/UDP and related information in the terminal-server command-line interface. To invoke the terminal-server interface, select System > Sys Diag > Term Serv and press Enter. The terminal-server command-line prompt appears: `ascend%.`

### Working with the IP routing table

The terminal-server IProute commands display the routing table and enable you to add or delete routes. The changes you make to the routing table by using the IProute command last only until the MAX unit is reset. To display the IProute commands, enter the IP route command with a question mark:

    ascend% iproute ?

    iproute ?              Display help information

    iproute add          iproute add <destination/size> <gateway> [ pref ] [ m

    iproute delete    iproute delete <destination/size> <gateway> [ proto ]

    iproute show        displays IP routes (same as "show ip routes" command)

#### Displaying the routing table

You can use either the IProute Show command or the Show IP Routes command to display the IP routing table: For example:

    ascend% iproute show

    Destination        Gateway        IF       Flg Pref  Met   Use   Age

    0.0.0.0/0          10.0.0.100     wan0     SG   1     1     0     20887

    10.207.76.0/24     10.207.76.1    wanidle0 SG   100   7     0     20887

    10.207.77.0/24     10.207.76.1    wanidle0 SG   100   8     0     20887

    127.0.0.1/32       -              lo0      CP   0     0     0     20887

    10.0.0.0/24        10.0.0.100     wan0     SG   100   1     21387 20887

    10.1.2.0/24        -              ie0      C    0     0     19775 20887

    10.1.2.1/32        -              lo0      CP   0     0     389   20887

    255.255.255.255/32 -              ie0      CP   0     0     0     20887

The output includes the following information:

#### Field | #### Destination
--- | ---
`Destination` | Target address of a route. To send a packet to this address, the MAX uses this route. Note that the router uses the most specific route (having the longest mask) that matches a given destination.
`Gateway` | Address of the next hop router that can forward packets to the given destination. Direct routes (without a gateway) do not show a gateway address in the gateway column.
`IF` | Name of the interface through which a packet addressed to this destination is sent. `ie0`-Ethernet interface `lo0`- Loopback interface `wanN`-Each of the active WAN interfaces `wanidle0`- Inactive interface (the special interface for any route whose WAN connection is down).
`Flg` | Flag values, including the following: `C`- A directly connected route, such as Ethernet `I`-ICMP Redirect dynamic route `N`-Placed in the table via SNMP MIB II `O`-Route learned from OSPF (Open Shortest Path First) `R`-Route learned from RIP `r`-RADIUS route `S`-Static route `?`-Route of unknown origin, which indicates an error `G`-Indirect route via a gateway `P`-Private route `T`-Temporary route `*`-Hidden route that will not be used unless another better route to the same destination goes down
`Pref` | Preference value of the route. Note that all routes that come from RIP have a preference value of 100, while the preference value of each individual static route can be set independently.
`Metric` | RIP-style metric for the route, with a valid range of 0-16. Routes learned from OSPF show a RIP metric of 10. OSPF Cost infinity routes show a RIP metric of 16.
`Use` | Count of the number of times the route was referenced since it was created. (Many of these references are internal, so this is not a count of the number of packets sent over this route.)
`Age` | Age of the route in seconds, used for troubleshooting to determine when routes are changing rapidly or flapping.

Continuing the example, the first route shown is the default route with destination 0.0.0.0/0, defined through the active Connection profile.

    0.0.0.0/0          10.0.0.100     wan0     SG   1     1     0     20887

The IP Route profile for the default route specifies a preference of 1, so this route is preferred over dynamically learned routes. The next route is specified in a Connection profile that is inactive:

    10.207.76.0/24     10.207.76.1    wanidle0 SG   100   7     0     20887

The next route in the table is a static route through an inactive gateway:

    10.207.77.0/24     10.207.76.1    wanidle0 SG   100   8     0     20887

The static route is followed by the loopback route:

    127.0.0.1/32       -              lo0      CP   0     0     0     20887

The loopback route specifies a special address. Packets sent to this special address will be handled internally. The C flag indicates a connected route, while the P flag indicates that the router will not advertise this route.

The next route is specified in a Connection profile that is currently active:

    10.0.0.0/24        10.0.0.100     wan0     SG   100   1     21387 20887

These are routes followed by a connection to the Ethernet interface. It is directly connected, with a preference and metric of zero.

    10.1.2.0/24        -              ie0      C    0     0     19775 20887

The last two routes are a private loopback route and a private route to the broadcast address:

    10.1.2.1/32        -              lo0      CP   0     0     389   20887

    255.255.255.255/32 -              ie0      CP   0     0     0     20887

The private loopback route shown is a host route with the Ethernet address. It is private, so it will not be advertised. The private route to the broadcast address is used in cases in which the router must to broadcast a packet but the route is otherwise unconfigured. It is typically used when the MAX is trying to locate a server on a client machine to handle challenges for a token security card.

#### Adding an IP route

To add to the MAX unit's routing table a static route that will be lost when the MAX resets, enter the IProute Add command in the following format:

    iproute add destination gateway [metric]

where `destination` is the destination network address, `gateway` is the IP address of the router that can forward packets to that network, and `metric` is the virtual hop count to the destination network (default 8). For example, to add a route to the 10.1.2.0 network and all of its subnets through the IP router located at 10.0.0.3/24 with a metric of 1 (the router is one hop away), enter the following command:

    ascend% iproute add 10.1.2.0 10.0.0.3/24 1

If you try to add a route to a destination that already exists in the routing table, the MAX replaces the existing route, but only if it has a higher metric than the new route. If you get the message `Warning: a better route appears to exist`, the MAX has rejected your attempt to add a route because the routing table already contained a route, to the same destination, with a lower metric. Note that RIP updates can change the metric for the route.

#### Deleting an IP route

To remove a route from the MAX unit's routing table, enter the IProute Delete command in the following format:

    iproute delete destination gateway

For example:

    ascend% iproute delete 10.1.2.0 10.0.0.3/24

Note: RIP updates can add back any route you remove with IProute Delete. Also, after a system reset, the MAX restores all routes listed in the Static Route profile.

### Displaying route statistics

The Traceroute command is useful for locating slow routers or diagnosing IP routing problems. It traces the route an IP packet follows by launching UDP probe packets with a low Time-To-Live (TTL) value and then listening for an ICMP time exceeded reply from a router. The Traceroute command uses the following syntax:

    traceroute [-n] [-v] [-m max_ttl][-p port] [-q nqueries]

    [-w waittime] host [datasize]

All flags are optional. The only required parameter is the destination hostname or IP address. The elements of the syntax are as follows:

#### Syntax element | #### Description
`-n` | Print hop addresses numerically rather than symbolically and numerically (this eliminates a name server address-to-name lookup for each gateway found on the path).
`-v` | Verbose output. Lists all received ICMP packets other than Time Exceeded and ICMP Port Unreachable are listed.
`-m` `max_ttl` | Sets the maximum time-to-live (maximum number of hops) for outgoing probe packets. The default is 30 hops.
`-p` `port` | Set the base UDP port number used in probes. Traceroute depends on having nothing listening on any of the UDP ports from the source to the destination host (so that an ICMP Port Unreachable message will be returned to terminate the route tracing). If something is listening on a port in the default range, you can set the `-p` option to specify an unused port range. The default is 33434.
`-q` `nqueries` | Set the maximum number of queries for each hop. The default is 3.
`-w` `waittime` | Set the time to wait for a response to a query. The default is 3 seconds.
`host` | The destination host by name or IP address.
`datasize` | Sets the size of the data field of the UDP probe datagram sent by Traceroute. The default is 0. This results in a datagram size of 38 bytes (a UDP packet carrying no data).

For example, to trace the route to the host `techpubs`:

    ascend% traceroute techpubs

    traceroute to techpubs (10.65.212.19), 30 hops MAX, 0 byte packets

     1  techpubs.eng.ascend.com (10.65.212.19)  0 ms  0 ms  0 ms

Probes start with a TTL of one and increase by one until one of the following conditions occurs:

- The MAX receives an ICMP Port Unreachable message.

  The UDP port in the probe packets is set to an unlikely value, such as 33434, because the target host is not intended to process the packets. A "port unreachable" message indicates that the packets reached the target host and were rejected.

- The TTL value reaches the maximum value.

  By default, the maximum TTL is set to 30. You can specify a different TTL by using the `-m` option. For example:

    ascend% traceroute -m 60 techpubs

    traceroute to techpubs (10.65.212.19), 60 hops MAX, 0 byte packets

     1  techpubs.eng.abc.com (10.65.212.19)  0 ms  0 ms  0 ms

Three probes are sent at each TTL setting. The second line of command output shows the address of the router and round trip time of each probe. If the probe answers come from different gateways, the address of each responding system is shown. If there is no response within a three second timeout interval, the command output is an asterisk. The following annotations can appear after the time field in a response:

- `!H`-Host reached.

- `!N`-Network unreachable.

- `!P`-Protocol unreachable.

- `!S`-Source route failed. Might indicate a problem with the associated device.

- `!F`-Fragmentation needed. Might indicate a problem with the associated device.

- `!h`-Communication with the host is prohibited by filtering.

- `!n`-Communication with the network is prohibited by filtering.

- `!c`-Communication is otherwise prohibited by filtering.

- `!?`-ICMP subcode detected. This event should not occur.

- `!??`-Reply received with inappropriate type. This event should not occur.

### Pinging other IP hosts

The terminal-server Ping command is useful for verifying that the transmission path is open between the MAX and another station. It sends an ICMP echo-request packet to the specified station. If the station receives the packet, it returns an ICMP echo-response packet. The Ping command has the following syntax:

    ping [-q] [-v] [-c count] [-i sec | -I msec] [-s packetsize]

    [-x src_address] host

All flags are optional. The only required parameter is the destination hostname or IP address. The elements of the syntax are as follows:

#### Syntax element | #### Description
`-q` | Quiet mode. The MAX displays only the summary of all Ping responses it has received.
`-v` | Verbose output. The MAX displays information from each ping response that it receives as well as the summary of all Ping responses. This is the default.
`-c` `count` | Specifies the number of Ping requests that the MAX sends to the host. By default, the MAX sends continual ping requests until you press Ctrl-C.
`-i` `sec` | Specifies the length of time, in seconds, between Ping requests. You can specify seconds, using the `-i` option, or milliseconds, using the `-I` option, but not both. The default is one second.
`-I` `msec` | Specifies the length of time, in milliseconds, between Ping requests. You can specify milliseconds, using the `-I` option, or seconds, using the `-i` option, but not both.
`-s` `packetsize` | Specifies the size of each Ping request packet that the MAX sends to the host. The default is 64 bytes.
`-x` srcaddress | Specifies a source IP address that overwrites the default source address.
`host` | The destination host by name or IP address.

For example, to Ping the host`techpubs`:

    ascend% ping techpubs

    PING techpubs (10.65.212.19): 56 data bytes

    64 bytes from 10.65.212.19: icmp_seq=0 ttl=255 time=0 ms

    64 bytes from 10.65.212.19: icmp_seq=3 ttl=255 time=0 ms

    ^C

    --- techpubs ping statistics ---

    2 packets transmitted, 2 packets received, 0% packet loss

    round-trip min/avg/MAX = 0/0/0 ms

You can terminate the Ping exchange at any time by pressing Ctrl-C. When you press Ctrl-C, the command reports the number of packets sent and received, the percentage of packet loss, any duplicate or damaged echo-response packets, and round-trip statistics. In some cases, round-trip times cannot be calculated.

During the Ping exchange, the MAX displays information about the packet exchange, including the Time-To-Live (TTL) of each ICMP echo-response packet.

Note: The maximum TTL for ICMP Ping is 255, and the maximum TTL for TCP is often 60 or lower, so you might be able to Ping a host but not be able to run a TCP application (such as Telnet or FTP) to that station. If you Ping a host running a version of Berkeley UNIX earlier than 4.3BSD-Tahoe, the TTL report is 255 minus the number of routers in the round-trip path. If you Ping a host running the current version of Berkeley UNIX, the TTL report is 255 minus the number of routers in the path from the remote system to the station performing the Ping.

The Ping command sends an ICMP Mandatory echo-request datagram, which asks the remote station "Are you there?" If the echo-request reaches the remote station, the station sends back an ICMP echo-response datagram, which tells the sender "Yes, I am alive." This exchange verifies that the transmission path is open between the MAX and a remote station.

### Configuring Finger support

You can configure the MAX to respond to Finger requests, as specified in RFC 1288, The Finger User Information Protocol.

To enable the MAX to respond to Finger requests:

1. Open the Ethernet > Mod Config.

2. Set Finger to Yes.

3. Exit and save the changes.

### Configuring the DNS Fallback Table

The local DNS table provides a list of IP addresses for a specific host name when the remote DNS server fails to resolve the host name. If the local DNS table contains the host name for the attempted connection, it provides the list of IP addresses.

You create the DNS table from the Ethernet > Mod Config > DNS menu by entering up to eight host names. Enter the IP addresses for each host through the terminal-server interface. You can configure a maximum of 35 IP addresses for each host. If you specify automatic updating, you only have to enter the first IP address of each host. Additional IP addresses are added automatically.

Automatic updating replaces the existing address list for a host each time the remote DNS server succeeds in resolving a connection to a host that is in the table. You specify how many of the addresses returned by the remote server can be included in the new list.

On the MAX, the table, which you display from the terminal-server interface, provides additional information for each table entry. The information is in the following two fields, which are updated when the system matches the table entry with a host name that was not found by the remote server:

- # Reads (the number of reads since entry was created). This field is updated each time a local name query match is found in the local DNS table.

- Time of Last Read

You can use the terminal-server command ``Show Dnstab to check the list of host names and IP addresses in the table. Figure 5-2 shows an example of a DNS table on a MAX.

Figure 5-2. Example of a local DNS table

### Displaying IP routing and related information

The following Show commands for monitoring IP routing and related protocols are described in this section:

    show arp		Display the Arp Cache

    show icmp		Display ICMP information

    show if	Display Interface info. Type 'show if ?' for help.

    show ip	Display IP information. Type 'show ip ?' for help.

    show udp	Display UDP information. Type 'show udp ?' for help.

    show tcp	Display TCP information. Type 'show tcp ?' for help.

    show pools	Display the assign address pools.

#### Displaying the ARP cache

To display the ARP cache, enter the Show ARP command. For example:

    ascend% show arp

    entry typ ip address      ether addr    if rtr pkt   insert

        0 DYN 10.65.212.199  00C07B605C07   0   0   0   857783

        1 DYN 10.65.212.91   0080C7C4CB80   0   0   0   857866

        2 DYN 10.65.212.22   080020792B4C   0   0   0   857937

        3 DYN 10.65.212.3    0000813DF048   0   0   0   857566

        4 DYN 10.65.212.250  0020AFF80F1D   0   0   0   857883

        5 DYN 10.65.212.16   0020AFEC0AFB   0   0   0   857861

        6 DYN 10.65.212.227  00C07B5F14B6   0   0   0   857479

        7 DYN 10.65.212.36   00C07B5E9AA5   0   0   0   857602

        8 DYN 10.65.212.71   0080C730041F   0   0   0   857721

        9 DYN 10.65.212.5    0003C6010512   0   0   0   857602

       10 DYN 10.65.212.241  0080C72ED212   0   0   0   857781

       11 DYN 10.65.212.120  0080C7152582   0   0   0   857604

       12 DYN 10.65.212.156  0080A30ECE6D   0   0   0   857901

       13 DYN 10.65.212.100  00C07B60E28D   0   0   0   857934

       14 DYN 10.65.212.1    00000C065D27   0   0   0   857854

       15 DYN 10.65.212.102  08000716C449   0   0   0   857724

       16 DYN 10.65.212.33   00A024AA0283   0   0   0   857699

       17 DYN 10.65.212.96   0080C7301792   0   0   0   857757

       18 DYN 10.65.212.121  0080C79BF681   0   0   0   857848

       19 DYN 10.65.212.89   00A024A9FB99   0   0   0   857790

       20 DYN 10.65.212.26   00A024A8122C   0   0   0   857861

       21 DYN 10.65.212.6    0800207956A2   0   0   0   857918

       22 DYN 10.65.212.191  0080C75BE778   0   0   0   857918

       23 DYN 10.65.212.116  0080C72F66CC   0   0   0   857416

       24 DYN 10.65.212.87   0000813606A0   0   0   0   857666

       25 DYN 10.65.212.235  00C07B76D119   0   0   0   857708

       26 DYN 10.65.212.19   08002075806B   0   0   0   857929

The ARP table displays the following information:

- `entry`-A unique identifier for each ARP table entry.

- `typ`-How the address was learned, dynamically (DYN) or statically (STAT).

- `ip address`-The address contained in ARP requests.

- `ether addr`-The MAC address of the host with that IP address.

- `if`-The interface on which the MAX received the ARP request.

- `rtr`-The next-hop router on the specified interface.

#### Displaying ICMP packet statistics

To display the number of ICMP packets received intact, received with errors, and transmitted, enter the `Show icmp` command. For example:

    ascend% show icmp

    3857661 packet received.

    20 packets received with errors.

       Input histogram: 15070

    2758129 packets transmitted.

    0 packets transmitted due to lack of resources.

       Output histogram: 15218

The Input and Output histograms show the number of ICMP packets received and transmitted, respectively.

#### Displaying interface statistics

To display the supported interface-statistics commands, enter the Show IF command with a question mark. For example:

    ascend% show if ?

    show if ?		Display help information

    show if stats		Display Interface Statistics

    show if totals		Display Interface Total counts

To display the status and packet count of each active WAN link and of local and loopback interfaces, enter the Show IF Stats command. For example:

    ascend% show if stats

    Interface    Name    Status  Type     Speed    MTU   InPackets    Outpacket

    ie0        ethernet    Up    6     10000000   1500     107385     85384

    wan0                 Down    1            0   1500      0         0

    wan1                 Down    1            0   1500      0         0

    wan2                 Down    1            0   1500      0         0

    wanidle0               Up    6     10000000   1500      0         0

    lo0       loopback     Up   24     10000000   1500      0         0

The output contains the following fields:

#### Field | #### Description
--- | ---
Interface | Interface name. For more information, see the Network Configuration Guide for your MAX.
Name | Name of the profile or a text name for the interface.
Status | Up (the interface is functional) or Down (the interface is not functional).
Type | Type of application being used on the interface, as specified in RFC 1213 (MIB-2). For example, 23 indicates PPP and 28 indicates SLIP.
Speed | Data rate in bits per second.
MTU | The maximum packet size allowed on the interface. MTU stands for Maximum Transmission Unit.
InPackets | The number of packets the interface has received.
OutPackets | The number of packets the interface has transmitted.

To display the packet count at each interface, broken down by type of packet, enter the Show If Totals command. For example:

    ascend% show if totals

    Name  --Octets----Ucast-- -NonUcast- Discard -Error- Unknown -Same IF-

    ie0  i:   7813606   85121     22383       0        0       0        0

         o: 101529978   85306       149       0        0       0        0

    wan0 i:         0       0         0       0        0       0        0

         o:         0       0         0       0        0       0        0

    wan1 i:         0       0         0       0        0       0        0

         o:         0       0         0       0        0       0        0

    wan2 i:         0       0         0       0        0       0        0

         o:         0       0         0       0        0       0        0

    wanidle0 i:     0       0         0       0        0       0        0

             o:     0       0         0       0        0       0        0

    lo0  i:         0       0         0       0        0       0        0

         o:         0       0         0       0        0       0        0

The output contains the following fields:

#### Field | #### Description
--- | ---
`Name` | Interface name. For more information, see the `Network Configuration Guide` for your MAX.
`Octets` | Total number of bytes processed by the interface.
`Ucast` | Packets with a unicast destination address.
`NonUcast` | Packets with a multicast address or a broadcast address.
`Discard` | Number of packets that the interface could not process.
`Error` | Number of packets with CRC errors, header errors, or collisions.
`Unknown` | Number of packets the MAX forwarded across all bridged interfaces because of unknown or unlearned destinations.
`Same IF` | Number of bridged packets whose destination is the same as the source.

#### Displaying IP statistics and addresses

To display the IP statistics and addresses supported commands, enter the Show IP command with a question mark:

    ascend% show ip ?

    show ip ?           Display help information

    show ip stats       Display IP Statistics

    show ip address     Display IP Address Assignments

    show ip routes      Display IP Routes

Note: For information about the Show IP Routes command, see Working with the IP routing table.

To display statistics on IP activity, including the number of IP packets the MAX has received and transmitted, enter the Show IP Stats command. For example:

    ascend% show ip stats

    107408 packets received.

         0 packets received with header errors.

         0 packets received with address errors.

         0 packets forwarded.

         0 packets received with unknown protocols.

         0 inbound packets discarded.

    107408 packets delivered to upper layers.

     85421 transmit requests.

         0 discarded transmit packets.

         1 outbound packets with no route.

         0 reassembly timeouts.

         0 reassemblies required.

         0 reassemblies that went OK.

         0 reassemblies that Failed.

         0 packets fragmented OK.

         0 fragmentations that failed.

         0 fragment packets created.

         0 route discards due to lack of memory.

         64 default ttl.

To display IP interface address information, enter the Show IP Address command. For example:

    ascend% show ip address

    Interface   IP Address    Dest Address   Netmask         MTU     Status

    ie0         10.2.3.4      N/A            255.255.255.224   1500      Up

    wan0        0.0.0.0       N/A            0.0.0.0           1500    Down

    wan1        13.1.2.0      13.1.2.128     255.255.255.248   1500    Down

    wan2        0.0.0.0       N/A            0.0.0.0           1500    Down

    wan3        0.0.0.0       N/A            0.0.0.0           1500    Down

    lo0         127.0.0.1     N/A            255.255.255.255   1500      Up

    rj0         127.0.0.2     N/A            255.255.255.255   1500      Up

    bh0         127.0.0.3     N/A            255.255.255.255   1500      Up

#### Displaying UDP statistics and listen table

To display the supported UDP-statistics commands, enter the Show UDP command with a question mark:

    ascend% show udp ?

    show udp ?          Display help information

    show udp stats      Display UDP Statistics

    show udp listen     Display UDP Listen Table

To display the number of UDP packets received and transmitted, enter the Show UDP Stats command. For example:

    ascend% show udp stats

    22386 packets received.

        0 packets received with no ports.

        0 packets received with errors.

        0 packets dropped

        9 packets transmitted.

The Show Udp Listen command displays the socket number, UDP port number and the number of packets queued for each UDP port on which the MAX is currently listening. The command's output also includes the following fields:

#### Field | #### Description
--- | ---
`InQMax` | Maximum number of queued UDP packets on the socket. (See Queue Depth and Rip Queue Depth parameters.)
`InQLen` | Current number of queued packets on the socket.
`InQDrops` | Number of packets discarded because it would cause InQLen to exceed InQMax.
`Total Rx` | Total number of packets received on the socket, including InQDrops.

For example:

    ascend% show udp listen

    udp:

    Socket Local Port InQLen InQMax    InQDrops    Total Rx

    0	1023	0	1	0	0

    1	520	0	50	0	532

    2	7 	0	32	0	0

    3 	123	0	32	0	0

    4 	1022	0	128	0	0

    5	161	0	64	0	0

#### Displaying TCP statistics and connections

To display the supported TCP-statistics commands, enter the Show TCP command with a question mark:

    ascend% show tcp ?

    show tcp ?          Display help information

    show tcp stats      Display TCP Statistics

    show tcp connection Display TCP Connection Table

To display the number of TCP packets received and transmitted, enter the Show TCP Stats command. For example:

    ascend% show tcp stats

         0 active opens.

        11 passive opens.

         1 connect attempts failed.

         1 connections were reset.

         3 connections currently established.

     85262 segments received.

     85598 segments transmitted.

       559 segments re-transmitted.

An active open is a TCP session that the MAX initiated, and a passive open is a TCP session that the MAX did not initiate.

To display current TCP sessions:

    ascend% show tcp connection

    Socket       Local               Remote                         State

    0            *.23                *.*                           LISTEN

    1            10.2.3.23           15.5.248.121.15003       ESTABLISHED

#### Displaying address pool status

To view the status of the MAX unit's IP address pool:

    ascend% show pools

    Pool #         Base        Count              InUse

    1              10.98.1.2     55               27

    2              10.5.6.1     128               0

       Number of remaining allocated addresses: 0

If you change an address pool while users are still logged in using the addresses from the previous pool, `Number of remaining allocated addresses` reflects how many users are currently using addresses from the previous pool. Typically, the value is 0 (zero).

## Monitoring IPX routes and sessions

Show commands for monitoring IPX connections in the MAX are available at the terminal-server command-line interface. To open the terminal-server interface select System > Sys Diag > Term Serv and press Enter.

### Verifying the transmission path to NetWare stations

The IPXping command provides network layer verification of the transmission path to NetWare stations. The command works on the same LAN as the MAX or across a WAN connection that has IPX Routing enabled. Following is the command's syntax:

    ipxping [-c count] [-i delay] [-s packetsize] hostname

where:

#### Option | #### Description
--- | ---
`hostname` | The IPX address of the host, or if the host is a NetWare server, its advertised name.
`-c` `count` | Stop the test after sending and receiving the number of packets specified by `count`.
`-i` `delay` | Wait the number of seconds specified by `delay` before sending the next packet. The default is for one second.
`-s` `packet-size` | Send the number of data bytes specified by `packet-size`.

You can specify `hostname` as is either the IPX address of the NetWare workstation or the advertised name of a server. The IPX address consists of the IPX network and node numbers for a station. For example:

    ascend% ipxping CFFF1234:000000000001

If you are using the IPXping command to verify connectivity with an advertised NetWare server, you can simply enter the symbolic name of the server. For example:

    ascend% ipxping server-1

You can terminate the IPXping command at any time by pressing Ctrl-C.

During the IPXping exchange, the MAX calculates and reports the following statistics:

    PING server-1 (EE000001:000000000001): 12 data bytes

    52 bytes from (EE000001:000000000001): ping_id=0 time=0ms

    52 bytes from (EE000001:000000000001): ping_id=1 time=0ms

    52 bytes from (EE000001:000000000001): ping_id=2 time=0ms

    ?

    --- novl1 Ping statistics ---

    3 packets transmitted, 3 packets received, 0% packet loss

    round-trip min/avg/MAX = 0/0/0 ms

These statistics include the following information:

- The IPX address of the source and destination nodes.

- The byte counts of the request and response packets.

- The ping ID of the command. (The ping Request # replied to by target host.)

- The number of milliseconds required to send the IPXping and receive a response.

- The number of packets transmitted and received.

- Duplicate or damaged packets, if applicable.

- Average round-trip times for the ping request and reply. In some cases, round-trip times cannot be calculated.

To display statistics related to the IPXping command, enter the Show Netware Pings command. For example:

    ascend% show netware pings

    InPing Requests/OutPing Replies OutPing Requests/InPing Replies

          10            10                  18            18

The output shows how many NetWare stations have pinged the MAX (InPing requests and replies) and how many times the IPXping command has been executed in the MAX (OutPing requests and replies).

### Displaying IPX packet statistics

To display IPX packet statistics, enter the Show Netware Stats command. For example:

    ascend% show netware stats

    27162 packets received.

    25392 packets forwarded.

    0 packets dropped exceeding maximum hop count.

    0 outbound packets with no route.

The MAX drops packets that exceed the maximum hop count (that have already passed through too many routers).

### Displaying the IPX service table

To display the IPX service table, enter the Show Netware Servers command. For example:

    ascend% show netware servers

    IPX address                     type              server name

    ee000001:000000000001:0040      0451              server-1

The output includes the following fields:

#### Field | #### Description
--- | ---
IPX address | IPX address of the server. The address uses this format: `network number`:`node number`:`socket number`
type | Type of service available (in hexadecimal format). For example, 0451 designates a file server
server name | The first 35 characters of the server name.

### Displaying the IPX routing table

To display the IPX routing table, enter the Show Netware Networks command:

    ascend% show netware networks

    network		next router		hops	ticks	origin

    CFFF0001		00000000000		0	1	Ethernet	S

The output includes the following fields:

#### Field | #### Descriptions
--- | ---
network | IPX network number.
next router | Address of the next router, or 0 (zero) for a direct or WAN connection.
hops | Hop count to the network.
ticks | Tick count to the network.
origin | Name of the profile used to reach the network.

Note: An S or an H flag might appear next to the origin. S indicates a static route. H indicates a hidden, or inactive, static route. Hidden static routes occur when the router learns of a better route.

## Managing OSPF routes and sessions

This section describes how to work with Open Shortest Path First (OSPF) information in the routing table and how to monitor OSPF activity in the terminal-server command-line interface.

To invoke the terminal-server interface, select System > Sys Diag > Term Serv and press Enter.

### Working with the routing table

The OSPF routing table includes routes built from the router's link-state database as well as those added by external routing protocols such as RIP. You can also add routes statically (for example, to direct traffic destined for a remote site through one of several possible border routers). For details about adding static routes (for example, if you want to force the use of one route over those learned from OSPF, see the Network Configuration Guide for your MAX).

To display the IP routing table with added OSPF information, invoke the terminal server (System > Sys Diag > Term Serv) and enter the IProute Show command with the `-l` option:

    ascend% iproute show -l

When you include the `-l` option, three columns of OSPF-specific fields appear at the routing table:

    ...     Cost        T        Tag
    ...     1           0        0xc0000000
    ...     9           1        0xc8000000
    ...     10          0        0xc0000000
    ...     9           1        0xc8000000
    ...     1           1        0xc0000000
    ...     3           1        0xc8000000
    ...     9           1        0xc8000000
    ...     4           1        0xc8000000
    ...     5           1        0xc8000000
    ...     3           1        0xc8000000
    ...     3           1        0xc8000000
    ...     3           1        0xc8000000

####

####

     Field

     Description

     Cost

     Cost of an OSPF route. The interpretation of this cost depends on the type of external metric, which is displayed in the next column. If the MAX is advertising Type-1 metrics, OSPF can use the specified number as the cost of the route. Type-2 external metrics are an order of magnitude larger.

     T

     Link-state advertisement (LSA)-type of the metric to be advertised for an external route. A 0 (zero) in this column means that the metric is an external-Type-1 or an OSPF internal route. A 1 means that the route is an external-Type-2 route.

     Tag

     Specifies a 32-bit hexadecimal number attached to each external route to tag it as external to the AS. The number may be used by border routers to filter this record.

#### Multipath routing

A MAX running OSPF can alternate between two equal-cost gateways. When OSPF detects equally good gateways, in terms of routing costs, it puts each equal-cost gateway on an equal-cost list. The router alternates between the gateways on the list in what is called equal-cost multipath routing.

For example, if router A has two equal-cost routes to `example.com`, one via router B and the other via router C, router A's routing table might include the following entries:

    Destination		Gateway		IF	Flg	Pref	Met	Use	Age

    10.174.88.0/25		10.174.88.12		wan2	OGM	10	10	52	19

    10.174.88.0/25		10.174.88.13		wan3	OGM 	10	10	52	19

    10.174.88.12/32		10.174.88.12		wan2	OG	10	10	0	28

    10.174.88.13/32		10.174.88.13		wan3	OG	10	10	0	28

    192.168.253.0/24			-	ie0	C	0	0	1	49

    192.168.253.6/32			-	lo0	CP	0	0	53	49

    223.1.1.0/24		10.174.88.12		wan2	OG	10	10	0	19

    223.5.1.0/24		10.174.88.12		wan2	OG	10	10	0 	19

    223.12.9.0/24		10.174.88.12		wan2	OG	10	10	0	19

    255.255.255.255/32		 	-	ie0	CP	0	0	0	49

The M in the Flg column indicates an equal-cost multipath. A Traceroute from router A to `example.com` would produce the following display:

    ascend% traceroute -q 10 example.com

    traceroute to example.com (10.174.88.1), 30 hops max, 0 byte packets

    1  C.example.com (10.174.88.13)  20 ms B .example.com (10.174.88.12)
    20 ms C.example.com (10.174.88.13)  20 ms B .example.com
    (10.174.88.12)  20 ms  20 ms C.example.com (10.174.88.13)  60 ms  20 ms
    B .example.com (10.174.88.12)  20 ms C.example.com (10.174.88.13)  20
    ms B .example.com (10.174.88.12)  20 ms

    2  example.com (10.174.88.1)  20 ms  20 ms  20 ms  20 ms  30 ms  20 ms
    20 ms  30 ms  20 ms  30 ms

Notice the alternating replies. The replies are statistically dispatched to router B and router C, with roughly 50% of the packets sent through each gateway. (For background information about the routing table and about the Traceroute command, see the Network Configuration Guide for your MAX.)

#### Third-party routing

A MAX running OSPF can advertise routes to external destinations on behalf of another gateway (a third-party). This is commonly known as advertising a forwarding address. Depending on the exact topology of the network, other routers might be able to use this type of link-state advertisement (LSA) and route directly to the forwarding address without involving the advertising MAX, thereby increasing the total network throughput.

Third-party routing requires that all OSPF routers know how to route to the forwarding address. This usually means that the forwarding address must be on an Ethernet that has an OSPF router acting as the forwarding router, or that the designated router is sending LSAs for that Ethernet to any area that sees the static route's forwarding-address LSAs. The following example shows how to configure a static route for OSPF to advertise a third-party gateway:

1. Open a static route in Ethernet > Static Rtes.

2. Set the Gateway to the forwarding address and set Third-Party to Yes.

    Ethernet

          Static Rtes

                Name=third-party

                Silent=No

                Active=Yes

                Dest=10.212.65.0/24

                Gateway=101.2.3.4

                Metric=3

                Preference=100

                Private=No

                Ospf-Cost=1

                LSA-Type=Type1

                ASE-tag=c00000000

                Third-Party=Yes

1. Close the static route.

#### How OSPF adds RIP routes

When the MAX establishes an IP routing connection with a caller that does not support OSPF, it imports the AS-external route from the Connection profile and adds it to the routing table. The MAX does not have to run RIP to learn these routes. RIP should be turned off when the MAX is running OSPF.

To enable OSPF to add the RIP-v2 routes to its routing table, configure RIP-v2 normally in the Connection profile. OSPF will import all RIP routes as Type-2 Autonomous System Externels (ASEs). The reason that RIP routes are imported with Type-2 metrics by default is that RIP metrics are not directly comparable to OSPF metrics. To prevent OSPF from interpreting RIP metrics, the imported ASE route is assigned a Type-2 metric, which is so large compared to OSPF costs that the metric can be ignored.

#### Route preferences

Route preferences provide additional control over which types of routes take precedence over others. They are necessary in a router that supports multiple routing protocols, largely because RIP metrics are not comparable with OSPF metrics.

For each IP address and subnet mask pair, the routing table holds one route per protocol. The routes are assigned preferences as follows:

- Connected routes, such as Ethernet, have Preference=0.

- Routes learned from ICMP Redirects have Preference=30.

- Routes placed in the table by SNMP MIB II have Preference=100.

- Routes learned from OSPF have a default of Preference=10. You can modify the default in Ethernet > Mod Config > Route Pref.

- Routes learned from RIP have a default of Preference=100. You can modify the default in Ethernet > Mod Config > Route Pref.

- A statically configured IP Route or Connection profile has a default of Preference=100. You can modify the default in the Connection or IP Route profile.

When choosing which routes should be put in the routing table, the router first compares the Preference values, preferring the lowest number. If the Preference values are equal, the router compares the Metric field and uses the route with the lowest Metric.

If multiple routes exist for a given address and subnet mask pair, the route with the lowest Preference is best. If two routes have the same Preference, then the lower Metric is better. The best route by these criteria is that actually used by the router. The others remain latent, or hidden, in case the best route is removed.

To assign a WAN link the same preference as a route learned from OSPF:

1. Open Connections > IP Options.

2. Specify a Preference value of 10 (the default value for OSPF routes). For example:

    Ethernet

          Connections

                IP options

                      LAN Adrs=10.9.8.10/22

                      WAN Alias=0.0.0.0

                      IF Adrs=0.0.0.0

                      Metric=5

                      Preference=10

                      Private=No

                      RIP=Off

                      Pool=0

1. Close the Connection profile.

On Ethernet, the route preferences also include ASE-type and ASE-tag information for routes learned from RIP. These values affect all RIP information learned across the Ethernet. To change the route preferences on Ethernet:

1. Open Ethernet > Mod Config > Route Pref.

2. Modify the parameters to adjust Preference values. For example, the following profile assigns static routes the same Preference value as those learned from OSPF:

    Ethernet

          Mod Config

                Route prefs...

                      Static Preference=10

                      Rip Preference=100

                      RipAseType=Type2

                      Rip Tag=c8000000

                      OSPF Preference=10

Or, you might change RIP metrics to Type-1:

    Ethernet

          Mod Config

                Route prefs...

                      Static Preference=100

                      Rip Preference=100

                      RipAseType=Type1

                      Rip Tag=c8000000

                      OSPF Preference=10

1. Close the Ethernet profile.

### Displaying OSPF information

The terminal-server command-line interface provides commands for monitoring OSPF in the MAX. To display the supported commands, enter the Show OSPF command with a question mark:

    scend% show ospf ?

    show ospf ?                    Display help information

    show ospf size              Display OSPF size

    show ospf areas            Display OSPF areas

    show ospf stats            Display OSPF statistics

    show ospf intf...        Display OSPF summary/detail interface information

    show ospf internal      Display OSPF internal routes

    show ospf lsa ...        Display OSPF detail link-state advertisements

    show ospf lsdb ...      Display OSPF link-state DB summary for an area

    show ospf nbrs ...      Display OSPF summary/detail neighbor information

    show ospf routers       Display OSPF routers

    show ospf ext                Display OSPF external AS advertisements

    show ospf rtab              Display OSPF routing table

    show ospf database      Display OSPF entire database summary

Note: For additional information, see RFC 1583.

#### Displaying the size of the OSPF routing table

To display the size of the OSPF routing table, enter the Show OSPF Size command. For example:

    ascend% show ospf size

                                    # Router-LSAs:                 2

                                    # Network-LSAs:                0

                                    # Summary-LSAs:                0

                                    # Summary Router-LSAs:         0

                                    # AS External-LSAs (type-5):   1

                                    # AS External-LSAs (type-7):   0

                                    # Intra-area routes:      4

                                    # Inter-area routes:      0

                                    # Type 1 external routes: 0

                                    # Type 2 external routes: 0

The output includes the following fields:

#### Fields | #### Description
--- | ---
`# Router-LSAs` | Number of router link advertisements that are also Type-1 Link State Advertisements.
`# Network-LSAs` | Number of network link advertisements that are also Type-2 LSAs.
`# Summary-LSAs` | Number of summary link advertisements that are also Type-3 LSAs. Type-3 LSAs describe routes to networks.
`# Summary Router-LSAs` | Number of summary link advertisements that are also Type-4 LSAs. Type-4 LSAs describe routes to AS boundary routers.
`# AS External- LSAs (type-5)` | Number of AS external link advertisements which are also Type-5 LSAs.
`# AS External- LSAs (type-7)` | Number of ASE-7 link advertisements that are also Type-7 LSAs.
`Intra-area routes` | Number of routes with a destination within the area.
`Inter-area routes` | Number of routes with a destination outside the area.
`Type 1 external routes` | Number of external Type-1 routes that are typically in the scope of OSPF-IGP.
`Type 2 external routes` | Number of external Type-2 routes that are typically outside the scope of OSPF-IGP.

#### Displaying OSPF areas

To display information about OSPF areas, enter the Show OSPF Areas command. For example:

    ascend% show ospf area

    Area ID    Authentication    Area Type  #ifcs    #nets    #rtrs    #brdrs    #intnr

    0.0.0.0    Simple-passwd      Normal            1            0            2              0              3

The output includes the following fields

#### Field | #### Description
--- | ---
`Area ID` | Area number in dotted-decimal format
`Authentication` | Type of authentication, Simple-passwd, MD5, or Null.
`Area Type` | Type of OSPF area: Normal, Stub, or NSSA
`#ifcs` | Number of MAX interfaces specified in the area.
`#nets` | Number of reachable networks in the area.
`#rtrs` | Number of reachable routers in the area.
`#brdrs` | Number of reachable area border routers in the area.
`#intnr` | Number of reachable internal routers in the area.

:

#### Displaying general information about OSPF

To display general information about OSPF, enter the Show OSPF Stats command. For example:

    ascend% show ospf stats

                          OSPF version:                          2

                          OSPF Router ID:                      192.192.192.2

                          AS boundary capability:      Yes

    Attached areas:                              1      Estimated # ext.(5) routes:            300

    OSPF packets rcvd:                94565      OSPF packets rcvd w/ errs:                  0

    Transit nodes allocated:      3058      Transit nodes freed:                        3056

    LS adv. allocated:                  1529      LS adv. freed:                                    1528

    Queue headers alloc:                  32      Queue headers avail:                            32

    # Dijkstra runs:                            4      Incremental summ. updates:                  0

    Incremental VL updates:              0      Buffer alloc failures:                          0

    Multicast pkts sent:            94595      Unicast pkts sent:                                  5

    LS adv. aged out:                          0      LS adv. flushed:                                      0

    Incremental ext.(5) updates:    0      Incremental ext.(7) updates:              0

    External (type-5) LSA database -

    Current state:                                Normal

    Number of LSAs:                              1

    Number of overflows:                    0

The output includes the following fields

#### Field | #### Description
--- | ---
`OSPF version` | Version of the OSPF protocols running.
`OSPF Router ID` | IP address assigned to the MAX, typically, the address specified for the Ethernet interface.
`AS boundary capability` | Displays Yes if the MAX functions as an ASBR or No if it does not. f
`Attached areas` | Number of areas to which this MAX attaches.
`Estimated # ext.(5) routes` | Maximum number of ASE-5 routes that the MAX can maintain before it goes into an overload state.
`OSPF packets rcvd` | Total number of OSPF packets received by the MAX.
`OSPF packets rcvd w/ errs` | Total number of OSPF erroneous packets received by the MAX.
`Transit nodes allocated` | Allocated transit nodes, which are generated only by Router LSAs (Type 1) and Network LSAs (Type 2).
`Transit nodes freed` | Freed transit nodes, which are generated only by Router LSAs (Type 1) and Network LSAs (Type 2).
`LS adv. allocated` | Number of LSAs allocated.
`LS adv. freed` | Number of LSAs freed.
`Queue headers alloc` | Number of queue headers allocated. LSAs can reside in multiple queues. Queue headers are the elements of the queues that contain the pointer to the LSA.
`Queue headers avail` | Available memory for queue headers. To prevent memory fragmentation, the MAX allocates memory in blocks and allocates queue headers from the memory blocks. When the MAX frees all queue headers from a specific memory block, it returns the block to the pool of available memory blocks.
`# Dijkstra runs` | Number of times that the MAX has run the Dijkstra algorithm (short path computation).
`Incremental summ. updates` | Number of summary updates that the MAX runs when small changes occur that result in generation of Summary LSAs (Type 3) and Summary Router LSAs (Type 4).
`Incremental VL updates` | Number of incremental virtual link updates that the MAX performs.
`Buffer alloc failures` | Number of buffer allocation problems that the MAX has detected and from which it has recovered.
`Multicast pkts sent` | Number of Multicast packets sent by OSPF.
`Unicast pkts sent` | Number of unicast packets sent by OSPF.
`LS adv. aged out` | Number of LSAs that the MAX has aged and removed from its tables.
`LS adv. flushed` | Number of LSAs that the MAX has flushed.
`Incremental ext.(5) updates` | Number of incremental ASE-5 updates.
`Incremental ext.(7) updates` | Number of incremental ASE-7 updates.
`Current state` | State of the External (Type-5) LSA database, either Normal or Overload.
`Number of LSAs` | Number of LSAs in the External (Type-5) LSA database.
`Number of overflows` | Number of ASE-5 that exceeded the limit of the database.

:

#### Displaying information about OSPF interfaces

Enter the Show OSPF Intf command to display either summarized information about all OSPF interfaces or specific information about a single interface.

##### Displaying summarized information

To display summarized information on OSPF interfaces, enter the Show OSPF Intf command. For example:

    ascend% show ospf intf

    Ifc Address     Phys    Assoc. Area     Type   State   #nbrs #adjs DInt

    194.194.194.2   phani   0.0.0.0         P-P    P-P       1     1   120

The output includes the following fields:

#### Field | #### Description
--- | ---
`Ifc Address` | Address assigned to the MAX's Ethernet interface. To identify WAN links, use the Type and Cost fields.
`Phys` | Name of the interface or the Connection profile for WAN links.
`Assoc. Area` | Area in which the interface resides.
`Type` | Point-to-Point (P-P) or Broadcast (Bcast). WAN links are P-P links.
`State` | State of the link according to RFC 1583. There are many possible states, and not all states apply to all interfaces.
`#nbrs` | Number of neighbors of the interface.
`#adjs` | Number of adjacencies on the interface.
`DInt` | Number of seconds that the MAX waits for a router update before removing the router's entry from its table. The interval is called the Dead Interval.

##### Displaying specific information on a specific interface

To display detailed information for a specific interface, enter the Show OSFP Intf command in the following format:

    ascend% show ospf intf (ip address or physical name)

For example:

    ascend% sh ospf intf 194.194.194.2

                                Interface address:      194.194.194.2

                                Attached area:          0.0.0.0

                                Physical interface:     phani (wan1)

                                Interface mask:         255.255.255.255

                                Interface type:         P-P

                                State:                  (0x8) P-P

                                Designated Router:      0.0.0.0

                                Backup DR:              0.0.0.0

                                Remote Address:         194.194.194.3

    DR Priority:              5    Hello interval:    30      Rxmt interval:    5

    Dead interval:      120    TX delay:                  1      Poll interval:    0

    Max pkt size:      1500    TOS 0 cost:            10

    # Neighbors:              1    # Adjacencies:        1      # Full adjs.:      1

    # Mcast floods:  1856    # Mcast acks:    1855

The output includes the following fields:

#### Field | #### Description
--- | ---
`Interface Address` | The IP address specified for the MAX's Ethernet interface.
`Attached Area` | Area in which the interface resides.
`Physical interface` | Name of the interface or the Connection profile for WAN links.
`Interface type` | Point-to-Point (P-P) or Broadcast (Bcast). WAN links are P-P links.
`State` | State of the link according to RFC 1583. There are many possible states, and not all states apply to all interfaces.
`Designated Router` | IP address of the designated router for the interface.
`Backup DR` | IP address of the backup designated router for the interface.
`Remote Address` | IP address of the remote end of a Point to Point (WAN) link.
`DR Priority` | Priority of the designated router.
`Hello interval` | Interval in seconds that the MAX sends Hello packets as defined in RFC 1583.
`Rxmt interval` | Retransmission interval as described in RFC 1583.
`Dead interval` | Number of seconds that the MAX waits for a router update before removing the router's entry from its table.
`TX delay` | Interface transmission delay.
`Poll interval` | Poll interval of non-broadcast multi-access networks.
`Max pkt size` | Maximum packet size that the MAX can send to the interface.
`TOS 0 Count` | Type of Service normal (0) cost.
`# neighbors` | Number of neighbors.
`# adjacencies` | Number of adjacencies.
`# Full adjs.` | Number of fully formed adjacencies.
`# Mcast floods` | Number of multicast floods on the interface.
`# Mcast acks` | Number of multicast acknowledgments on the interface.

#### Displaying OSPF Link-State Advertisements (LSAs)

You can enter Show OSPF commands to display a router's link state database and to expand the display of a particular LSA.

##### Displaying the OSPF link-state database

To display the router's link-state database, enter the Show OSPF LSDB command. For example:

    ascend% show ospf lsdb

                                                    Area: 0.0.0.0

    Type  LS ID                            LS originator            Seqno          Age        Xsum

    RTR    192.192.192.2            192.192.192.2      0x800005f8      696      0x6f0b

    RTR    192.192.192.3            192.192.192.3      0x800005f8      163      0x6f09

                                    # advertisements:              2

                                    Checksum total:                  0xde14

The output includes the following fields:

#### Field | #### Description
--- | ---
`Area` | Area ID.
`Type` | Type of link as defined in RFC 1583: Type 1 (RTR)-Outer-LSAs that describe the collected states of the router's interfaces. Type 2 (NET)-Network-LSAs that describe the set of routers attached to the network. Types 3 and 4 (SUM)-Summary-LSAs that describe point-to-point routes to networks or AS boundary routers. Type 7 (ASE)-Link advertisements that are flooded only within an NSSA.
`LS ID` | Target address of the route.
`LS originator` | Address of the advertising router.
`Seqno` | Hexadecimal number that begins with 80000000 and increments by one for each LSA received.
`Age` | Age of the route in seconds.
`Xsum` | Checksum of the LSA.
`# advertise- ments` | Total number of entries in the link-state database.
`Checksum total` | Checksum of the link-state database.

##### Displaying expanded OSPF link-state advertisements

To specify a link-state advertisement to be expanded, first display the database. To specify an LSA, enter a Show OSPF command in the following format, then specify the LSA to expand:

    show ospf lsa area ls-type ls-id ls-orig

The Show OSPF LSA command requires that you include the first four fields of the LSA as listed in the database. You can select the first four fields and paste them into the command line. For example, to display an expanded view of the last entry in the link-state database shown in the preceding section:

    ascend% show ospf lsa 0.0.0.0 ase 10.5.2.160 10.5.2.162

    LSA  type: ASE ls id: 10.5.2.160 adv rtr: 110.5.2.162 age: 568

                        seq #: 80000037 cksum: 0xfffa

                        Net mask: 255.255.255.255 Tos 0 metric: 10 E type: 1

                        Forwarding Address: 0.0.0.0 Tag: c0000000

The output includes the following fields:

#### Field | #### Description
--- | ---
`LSA type` | Type of link as defined in RFC 1583 and identified by the type of LSA: Type 1 (RTR)-Outer-LSAs that describe the collected states of the router's interfaces. Type 2 (NET)-Network-LSAs that describe the set of routers attached to the network. Types 3 and 4 (SUM)-Summary-LSAs that describe point-to-point routes to networks or AS boundary routers. Type 7 (ASE)-Link advertisements that are flooded only within an NSSA.
`ls id` | Target address of the router.
`adv rtr` | Address of the advertising router.
`age` | Age of the route in seconds.
`seq #` | Number that begins with 80000000 and increments by one for each LSA received.
`cksum` | Checksum for the LSA.
`Net mask` | Subnet mask of the LSA.
`Tos` | Type Of Service for the LSA.
`metric` | Cost of the link, not of a route. The cost of a route is the sum of all intervening links, including the cost of the connected route.
`E type` | External type of the LSA indicating either 1 (Type 1) or 2 (Type 2).
`Forwarding Address` | Forwarding Address of the LSA, described in RFC 1583.
`Tag` | Tag of the LSA which is described in the OSFP RFC.

#### Displaying OSPF neighbor information

    To display information about OSPF neighbors to the MAX, enter the Show OSPF NBRS command.
    For example:

    ascend% show ospf nbrs

    Neighbor ID     Neighbor addr   State      LSrxl DBsum LSreq Prio Ifc

    192.192.192.3   194.194.194.3   Full/-       0     0     0     5  phani

The output includes the following fields

#### Field | #### Description
--- | ---
`Neighbor ID` | Address assigned to the interface. In the MAX, the IP address is always the address assigned to the Ethernet interface.
`Neighbor addr` | IP address of the router used to reach a neighbor. This is often the same address as the neighbor itself.
`State` | State of the link-state database exchange. Full indicates that the databases are fully aligned between the MAX and its neighbor.
`LSrxl` | Number of LSAs in the retransmission list.
`DBsum` | Number of LSAs in the database summary list.
`LSreq` | Number of LSAs in the request list.
`Prio` | Designated router election priority assigned to the MAX.
`Ifc` | Name for the Ethernet or Connection profile name for the WAN.

:

#### Displaying OSPF routers

To display OSPF routers, enter the Show OSPF Routers command. For example:

    ascend% show ospf routers

    DType    RType    Destination        Area            Cost                Next hop(s)          #

    ASBR      OSPF      192.192.192.3    0.0.0.0        10                  194.194.194.3      2

#### Field | #### Description
--- | ---
`DType` | Internal route type.
`RType` | Internal router type.
`Destination` | Router's IP address.
`Area` | Area in which the router resides.
`Cost` | Cost of the router.
`Next hop(s)` | Next hop in the route to the destination.
`#` | Number of the interface used to reach the destination.

The output includes the following fields:

#### Displaying OSPF External AS advertisements

To display OSPF External AS advertisements, enter the Show OSPF Ext command. For example:

    ascend% show ospf ext

    Type LS ID              LS originator     Seqno     Age   Xsum

    ASE5 192.192.192.0      192.192.192.2   0x800005f6  751  0xc24d

    # advertisements:       1

    Checksum total:         0xc24d

The output includes the following fields:

#### Field | #### Description
--- | ---
`Type` | Displays `ASE5`.
`LS ID` | Target address of the route.
`LS originator` | Address of the advertising router.
`Seqno` | Hexadecimal number that begins with 80000000 and increments by one for each LSA received.
`Age` | Age of the route in seconds.
`Xsum` | Checksum of the LSA.
`# advertise- ments` | Total number of entries in the ASE5 database.
`Checksum total` | Checksum of the ASE5 database.

#### Displaying the OSPF routing table

To display the OSPF routing table, enter the Show OSPF Rtab command. For example:

    ascend% show ospf rtab

    DTyp		RType	Destination	Area		Cost	Flags	Next hop(s)	#

    RTE		FIX	192.192.192.0/24		-	1	0x82	0.0.0.170	170

    RTE		OSPF	194.194.194.2/32	0.0.0.0		20	0x1	194.194.194.3	2

    ASBR		NONE	192.192.192.2/32		-	0	0x0	None	-1

    RTE		OSPF	192.192.192.2/32	0.0.0.0		0	0x1	0.0.0.170	170

    RTE		OSPF	194.194.194.3/32	0.0.0.0		10	0x101	194.194.194.3	2

    RTE		NONE	194.194.194.0/24		-	0	0x2	None	-1

    ASBR		OSPF	192.192.192.3/32	0.0.0.0		10	0x100	194.194.194.3	2

    RTE		OSPF	192.192.192.3/32	0.0.0.0		10	0x1	194.194.194.3	2

The output includes the following fields

#### Field | #### Description
--- | ---
`DType` | Internal route type. DType displays one of the following values: RTE (generic route), ASBR (AS border route), or BR (area border route).
`RType` | Internal router type. RType displays one of the following values: FIX (static route), NONE, DEL (deleted or bogus state), OSPF (OSPF-computed), OSE1 (type 1 external), or OSE2 (type 2 external).
`Destination` | Destination address and subnet mask of the route.
`Area` | Area ID of the route.
`Cost` | Cost of the route.
`Flags` | Hexadecimal number representing an internal flag.
`Next hop(s)` | Next hop in the route to the destination.
`#` | Number of the interface used to reach the destination.

:

#### Displaying summarized OSPF database information

To display summarized information about the OSPF database, enter the Show OSPF Database command. For example:

    ascend% show ospf database

                                                    Router Link States (Area: 0.0.0.0)

    Type LS ID                            LS originator          Seqno          Age      Xsum

    RTR    192.192.192.2            192.192.192.2      0x800005f8    783    0x6f0b

    RTR    192.192.192.3            192.192.192.3      0x800005f8    250    0x6f09

                                    # advertisements:              2

                                    Checksum total:                  0xde14

                                                    External ASE5 Link States

    Type  LS ID                            LS originator          Seqno          Age      Xsum

    ASE5  192.192.192.0            192.192.192.2      0x800005f6    783    0xc24d

                                    # advertisements:              1

                                    Checksum total:                  0xc24d

The output includes the following fields:

#### Type | RTR (Router LSAs), NET (Network LSAs), ASE5 (External ASE5 link advertisements to destinations external to the autonomous system), or ASE7 (ASE-7 link advertisements that are flooded only within an NSSA).
--- | ---
`LS ID` | Target address of the route.
`LS originator` | Address of the advertising router.
`Seqno` | Hexadecimal number that begins with 80000000 and increments by one for each LSA received.
`Age` | Age of the route in seconds.
`Xsum` | Checksum of the LSA.
`# advertise- ments` | Total number of entries in the database.
`Checksum total` | Checksum of the database.

## Managing multicast routing

The terminal-server command-line interface provides commands to support IP multicast functionality. To display the options, invoke the terminal-server interface (System > Sys Diag > Term Serv) and enter the Show IGMP and/or show Mrouting command with a question mark:

    ascend% show igmp ?

    show igmp ?		Display help information

    show igmp stats		Display IGMP Statistics

    show igmp groups		Display IGMP groups Table

    show igmp clients		Display IGMP clients

    ascend% show mrouting ?

    show mrouting ?		Display help information

    show mrouting stats		Display MROUTING Statistics

### Displaying the multicast forwarding table

To display active multicast group addresses and clients (interfaces) registered for each group:

    ascend% show igmp groups

    IGMP Group address Routing Table Up Time: 0:0:22:17

    Hash      Group Address    Members    Expire time   Counts

    N/A      Default route      *(Mbone)    ......     2224862

    10       224.0.2.250

                                 2           0:3:24       3211 :: 0 S5

                                 1           0:3:21       145 :: 0 S5

                                 0(Mbone)    ......       31901 :: 0 S5

The output includes the following fields:

#### Field | #### Description
--- | ---
`Hash` | Index to a hash table that is displayed for debugging purposes only. The Default route is not an entry in the hash table.
`Group Address` | IP multicast address used. The Default route is the interface on which the multicast router resides. Note: The IP multicast address being monitored is marked with an asterisk, meaning that this address is joined by local application.
`Members` | Interface ID on which the membership resides. The number 0 represents the Ethernet interface. Other numbers represent WAN interfaces, numbered according to when they became active. The interface labeled `Mbone` is the one on which the multicast router resides.
`Expire time` | Time at which this membership expires. The MAX sends out IGMP queries every 60 seconds, so the expiration time is usually renewed. If the expiration time is reached, the entry is removed from the table. Periods in this field indicates that the membership never expires.
`Counts` | Number of packets forwarded to the client, number of packets dropped because of a lack of resources, and state of the membership (the state is displayed for debugging purposes).

### Listing multicast clients

To display a list of multicast clients, enter the Show IGMP Clients command. For example:

    ascend% show igmp clients

    IGMP Clients

    Client      Version  RecvCount  CLU      ALU

      0(Mbone)      1       0          0       0

      2             1      39         68       67

      1             1   33310         65       65

The output includes the following fields:

#### Field | #### Description
`Client` | Interface ID on which the client resides. The number 0 represents the Ethernet. Other numbers are WAN interfaces, numbered according to when they became active. The interface labeled `Mbone` is the one on which the multicast router resides.
`Version` | Version of IGMP being used.
`RecvCount` | Number of IGMP messages received on that interface.
`CLU` (CurrentLine Utilization) and `ALU` (Average Line Utilization) | Percentage of bandwidth utilized across this interface. If bandwidth utilization is high, some IGMP packet types will not be forwarded.

### Displaying multicast activity

To display the number of IGMP packet types sent and received, enter the Show IGMP Stats command. For example:

    ascend% show igmp stats

                  46 packets received.

            0 bad checksum packets received.

            0 bad version packets received.

            0 query packets received.

           46 response packets received.

            0 leave packets received.

           51 packets transmitted.

           47 query packets sent.

            4 response packets sent.

            0 leave packets sent.

To display the number of multicast packets received and forwarded, enter the Show Mrouting Stats commands. For example:

    ascend% show mrouting stats

    34988 packets received.

        57040 packets forwarded.

            0 packets in error.

           91 packets dropped.

            0 packets transmitted.

In many cases, the number of packets forwarded is greater than the number of packets received, because packets can be duplicated and forwarded across multiple links.

## Monitoring Frame Relay connections

The terminal-server command-line interface includes Show FR commands for monitoring Frame Relay in the MAX. To display the options, invoke the terminal-server interface (System > Sys Diag > Term Serv) and enter the Show FR command with a question mark:

    ascend% show fr ?

    show fr ?		Display help information

    show fr stats		Display Frame Relay information

    show fr lmi		Display Frame Relay LMI information

    show fr dlci [name]		Display all DLCI information or just for [name]

    show fr circuits		Display the FR Circuit table

### Displaying Frame Relay statistics

To display Frame Relay statistics, enter the Show FR Stats commands: For example:

    ascend% show fr stats

    Name         Type   Status    Speed    MTU     InFrame     OutFrame

    fr1          DCE    Down     64000    1532           0            1

    fr1-temp     DCE      Up     64000    1532           0            1

    fr1-temp-9   DCE      Up     64000     1532          0            0

The output includes the following fields:

#### Field | #### Description
--- | ---
`Name` | Name of the Frame Relay profile associated with the interface.
`Type` | Type of interface.
`Status` | Status of the interface. Up means the interface is functional, but is not necessarily handling an active call. Down means the interface is not functional.
`Speed` | Data rate in bits per second.
`MTU` | Maximum packet size allowed on the interface.
`InFrame` | Number of frames the interface has received.
`OutFrame` | Number of frames transmitted.

### Displaying link management information

To display Link Management Information (LMI) for each link activated by a Frame Relay profile, enter the Show FR LMI command. For example:

    ascend% show fr lmi

    T1_617D LMI for fr1

      Invalid Unnumbered info         0  Invalid Prot Disc                0

      Invalid Dummy Call Ref          0  Invalid Msg Type                 0

      Invalid Status Message          0  Invalid Lock Shift               0

      Invalid Information ID          0  Invalid Report Type              0

      Num Status Enqs Sent            0  Num Status Msgs Rcvd             0

      Num Update Status Rcvd          0  Num Status Timeouts           2779

    LMI is not on for fr1-temp

    LMI is not on for fr1-temp-9

ANSI T1.617 Annex D local in-channel signaling protocol is the basis for this information. (For a full definition of each of the fields reported, see Annex D.)

### Displaying Data Link Connection Indicator (DLCI)status

To display the status of each Data Link Connection Indicator (DLCI), enter the Show FR LMI command. For example:

    ascend% show fr dlci

    DLCIs for fr1

    DLCIs for fr1-temp

    eng-lab-236-Cir		DLCI =   17		Status = ACTIVE

    		input pkts	0	output pkts	0

    		input octets	0	output octets	0

    		input FECN	0	input DE	0

    		input BECN	0

    last time status changed: 03/05/1997  14:44:17

    DLCIs for fr1-temp-9

    eng-lab-236-Cir-9  DLCI =   16    Status = ACTIVE

    		input pkts	0	output pkts	0

    		input octets	0	output octets	0

    		input FECN	0	input DE	0

    		input BECN	0

    last time status changed: 03/05/1997  14:45:07

    DLCIs not assigned

The output includes the following fields:

#### Field | #### Description
--- | ---
`DLCI` | DLCI number.
`Status` | ACTIVE if the connection is up or INACTIVE if not.
`input pkts` | Number of frames the interface has received.
`output pkts` | Number of frames the interface has transmitted.
`input octets` | Number of bytes the interface has received.
`output octets` | Number of bytes the interface has transmitted.
`in FECN pkts` | Number of packets received with the Forward Explicit Congestion Notification (FECN) bit set. This field always contains a 0 (zero), because congestion management is not currently supported.
`in BECN pkts` | Number of packets received with the Backward Explicit Congestion Notification (BECN) bit set. This field always contains a 0 (zero), because congestion management is not currently supported.
`in DE pkts` | Number of packets received with the Discard Eligibility (DE) indicator bit set.
`last time status changed` | Time at which the DLCI state changed.

### Displaying circuit information

The Show FR Circuits command displays the Frame Relay profile name, the DLCI, and the status of configured circuits. For example:

    ascend% show fr circuits

    cir-9 User Setting Up

    fr1-temp-9		16		Up

    fr1-temp		17		Up

### Turning off a circuit without disabling its endpoints

The Set Circuit command enables you to turn off traffic going through a Frame Relay circuit without disabling the circuit endpoints. This command prevents traffic from traveling between endpoints, but does not disrupt the state of the DLCI. To display the support options:

    ascend% set circuit ?

    set circuit ?       Display help information

    set circuit active [name]  Set the CIRCUIT to active

    set circuit inactive [name]  Set the CIRCUIT to inactive

To allow data to flow through a circuit, enter the Set Circuit Active command and append the name of the circuit. parameter. For example:

    ascend% set circuit active circuit-1

To turn off data flow without disrupting the state of the DLCIs, enter the Set Circuit Inactive command and append the name of the circuit. For example:

    ascend% set circuit inactive circuit-2

## Monitoring X.25 and PAD connections

The terminal server supports two commands for obtaining information about X.25 and PAD service. To invoke the terminal server, select System > Sys Diag > Term Serv and press Enter.

### Displaying information about PAD sessions

To display information about PAD sessions, enter the Show PAD commands. For example:

    ascend% show pad

    Port   State        LCN        BPS       User     Called Addr.

    1     connected      0         9600      rchan     419342855555

    2     connected      0         9600      dhersh

The output includes the following fields:

#### Field | #### Description
--- | ---
`Port` | Port for the X.25 connection.
`Stat` | State of the connection, which can be one of the following: `Idle`-The PAD is open, but no call has been issued. `Calling`-A call has been issued and is awaiting acceptance. `Connected`-The call is connected and in session. `Clearing`-A Clear command has been issued and the transmitter is awaiting a clear confirmation.
`LCN` | Logical Channel Number for a PVC. An LCN of 0 means the circuit is not a PVC (but is a switched virtual circuit).
`BPS` | Data rate of the connection in bits per second.
`User` | Connection profile name of the caller.
`Called Add` | X.121 address of the remote node.

### Displaying information about X.25

To display information about X.25 frame and packet layers, enter the Show X25 command. For example:

    ascend% show x25

    Frame     State           BytesIn        BytesOut

     1        LinkUp            15             45

    Packet     State          BytesIn         BytesOut

     1         Ready             0              0

The output includes the following fields:

#### Field | #### Description
--- | ---
`Frame` | Frame layer and packet layer, respectively.
`Stat` | State of the connection at that layer. For the frame layer, the following states can occur: `SABMSent`-The MAX has sent an Set Asynchronous Balanced Mode (SABM) message to establish the operating mode as Link Access Balanced Protocol (LABP), and the transmitter is waiting for a an Unnumbered Acknowledge response (UA). `DISCSent`-The MAX sends a DISC message to disconnect the frame level, and the transmitter is waiting for a UA. `FRMRSent`-The MAX sends an FRMR message, indicating that the MAX received a malformed frame, and the sender is waiting for a SABM message. `LinkUp`-The link is up and sending I-frames and S-frames. `Disconnected`-The MAX requests a disconnect, and the sender is waiting for a SABM message. For the packet layer, the following states can occur: `Ready`-The packet layer is ready to send and receive data. `DTERestart`-The DTE issues a Restart Request. `DCERestart`-The DCE issues a Restart Request. `BothRestart`-The MAX sends Restart Requests to both the DTE and the DCE. `InitState`-Indicates the initial state of a call.
`BytesIn` | Number of bytes the MAX receives from the remote node.
`BytesOut` | Number of bytes the MAX transmits to the remote node.

## Setting up ISDN D-channel X.25 support

### PAD service signals

The PAD transmits PAD service signals to the terminal server to acknowledge PAD commands and to inform the user about the internal state of the PAD. The terminal-server user can suppress the reception of PAD service signals by setting PAD parameter #6 to 0 (zero). Figure 5-1 lists the PAD service signals.

Table 5-1. PAD service signals

#### Service signal

#### Description

RESET DTE

The remote DTE has reset the virtual circuit.

RESET ERR

A reset has occurred because of a local procedure error.

RESET NC

A reset has occurred because of network congestion.

COM

A call has been connected.

`PAD ID`

Precedes a string that identifies the PAD.

`ERROR`

The terminal-server user used faulty syntax when entering an X.25/PAD command.

`CLR`

A virtual circuit has been cleared.

`ENGAGED`

In response to the Stat command, indicates that a virtual call is up.

`FREE`

In response to the Stat command, indicates that a virtual call is cleared.

`PAR` with X.3 parameter reference numbers and their current values

A response to the Set? command.

### X.25 clear cause codes

Table 5-2 shows hexadecimal X.25 clear cause codes.

Table 5-2. Clear cause codes

#### Hex value

#### Cause code

01

Number busy

03

Invalid facility request

05

Network congestion

09

Out of order

0B

Access barred

0D

Not obtainable

11

Remote procedure error

13

Local procedure error

15

RPOA out of order

19

Reverse charging acceptance not subscribed

21

Incompatible destination

29

Fast select acceptance not subscribed

39

Ship absent

C1

Gateway-detected procedure error

C3

Gateway congestion

### X.25 diagnostic field values

Table 5-3 shows X.25 diagnostics:

Table 5-3. X.25 diagnostic field values

#### Hex value

#### Dec value

#### Diagnostic

0

0

No additional information

1

1

Invalid P(S)

2

2

Invalid P(R)

10

16

Packet type invalid

11

17

State r1

12

18

State r2

13

19

State r3

14

20

State p1

15

21

State p2

16

22

State p3

17

23

State p4

18

24

State p5

19

25

State p6

1A

26

State p7

1B

27

State d1

1C

28

State d2

1D

29

State d3

20

32

Packet not allowed

21

33

Unidentifiable packet

22

34

Call on one-way LC

23

35

Invalid packet type on a PVC

25

37

Reject not subscribed to

26

38

Packet too short

27

39

Packet too long

29

41

Restart packet with non-zero LC

2B

43

Unauthorized interrupt confirmation

2C

44

Unauthorized interrupt

2D

45

Unauthorized reject

30

48

Timer expired

31

49

Incoming call (or DTE timer expired for call request)

32

50

Clear indication (or DTE timer expired or retransmission count surpassed for clear request)

33

51

Reset indication (or DTE timer expired or retransmission count surpassed for reset request)

34

52

Rstart indication (or DTE timer expired or retransmission count surpassed for restart request)

40

64

Call setup, call clearing, or registration problem

41

65

Facility/registration code not allowed

42

66

Facility parameter not allowed

43

67

Invalid called address

44

68

Invalid calling address

45

69

Invalid facility/registration length

46

70

Incoming call barred

47

71

No logical channel available

48

72

Call collision

49

73

Duplicate facility requested

4A

74

Nonzero address length

4B

75

Nonzero facility length

4C

76

Facility not provided when expected

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