![[Top]](../images/home.jpg){kind=small}
![[Contents]](../images/contents.jpg){kind=small}
![[Prev]](../images/previous.jpg){kind=small}
![[Next]](../images/next.jpg){kind=small}
![[Last]](../images/index.jpg){kind=small}
This chapter covers the following topics:
Overview
The MAX TNT supports several network management commands, which are useful for locating the sources of problems on the network and for communicating with other hosts for management purposes.
Diagnostic tools for TCP/IP networks
The MAX TNT maintains an internal IP routing table. You can configure the system to use RIP or OSPF to propagate the information in that table to other routers, receive information from other routers, or both, on any LAN or WAN interface. For information about configuring the router, see the MAX TNT Network Configuration Guide. Using the Ping command to test connectivity
The Ping command is useful for verifying that the transmission path between the MAX TNT and another station is open. Ping sends an ICMP echo_request packet to the specified station. It the station receives the packet, it returns an ICMP echo_response packet. For example, to Ping the host techpubs:
admin> ping techpubs
PING techpubs (10.65.212.19): 56 data bytesYou 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, the number of duplicate or damaged echo_response packets (if any), and round-trip statistics. In some cases, round-trip times cannot be calculated.
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
During the Ping exchange, the MAX TNT displays information about the packet exchange, including the Time-To-Live (TTL) of each ICMP echo_response packet.
The maximum TTL for ICMP Ping is 255, while 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 before 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.
IP interfaces change between the active and inactive state as switched calls are brought up and down. To display the interface table, enter the Netstat command with the
-in option, as in the following example:
admin> netstat -inThe interface table contains the following information:
Name MTU Net/Dest Address Ipkts Ierr Opkts Oerr
ie0 1500 10.103.0.0/16 10.103.0.254 17889 0 8819 0
ie0-3 1500 10.235.0.0/16 10.235.0.254 0 0 0 0
ie0-1 1500 10.233.0.0/16 10.233.0.254 0 0 0 0
lo0 1500 127.0.0.1/32 127.0.0.1 116 0 116 0
rj0 1500 127.0.0.2/32 127.0.0.2 0 0 0 0
bh0 1500 127.0.0.3/32 127.0.0.3 29 0 29 0
wanabe 1500 127.0.0.3/32 127.0.0.3 0 0 0 0
local 65535 127.0.0.1/32 127.0.0.1 19783 0 19783 0
mcast 65535 224.0.0.0/4 224.0.0.0 0 0 0 0
tunnel9 1500 10.103.0.0/16 10.103.0.254 0 0 0 0
wan10 1500 130.57.40.243 - 0 0 0 0
wan11 1500 140.57.40.244 - 0 0 0 0
wan12 1500 150.57.40.245 - 0 0 0 0
wan13 1500 10.101.0.2 - 0 0 0 0
wan14 1500 12.151.0.2 12.151.0.1 0 0 0 0
wan15 1500 160.57.40.246 - 0 0 0 0
wan16 1500 50.151.0.2 50.151.0.1 0 0 0 0
wan17 1500 10.102.0.2 - 0 0 0 0
ie1-7-1 1500 10.105.0.0/16 10.105.0.254 1871 0 2686 0
ie1-7-2 1500 10.106.0.0/16 10.106.0.254 0 0 327 0
ie1-7-3 1500 10.107.0.0/16 10.107.0.254 329 0 0 0
ie1-7-4 1500 10.108.0.0/16 10.108.0.254 0 0 985 0
ie1-7-4-1 1500 101.108.0.0/16 101.108.0.254 0 0 0 0
ie1-7-4-2 1500 201.108.0.0/24 201.108.0.254 0 0 0 0
Column name |
Description |
|---|---|
Name |
Name of the interface:
|
MTU |
(Maximum Transmission Unit) The maximum packet size allowed on the interface.
|
Net/Dest |
Network or the target host this interface can reach.
|
Address |
Address of this interface.
|
Ipkts |
Number of packets received.
|
Ierr |
Number of packets that contain errors.
|
Opkts |
Number of packets transmitted.
|
Oerr |
Number of transmitted packets that contain errors.
|
Displaying and modifying IP routes
This section explains how to display the MAX TNT IP routing table. It also explains how to use the Netstat command to display the IP routing table and the IProute command to add or delete static routes. For complete information about configuring IP routing on the MAX TNT, see the MAX TNT Network Configuration Guide. Using the Netstat command to display the routing table
To display the routing table, enter the Netstat command with the -rn argument, as in the following example:
admin> netstat -rnThe routing table contains the following information:
Destination Gateway IF Flg Pref Met Use Age
9.64.254.0/24 10.63.254.1 wanabe SGP 120 5 0 3297
9.70.254.0/24 10.63.254.1 wanabe SGP 120 5 0 3349
10.63.254.0/24 10.63.254.1 wanabe SGP 120 5 0 3297
10.103.0.0/16 - ie0 C 0 0 2001 3352
10.103.0.254/32 - local CP 0 0 1464 3352
10.105.0.0/16 - ie1-7-1 C 0 0 692 3300
10.105.0.254/32 - local CP 0 0 506 3300
10.106.0.0/16 - ie1-7-2 C 0 0 8 3298
10.106.0.254/32 - local CP 0 0 0 3298
10.107.0.0/16 - ie1-7-3 C 0 0 8 3298
10.107.0.254/32 - local CP 0 0 0 3298
10.108.0.0/16 - ie1-7-4 C 0 0 8 3298
10.108.0.254/32 - local CP 0 0 0 3298
10.113.0.0/16 10.103.0.1 ie0 OG 10 2 0 194
10.115.0.0/16 10.105.0.1 ie1-7-1 OG 10 2 0 2288
10.123.0.0/16 10.103.0.8 ie0 OG 10 10 0 3322
10.233.0.0/16 - ie0-1 C 0 0 11629 3352
10.233.0.254/32 - local CP 0 0 174 3352
12.151.0.1/32 - local C 0 0 0 3352
13.103.0.140/32 10.103.0.2 ie0 OG 150 1 0 35
50.151.0.1/32 - local C 0 0 0 3352
127.0.0.0/8 - bh0 CP 0 0 0 3352
127.0.0.1/32 - local CP 0 0 0 3352
127.0.0.2/32 - rj0 CP 0 0 0 3352
130.57.0.0/16 130.57.40.243 wan10 SG 120 7 0 3298
160.57.0.0/16 160.57.40.246 wan15 SG 120 7 0 3298
160.57.40.246/32 160.57.40.246 wan15 S 120 7 1 3298
192.31.114.0/24 192.31.114.254 wanabe SGP 120 5 0 3298
224.0.0.0/4 - mcast CP 0 0 0 3352
224.0.0.1/32 - local CP 0 0 0 3352
224.0.0.2/32 - local CP 0 0 0 3352
224.0.0.5/32 - local CP 0 0 8794 3352
224.0.0.6/32 - local CP 0 0 6602 3352
224.0.0.9/32 - local CP 0 0 0 3352
255.255.255.255/32 - ie0 CP 0 0 0 3352
Modifying the routing table
The IProute command enables you to manually add routes to the routing table, delete them, or change their preference or metric values. The command is useful for temporary routing changes. Changes you make to the routing table with the IProute command do not persist across system resets. RIP and OSPF updates can add back any route you remove with IProute Delete. Also, the MAX TNT restores all routes listed in the IP-Route profile after a system reset.
Syntax element |
Description |
|---|---|
add |
Add an IP route to the routing table.
|
delete |
Delete an IP route from the routing table.
|
iprouteadddest_IPaddr[/subnet_mask]gateway_IPaddr[/subnet_mask] [pref] [metric]
admin> iproute add 10.1.2.0/24 10.0.0.3/24 1It adds 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. The metric to the route is 1 (one hop away).
If you try to add a route to a destination that is already in the routing table, the MAX TNT does not replace the existing route unless it has a higher metric than the route you attempt to add. If you get the message
Warning: a better route appears to exist, the MAX TNT has rejected your attempt to add a route.
iproutedeletedest_IPaddr[/subnet_mask][gateway_IPaddr[/subnet_mask]]
The arguments are the same as for IP Route Add. For example, the following command removes the route to the 10.1.2.0 network:
admin> iproute delete 10.1.2.0 10.0.0.3/24You can also change the metric or preference value of an existing route by using the IProute command. For example, if the routing table contains the following route:
Destination Gateway IF Flg Pref Met Use AgeYou could change the mteric as follows:
10.122.99.0/24 10.122.99.1 wan4 SG 100 7 0 48630
admin> iproute add 10.122.99.0/24 10.122.99.1 50 3
time exceeded reply from a router. For example, to trace the route to the host techpubs:
admin> traceroute techpubs
traceroute to techpubs (10.65.212.19), 30 hops max, 0 byte packetsProbes start with a TTL of one and increase by one until of the following conditions occurs:
1 techpubs.eng.ascend.com (10.65.212.19) 0 ms 0 ms 0 ms
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.)
-m option to specify a different TTL. For example:
admin> traceroute -m 60 techpubs
traceroute to techpubs (10.65.212.19), 60 hops max, 0 byte packetsTraceRoute sends three probes at each TTL setting. The second line of output shows the address of the router and the 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 second line of output an asterisk.
1 techpubs.eng.abc.com (10.65.212.19) 0 ms 0 ms 0 ms
For the details of the TraceRoute command, see the MAX TNT Reference Guide.
To retrieve the IP address of the host
techpubs, proceed as in the following example:
admin> nslookup techpubs
Resolving host techpubs.
IP address for host techpubs is 10.65.212.19.
The MAX TNT maintains a cache of known IP addresses and host MAC, addresses which enables it to act as a proxy for ARP requests for target hosts across the WAN, provided that proxy mode is turned on. (For configuring proxy ARP, see MAX TNT Network Configuration Guide.)
With the ARPtable command, you can display the ARP table, add or delete ARP table entries, or clear the ARP cache entirely. To display the ARP cache, enter the ARPtable command without any arguments, as in the following example:
admin> arptableThe ARP table displays the following information:
IP Address MAC Address Type IF Retries/Pkts/RefCnt Time Stamp
10.103.0.141 00:B0:24:BE:D4:84 DYN 0 0/0/1 23323
10.103.0.2 00:C0:7B:7A:AC:54 DYN 0 0/0/599 23351
10.103.0.220 00:C0:7B:71:83:02 DYN 0 0/0/2843 23301
10.103.0.1 08:00:30:7B:24:27 DYN 0 0/0/4406 23352
10.103.0.8 00:00:0C:06:B3:A2 DYN 0 0/0/6640 23599
10.103.0.7 00:00:0C:56:57:4C DYN 0 0/0/6690 23676
10.103.0.49 00:B0:80:89:19:95 DYN 0 0/0/398 23674
To add an ARP table entry, use the
-a option, as in the following example:
admin> arptable -a 10.65.212.3 00:00:81:3D:F0:48To delete an ARP table entry, use the
-d option, as in the following example:
admin> arptable -a 10.9.8.20To clear the entire ARP table, use the
-f option:
admin> arptable -f
-n option to display the information in numeric format:
admin> netstat -nWithout the
udp:
-Socket- Local Port InQLen InQMax InQDrops Total Rx
1/c 0 1023 0 1 0 0
1/c 1 route 0 0 0 25
1/c 2 echo 0 32 0 0
1/c 3 ntp 0 32 0 1
1/c 4 1022 0 128 0 0
1/c 5 snmp 0 128 0 0
1/1 0 1 0 256 0 0
1/1 1 1018 0 128 0 0
1/3 0 3 0 256 0 0
1/3 1 1021 0 128 0 0
1/5 0 5 0 256 0 0
1/5 1 1020 0 128 0 0
1/8 0 8 0 256 0 0
1/8 1 1019 0 128 0 0
tcp:
Socket Local Remote State
1/c 0 *.23 *.* LISTEN
1/c 1 10.2.3.114.23 15.5.248.121.44581 ESTABLISHED
-n option, the output contains symbolic names instead of numeric values. The Netstat command also supports UDP and TCP arguments, which you can use in conjunction with existing options (such as
-n). For example, to view information about UDP sockets, use this command:
admin> netstat udpThe output shows the queue depth of various UDP ports, as well as the total packets received and total packets dropped on each port. The total-packets-received count includes the total packets dropped. For this sample output, the SNMP queue depth was set to 32. For information about queue depths, see the MAX TNT Network Configuration Guide.
udp:
Socket Local Port InQLen InQMax InQDrops Total Rx
0 1023 0 1 0 0
1 route 0 50 0 509
2 echo 0 32 0 0
3 ntp 0 32 0 0
4 1022 0 128 0 0
5 snmp 32 32 5837 20849
...
The Netstat command supports the
-s option, which displays protocol statistics. The -s option uses the following syntax:
netstat -s identifiersIf no identifiers follow the
-s option, all protocol statistics are shown. If specified, the identifiers determine the type of protocol statistics to display. Valid identifiers include udp, tcp, icmp, ip, igmp, or mcast. Following is an example that displays IP and multicast statistics:
admin> netstat -s ip mcast
ip:
3354 packets received
0 packets received with header errors
0 packets received with address errors
0 packets received forwarded
0 packets received with unknown protocols
0 inbound packets discarded
41357 packets delivered to upper layers
35461 transmit requests
0 discarded transmit packets
78 outbound packets with no route
0 reassemblies timeout
0 reassemblies required
0 reassemblies succeeded
0 reassemblies failed
0 fragmentation succeeded
0 fragmentation failed
0 fragmented packets created
0 route discards due to lack of memory
64 default ttl
mcast:
445 packets received
445 packets forwarded
0 packets in error
0 packets dropped
0 packets transmitted
techpubs, first open a session with the host card. Then issue the Rlogin command:
hdlc-1/16> rlogin techpubs
Password:You can log out of the remote host by entering the Rlogin escape sequence (tilde-dot):
Last login: Wed Oct 2 10:31:36 from marcel.marceau
SunOS Release 4.1.4 (TECHPUBS-BQE) #1: Wed Feb 4 08:56:59 PDT 1998
techpubs%
techpubs% ~.Or, you can log out explicitly:
Connection closed.
techpubs% logoutIf you wish, you can change the default escape character from a tilde to any other character. For details, see the MAX TNT Reference Guide.
Connection closed.
If your user name on the MAX TNT is different from your user name on the remote host, you can specify a user name on the Rlogin command line. For example:
admin> rlogin -l marcel techpubs
Password:
techpubs:
admin> telnet techpubs
Connecting to techpubs (10.65.212.19) ...You can close the Telnet session by logging out of the remote host:
Escape character is '^]'
Connected
SunOS UNIX (techpubs)
techpubs% logout
Connection closed.
Diagnostic tools for IGMP multicast interfaces
The IGMP command displays information about IGMP groups and clients. This can be useful for tracking the IGMP group memberships and active client interfaces. Displaying IGMP group information
To display active multicast group addresses and clients (interfaces) registered for each group, enter the IGMP command with the group option:
admin> igmp groupThe output contains the following fields:
IGMP Group address Routing Table Up Time: 0:0:22:17
Hash Group Address Members Expire time Counts
10 224.0.2.250
2 0:3:24 3211 :: 0 S5
1 0:3:21 145 :: 0 S5
0(Mbone) ...... 31901 :: 0 S5
Displaying IGMP client information
To display a list of multicast clients, enter the IGMP command with the client option:
admin> igmp clientThe output contains the following fields:
IGMP Clients
Client Version RecvCount CLU ALU
0(Mbone) 1 0 0 0
2 1 39 68 67
1 1 33310 65 65
Diagnostic tools for OSPF routers
The OSPF diagnostic-level commands enable the administrator to display information related to OSPF routing, including the link state advertisements (LSAs), border routers' routing table, and the OSPF areas, interfaces, statistics, and routing table. To display the usage statement, enter the OSPF command with the ? option:
admin> ospf ?
ospf usage:
ospf ? Display help information
ospf areas Display OSPF areas
ospf border-routers Display OSPF border router information
ospf database Display OSPF link-state database
ospf errors Display OSPF errors
ospf general Display OSPF general info
ospf interfaces Display OSPF interfaces
ospf neighbor Display OSPF neighbors
ospf rtab Display OSPF routing tab
ospf timer-queue Display OSPF timer queue
ospf stats Display OSPF stats
general option with the OSPF command:
admin> ospf generalOr, you can simply enter the OSPF command without any arguments. For example:
admin> ospf
Rtr ID: 10.168.6.148In either case, the output contains the following fields:
Status: Enabled Version: 2 ABR: Off ASBR: On
LS ASE Count: 4 ASE Cksum sum: Ox241b3 Tos Support: TOS 0 Only
New LSA Originate Count: 17 Rx New LSA Count: 9
Displaying information about OSPF areas
To display information about OSPF areas, include the areas option with the OSPF command. For example:
admin> ospf areas
Area ID: 0.0.0.0The output includes the following fields:
Auth Type: Simple Passwd Import ASE: On Spf Runs: 5
Local ABRs: 0 Local ASBRs: 2 Inter LSAs: 3 Inter Cksum sum: 0x22298
Displaying information about AS border routers
To display AS border-router information, include the border routers option with the OSPF command. For example:
admin> ospf border routersThe output includes the following fields:
Dest Area Cost E Path Nexthop AdvRtr L
AS Border Routes:
170.57.40.254 0.0.0.0 10 RTR 50.151.0.2 170.57.40.254
10.123.0.254 0.0.0.0 11 RTR 10.103.0.7 10.123.0.254
10.103.0.254 0.0.0.0 0 RTR 0.0.0.0 10.103.0.254
10.103.0.220 0.0.0.0 1 RTR 10.103.0.220 10.103.0.220
10.103.0.204 0.0.0.0 1 RTR 10.103.0.204 10.103.0.204
10.123.0.8 0.0.0.0 1 RTR 10.103.0.8 10.123.0.8
10.123.0.7 0.0.0.0 1 RTR 10.103.0.7 10.123.0.7
10.103.0.4 0.0.0.0 1 RTR 10.103.0.4 10.103.0.4
10.103.0.3 0.0.0.0 1 RTR 10.103.0.3 10.103.0.3
10.104.0.2 0.0.0.0 11 RTR 10.103.0.3 10.104.0.2
10.103.0.2 0.0.0.0 1 RTR 10.103.0.2 10.103.0.2
10.102.0.2 0.0.0.0 10 RTR 10.102.0.2 10.102.0.2
10.101.0.2 0.0.0.0 10 RTR 10.101.0.2 10.101.0.2
10.105.0.1 0.0.0.0 1 RTR 10.105.0.1 10.105.0.1
10.104.0.1 0.0.0.0 12 RTR 10.103.0.3 10.104.0.1
10.103.0.1 0.0.0.0 1 RTR 10.103.0.1 10.103.0.1
10.102.0.1 0.0.0.0 11 RTR 10.102.0.2 10.102.0.1
10.101.0.1 0.0.0.0 11 RTR 10.101.0.2 10.101.0.1
Displaying the link-state database
To display the router's link-state database, use the database option. For example:
admin> ospf databaseThe database is segmented by the type of link as defined in RFC 1583:
ospf database
Stub Link States (Area 0.0.0.0)
Link ID Adv Router Age Len Seq# Metric
10.67.0.0 10.67.0.0 229 24 0x0 0
10.101.0.2 10.101.0.2 217 24 0x0 0
10.102.0.2 10.102.0.2 60 24 0x0 0
10.103.0.2 10.103.0.2 25 24 0x0 0
.
.
.
Router Link States (Area 0.0.0.0)
Link ID Adv Router Age Len Seq# Metric
10.101.0.1 10.101.0.1 1565 48 0x800005fb 0
10.101.0.2 10.101.0.2 65 84 0x80000073 0
10.102.0.1 10.102.0.1 827 48 0x80000e50 0
10.102.0.2 10.102.0.2 223 84 0x80000079 0
.
.
.
Network Link States (Area 0.0.0.0)
Link ID Adv Router Age Len Seq# Metric
10.101.0.1 10.101.0.1 1565 32 0x80000061 0
10.102.0.1 10.102.0.1 827 32 0x80000066 0
10.103.0.8 10.123.0.8 240 64 0x8000002f 0
10.104.0.1 10.104.0.1 1166 32 0x800002fc 0
10.105.0.1 10.105.0.1 1443 32 0x80000007 0
10.123.0.7 10.123.0.7 452 36 0x80000008 0
Type-5 AS External Link States
Link ID Adv Router Age Len Seq# Metric
0.0.0.0 10.123.0.7 452 36 0x800003c7 1
10.63.254.1 10.103.0.204 1331 36 0x800003d5 10
10.105.0.0 10.103.0.204 1331 36 0x80000006 1
10.107.0.0 10.103.0.254 1631 36 0x8000015b 1
10.132.0.2 10.103.0.254 35 36 0x80000001 1
10.134.0.2 10.103.0.254 29 36 0x80000001 1
.
.
.
Displaying details about a route in the database
The database option includes suboptions for focusing on particular areas of the database. To display the suboptions, enter the OSPF command with the database and ? arguments:
admin> ospf database ?
ospf database ? Display help informationFor example, you might focus on the network link states:
ospf database asb Display OSPF ASB summary link states
ospf database ase Display OSPF external link states
ospf database network Display OSPF network link states
ospf database router Display OSPF router link states
ospf database summary Display OSPF network summary link states
ospf database ase7 Display OSPF type-7 external link states
admin> ospf database network
Network Link States (Area 0.0.0.0)
LS Age: 1473The following example shows information about Type-7 ASE link states:
Options: No TOS-capability
Link State ID: 10.168.6.181
Advertising Router: 10.168.6.181
Sequence Number: 0x80000003
Checksum: 0x8e58
Length: 32
Network Mask: /24
Attached Router: 10.168.6.181
Attached Router: 10.168.6.148
admin> ospf database ase7
Type-7 AS External Link States (Area 0.0.0.10)
LS Age: 539
Options: No TOS-capability
Link State ID: 11.67.0.0
Advertising Router: 10.31.114.254
Sequence Number: 0x8000000b
Checksum: 0x7f9f
Length: 36
Network Mask: /16
Metric Type (bit E): 1
TOS: 0
Metric: 1
Forwarding address: 10.31.114.254
External Route Tag: c0000000
LS Age: 13
Options: No TOS-capability
Link State ID: 199.199.10.0
Advertising Router: 11.57.4.254
Sequence Number: 0x80000014
Checksum: 0x99cd
Length: 36
Network Mask: /24
Metric Type (bit E): 1
TOS: 0
Metric: 1
Forwarding address: 11.57.4.254
External Route Tag: c0000000
interfaces option with the OSPF command, for example:
admin> ospf interfacesThe output contains the following fields:
Area IP Address Remote Addr Type State Cost Pri DR BDR
---------------------------------------------------------------------------
0.0.0.0 10.2.6.4 10.2.6.4 Bcast BackupDR 1 5 10.2.6.8 10.2.6.4
Displaying OSPF neighbors
To display adjacencies, include the neighbor option with the OSPF command. For example:
admin> ospf neighbor
Area Interface Router Id Nbr IP Addr State Mode PriThe output contains the following fields:
0.0.0.0 10.168.6.148 10.168.6.181 10.168.6.181 Full Slave 5
Displaying the OSPF routing table
To display the OSPF routing table, include the rtab option with the OSPF command. For example:
admin> ospf rtab
Dest Area Cost E Path Nexthop AdvRtr LThe routing table is segmented by the type of route. Each segment contains the following fields:
AS Border Routes:
10.168.6.181 0.0.0.0 1 RTR 10.168.6.181 10.168.6.181
10.168.6.148 0.0.0.0 0 RTR 0.0.0.0 10.168.6.148
Nets: Rtab Version 5
0.0.0.0/0 0.0.0.0 2 0 EXT 10.168.6.181 10.168.6.181 0
8.0.0.0/8 imported: 2
10.168.6.0/24 0.0.0.0 1 0 INT 10.168.6.148 10.168.6.181 1
10.168.6.152/32 imported: 2
Displaying the timer queue
To display information about the timer queue, include the timer-queue option with the OSPF command. For example:
admin> ospf timer-queue
ospf timer-queue
Current Timerq:
Type Minutes Seconds Area Intf
-----------------------------------------------------------
TQAck 0 1 No Area No Intf
TQRetrans 0 1 No Area 10.108.0.254
TQRetrans 0 2 No Area 101.108.0.254
TQRetrans 0 3 No Area 10.103.0.254
TQLsaLock 0 3 0.0.0.0 No Intf
TQRetrans 0 3 No Area 50.151.0.1
TQHelloTimer 0 3 No Area 10.103.0.254
TQRetrans 0 4 No Area 10.105.0.254
TQRetrans 0 4 No Area 10.103.0.254
TQHelloTimer 0 4 No Area 10.105.0.254
TQRetrans 0 5 No Area 10.106.0.254
TQRetrans 0 5 No Area 10.103.0.254
TQHelloTimer 0 5 No Area 10.106.0.254
TQHelloTimer 0 6 No Area 10.108.0.254
TQHelloTimer 0 7 No Area 101.108.0.254
TQAseLsdbAge 0 15 No Area No Intf
TQHelloTimer 0 28 No Area 50.151.0.1
TQHelloTimer 0 29 No Area 10.103.0.254
TQHelloTimer 0 30 No Area 10.103.0.254
TQSumLsdbAge 0 30 No Area No Intf
TQAse7LsdbAge 0 52 No Area No Intf
TQIntLsdbAge 14 53 No Area No Intf
TQIntLsa 18 12 No Area No Intf
TQAseLsa 25 6 No Area No Intf
TQAse7Lsa 25 6 No Area No Intf
errors option with the OSPF command. For example:
admin> ospf errors
ERRORS from: bootThe output lists all error messages related to OSPF, with each message preceded by the number of times it has been generated since the MAX TNT powered up. Immediately following the number is a field indicating one of the following packet types:
0: IP: Bad OSPF pkt type 0: IP: Bad IP Dest
0: IP: Bad IP proto id 0: IP: Pkt src = my IP addr
0: OSPF: Bad OSPF version 0: OSPF: Bad OSPF checksum
0: OSPF: Bad intf area id 0: OSPF: Area mismatch
0: OSPF: Bad virt link info 0: OSPF: Auth type != area type
0: OSPF: Auth key != area key 0: OSPF: Packet is too small
0: OSPF: Packet size > IP length 0: OSPF: Transmit bad
1: OSPF: Received on down IF 0: Hello: IF mask mismatch
0: Hello: IF hello timer mismatch 0: Hello: IF dead timer mismatch
909: Hello: Extern option mismatch 0: Hello: Nbr Id/IP addr confusion
0: Hello: Unknown Virt nbr 0: Hello: Unknown NBMA nbr
0: DD: Unknown nbr 0: DD: Nbr state low
0: DD: Nbr's rtr = my rtrid 0: DD: Extern option mismatch
17: Ack: Unknown nbr 0: Ack: Nbr state low
0: Ls Req: Nbr state low 0: Ls Req: Unknown nbr
0: Ls Req: Empty request 0: LS Req: Bad pkt
0: LS Update: Nbr state low 21: Ls Update: Unknown nbr
0: Ls Update: Newer self-gen LSA 0: Ls Update: Bad LS chksum
5: Ls Update: less recent rx 0: Ls Update: Unknown type
stats option with the OSPF command. For example:
admin> ospf stats
ospf stats
IO stats from: boot
>> RECEIVED:
0: Monitor request
8506: Hello
188: DB Description
134: Link-State Req
9024: Link-State Update
20999: Link-State Ack
>> SENT:
4833: Hello
199: DB Description
50: Link-State Req
30671: Link-State Update
1654: Link-State Ack
Diagnostic tools for IPX routers
The MAX TNT provides two diagnostic commands for monitoring IPX networks, Show Netware Servers and Show Netware Networks. netware servers option. For example:
ascend% show netware servers
IPX address type server nameThe output contains these fields:
ee000001:000000000001:0040 0451 server-1
IPX address: The IPX address of the server. The address uses this format:
type: The type of service available (in hexadecimal format). For example, 0451 designates a file server.
server name: The first 35 characters of the server name.
netware networks option. For example:
ascend% show netware networks
network next router hops ticks originThe output contains these fields:
CFFF0001 00000000000 0 1 Ethernet S
Displaying Ethernet packet contents
The Ether-Display command displays the hexadecimal contents of Ethernet packets being received and transmitted on the specified Ethernet port. You must specify how many octets of each packet you want to display.
admin> ether-display 1 12
ETHER XMIT: 12 of 60 octetsTo stop displaying the Ethernet statistics, specify 0 (zero) octets:
10799E40: 08 00 20 75 80 6b 00 c0 7b 5e ad 3c .. u.k.. {^.<
ETHER RECV: 12 of 60 octets
1077D980: 00 c0 7b 5e ad 3c 00 80 c7 2f 27 ca ..{^.<.. ./'.
ETHER XMIT: 12 of 509 octets
1079A480: 00 80 c7 2f 27 ca 00 c0 7b 5e ad 3c .../'... {^.<
...
admin> ether-display 1 0For complete information about the Ether-Display command, see the MAX TNT Reference Guide.
Copyright © 1997, Ascend Communications, Inc. All rights reserved.