What are useful commands for 3Com routers?

3Com NetBuilder OS Key Trouble-Shooting Commands

The following are some of the key OS (v11.4) commands for trouble shooting 3Com NetBuilder routers (also referred to as SuperStack « II)

Examining Network Devices
To examine the status of the IP router, follow these steps:
1 Display information on the attached networks by entering:
SHow -IP NETaddr
2 Determine which stations or networks are reachable from the router by entering:
SHow -IP AllRoutes
3 Display information from the Address Translation Table by entering:
SHow -IP ADDRess

Getting Statistics
After you have followed the necessary setup and checking procedures using the
PING command, examine the statistics by entering:
SHow -SYS STATistics -IP
You can collect statistics for a specific period by using the SampleTime and
STATistics parameters.

Checking the Overall Status
The following information pertains to checking the status of the router.
Procedure
To check the overall status of the IP router, follow these steps:
1 Examine the path configurations by entering:
SHow -PATH CONFiguration
2 Examine the port configurations by entering:
SHow -PORT CONFiguration
3 Examine the IP configurations by entering:
SHow -IP CONFiguration
4 Examine the RIPIP configurations by entering:
SHow -RIPIP CONFiguration
5 Examine the OSPF configurations by entering:
SHow -OSPF CONFiguration
6 Examine the ARP configurations by entering:
SHow -ARP CONFiguration
7 Verify the IPX configuration by entering:
SHow -IPX CONFiguration
The router displays the IPX configuration information.

Verifying IPX Protocol Configuration
This section explains how to verify the status of networks that are reachable from
the router and how to get statistics from the router and from other networks and stations.

1 Check the state of the current configuration by entering:
SHow -IPX DIAGnostics
The diagnostics command will display any configuration errors that have occurred.
2 Check the state of the NRIP and SAP Services by entering:
SHow -NRIP CONTrol
SHow -SAP CONTrol
The control parameter for both of these services should be set to Talk and Listen to
enable dynamic route learning.
3 Check the state of all networks assigned to the ports of a router by entering:
SHow -IPX NETnumber
SHow -IPX CONTrol
The first command displays the network numbers assigned to each port on this
router and the state that each network is in. Each network should be in the UP
state. If a network is in the DOWN state, check that the -IPX CONTrol parameter is
enabled. If the network is in the DISABLE state, make sure that all PORT and PATH
parameters are configured appropriately. The second command allows you to
verify if routing is enabled on the ports.
4 Verify that the router can access the networks it was configured to access by
entering:
SHow -IPX AllRoutes Long
This command displays all known routes (dynamic, static, and default, if
configured), hop counts, and cost in the IPX Routing Table. Adding ôLongö to the
command also displays gateway information.
5 Verify that the router can learn and exchange service information from servers on
the directly connected networks and other routers, by entering:
SHow -IPX AllServers Long
The router displays a server table. For more information on the contents of the
server table, see ôLearning Routes and Service Informationö later in this chapter.
Adding ôLongö to the command also displays gateway information.
6 Display the configuration information for all paths by entering:
SHow -PATH CONFiguration
Check that the configuration information is correct for all paths.
7 Display the configuration information for all ports by entering:
SHow -PORT CONFiguration
Check that the configuration information is correct for all ports.
8 Verify the setting of the -PORT ProtMacAddrFmt parameter using:
SHow !<port> -PORT ProtMacAddrFmt
9 Display the current IPX configuration parameters by entering:
SHow -IPX CONFiguration
Check that the configuration information is correct.
10 Determine connectivity to an IPX node on the network using:
NetwarePING &<network>%<host> [timeout (1û300 seconds)]
11 Display the NLSP, NRIP, and SAP Services and verify the configuration information
by entering:
SHow -NLSP CONFiguration
SHow -NRIP CONFiguration
SHow -SAP CONFiguration
12 Make a connection from a workstation on one attached network to a file server
on another network to see if packets can be routed across the router.
13 Obtain configuration information from a NetWare server using:
NetwareView &<network>%<host> [timeout (1û300 seconds)]
14 Obtain the status of the router by entering:
SHow -IPX DIAGnostics
Getting Statistics To view statistics, enter:
SHow -SYS STATistics -IPX
SHow -SYS STATistics -NRIP
SHow -SYS STATistics -SAP
SHow -SYS STATistics -NLSP
You can collect statistics for a specific time period by using the SampleTime and
STATistics parameters.

Troubleshooting the Configuration
If you are unable to make connections to other networks after setting up the
router, review the following troubleshooting procedure. This procedure can help
correct problems in making single-hop (involving one router) and multiple-hop
(involving more than one router) connections. If the router continues to operate
improperly after you have completed the troubleshooting procedure, contact your
network supplier for assistance.
To troubleshoot the configuration, follow these steps:
1 If you are experiencing problems because of configuration errors, examine the
service diagnostics information using:
SHow !<port> -IPX DIAGnostics
The diagnostics command displays troubleshooting information about IPX routing
and gives suggestions for corrective actions. The troubleshooting information
consists of global diagnostic messages, port specific diagnostic messages, NRIP
diagnostic messages, and SAP diagnostic messages.
The following display appears:
--------------------IPX Diagnostic Information------------------
No global diagnostic information available.
---------------------------Port 1------------------------------
This port seems to be normal.
---------------------------Port 2------------------------------
Network &00000300 conflicts with &DDDDD200 on node 080002A078DB.
---------------------------Port 3------------------------------
IPX Routing is not enabled.Please configure IPX CONTrol parameter.
---------------------------Port 4-------------------------------
IPX Routing is not enabled.Please configure IPX CONTrol parameter.

In this example, the network assigned to port 2 is shown as &00000300, but node
2 at 080002A078DB thinks that the network should be &DDDDD200.
2 Make sure all cables are properly connected and that the router is properly
installed.
For installation instructions, see the installation guide provided with your
bridge/router.
3 Verify that routing is enabled by entering:
SHow -IPX CONTrol
The router displays the current values for the CONTrol parameter for each port. If
the values are set to ROute, no action is necessary. If the values are set to
NoROute, to enable the IPX router use:
SETDefault !<port> -IPX CONTrol = ROute
4 Check the network number and status by entering:
SHow -IPX NETnumber
Look at the status of the networks: each configured network should be in the UP
state. If it is in the DOWN state, check to make sure that all PORT and PATH
parameters are configured correctly. If the port is in the DISABLED state, make sure
IPX routing is enabled for the port.
Look at the current network configuration: if no network is configured on the
specific port, to add a network number to that port use:
SETDefault !<port> -IPX NETnumber = &<number>(0-FFFFFFFD) [Ethernet | Ieee
| Llc | Snap | X25 | PPP | Frame | SMDS | ATM]
Make sure that you assign the network number to the correct port. Network
numbers consist of eight hexadecimal digits. For example, to assign network
number 4321 to port 2 on the router, enter:
SETDefault !2 -IPX NETnumber = &4321
If this is an Ethernet port, all IPX packets sent from this port will be encapsulated
with the IEEE header format, because IEEE is the default format and no format is
specified in the command. Make sure that the header type configured matches
that of the NetWare servers and clients.
The software detects the media type and sets the header format correctly. You do
not need to specify the header format type in the NETnumber parameter for a
WAN. Each LAN must be configured if the default is not appropriate.
To detect a mismatch of encapsulation type or network, enter:
SHow -IPX DIAGnostics
5 Verify that dynamic learning and NRIP updates are enabled on the port by
entering: SHow -NRIP CONTrol
The router displays the current values for the NRIP CONTrol parameter. If dynamic
learning and NRIP updates are disabled on the port, enable it using:
SETDefault !<port> -NRIP CONTrol = (Talk, Listen, PEriodic)
SETDefault !<port> -SAP CONTROL = (Talk, Listen, PEriodic)
6 Verify that the network you are trying to reach is in the IPX Routing Table by
entering:
SHow -IPX AllRoutes
The IPX router displays the routing table entries. From the table entry, you can
determine which path is being used. Examine the entries to make sure a route in
the table is taking the appropriate path. You can also specify a network number
using the SHow -IPX AllRoutes <NETnumber> syntax to verify single route
reachability.
If the entry in the table has a hop number of 16, the network is unreachable at the
present time. Wait several minutes and use the SHow -IPX AllRoutes
<NETnumber> syntax again. Optionally, you can use the FLush -IPX AllRoutes
command to remove dynamically learned routes and services. After flushing the
table, wait a few minutes before reentering the SHow -IPX AllRoutes command.
7 Verify that the server you are trying to reach is in the IPX Server Table by entering:
SHow -IPX AllServers
The IPX router displays all known servers in the IPX Server Table, including server
addresses, server names, and the number of hops involved. Make sure the server
name to which you are trying to connect is in the table.
You can also specify a server name using the SHow -IPX AllServers ô<string>ö
syntax to verify single server reachability.
8 If you are experiencing connectivity problems due to routing and service tables
that are not synchronized between IPX routers on your internetwork, flush the
routing and service table entries by entering:
FLush -IPX AllRoutes
FLush -IPX AllServers
These commands remove all dynamically learned entries from the routing table
and all entries from the server table, and then rebuild these tables.
9 Display statistics for the IPX Service by entering:
SHow -SYS STATistics -IPX
For information on interpreting statistics displays, see the Statistics Displays
appendix.
10 Display statistics for the NRIP and SAP Services by entering:
SHow -SYS STATistics -NRIP
SHow -SYS STATistics ûSAP




Dial Port ISDN Connections
HangUp
Syntax For non-ISDN interfaces
Port-based disconnecting:
Hangup ! <port> [-PORT]
Path-based disconnecting:
HangUp ! <path> -PATH
For built-in ISDN interfaces
Port-based disconnecting:
Hangup ! <port> [-PORT]
Path-based disconnecting:
HangUp ! <connectorID.channelID> -PATH
Minimum Privilege Level Network Manager
Default Port-based hangup
Description The HangUp command disconnects a dial-up path manually (path-based
disconnecting) or allows you to disconnect all phone connections on the specified
port (port-based disconnecting). By default, port-based disconnecting is
performed. This command can hang up calls on dynamic paths or static paths. If
the path is dynamic and is currently bound to a port, the HangUp command
disconnects the call, unbinds the path, and places the path back into the dial pool.
Bandwidth management compares the bandwidth of the current port against the
bandwidth set with the -PORT NORMalBandwidth parameter for actions such as
hanging up the line or changing the NORMalBandwidth setting, and makes any
required adjustments.
This command can disconnect a dial-up path used for disaster recovery or
bandwidth-on-demand tuning. If disaster recovery or bandwidth-on-demand is
configured and an additional path is activated (due to failure or bandwidth
overload of the line), when the HangUp command is issued on the additional
path, the call is disconnected. BOD will bring up the lines again only if congestion
persists. If you do not want the additional path to be reconnected after
disconnection, you must change the dial-up configuration before or immediately
after you issue the HangUp command.


DialHistory
Syntax SHow -POrt DialHistory
Default No default
Description The DialHistory parameter displays a time-stamped dial history for all ports. The information in the display can be used for troubleshooting purposes.

DialSTatus
Syntax SHow [!<port> | !*] -POrt DialSTatus
Default No default
Description The DialSTatus parameter shows the current status and dial path status
information for the specified dial port or for all dial ports. A message is displayed
for each port describing its state under the bandwidth manager. The display
includes the path number and its state (up, down, or disabled). If the port is to be
used for an outgoing call, the dial string (phone number) is displayed. This
parameter also displays port-level dial diagnostic messages that can be used for
troubleshooting disaster recovery and BOD configurations.

CLIList
Syntax ADD !<port> -POrt CLIList ôdial stringö
DELete !<port> -POrt CLIList ôdial stringö
SHow [!<port> | !*] -POrt CLIList
SHowDefault [!<port> | !*] -POrt CLIList
Default No default
Description The CLIList parameter adds or deletes a dial string (the ISDN phone number and subaddress) to a list of numbers used by the called party to map the incoming call
to the appropriate port and to bind an ISDN dynamic path to that port to
complete the call. This parameter is used also for security reasons to screen any calls
that do not have a match in the calling line identifier list database.
Up to 32 calling line identifier list entries can be made per port.
The calling line identifier list entries take effect only if -POrt DialRcvrState has been
set to AnswerCLI. See ôDialRcvrStateö later in this chapter for more details.
The binding of a path to a port with a calling line identifier list number supersedes
and ignores the binding between path and port set up by a system caller ID (SCID)
number.
Valuesôdial stringö
Identifies the ISDN address number and subaddress to be added to the calling line identifier list database. This dial string is used by the called party to map the incoming call to the appropriate port and to bind a dynamic path to that port. The dial string can be up to 50 alphanumeric characters and must be enclosed in quotation marks. If a subaddress is specified, the subaddress follows and must be separated from the ISDN phone number with a semicolon (. The dial string must be unique to the system.

DialCarrierTime
Syntax For non-ISDN interfaces
SETDefault !<path> -PAth DialCarrierTime = <seconds> (30û300)
SHow [!<path> | !*] -PAth DialCarrierTime
SHowDefault [!<path> | !*] -PAth DialCarrierTime
For built-in ISDN interfaces
SETDefault !<connectorID.channelID> -PAth DialCarrierTime = <seconds>
(50û300)
SHow [!<connectorID.channelID> | !<connectorID>.*] -PAth DialCarrierTime
SHowDefault [!<connectorID.channelID> | !<connectorID>.*] ûPath DialCarrierTime
Default 120
Description The DialCarrierTime parameter defines the number of seconds the system must
wait for the carrier signals on the connected line. If this timer expires before the
carrier is detected, the interface is disconnected; the system retries the call after
the retry timer times out.


MEnu
Syntax MEnu [-<service>] [<param-name>]
Minimum Privilege Level Network Manager
Description The MEnu command can display three levels of menus. From these menus you can
display and modify parameters and be prompted for the appropriate sequence to
enter.
If the CurrentServices parameter is set to ALL, the Main menu appears after you
enter the MEnu command, allowing you to choose a service.
Depending on your hardware and software configuration, the list of available
services on the Main menu may differ.
If the CurrentServices parameter is set to a particular service, the Main menu
displays only that service. For example, if the current service is PORT, only the PORT
Service entry appears in the Main menu.
If you specify the service in the MEnu command, the parameters in the specified
service are displayed, not the ones in the current service. For example, if the current
service is PORT, and you enter MEnu -PATH, the PATH Service menu containing
parameters in the PATH Service is displayed.
The Environment parameters are not accessible through the MEnu command. To
manipulate these parameters (for example, the InterAction and PRIvilege
parameters), enter the appropriate command at the system prompt. Environment
parameters are available regardless of the current service.
In the service menu, the parameters are numbered. The commands that can be
used to modify the parameters are enclosed in parentheses. If no commands follow
a parameter, as in the case of the CONFiguration parameter in the PORT Service
menu, the parameter can only be displayed.
If you select a configurable parameter from the service menu, another menu
displays information on that parameter and prompts you for the port number (if
appropriate) and command.
When entering the MEnu command, if you include the parameter to be modified or
displayed, the first two levels of the service menu are skipped.
For example, if you enter MEnu -PATH NAme, the following menu appears:
==================== SHow -PATH NAme ==================
Path !1 NAme = Path1
Path !2 NAme = Path2
========= -PATH NAme parameter menu (Level 3)==========
1 - SetD
Select (1-1) ... <CR> to Exit ====>


NetwarePING
Syntax NetwarePING &<network>%<host> [timeout (1û300 seconds)]
Minimum Privilege Level User
Description The NetwarePING command determines connectivity to an Internet Packet
Exchange (IPX) node on the network, including other 3Com bridge/routers.


NetwareTraceRoute
Syntax NetwareTraceRoute &<network>%<host>
Minimum Privilege Level User
Description The NetwareTraceRoute command is a troubleshooting tool used for locating
malfunctioning devices. When you specify a destination IPX address, this
command probes all the intermediate routers and servers traversed along the path
before reaching the final destination node, measures round trip delays, and
displays the results.
Error Messages (Optional) CanÆt trace route to &300%080002001234 now - try later.
Example In this example, the destination node is 3 hops away. The trace route requester has
tried trace route requests four times including those routes on the local network
and one diagnostic request because the target server does not support NetWare
trace route. Enter:
NetwareTraceRoute &00000101%000000000001
Only the second router responded to the trace route request. Non-participating
routers are shown by the <skipping a router> value. If the target server supported
the trace route protocol, there is not a diagnostic request.
NetwareTraceRoute to &00000101%000000000001 ...
Hops Next Router Address Round Trip Delays
0 <skipping a router> * * *
1 &00000200%080002A00AF0 3 ms 5 ms 4 ms
2 <skipping a router> * * *
3 <skipping a router> * * *
3 &00000101%000000000001 6 ms 7 ms 6 ms

NetwareView
Syntax NetwareView &<network>%<host> [timeout (1û300 seconds)]
Minimum Privilege Level User
Description The NetwareView command obtains configuration information from a NetWare
server. This command uses NetWare diagnostic request and response packet types.
Normal Response The following is a sample display of a target server configuration received by the
NetwareView command:
Major version: 1
Minor version: 0
SPX Diagnostic Socket: 4002
Number of Components: 3
Component ID: 0 (IPX/SPX)
Component ID: 1 (Router Driver)
Component ID: 6 (File Server/Router)
Number of Local Networks: 2
Local Network Type: 1 (Non-dedicated File Server (virtual board)
Network Address1 &0000DADA
Node Address1 %000000000001
Local Network Type: 0 (LAN/WAN board)
Network Address2 &00000303
NodeAddress2 %2608C4C5755


PING
Syntax PING [!<source port> | !<source-IP>] [C<Count>] [W<Wait>]
[T<TTL>][L<Length>] [I<Increment>] [D<ôDataö>] [Record] <target-IP |
target-name>
Minimum Privilege Level User
Description The PING command determines whether or not a specified IP device is operating
without connecting to that device. The specified device must support the Internet
Control Message Protocol (ICMP). Use the Internet address or the name of the
destination in the command.
You may want to use the PING command to check whether an IP host on the
network is up and running.
Normal Response If the host responds within the specified time, the <IP address> is alive
message appears.
Values <source-port> Specifies a port designator for the packet that will be sent, which
will use the source IP address of the indicated port. If multiple
addresses are assigned to the port, the primary address that is
assigned with the SETDefault command is used.
<source-IP> Specifies the source IP address to be used when sending the
packets. The address must be an IP address currently configured
on the system.
(C)ount Indicates the total number of ping packets to be sent to the
destination. The valid range is from 1 to 1,000,000.
(W)ait Indicates the time in milliseconds to wait for each reply. The range
is from 100 to 1,000,000 milliseconds.
(T)TL Indicates of hop count. The valid range is from 1 to 255.
(L)ength Designates the size of the ping packet starting at the ICMP data
portion of the packet. The valid range is from 1 to 16,000.
I(I)ncrement Specifies that if there is more than one ping packet, and the
length of the data is defined, then each packet is sent after the
increment number of data bytes have been added. For example, if
you ping with a count of 5, length of 1,000 and an increment of
50, then the first ping is sent with 1,000 bytes of data and the
successive pings is sent with 1,050, 1,100, 1,150, and 1,200
bytes of data. The valid range of the increment is from 1 to 1,024.
(D)ata Specifies an ASCII string to be included in each ping packet. The
string is placed at the beginning of the data portion of the
packet. The maximum length of the data string is 80 characters. If
the data length specified with the Length option is greater than
the string, the remainder of the ICMP packet is filled with this
ASCII string and repeated until the packet is filled.
Record Specifies the record route option. A ping packet with record route
records the IP addresses of the gateways as it travels through
them. Because the maximum number of routes that can be
recorded in an IP packet are nine, when the sending station
receives the response back, the packet may or may not contain
the round-trip record route information in it.
<Target-IP | Specifies the IP address of the destination machine.
Target-name> Specifies the domain name of the destination machine.


SysInfo
Syntax SysInfo [<number>]
Minimum Privilege Level Network Manager
Description The SysInfo command shows CPU, firmware version, RAM size, drive information,
and MAC addresses of the NETBuilder bridge/router.
You cannot use the SysInfo command when you access the NETBuilder II
bridge/router with the REMote command.
Normal Response The system information is displayed, or a menu appears that allows you to access
the system information.

ALL
Syntax SHow -DIAGnostic ALL
Default No default
Description The ALL parameter displays diagnostic information for all the parameters in the
DIAGnostic Service.

IPX
Syntax FLush -DIAGnostic IPX
SHow [!<port>| *] -DIAGnostic IPX
Default No default
Description The IPX parameter displays current information about the IPX Service. The display
shows most of the potential configuration errors, run timer errors, incompatibility
issues, boundary conditions, and resource allocation failures that may occur in IPX,
NetWare Routing Information Protocol (NRIP), and SAP. The display provides the
same information as the display obtained using the SHow -IPX DIAGnostics
command.

POrt
Syntax SHow [!<port>| *] -DIAGnostic POrt
Default No default
Description The POrt parameter displays diagnostic information about the PORT Service. The
display provides the same information as the display obtained using the SHow
-PORT DIAGnostics command. For more information, see the PORT Service
Parameters chapter.

CONFiguration
Syntax SHow [!<port> |!*] -IP CONFiguration
Default No default
Description The CONFiguration parameter displays the global IP configuration parameters for
all ports and the information on the directly connected networks.

SMDSGroupAddr
Syntax ADD -IP SMDSGroupAddr <IP address> $<E0ûE999999999999999>
DELete -IP SMDSGroupAddr <IP address>
SHow -IP SMDSGroupAddr
SHowDefault -IP SMDSGroupAddr
Default No default
Description The SMDSGroupAddr parameter defines a multicast address for use by routing
protocols within a logical IP subnetwork (LIS) on the SMDS network. An LIS is a
group of SMDS nodes running IP that all use the same IP subnet for the SMDS
interface. A group address begins with the letter E and is followed by the 15 digits
of the network number. If the number is less than 15 digits, the software pads it
on the right with Fs.
Values
<IP address> Specifies the IP network address, for example,
129.2.0.0.
<E0ûE999999999999999> Specifies the format for an SMDS group, or multicast,
address. The group address type is used to route data
to all routers with the same group address. The group
address begins with the letter E and is followed by the
15 digits of the network number. If the number is less
than 15 digits, it is padded on the right with Fs. An
SMDS group address is the only valid address that can
be used with this parameter.