3Com Router User Manual

							Test Tool of Network Connection87
Please see relevant chapters in the 3Com Router Command Reference Guide for 
detailed meanings of various options and parameters. 
Ping supporting IP protocol
■For each ping message sent, if the response message has not been received 
when the waiting time crosses the threshold, then 
Request time out is 
output.
■Otherwise, the data byte number, message sequence number, TTL, and 
response time in the response message will be displayed. 
■Finally, the statistic information will be output, including the sent message 
number, received response message number, percentage of messages 
unresponded, and the minimum, maximum, and average values of the 
response time.
Examples:
[Router]ping 202.38.160.244
The system displays:
 ping 202.38.160.244 : 56 data bytes, press CTRL_C to break
  Reply from 202.38.160.244 : bytes=56 sequence=1 ttl=255 time = 1ms
  Reply from 202.38.160.244 : bytes=56 sequence=2 ttl=255 time = 2ms
  Reply from 202.38.160.244 : bytes=56 sequence=3 ttl=255 time = 1ms
  Reply from 202.38.160.244 : bytes=56 sequence=4 ttl=255 time = 3ms
  Reply from 202.38.160.244 : bytes=56 sequence=5 ttl=255 time = 2ms
 --202.38.160.244 ping statistics--
  5 packets transmitted
  5 packets received
  0% packet loss
  round-trip min/avg/max = 1/2/3 ms
Ping supporting IPX protocol
■For each Ping message sent, the response information is output. “!” indicates 
the response message is received, while “.” indicates not received. 
■Finally, the statistic information is output, including sent message number, 
received response message number, percentage of messages unresponded, 
and the minimum, maximum, and average values of the response time.
Examples:
[Router]ping ipx 2.0.0c91.f61f 
The system displays:
 Press CTRL_C to break
 Sending 5, 100-byte IPX Echoes to 2.0.0c91.f61f, timeout is 2 
 seconds
ping supporting IP protocolping [ip] [-Rdnqrv] [-c count] [-p pattern] 
[-s packetsize] [-t timeout] { host | 
ip-address }
ping supporting IPX 
protocolping [ipx] [-n] [-v] N.H.H.H [count [,timeout 
[,packetsize]]] 
						

							88CHAPTER 6: DISPLAY AND DEBUGGING TOOLS
  !!!!!
 --2.0.0c91.f61f IPX ping statistics--
  5 packets transmitted
  5 packets received
  0% packet loss
  round-trip min/avg/max = 1/2/3 ms
tracert command (Trace 
Route Command)The trace route command helps to trace the current network path to a 
destination. With 
tracert command, all gateways by which the test packet 
passes from the source address to the destination address can be displayed. It can 
be used to check network connection and locate fault. 
The tracert command is executed as follows: first, send a packet with TTL 1, and 
the first hop returns an ICMP error message, indicating that this packet cannot be 
sent (for TTL timeout). Then, this packet is re-sent with TTL added by 1 (namely 2). 
Similarly, the next hop returns TTL timeout. In this way, the procedure continues till 
the destination is reached. The purpose of these procedures is to record the source 
address of each ICMP TTL timeout message, so as to provide the path by which an 
IP packet has to pass to reach the destination address. 
The following command can be executed in any command modes:
Ta b l e 66   tracert command
Please see relevant chapters in the 3Com Router Command Reference Guide for 
detailed meanings of various options and parameters. 
Described below are two examples to analyze the network connection with 
tracert command. In the former example, network connection is correct, while in 
the latter, network connection is faulty. 
[Router]tracert 35.1.1.48
Trace route to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte packet
 1  helios.ee.lbl.gov (128.3.112.1)  19 ms  19 ms  0 ms
 2  lilac-dmc.Berkeley.EDU (128.32.216.1)  39 ms  39 ms  19 ms
 3  ccngw-ner-cc.Berkeley.EDU (128.32.136.23)  39 ms  40 ms  39 ms
 4  ccn-nerif22.Berkeley.EDU (128.32.168.22)  39 ms  39 ms  39 ms
 5  128.32.197.4 (128.32.197.4)  40 ms  59 ms  59 ms
 6  131.119.2.5 (131.119.2.5)  59 ms  59 ms  59 ms
 7  129.140.70.13 (129.140.70.13)  99 ms  99 ms  80 ms
 8  129.140.71.6 (129.140.71.6)  139 ms  239 ms  319 ms
 9  129.140.81.7 (129.140.81.7)  220 ms  199 ms  199 ms
 10  nic.merit.edu (35.1.1.48)  239 ms  239 ms  239 ms
The above results indicate which gateways (1~9) are passed from the source 
address to the destination address. That is very useful to network analysis. 
[Router]tracert 18.26.0.115
traceroute to allspice.lcs.mit.edu (18.26.0.115), 30 hops max
 1  helios.ee.lbl.gov (128.3.112.1)  0 ms  0 ms  0 ms
 2  lilac-dmc.Berkeley.EDU (128.32.216.1)  19 ms  19 ms  19 ms
OperationCommand
Display the path from the source 
address to the destination 
addresstracert [ -a ip-address ] [ -f first_TTL ] 
[ -m max_TTL ] [ -p port ] [ -q nqueries ] 
[ -w timeout  ] host 
						

							Log Function89
 3  lilac-dmc.Berkeley.EDU (128.32.216.1)  39 ms  19 ms  19 ms
 4  ccngw-ner-cc.Berkeley.EDU (128.32.136.23)  19 ms  39 ms  39 ms
 5  ccn-nerif22.Berkeley.EDU (128.32.168.22)  20 ms  39 ms  39 ms
 6  128.32.197.4 (128.32.197.4)  59 ms  119 ms  39 ms
 7  131.119.2.5 (131.119.2.5)  59 ms  59 ms  39 ms
 8  129.140.70.13 (129.140.70.13)  80 ms  79 ms  99 ms
 9  129.140.71.6 (129.140.71.6)  139 ms  139 ms  159 ms
 10  129.140.81.7 (129.140.81.7)  199 ms  180 ms  300 ms
 11  129.140.72.17 (129.140.72.17)  300 ms  239 ms  239 ms
 12  * * *
 13  128.121.54.72 (128.121.54.72)  259 ms  499 ms  279 ms
 14  * * *
 15  * * *
 16  * * *
 17  * * *
 18  ALLSPICE.LCS.MIT.EDU (18.26.0.115)  339 ms  279 ms  279 ms
The above results indicate which gateways (1~17) are passed from the source host 
to the destination host, and which gateways are faulty (12, 14, 15, 16 and 17). 
Log FunctionThis section describes the various attributes that form the log function and how to 
configure on the router.
Syslog OverviewThe 3Com Router 1.x is configured with Syslog (log system). As an indispensable 
part of the 3Com Router 1.x, Syslog serves as the information junction of the 
3Com Router 1.x system software module. The log system is responsible for most 
of the information output and can perform detailed classification so as to filter 
information effectively. In combination with the 
debugging command, the system 
provides powerful support for the network administrator and development staff to 
monitor the network running state and diagnose the network faults. 
The Syslog of the 3Com Router 1.x features the following:
■Support log output in four directions, i.e. to the control console (Console), to 
the telnet terminal and the dumb terminal (Monitor), to the internal buffer 
(Buffer), and to the log host (Loghost).
■Log information is divided into eight levels according to the importance and 
filter based on the levels.
■Information is classified according to the source modules and filter based on 
the modules.
■Information can be output in Chinese or English.
Configure Syslog The configuration tasks of Syslog include:
■Set the direction of Syslog outputting log information 
■Set the Severity of log information
■Set the Filter of log information
■Turn on/off Syslog 
						

							90CHAPTER 6: DISPLAY AND DEBUGGING TOOLS
Set the direction of syslog outputting log information 
As described before, Syslog of the 3Com Router 1.x can output various log 
information in four directions: 
■Output log information to local control console via Console port
■Output log information to remote Telnet terminal or dumb terminal. This 
function is helpful to remote maintenance.
■Allocate proper router buffer to record log information. 
■By configuring the log host, log information is directly sent by Syslog to the log 
host and then saved as file for later view.
Please enter the following commands in system view.
Figure 38   Set the direction of syslog output log information
Here, Console and Monitor stand for default output directions.
The setting of output direction of the log information will be effective only if 
Syslog is turned on. 
The settings of the output log information in four directions are independent. The 
shutdown of an output in any direction will not affect the output in other 
directions.
When there are multiple telnet users or dumb terminal users simultaneously, 
various users share the same configuration parameters, which include the filtering 
setting based on the module, Chinese/English selection and severity threshold. 
When a user changes the values of these parameters, other user terminals will also 
be affected. At this time, the 
undo info-center monitor command can only turn 
off the log information output on the respective terminal. Therefore, to turn off 
the log information outputs of all telnet terminals and dumb terminals, please use 
the 
undo info-center monitor all command.
OperationCommand
Enable to output log information to local control 
consoleinfo-center console 
Disable to output log information to local control 
consoleundo info-center console
Enable to output log information to the terminalinfo-center monitor
Disable to output log information to the terminalundo info-center monitor
Enable to output log information to internal 
buffer info-center logbuffer
Disable to output log information to internal 
buffer undo info-center logbuffer
Define the size of internal buffer of output log 
informationinfo-center logbuffer size
Enable to output log information to the log hostinfo-center loghost
Disable to output log information to the log hostundo info-center loghost
Change the language mode (Chinese | English) of 
output log information info-center { console | monitor 
| logbuffer | loghost} { 
chinese | english } 
						

							Log Function91
Set Severity of Log Information
Syslog is divided into 8 levels according to the Severity (or priority) of the 
information. The rule to filter the log information according to the level is: the 
more urgent the log information is, the less severe it will be. The log information 
with severity higher than the set threshold is forbidden to be output. Only the log 
information with severity no higher than this threshold can be output. 
Perform the following task in system view.
Ta b l e 67   Enable to output log information with priority 
Sylog-defined severity is as follows:
Ta b l e 68   Syslog-defined severity
Set Filter of Log Information
In different output modes, the Filter can be set according to the source of log 
information. Only the log information complying with the Filter definition can be 
output.
Please enter the following commands in system view.
Ta b l e 69   Set filter of the log information
OperationCommand
Enable to output log information 
with priority to local control 
consoleinfo-center console {emergencies |alerts 
| critical | errors | warnings | 
notifications |informational |debugging}
Enable to output log information 
with priority to the terminalinfo-center monitor {emergencies |alerts 
| critical | errors | warnings | 
notifications |informational |debugging}
Enable to output log information 
with priority to internal bufferinfo-center logbuffer {emergencies 
|alerts | critical | errors | warnings | 
notifications |informational |debugging}
Enable to output log information 
with priority to the log hostinfo-center loghost  
{local|ip-address} {emergencies 
|alerts | critical | errors | warnings 
notifications |informational |debugging} 
Disable to output log information 
with priority to the log host.undo info-center { console | monitor | 
logbuffer | loghost}
SeverityDescriptions
Emergencies (0)Most severe/emergent fault
Alerts (1)Fault needs to be corrected immediately
Critical (2)Major fault
Errors (3)Noticeable but not major fault
Warnings (4)Cautions, it is possible there may be a fault 
Notifications (5) Information needs to pay attention to
Informational (6)Ordinary prompt information:
Debugging (7)Debugging information
OperationCommand
Set Filter of the control console info-center console filter module
Delete Filter of the control console undo info-center console filter 
						

							92CHAPTER 6: DISPLAY AND DEBUGGING TOOLS
Here, module stands for the module name. Only the log information related to a 
specified module can be filtered and output.
Turn on/turn off syslog
Please enter the following commands in system view.
Ta b l e 70   Turn on/turn off syslog
When Syslog is turned on, the performance of the system will be affected due to 
the information classification and output - especially when processing a large 
amount of information.
Display and Debug 
Syslog Perform the following configuration in all views.
Ta b l e 71   Display and debug syslog 
Typical Syslog 
Configuration ExampleConfiguration of Log Host
The configuration, implemented on SunOS 4.0, is almost the same as that 
performed on the Unix operating system of other manufacturers. 
1Execute following commands as root (supervisor)
#mkdir           /var/log/Router
#touch           /var/log/Router/config
#touch           /var/log/Router/security
2Edit the file /etc/syslog.conf as the root and add the following selector/action 
pairs.
#Router configuration messages
Local4.crit     /var/log/Router/config
When editing /etc/syslog.conf, note the following:
■The comments can only be in separate lines, beginning with character #. 
■The selector/action pairs must be separated with one Tab instead of a space.
■There must not be redundant spaces behind the file name. 
Set terminal Filterinfo-center monitor filter module
Delete terminal Filter undo info-center monitor filter
Set Filter of internal buffer info-center logbuffer filter module
Delete Filter of terminal buffer undo info-center logbuffer filter
Set Filter of log hostinfo-center loghost  { local 
| ip-address } filter module
Delete Filter of log host undo info-center loghost  { 
local | ip-address } filter
OperationCommand
Turn on Sysloginfo-center enable
Turn off Syslogundo info-center enable
OperationCommand
Display basic configuration information of Syslogdisplay info-center 
Display internal buffer information of Syslogdisplay info-center logbuffer 
						

							Log Function93
3When log files like config and security are created and /etc/syslog.conf file is 
modified, an HUP will be sent to the system daemon, Syslogd, by executing the 
following commands to make Syslogd re-read its configuration file 
/etc/syslog.conf. 
#ps -ae | grep syslogd
147
#kill -HUP 147
After the above operations, the router can record information in relevant log files. 
Configure Facility (facility name), Severity (severity threshold), Filter, and 
syslog.conf file to make a detailed classification of information, so as to filter the 
information.
Syslog Configuration Example
■Configure log information output of the control console.
1Turn on the log system 
[Router]info-center enable
2Configure the log information output of the control console, severity ranging 
between emergencies ~ debugging, and do not filter the log information output 
of PPP module.
[Router]info-center console
[Router]info-center console debugging
3Turn on debugging switch of PPP module. 
[Router]debug ppp all
■Configure the log host
The router-side configuration is as follows: 
1Turn on the log system 
[Router]info-center enable
2Use the host with IP address of 10.110.12.119 as the log host, set the severity 
threshold to informational, and choose English as the output language.
[Router]info-center loghost 10.110.12.119 language english
Please see “Configuration of log host” for the host-side configuration. 
						

							94CHAPTER 6: DISPLAY AND DEBUGGING TOOLS 
						

							7
POS TERMINAL ACCESS SERVICE
This chapter contains information on the following topics:
■POS Access Service Overview
■POS Access Service Configuration
■Display and Debug POS Access
■Typical Configuration Example of POS Access Service
POS Access Service 
OverviewPoint of Sale (POS) service is a type of smart card service widely used in shopping 
malls, gas stations, and so on. It links the POS terminal device at the commercial 
client (located in shopping mall or gas station) to the bank card accounting system 
to provide service.
The POS terminal device is widely used in the fields of commerce, finance, 
taxation, and so on. The earlier POS terminal devices worked independently in 
different banks, and they could not communicate with each other. The technology 
based on a shared POS access service has solved this problem and makes it 
possible to use different bank cards on the same POS.
The POS terminal is connected to the transaction center in two ways, namely, 
through dial-up POS access and POS network access.
Dial-up POS Access
In the dial-up POS access mode, after responding to the smart card, the POS 
terminal device will synchronously or asynchronously dial up with the built-in 
modem. Thus the POS terminal device at the commercial client accesses the bank 
card accounting system. In this case, the 3Com Router series providing POS access 
service can be placed at the commercial client side. The routers can be connected 
to the front end processor via the WAN. They can also be connected to the front 
end processor of the bank via the asynchronous interface or Ethernet port.
The following figure shows the networking diagram of the typical dial-up POS 
access.
Figure 39   Dial-up access when the POS access router is located at the FEP side 
POS  term inal
PSTN
Quidw ayFCM
UNIX FEP
Ethernet
interface Serial portRouter 
						

							96CHAPTER 7: POS TERMINAL ACCESS SERVICE
Figure 40   Dial-up access when the POS access router is located at the commercial client 
side
Due to the way POS access service usually operates, that is, low speed, high 
frequency and small traffic, it is rather sensitive to the dial-up connection time and 
requires the interface board for fast dial-up function. However, the present 
common PC modem cannot meet the response time requirements of 10 to 20 
seconds. At present, most POS equipment manufacturers use the special modem 
chip that supports fast connection to implement the function. The FCM card of 
the 3Com Router series is a fast handshaking modem specially designed for POS 
dial-up access service. 
POS Network Access
In the POS network access mode, the router providing POS access service is 
located at the commercial client end and helps all the POS terminals access the 
3Com Router series. The router located at the FEP side can be any router and 
communicates with the 3Com Router series through X.25, FR, DDN, ISDN or 
modem. 
The following figure shows the networking of typical POS network access.
Figure 41   Access mode when the POS access router located at the commercial client end
In the POS network access mode, 3Com Router series can be connected to the 
POS terminal in the following two ways:
■Directly connect the POS RS-232 connector with the asynchronous interface 
(including the asynchronous mode of the synchronous/asynchronous interface) 
of the 3Com Router series. If the distance between them exceeds 15 meters, it 
will be necessary to install a long-line-driver at each end of the connection line. 
The valid connection distance of a pair of passive long-line-drivers is about 
1200 meters. 
■Set up an RS-485 network with the POS terminal device and POS concentrator, 
then connect the RS-232 connector of the POS concentrator with the 
asynchronous interface of the 3Com Router series. The 3Com Router series 
communicate on the egress port in the same way as the first connection 
method. Access in this way can save the router interface source greatly. 
The advantages of POS network access are as follows:
POS terminal
FCM
Quidw ay
PSTN/
PBXPSTN/ISDN
X. 25/ FR/DDN
RouterUNIX FEP
POS terminal
POS terminalRouterRouter
Quidw ay
PSTN, ISDN
X. 25, F R , DDN
RS-232 RS-232
Serial
port
Ethernet
interface
Long line
driv e
UNIX FEPPOS1
RS-485
POS2
POS
c oncentratorPOSRouterRouter