JPH0991224A - Lan diagnostic device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily diagnose whether the soft environments of the cables, the LAN devices, a personal computer and a network are normal or not by confirming the possibility of communication to be secured between its own device and another device that is connected to a LAN. SOLUTION: The terminating resistors 2 are connected to both ends of a coaxial cable 1, and plural transceivers 3 are attached at the middle points of the cable 1. One of both ends of an AUI cable 4 is connected to every transceiver 3, and the diagnostic devices 5 are attached to the other end of each of plural cables 4. The communication is confirmed between the different devices 5, so that the normality is confirmed for the cable 1, the attachment of transceivers 3 and the cable 4. At the same time, the T branch connectors 6 are attached at the middle points of the cable 1, and the devices 5 are connected to the connectors 6. In such a case, the transceivers 3 are contained in the devices 5.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a LAN diagnostic device used when diagnosing a LAN.

[0002]

2. Description of the Related Art At present, there are a cable tester, a TDR (time domain reflect meter), a protocol analyzer and the like as diagnostic equipment used for diagnosing a LAN. When diagnosing a LAN, stop the trunk line and make a physical judgment with a cable tester. In addition, it analyzes with a protocol analyzer. Both require considerable analysis capability and are time consuming to use. However, the cable tester and TDR are physical cable diagnostics, and if a failure occurs, a soft failure or LA
It is not possible to judge whether it is an N board failure. Further, although it is possible to perform software diagnosis and physical cable diagnosis using a protocol analyzer, it requires considerable analysis capability.

[0003]

SUMMARY OF THE INVENTION The present invention has been made in view of this point, and includes a user's cable and LA.
It is an object of the present invention to provide a LAN diagnostic device capable of easily diagnosing whether or not N software, personal computer, and network software environment are normal.

[0004]

FIG. 1 is a diagram illustrating the principle of the present invention. The LAN diagnostic device according to claim 1 is a LAN diagnostic device capable of communicating with another device connected to the LAN, and confirms whether communication can be performed between the device itself and another device connected to the LAN. It is characterized in that it is provided with a communication confirmation processing means that can be used.

According to a second aspect of the LAN diagnostic apparatus of the present invention, in the LAN diagnostic apparatus of the first aspect, the communication confirmation processing means requests a file transfer to another device, and the file sent from the other device and the own device. It has a file transfer test processing unit for comparing the file with the file and a loopback test processing unit for executing the loopback test.

[0006]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 2 is a diagram for explaining an operation confirmation test (part 1) of a cable and LAN equipment after completion of LAN construction. In the figure, 1 is a coaxial cable, 2 is a terminating resistor, 3 is a transceiver, 4 is an AUI cable (attachment unit interface cable), and 5 is a LAN diagnostic device.

FIG. 2A is a diagram showing a state after completion of LAN construction. A terminating resistor 2 is connected to both ends of the coaxial cable 1, a plurality of transceivers 3 are attached in the middle of the coaxial cable 1, and one end of an AUI cable is connected to each transceiver 3.

FIG. 2B is a diagram showing an example of the operation confirmation test. A diagnostic device 5 is attached to the other ends of the plurality of AUI cables 4 to confirm communication between different diagnostic devices 5. By such an operation confirmation test, it is possible to confirm the attachment of the coaxial cable 1, the transceiver 3, and the normality of the AUI cable 4.

FIG. 3 shows the cable and LA after the LAN construction is completed.
It is a figure explaining the operation confirmation test (the 2) of N equipment.
In the figure, 6 indicates a T-type branch connector. In this example, a T-type branch connector 6 is attached in the middle of the coaxial cable 1, and the diagnostic device 5 is connected to the T-type branch connector 6. By confirming the communication between the different diagnostic devices 5, it is possible to confirm the normality of the installation of the coaxial cable 1. In this case, the transceiver 3 is present in the diagnostic device 5.

FIG. 4 shows the cable and LA after the LAN construction is completed.
It is a figure explaining the operation confirmation test (the 3) of N equipment.
In the figure, 7 is a concentrator and 8 is a twisted pair cable. Concentrator 7 (not shown)
Is connected to the coaxial cable 1, one end of a plurality of twisted pair cables 8 is connected to the concentrator 7, and the diagnostic device 5 is connected to the other end of each twisted pair cable 8. By confirming the communication between the different diagnostic devices 5 connected to the concentrator 7, it is possible to confirm the normality of the concentrator 7 and the twisted pair cable 8.

FIG. 5 shows the cable and LA after the LAN construction is completed.
It is a figure explaining the operation check test (the 4) of N equipment.
In the figure, 9 is a router, 10 is a bridge, and 11 is a repeater. In the illustrated example, the first (leftmost) coaxial cable 1 is connected to the second coaxial cable 1 via the router 9, and the second coaxial cable 1
Is connected to the third coaxial cable 1 via the bridge 10, and the third coaxial cable 1 is connected to the fourth coaxial cable 1 via the repeater 11.

By confirming communication between the diagnostic device 5 connected to the first coaxial cable 1 and the diagnostic device 5 connected to the second coaxial cable 1, the normality of the router 9 and the cable laying can be confirmed. You can check. Also,
By performing communication confirmation between the diagnostic device 5 connected to the second coaxial cable 1 and the diagnostic device 5 connected to the fourth coaxial cable 1, the bridge 10 and the repeater 11
And the normality of cable laying can be confirmed.

FIG. 6 is a diagram showing an example of separation in the event of a failure. In the figure, A, B and C indicate user personal computers. When communication between PC A and PC B becomes unavailable during work, the following test is conducted.
First, replace the personal computer of A with the diagnostic device, and
Test with your computer. If this test is OK, it is determined that there is a problem with A's personal computer. If this test is NG, the C personal computer is replaced with another diagnostic device, and a test is performed between the diagnostic device and the other diagnostic device. If this test is OK, it is determined that there is a problem with the C personal computer. If this test is NG, it can be seen that at least PCs A and C have no problem.

FIG. 7 is a diagram showing an example of the configuration of the diagnostic device.
In the figure, 12 is a CPU, 13 is a memory, 14 is a disk, 15 is a LAN board, and 16 is a keyboard. FIG. 7A shows the hardware configuration of the LAN diagnostic device 5. The hardware configuration of the LAN diagnostic device is the same as that of the personal computer. The diagnostic device is portable.

FIG. 7B is a diagram showing the software configuration of the LAN diagnostic device. The LAN diagnostic device is an application program, Windows, as software.
s, NetWare 3.11J (or 3.12)
J), NetWare Lite, PCTCP and M
It has S-DOS. The present invention resides in an application program. Windows and MS-
DOS constitutes an OS (operating system), and NetWare 3.11J (or 3.12)
J), NetWare Lite, PCTCP, etc. constitute a network OS. In addition, Windows
And MS-DOS are trademarks of Microsoft Corporation, Ne
tWare3.11J and NetWare3.12J and N
etWareLITE is a trademark of Novell, Inc., PCT
CP is a trademark of Allied Telesis.

FIG. 8 is a diagram showing an example of a protocol stack. The protocol is layered into an application layer, a presentation layer, a session layer, a transport layer, a network layer, a data link layer, and a physical layer.

FIG. 9A is a diagram showing an example of the test. For example, in a test using TCP / IP, a transfer test and a compare check are performed between diagnostic devices by using a file transfer by FTP (File Transfer Protocol) located in the upper layer, and communication confirmation is performed. The diagnostic device that requested the file transfer compares and checks its own file A and the file A transferred from the other diagnostic device. FIG. 9B is a diagram showing another example of the test. In another test using TCP / IP, a loopback test is performed using a ping command (existing command) located in the upper layer. Similar test to NetWa
re. Perform on IPX.

FIG. 10 is a list of screens of the LAN diagnostic device. LAN diagnostic tool (LAN
When the diagnostic program) is started, the test selection menu screen is displayed. Figure 11 shows the test selection menu screen.
Is shown in The test selection menu screen is TCP / IP
This is for selecting one of the test, NetWare test, and F6680 emulator.

Display the TCP / IP test menu. Display the NetWare test menu. Start the F6680 emulator. Display the selected test item or start the F6680 emulator. Exit the LAN diagnostic tool.

FIG. 12 shows the TCP / IP test menu screen. TCP from the test selection menu screen
When / IP is selected, the TCP / IP test menu screen is displayed. On this TCP / IP test menu screen, each test item of the TCP / IP test is selected.

Start TCP / IP setup. Trigger a wrap test using the ping protocol. Start the file transfer test using FTP. Launch the selected TCP / IP test item or setup. Return to the test selection menu.

FIG. 13 is a diagram showing a NetWare test screen. When NetWare is selected from the test selection menu, the NetWare test menu screen is displayed. From the NetWare test menu screen, select each test item of the NetWare test.

Launch the NetWare setup. Select the file copy test with NetWare Lite. Launch the test to log in to the NetWare file server. Start the connection status check (comcheck). Start the file server information (slist). Launch the selected NetWare test item or setup. Return to the test selection menu.

FIG. 14 is a diagram showing a TCP / IP setup screen. In the TCP / IP setup process, the IP address, host name, and subnet mask of the own station are selected or entered on the screen, and PCTCP. Store in INI file. PCTCP. What is an INI file?
This file stores the host name, IP address, and subnet mask of its own station. The own station's IP address, host name, and subnet mask are set with the acquired IP address for MD (for diagnostic device). It is also possible to set by arbitrary input. It is also possible to set partner station information.

The TCP / IP setup screen will be described. Displays the host name for the diagnostic device. Displays the diagnostic device IP address. "Host" is displayed in place of the host name and IP address of the information set as the host. Enter the subnet mask assigned to your station.
The default display is performed according to the selected IP address. The IP address and host name acquired for MD are displayed. Switches between the arbitrary input mode and the default mode. TCP / I without storing the set contents in a file
P Setup ends. The set contents are stored in the file and the TCP / IP setup is completed.

When the cancel end is selected, the set contents are invalidated, and the setup process is ended without executing.
When storage end is selected, a start message is displayed to display the IP address, host name, subnet mask to be set and confirmation is possible (cancellation is possible). PCTCP. IN
Update I-file, exit TCP / IP setup and display TCP / IP test menu.

FIG. 15 is a diagram showing a loopback test screen. In the loopback test process, a looping test is performed by using a ping protocol and using several portable PC systems (synonymous with a diagnostic device). It is also possible to perform a loopback test with a UNIX machine.

The loopback test screen will be described. Display the destination host name. Displays the return IP address. The progress of processing is displayed as "processing in progress" or "processing completed". In addition, "unprocessed" is displayed in a place where the loopback is not executed. Display the number of loopback transfers (count up every 10 times). Displays the number of error packets (updates the contents every 10 transfer times.) Displays "Own station" at the location of the currently set IP address and host name of the own station. The transfer data length can be set from 18 to 1472. Enter the transfer count. In case of arbitrary input, enter a multiple of 10. Execute the loopback test (issue the ping command). Finish the loopback test and display the TCP / IP test menu.

The test process will be described. (1) Input the terminal for which you want to execute the loopback test from the contents displayed on the screen or the input contents. (2) Enter the transfer data length. (Abends if the transfer data length is out of range.) (3) Enter the transfer count. Between 10 and 9990, 10
Enter a multiple of. (4) After setting each item, press the execute key to start the loopback test. (The start message is displayed and the loopback test can be canceled.) (5) Pass the parameters to the batch file and switch to the DOS screen. (The screen is switched back and forth 10 times each.) (6) "Processing" is displayed on the screen as the processing progress until the specified transfer count is reached, and the transfer count and error packet count are displayed (1 return destination) Display each one). When the looping back for the number of transfers is completed, "Processing completed" is displayed, and the number of transfers and the total number of error packets are displayed.

FIG. 16 is a diagram showing a file transfer test screen. The file transfer test uses FTP to
A file transfer test is performed by several MD terminals (synonymous with a diagnostic device). (1) Display the host names and IP addresses registered in the file on the screen (up to 8). (2) Select the transfer destination from the displayed transfer destinations. (3) Select the transfer mode, enter the transfer count, and perform the file transfer test.

The file transfer screen will be described. Displays the transfer destination host name. The transfer destination IP address is displayed. Display the login name corresponding to the forwarding destination. Display the results of the file transfer test. "Host" is displayed at the location of the host name and IP address of the currently set station. Enter the number of file transfers. Select either ASCII or binary as the transfer mode for file transfer. Execute a file transfer test (issue an FTP command). The file transfer test is terminated and the TCP / IP test menu is displayed.

The test process will be described. (1) From the transfer destinations displayed on the screen, select the terminal you want to perform the file transfer test (multiple). (2) Enter the number of transfers. (3) Select either ASCII or binary as the transfer mode. (4) After setting each item, press the execute key to start the file transfer test. (5) Pass parameters to the batch file and switch to the DOS screen. (6) During the file transfer test, "Processing" is displayed at the location of the execution result on the screen. (7) When the file transfer for the number of transfers is completed, the execution result message is displayed in the execution result on the screen.

The NetWare setup will be described. The processing contents of NetWare setup are as follows. (1) Set up the environment to be used in NetWare Lite. (2) Windows version of Ne using pif file
Start up tWare Lite. (3) Make each setting on the displayed screen.

Execution contents of NetWare setup are as follows. (1) When this process is selected from the NetWare test menu, the NetWare Lite screen is displayed. (2) Enter the user name and password to log in. (3) After logging in, make each setting. (4) After completing each setting, log out, and then NetWare L
terminate ite. (5) After NetWare Lite ends, NetW
Return to are test menu.

FIG. 17 is a diagram showing a file transfer test screen. The processing contents of the file transfer test will be described. In the file transfer test, NetWare Lit
Perform a file transfer test on the MD terminal using e. (1) Display the server name, user name, and password registered in the file (up to 6). (2) From the displayed transfer destinations, select your station and the transfer destination station. (3) Execute the file transfer test (only in the mode of copying to the local station).

The file transfer test screen will be described. Select the server name, user name, and password to set as your own station. Select the transfer destination for file transfer (s). Displays the server name for MD. The user name for MD is displayed. Display the password for MD. Display the execution result of the file transfer test. Enter the number of times to transfer the file. Perform a file transfer test. The file transfer test is terminated and the NetWare test menu is displayed.

The test process will be described. In this test process, the test across the router cannot be executed. (1) Select the server name, user name, and password name set as your own station. (2) Select the transfer destination station to execute the file transfer test. (3) Enter the number of transfers. (4) After setting each item, press the execute key to start the file transfer test (a start message is displayed and the file transfer test can be canceled). (5) Start NetWare Lite and log in automatically with your user name. (6) After logging in, pass the parameters to the batch file,
Switch to the DOS screen. (7) Performs drive mapping, file copy, and file compare in batch mode (file copy is performed for the specified number of transfers). (8) When all files have been transferred, log out and display the execution result message on the screen.

FIG. 18 is a diagram showing a log-in test screen. In the login test process, a test of logging in to the NetWare file server is performed. (1) Enter the server name, user name, and password to log in to the file server. (2) Log out manually.

The login / test screen will be described.
Note that this test cannot be executed if there is no NetWare file server on the network. Select the file server name to log in. Select from the list of file servers displayed. Enter the user name to log in. Enter the password corresponding to your login name. Select either 3.11J or 3.12J as the NetWare version. Perform a login test. Finish the login test and display the NetWare test menu.

FIG. 19 is a diagram showing an outline of the LAN diagnostic device,
20 is a diagram showing a process flow of the TCP / IP test execution unit, and FIG. 21 is a diagram showing a process flow of the NetWare test execution unit. When the TCP / IP test menu is selected in the test selection menu of FIG.
When the P / IP test execution unit is activated and the NetWare test menu is selected, the NetWare test execution unit is activated.

The TCP / IP test execution unit (see FIG. 20) displays the TCP / IP test menu screen of FIG. When the operator selects TCP / IP setup on the TCP / IP test menu screen and selects the execute button, the TCP / IP test execution unit displays TC in FIG.
Display the P / IP setup screen.

The operator sets the test environment on the TCP / IP setup screen shown in FIG. 14, and when finished, selects the end storage button on the TCP / IP setup screen. If the store end button is selected, TCP / IP
The test execution unit checks whether the test environment is OK. O
If it is not K, a message prompting the correction of the test environment is displayed on the TCP / IP setup screen, and if it is OK, the TCP / IP test menu screen of FIG. 12 is displayed.

When the operator selects the return test on the TCP / IP test menu screen of FIG. 12, TCP / IP
The IP test execution unit displays the loopback test screen of FIG. The operator sets the return partner, the number of transfers, the transfer data length, etc. on the return test screen and selects the execute button. Then, the TCP / IP test execution unit executes the test using the ping command and displays the processing result.

When the file transfer test is selected on the TCP / IP test menu screen of FIG. 12, TCP / I
The P test execution unit displays the file transfer test screen of FIG. The operator selects the own station and the other party on the file transfer test screen. Then, ft in MD of the partner station
Run pserver. That is, the program that sets the MD to be the server is executed. Next, the operator sets the transfer count, transfer mode, login name, etc. on the file transfer test screen, and selects the execute button. When the execute button is selected, the TCP / IP test execution unit checks whether the transfer mode is ASCII or binary.

When the transfer mode is ASCII, the TCP / IP test execution unit gets the ASCII file from the other station to the own station, and obtains the ASCII file and get of the own station.
Compare the ASCII files you have created and display the comparison and transfer results. This process is performed multiple times. In addition,
Each of the plurality of MDs, which is the own station or the partner station, has the same ASCII file.

When the transfer mode is binary, the TCP / IP test execution unit gets the binary file from the partner station to its own station, and obtains the binary file and get of the own station.
Compare the binary files you have created and display the comparison and transfer results. This process is performed multiple times. In addition,
Each of a plurality of MDs serving as its own station or a partner station has the same binary file.

When the operator selects the end button on the file transfer test screen, the TCP / IP test menu screen of FIG. 12 is displayed.

The NetWare test execution unit (see FIG. 21) displays the NetWare test menu screen of FIG. When the operator selects NetWare setup on the NetWare test menu screen and presses the execution button, the NetWare test execution unit is set to Ne.
Display the tWare setup screen.

The operator sets the test environment on the NetWare setup screen, and when finished, Net
Select the end storage button on the Ware setup screen. When the storage end button is selected, the NetWare test execution unit checks whether the test environment is OK. OK
If not, a message prompting correction of the test environment is displayed on the NetWare setup screen, and if OK, the NetWare test menu screen of FIG. 13 is displayed.

The operator selects the NetWare test shown in FIG.
When the file transfer test is selected on the menu screen and the execute button is selected, the file transfer test screen of FIG. 17 is displayed. The operator selects his / her station, the partner station, and the user name on the file transfer test screen of FIG. 17, and then selects the execute button. Then, the NetWare test execution unit copies the file of the partner station, compares the transfer data from the partner station with the file of the own station, and displays the comparison result. This process is performed multiple times. When the end button on the file transfer test screen shown in FIG. 17 is selected, the screen shown in FIG.
The NetWare test menu screen of No. 3 is displayed. It should be noted that each of the plurality of MDs serving as the own station or the partner station has the same file.

The operator selects the NetWare test shown in FIG.
When the login test is selected on the menu screen and the execute button is selected, the login test screen of FIG. 18 is displayed. The operator selects the server name from the file server information on the login test screen of FIG. 18, inputs the user name and password, selects the NetWare version, and selects the execute button. Then Net
The ware test execution unit performs a login test according to the selected version and displays the result. When the end button on the login test screen of FIG. 18 is selected,
The NetWare test menu screen of FIG. 13 is displayed. In addition, netx exe is NetWare 3.1.
1J shell, vlm exe is NetWare
It is a 3.12J shell.

The F6680 emulator will be described. When the F6680 emulator is started up, it is necessary to make settings on the host side. (1) WSMGRSYS.NET in the WSMGR directory. E
Execute XE to start the F6680 emulator. (2) Display the test selection menu after SIGN OFF.

[0053]

As is apparent from the above description, by using the LAN diagnostic apparatus of the present invention, it is possible to isolate the faults of the LAN trunk line and the LAN equipment by a simple operation even during work.

[Brief description of drawings]

FIG. 1 is a diagram illustrating the principle of the present invention.

FIG. 2 is a diagram for explaining a cable and LAN device operation confirmation test (part 1) after LAN construction is completed.

FIG. 3 is a diagram for explaining a cable and LAN device operation confirmation test (part 2) after completion of LAN construction.

FIG. 4 is a diagram for explaining an operation confirmation test (part 3) of cables and LAN devices after completion of LAN construction.

FIG. 5 is a diagram for explaining an operation confirmation test (No. 4) of cables and LAN devices after LAN construction is completed.

FIG. 6 is a diagram for explaining an example of isolation when a failure occurs.

FIG. 7 is a diagram illustrating a configuration example of a diagnostic device.

FIG. 8 is a diagram showing an example of a protocol stack.

FIG. 9 is a diagram showing an example of a test.

FIG. 10 is a screen list view of the LAN diagnostic device.

FIG. 11 is a diagram showing a test selection menu screen.

FIG. 12 is a diagram showing a TCP / IP test menu screen.

FIG. 13 is a diagram showing a NetWare test screen.

FIG. 14 is a diagram showing a TCP / IP setup screen.

FIG. 15 is a diagram showing a loopback test screen.

FIG. 16 is a diagram showing a file transfer test screen.

FIG. 17 is a diagram showing a file transfer test screen.

FIG. 18 is a diagram showing a login test screen.

FIG. 19 is a diagram showing an outline of LAN diagnosis processing of the present invention.

FIG. 20 is a diagram showing a processing flow of a TCP / IP test execution unit.

FIG. 21 is a diagram showing a processing flow of a NetWare test execution unit.

[Explanation of symbols]

 1 coaxial cable 2 terminating resistor 3 transceiver 4 AUI cable 5 LAN diagnostic device 6 T-type branch connector 7 concentrator 8 twisted pair cable 9 router 10 bridge 11 repeater 12 CPU 13 memory 14 disk 15 LAN board 16 keyboard

Claims (2)

[Claims] 1. A LAN diagnostic device capable of communicating with another device connected to a LAN, and a communication confirmation process capable of confirming whether communication can be performed between the device itself and another device connected to the LAN. A LAN diagnostic device comprising means. 2. A file transfer test processing unit for requesting a file transfer to another device and comparing a file sent from the other device with a file of the own device, and a loopback test. The LAN diagnostic device according to claim 1, further comprising a loopback test processing unit that executes the test.