HP Web Jetadmin Software Instrukcja Użytkownika Pobierz pdf (Strona 15)

APPENDIX A—TROUBLESHOOTING DISCOVERY

Discovery troubleshooting can seem a daunting task. Most of the time, troubleshooting

network-connected devices can be broken down into one question: is SNMP communication possible?

Here are some helpful tips for these possible scenarios:

“Quick Device Discovery finds one device at a time, but I can’t find a lot of devices with other

discovery settings.”

 The IP ranges may be too large, causing discovery to run too long and never search the part of

the network where devices exist. Try using a small range where devices are known to exist.

 IP broadcasts may be blocked. Try using another method such as IP range or Specified addresses.

 SLP traffic may be blocked. Try using another method such as IP range or Specified addresses.

 Check the local firewall, which may be blocking traffic on incoming or outgoing ports.

“I can’t find the device through Quick Device Discovery, nor through any other means in HP Web

Jetadmin. HP Embedded Web Server (EWS) works, telnet works, ping works.”

 The device’s SNMP stack may be disabled. Open the device’s HP EWS interface, select Network,

and look at the SNMP settings. The Disable SNMPv1/v2 option will keep HP Web Jetadmin from

discovering the device.

 The device may have had the “public” Get community name disabled. Learn the community name

for that device and use HP Web Jetadmin global credentials to configure well-known community

names.

“HP Web Jetadmin can only discover devices on the local network. Any devices on remote networks

cannot be discovered.”

 Routers may be blocking SNMP queries. Work with network administration teams to resolve this

issue.

“I’ve tried everything and cannot discover the device with HP Web Jetadmin.”

 Check the Blocked Devices list under Tools > Options > Device Management Discovery. If the

device address exists in this list, HP Web Jetadmin will never find it.

“PC-connected device discovery does not find devices.”

 Make sure the HP SNMP Proxy Agent is installed on the remote hosts and that port 161 is not

being blocked by a firewall. Make sure the WMI service is started on the remote hosts and that

local administrative credentials are being used in discovery settings. This discovery is best

planned in coordination with workstation and server administrative teams.

“HP FutureSmart devices do not display correct features.”

 Beginning in Web Jetadmin 10.3 SR4, Universal Plug-ins (UPI) are used to define which features

are displayed for recent FutureSmart devices. For UPI device resolution during discovery, Web

Jetadmin performs Web Service discovery for Enterprise devices to determine if the device is and

enterprise device and supports Web Service communication. Based on those responses, Web

Jetadmin selects the HP Enterprise UPI to manage the device using the Web Service protocol. If

the WS* discovery option under EWS is disabled for the device, it will fail the UPI resolution and

will fall on the SNMP generic plug-in instead of UPI. Generic support will only display a fraction

of the features that should be displayed for a FutureSmart device. In order to ensure FutureSmart

devices are supported correctly, make sure the WS* discovery option under EWS is enabled for

the device

1 2 ... 10 11 12 13 14 15 16 17 18 19 20 21 22

Brak uwag

HP Web Jetadmin Software Instrukcja Użytkownika Strona 15