3 Troubleshooting Functional Failures During Operation
69
3.8.4 Communication failures occurring when secure Wake-on-LAN is used
[OS-L2A]
If a failure occurs when secure Wake-on-LAN is used, isolate the cause of the problem
according to the failure analysis method described in the table below.
Internal DB for registering the terminal that sends the startup command: WOL
terminal DB
Internal DB for user authentication: WOL user DB
Table 3-27
Failure analysis method for secure Wake-on-LAN
No.
Items to check and commands
Action
1
Check whether the user
authentication page for secure
Wake-on-LAN appears on the
terminal.
If the user authentication page does not appear, go to No. 2.
If the user authentication page appears:
If user authentication is not possible, go to No. 3.
If user authentication is possible:
If
Not
available.
appears on the page used for selecting the
terminal and sending the startup command, go to No. 5.
If startup of the terminal cannot be confirmed after the startup
command is sent, go to No. 6.
2
Make sure the URL of the user
authentication page is correct.
If the URL of the user authentication page is not correct, use the
correct URL. For the IP address of the URL, use the IP address of
the VLAN used for secure Wake-on-LAN.
3
Use the
show
wol-authentication
user
operation command to check
whether user information is
registered.
If the user is not registered, use the
set
wol-authentication
user
operation command to register the user.
If the user ID is not correct, delete it with the
remove
wol-authentication
user
operation command, and then use
the
set
wol-authentication
user
operation command to
register the correct user ID.
After the change, use the
commit
wol-authentication
operation command to apply the information to the operation.
For other cases, go to No. 4.
4
Use the
show
wol
operation
command to check the number of
users who are using the secure
Wake-on-LAN functionality.
A maximum of 32 users can use the secure Wake-on-LAN
functionality concurrently. If the maximum number of users is
exceeded, this functionality cannot be used. Wait a while until the
processing of other users terminates.
5
Use the
show
wol-authentication
user
operation command with the target
user ID and
detail
option
specified to check the terminal
access permissions and the
terminal name.
If an asterisk (
*
) appears for the target user's entry:
The terminal name is not registered in the WOL terminal DB. Use
the
show
wol-device
name
operation command to check the
terminal name, and then use the
set
wol-authentication
permit
operation command to change the terminal name. After
the change, use the
commit
wol-authentication
operation
command to apply the information to the operation.
Summary of Contents for AX2500S
Page 1: ...AX2500S Troubleshooting Guide AX25S T001X 60...
Page 6: ......
Page 34: ...1 Overview 8...
Page 40: ...2 Troubleshooting Switch Failures 14...
Page 106: ...3 Troubleshooting Functional Failures During Operation 80 config...
Page 116: ...3 Troubleshooting Functional Failures During Operation 90...
Page 121: ...95 5 Line Testing 5 1 Testing a line...
Page 126: ...5 Line Testing 100...
Page 127: ...101 Appendix A Detailed Display Contents of the show tech support Command...