Problem
You still experience a failure in the transmission paths even after replacing the NIC.
Cause
NIC replacement may have disabled recognition of the physical adapters bundled together in the virtual adapters.
Action
Check the existence of adapters by following the procedure below, and then restore the transmission path.
Check that the adapters exist.
Check the physical adapter which has an error by using the dsphanet command.
If there is a physical adapter whose status is "FAIL":
Using the Properties of the Internet Protocol (TCP/IP), check whether any physical adapters where an error such as linkdown occurs exist. You should also check the network switches for errors.
> dsphanet
Name Status Adapters
+-------+--------+-------------------------------------------------------------+
sha0 Active Local Area Connection 1(ON), Local Area Connection 2(FAIL) |
If there is a physical adapter whose status is "OFF":
The adapter name might be changed after replacement of the physical adapter. Check that the physical adapter name after replacement is different from the name defined in GLS setting in the [Network Connections] window. In this case, go to step 2.
> dsphanet
Name Status Adapters
+-------+--------+-------------------------------------------------------------+
sha0 Active Local Area Connection 1(ON), Local Area Connection 2(OFF) |
Install the physical adapter after replacement into the GLS virtual adapter.
The subsequent steps are different between "Windows Server 2003 R2" and "Windows Server 2008 or later operating systems."
Deactivate the GLS virtual adapter.
Use the stphanet command.
> stphanet |
Change the physical adapter name after replacement to the physical adapter name before replacement.
Right-click the icon of the physical adapter after replacement displayed in the [Network Connections] window.
Click [Rename] and change the name to the physical adapter name before replacement (the physical adapter name in the "OFF" state, which is displayed by the dsphanet command).
Activate the GLS virtual adapter.
Use the strhanet command.
> strhanet |
Restart the system.
Check the status of GLS.
By using the dsphanet command, check that the virtual adapter is activated and the physical adapter is in "ON" or "STBY" state.
> dsphanet Name Status Adapters +-------+--------+-------------------------------------------------------------+ sha0 Active Local Area Connection 1(ON), Local Area Connection 2(STBY) |
Check that the ping monitoring is started.
Execute the dsphanet command with the -r option and check that the ping monitor status of all physical adapters in "ON" state is "O."
> dsphanet -r
[sha0]
Adapters Resources
+-------------------------------+---------------------------------------------+
Local Area Connection 1(ON) LINK(O)
PING(O)
192.168.2.10(O),192.168.2.20(O)
Local Area Connection 2(STBY) LINK(O)
PING(-)
192.168.2.10(-),192.168.2.20(-) |
Note
If you deactivate the virtual adapter by executing the stphanet command, the information such as IP addresses set to the virtual adapter is deleted. Therefore, if you do not use the adapter setting script provided with GLS, you need to set the virtual adapter again after reactivating the virtual adapter.
For information on deactivating virtual adapters, refer to "5.1.2 Activating and Deactivating Virtual Adapters."
For details on how to set an IP address for the virtual adapter, refer to "3.4.5 Follow-up Tasks: IP Address Settings."
When you connect via Remote Desktop Connection by using the IP address set in the GLS virtual adapter, the communications are disconnected by executing stphanet. Take actions above on the console.
Stop the ping monitor function.
Execute the off subcommand of the hanetpoll command.
> hanetpoll off |
Check that the ping monitor function is stopped.
Execute the dsphanet command with the -r option and check that the ping monitor status of all physical adapters is "-."
> dsphanet -r
[sha0]
Adapters Resources
+-------------------------------+---------------------------------------------+
Local Area Connection 1(ON) LINK(O)
PING(-)
192.168.2.10(-),192.168.2.20(-)
Local Area Connection 2(OFF) LINK(-)
PING(-)
192.168.2.10(-),192.168.2.20(-) |
Back up the information of the ping monitor target set for the physical adapter.
Check that there is no file storing the information of the ping monitor target.
> dir /b C:\glspollbackup File Not Found |
Save the information of the ping monitor target to a file.
Use the print subcommand of the hanetpoll command.
> hanetpoll print > C:\glspollbackup |
Delete the information of the ping monitor targets.
Delete the information of the ping monitor target set for the physical adapter in the "OFF" state, which was checked in step 1 of Action.
Use the delete subcommand of the hanetpoll command.
> hanetpoll delete -t "Local Area Connection 2" |
Check that no ping monitor targets are set.
Use the print subcommand of the hanetpoll command.
> hanetpoll print
Polling Status = OFF
interval(idle) = 3( 60) sec
times = 5 times
Adapter Fo Target ip
+-------------------------------+---+-----------------------------------------+
Local Area Connection 1 YES 192.168.2.10,192.168.2.20 |
Delete the information of the physical adapter in the "OFF" state, which was checked in step 1 of Action, from the definition data for the virtual adapter.
Use the delete subcommand of the hanetnic command.
> hanetnic delete -n sha0 -t "Local Area Connection 2" |
Check that the physical adapters in the "OFF" state are not bundled in the virtual adapter.
Execute the dsphanet command.
> dsphanet Name Status Adapters +-------+--------+-------------------------------------------------------------+ sha0 Active Local Area Connection 1(ON) |
Install the physical adapter after replacement into the definition data for virtual adapters.
Execute the add subcommand of the hanetnic command.
The physical adapter name after replacement is "Local Area Connection 3" in the following example:
> hanetnic add -n sha0 -t "Local Area Connection 3" |
Check that the physical adapter after replacement is bundled in the virtual adapter.
Use the dsphanet command.
> dsphanet Name Status Adapters +-------+--------+-------------------------------------------------------------+ sha0 Active Local Area Connection 1(ON),Local Area Connection 3(STBY) |
Set the ping monitor target for the installed physical adapter.
Display the contents of the file saved in step 2 and check the information of the ping monitor target to be set.
> type C:\glspollbackup
Polling Status = OFF
interval(idle) = 3( 60) sec
times = 5 times
Adapter Fo Target ip
+-------------------------------+---+---------------------------------------+
Local Area Connection 1 YES 192.168.2.10,192.168.2.20
Local Area Connection 2 YES 192.168.2.10,192.168.2.20 |
Set the ping monitor target for the physical adapter.
Use the create subcommand of the hanetpoll command.
> hanetpoll create -t "Local Area Connection 3" -p 192.168.2.10,192.168.2.20 |
Check that the information of the ping monitor targets is set.
Use the print subcommand of the hanetpoll command.
> hanetpoll print
Polling Status = OFF
interval(idle) = 3( 60) sec
times = 5 times
Adapter Fo Target ip
+-------------------------------+---+---------------------------------------+
Local Area Connection 1 YES 192.168.2.10,192.168.2.20
Local Area Connection 3 YES 192.168.2.10,192.168.2.20 |
Start the ping monitor function.
Use the on subcommand of the hanetpoll command.
> hanetpoll on |
Check that the ping monitor function is started.
Execute the dsphanet command with the -r option and check that the ping monitor status of all physical adapters in "ON" state is "O."
> dsphanet -r
[sha0]
Adapters Resources
+-------------------------------+---------------------------------------------+
Local Area Connection 1(ON) LINK(O)
PING(O)
192.168.2.10(O),192.168.2.20(O)
Local Area Connection 3(STBY) LINK(O)
PING(-)
192.168.2.10(-),192.168.2.20(-) |
