Common Network Faults

This section describes the common network faults.

A.1.1 Failure of WS to Connect with M2000 Server

I. Fault Description

The WS fails to connect with the M2000 Server, and M2000 Server cannot be pinged on the WS.

II. Fault Analysis

To locate the faults, check the M2000 Server, the terminal, and network cables.

z Checking the M2000 Server

To check the M2000 Server,

--Log in as root and execute the command "ifconfig -a" to check the setting of the IP address.

--Execute the command "ping 129.9.10.10" (suppose 129.9.10.10 is the IP address of the Server).

If the server can be pinged, it indicates the network adapter and the IP address of the M2000 are set correctly. Otherwise, check and reset the IP address of the M2000 Server.

z Checking the terminal

To check the terminal, --Select [Start/Run].

--Execute the command ping 129.9.200.51 (suppose 129.9.200.51 is the IP address of the terminal).

If the terminal can be pinged, it indicates the network adapter and the IP address of the terminal are set correctly. Otherwise, check the relevant settings of the network adapter and the IP address.

z Checking whether the LAN Switch between the terminal and the M2000 Server

works normally. Perform the following,

--Check indicators to see whether the connection among other workstations through the LAN Switch is normal.

--Replace the network cable between the workstation and the M2000 Server to remove the fault caused by the network cable.

A.1.2 Failure of WS in Far-end NMC to Connect with M2000 Server

I. Fault Description

The WS of the far-end network management center (NMC) fails to connect with the M2000 Server. The Ethernet 0 interface of the M2000 LAN router can be pinged at the far end, but the IP address of the M2000 server cannot be pinged.

II. Fault Analysis

The E0 interface of the M2000 LAN router can be pinged at the far end, which indicates that the far-end network and the near-end router are operating normally. The IP address of the M2000 Server cannot be pinged, which indicates that the gateway at the M2000 Server is not properly set. Add the gateway at the M2000 Server.

Suppose the IP address of the E0 interface of the router is 129.9.10.11, and perform the following:

1) Execute the following commands as root on the M2000 Server:

# route add default

# route add 129.9.0.0 129.9.10.11

2) Add the above commands to the file /etc/rc2.d/S97sybsvr when the connection is normal.

Note:

The purpose of adding the above commands is to add the gateway to the file /etc/rc2.d/S97sybsvr so that the gateway can be set automatically when the server restarts. Otherwise, you need to enter the above commands manually.

A.1.3 Failure to Log in to M2000 Server

I. Fault Description

The following command is executed on the WS of the far-end NMC.

$isql –Usa –Pserver1234 -Ssybwf

Note:

z U: Username. A user can specify a registration name.

z P: Password. A user can specify the current password for the SQL Server.

z S: Server. The name of the SQL Server connected to the WS is specified by a user.

It is failed to log in to the M2000 Server. The system prompts that the connection to the Client database fails. If the Sybase database is shut down and restarted, the connection is normal.

II. Fault Analysis

To locate the fault, proceed as follows:

1) Ping the IP address of the M2000 Server at the far end.

If the server can be pinged, it shows that the connection between the far end and the M2000 Server is normal.

2) Run $isql -Usa -Pserver1234 on the M2000 Server.

If the connection can be established normally, it shows that the Sybase database runs normally.

3) Shut down the Sybase database and restart it.

The Sybase Client at the far end is connected with the M2000 Server database through a virtual IP address. The self-start file is stored in the file /etc/rc2.d/S99dtlogin when the virtual IP address is set. When the server is started, the system invokes the file /etc.rc2.S97sybsvr to start the Sybase, and then the file

/etc/rc2.d/S99dtlogin to set the virtual IP address. Consequently, the system cannot identify the Client IP address used when the Sybase is started.

III. Troubleshooting

Set the relevant virtual IP in the file /etc/rc2.d/S99dtlogin before starting the Sybase. For instance, the file S97sybsvr can be set as follows (the first three lines are the settings of relevant virtual IP):

ifconfig hme0:1 inet 134.38.19.77 netmask 255.255.255.0 up route add default 129.9.200.31

route add 134.32.0.0 134.38.19.65 su - sybase -c "/install/startserver \ -f /install/RUN_sybserver \

-f /install/RUN_sybserver_back" sleep 20

A.1.4 Failure of BAM to Connect with WS

I. Fault Description

The WS fails to connect with the BAM. It fails to ping the IP address of BAM on the WS.

II. Fault Analysis

Generally, you must check the network adapter setting, network cable, and LAN Switch.

1) Check the relevant settings of the network adapter and the IP address.

Click [Start/RUN] on the BAM to execute the command "ping 129.9.200.7" (suppose 129.9.200.7 is the IP address of the BAM).

If the IP address can be pinged, it shows the settings of the BAM network adapter and the IP address are correct.

2) Check whether the LAN Switch that connects to the BAM is working normally. Check indicators to see whether the connection among other workstations through the LAN Switch is normal. Replace the network cable between the BAM and the LAN Switch to remove the fault caused by network cable.

a) Check whether the network adapter is normal in [Control

Panel/System/Network Adapter].

b) Select the network adapter attributes to check whether the network adapter resources conflict with each other and whether the interruption of network adapters conflicts with I/O address.

If there is a conflict, use the driver disk of the network adapter to run the installation program of the network adapter for diagnosis and modification.

For instance, for the 3COM network adapter,

a) Run 3c90xcfg.exe on the installation disk in the DOS mode and enter the VIEW menu to check the original settings.

b) Select the INSTALL menu to change the relevant settings or check the network adapter.

c) Save the changes and exit

d) Make the relevant settings in [Control Panel/Network] of Windows and install the relevant TCP/IP.