whitepaper Table of Contents:

Transcription

1 whitepaper Table of Contents: Discovering Devices Using HP Web Jetadmin 10.0 Overview... 2 Part 1 How Discovery Works... 2 Discovery Settings... 3 Network Device Discovery vs. PC Connected Discovery... 3 Network Discvoery Specifics... 3 PC Discovery Specifics... 3 Using Credentials with Discovery... 4 PC-Connected Device Discovery Using WMI... 4 Network Device Discovery on Devices Using SNMP Get Community Names... 5 Network Device Discovery on SNMPv3 Devices... 5 Discovery Progress Display... 5 Discovery History... 6 Scheduling Discovery... 6 Discovery Templates... 7 Last Communication and Last Discovery Columns... 7 Device Quick Monitor Task Module... 7 Device Blocking... 7 Part 2 - Discovery Methods... 8 Quick Device Discovery... 8 SLP (Service Location Protocol) Multicast Discovery... 8 IP Broadcast Discovery... 9 IP Range Discovery... 9 Specified Address Discovery Active Directory Discovery Domain Discovery Using the Customize Feature Discover and Synchronize Other Web Jetadmin Servers Appendices Appendix A Troubleshooting Discovery...14 Appendix B Discovery Traffic Appendix C Setting Realistic IP Ranges Appendix D SNMP Proxy Agent Appendix E Maintaining Accurate Address Information Appendix F Global Discovery Settings Page 1

2 Overview Discovery features enable HP Web Jetadmin 10.0 to find both network-connected and PC-connected printers and multi-function peripherals (MFPs) and then add them to the HP Web Jetadmin 10.0 All Devices list. In many cases, the administrator may have information about the network that can be used in HP Web Jetadmin 10.0 discovery settings. Some discovery features enable the administrator to search for devices without the benefit of networking details. A powerful discovery engine exists within HP Web Jetadmin 10.0 enabling administrators to locate most devices on both small and large networks. Web Jetadmin 10.0 now includes a new discovery for printers located in Active Directories. Scheduling and discovery templates allow administrators to tailor HP Web Jetadmin 10.0 features to any topology or geographically deployed printer fleet. New in HP Web Jetadmin 10.0 Discovery Integrated PC-connected Device Discovery IP Range Import/Export Discovery Templates Active Directory Discovery Live Discovery Progress and Discovery History IP Range Calculator Device Blocking Credentials Settings Differences from Web Jetadmin 8.x and Previous Versions HP Web Jetadmin 10.0 has been created without several discovery features and options used in previous versions of the software. Simplification, ease of use and newer, more valuable features are reasons for this re-design. No IPX protocol support No IPX or Netware related discovery No BootP or DHCP listener discovery No BootP server No Arp discovery No RDA (Remote Discovery Agent) Part 1 How Discovery Works Discovery is a two-part process. HP Web Jetadmin 10.0 discovery always begins by scanning the network to find active nodes. Active nodes are any networked device that will respond to the discovery method used by HP Web Jetadmin Once the node discovery portion of the discovery is complete, HP Web Jetadmin 10.0 begins a resolution process to qualify either PC-connected devices or network-connected devices. Here is a look at a typical discovery sequence: Start Type: PC-connected device OR network-connected device Node Discovery First method Scan: execute scan based on method settings Second method scan: execute scan based on method settings more method scans end node discovery Node Resolve Query all discovered nodes to discern PC connected or network devices Add resolved nodes to All Devices End Page 2

3 Discovery Settings Figure 1 shows the Device Discovery wizard s Specify discovery options pane which is used to initialize discovery settings. Launch the Device Discovery wizard by right-clicking the Discovery node in the HP Web Jetadmin 10.0 navigation tree. Use template, Specify credentials for this discovery and Schedule discovery are all discovery options that are covered in the following sections of this document. To begin a discovery, choose either Network devices or PC connected devices. Then choose from the various methods of discovery available for the discovery type selected. Multiple methods can be chosen and the following options within the wizard will vary depending on the methods selected. It is not possible to run both PC connected and Network device discovery at Figure 1 Device Discovery > Specify discovery options page the same time, but it is possible to schedule these types of discoveries to run concurrently. Choosing Next in this pane will advance the wizard to more settings needed to complete the discovery setup. Network Device Discovery vs. PC Connected Discovery Both PC connected and Network device discoveries are possible in HP Web Jetadmin Both of these discoveries will result in devices added to the All Devices list. Network devices, when discovered, are manageable from within HP Web Jetadmin 10.0 software. That is, the devices can have settings remotely altered, troubleshooting details can be obtained, and many device specifics can be collected and stored by HP Web Jetadmin 10.0 reports feature. PC-connected devices are less manageable due to the restrictive nature of the connection to the computing system hosting them. Network Discvoery Specifics SNMP (simple network management protocol) is used as the primary communication through which network connected devices are found and qualified before being added to the All Devices list. HP Web Jetadmin 10.0 uses a combination of standard and proprietary MIB (management information base) objects to not only discover but manage network devices. In fact, HP Web Jetadmin 10.0 is capable of discovering non-hp devices through the standard MIB; manageability will vary depending on the manufacture and model of the device). PC Discovery Specifics PC-connected devices are found by HP Web Jetadmin 10.0 by first discovering the Windows host and then by interrogating that host to find devices connected through the LPT or USB port. Once HP Web Jetadmin 10.0 has finished the first or node portion of the discovery, it will use either SNMP or WMI (Windows Management Instrumentation) to discover devices. In the case of SNMP, the HP SNMP Proxy Agent will have been deployed onto the Windows hosts (discussed in detail later in this document). In the case of WMI, HP Web Jetadmin 10.0 will have been given Windows credentials (required) that provide local administrator access to the Windows hosts being interrogated. If a PC-connected device has been discovered with the HP SNMP Proxy Agent, HP Web Jetadmin 10.0 will collect a limited set of information from the device and support a few management features such as Status, Troubleshooting and Reporting. In the case where the PC-connected device has been Page 3

4 discovered via WMI, only limited device model information will appear in the All Devices list. Again, administrative credentials are required to discover PC-connected devices using WMI. It is important to note how HP Web Jetadmin 10.0 performs the second portion or node resolution in PC Connected Discovery. Each Windows host discovered is then queried first using SNMP, if a response is encountered, special printer queries are used to discover a device on the LPT or USB port. If the SNMP Proxy Agent and other requirements are met, a device connected to that host should be discovered. More will be said about SNMP Proxy Agent later in this document. If the SNMP discovery is not successful and if the user added Windows credentials to the Discovery settings, a WMI query will be made to determine if a plug and play device is installed on any system ports. If a Windows plug and play printer is installed and active on the host, the device should be discovered and added to the HP Web Jetadmin all devices list. The table below shows each of the PC Connected Discovery methods and the primary and secondary protocols used in discovery. PC-Connected Discovery Method Primary Protocol Secondary Protocol IP Broadcast SNMP* WMI** IP Range SNMP* WMI** Specified Devices SNMP* WMI** Active Directory SNMP* WMI** Domain SNMP* WMI** *SNMP Proxy Agent is required as a deployed service on remote Windows hosts **Local administrator credentials required. Using Credentials with Discovery Figure 1 (earlier) shows the Specify discovery options pane where, in the lower left, the Specify Credentials for this discovery can be located. Place a check in this box any time credentials are needed as part of a HP Web Jetadmin 10.0 discovery. Credentials are needed when: a. PC-connected device discovery is being performed using WMI, or b. Network device discovery is being performed on devices with SNMP Get community name, or c. Network connected device discovery is being performed on SNMPv3 devices. All three of these conditions are outlined here. NOTE: Specify Credentials interface follows Discovery methods settings (covered later in this document) in the Device Discovery wizard. PC-Connected Device Discovery Using WMI PC-connected device discovery via WMI will take place only when an SNMP proxy agent cannot be found on the Windows host and when the user supplied Windows credentials as part of Discovery settings. Figure 2 is the pane for supplying Windows credentials. These credentials should allow local administrator access to the hosts on which PC connected device discovery is desired. Check Windows Credential and add your User name, Password and Domain name to the Specify credentials pane when WMI discovery is desired. Figure 2 Discovery > Specify Credentials Page 4

5 Network Device Discovery on Devices Using SNMP Get Community Names If SNMP Get community names other than the default public are used, HP Web Jetadmin 10.0 must have awareness of the Get community name value. Devices with a value other than public in their Get community name will not respond and therefore will not be discovered. Figure 2 (earlier) shows two options for providing HP Web Jetadmin 10.0 with Get community name string values. Under SNMPv1 Get Community Name First, check Use and then add the appropriate string in Figure 3 Global Credentials > SNMPv1 Get Community Name the field provided. Global credentials can also be used to designate SNMP Get community names. Check Use global credentials; then add the appropriate value(s) into Tools > Options > Application Management > Credentials > SNMPv1 Get Community Name (Figure 3). Network Device Discovery on SNMPv3 Devices SNMPv3 devices can be discovered by HP Web Jetadmin 10.0 when SNMPv3 discovery has been enabled and when HP Web Jetadmin 10.0 contains valid SNMPv3 credentials. Once HP Web Jetadmin 10.0 has discovered these devices, the SNMPv3 credentials are placed into the Credential Store. Initial discovery of these devices can be completed by following these two steps: 1) Navigate to Tools > Options > Device Management > Discovery > General. Enable Discover SNMPv3 Devices and then click OK. 2) Navigate to Tools > Options > Application Management > Credentials > SNMPv3 Credentials. Add the appropriate credentials and then click OK. With these two items complete, HP Web Jetadmin 10.0 will detect and discover SNMPv3 devices. Discovery Progress Display Discovery results provides ongoing progress through both the node and node-resolve portion of a discovery. This can make it easy to determine which method is currently executing or whether node-discovery or node-resolve portions have begun execution. The Nodes found counter shows how many devices were found using various discovery methods. After the first portion of the discovery is complete, Nodes resolved and Devices found indicate device resolution. A counter showing devices new to this discovery is also included. The active discovery can be stopped at any time by using the Stop button or can be put into background tasks by using the Hide button. Any user can find out if a discovery is currently running by navigating to Devices > Active Tasks task module (found under Overview in the navigation tree). Device Discovery > Progress can be launched by selecting the View button from within this task module. Figure 4 Device Discovery Results Page 5

6 While Discovery is Running As stated in the last section, Device Discovery > Progress can be launched by selecting View from within the Active Tasks task module. In fact, any time a user chooses to invoke a Discovery while an active Discovery is running in the background, a small control appears that allows the user to View current discovery, Queue a discovery to start in turn, or Schedule a discovery (Figure 5). Any user logged into HP Web Jetadmin 10.0 has the ability to invoke any of these controls. Figure 5 Discovery in Progress Discovery History Discovery History can be viewed by selecting its node from the navigation tree beneath Discovery. This provides a way to analyze discovery effectiveness, who performed discovery, and which methods were used. The tool allows a user to view each discovery by date, identity that launched it, the time it took to complete and the result in devices found. By expanding a specific discovery, the user can view the methods that were used and determine how many devices were found per method. Figure 6 Discovery History Scheduling Discovery A flexible scheduler exists within HP Web Jetadmin 10.0 Device Discovery wizard and allows a wide variety of options (Figure 7). Unique device discovery schedules can be created that allow scanning different parts of the network on different days, times and recurrence levels. Also, PC connected devices can be found during the day when most people are logged onto the network while network devices can be found later in the evening. Use the Allow start time to occur between the specified hours of: control to limit discoveries from running outside of appropriate timeframes. This is especially helpful on systems where many scheduled tasks have been configured. Existing Discovery schedules can be viewed and edited by using one of several task modules: launch Scheduled Tasks from the Application Management > Overview workspace or Discovery > Scheduled Discoveries. Figure 7 Device Discovery > Specify schedule options pane Page 6

7 Discovery Templates Discovery templates are like other templates in HP Web Jetadmin They store pre-defined settings that can be retrieved at a later time. Both PC-connected printer discovery and network printer discovery settings can be stored in many uniquely named templates. Once a discovery template has been created, it can be launched or scheduled for launch through the Device Discovery wizard with the Use template option. Create, Edit, Remove, Launch, and View features are all available through the Device Management > Discovery > Templates. Last Communication and Last Discovery Columns Two columns in HP Web Jetadmin 10.0 allow the administrator to track the last discovery date and time as well as the last application-to-device communication date and time (Figure 8). These columns are useful for troubleshooting to determine weather a device exists on the network, has communication issues, and more. These also allow the administrator to track how current the device data is as it is being represented by the application interface. Figure 8 Last Communication/Discover Device Quick Monitor Task Module HP Web Jetadmin 10.0 allows discovery of a specific device to monitor its status from anywhere in the client application. The Quick Monitor task module can be enabled from the Task Module docking area or from within the Discover overview workspace (Figure 9). Enter the device's IP address in Device and then click Go, or- drag a device from any device list into the Quick Monitor task module. Note: Task modules are elements that can be activated from within most of the top level summary workspaces and from within the task Figure 9 Device Quick Monitor Task Module module docking area. Task modules quickly supply the user with instant information and sometimes offer action or controls into the specific feature. Device Blocking A list exists in Tools > Options > Device Management > Device Lists > Blocked Devices that will keep HP Web Jetadmin 10.0 from discovering a device. Sometimes, administrators may desire that a device not appear in Discoveries. This list can be manually edited or devices can be added by using right-click from the All Devices list. The Delete and Block option will place the device into this list where it will stay until manually removed. Page 7

8 Part 2 - Discovery Methods Now that we have looked at the Discovery features and workflows, we can circle back and talk about individual methods used to find nodes. Remember, node discovery is the first part of any discovery. Methods provided flexibility in tailoring discoveries to fit within a certain environment. Some administrators need to find all devices in an enterprise and may find that IP Ranges, when correctly configured, result in successful and efficient use of the application. Some administrators may only have a need to discover devices immediately near the HP Web Jetadmin 10.0 installation. These administrators might find that IP Broadcast in combination with SLP Multicast methods work best. In all cases, HP Web Jetadmin 10.0 discoveries require SNMP communication between the devices and the application. Most modern networks allow this protocol, which makes HP Web Jetadmin 10.0 a robust platform from which to launch device discovery. Quick Device Discovery Quick Device discovery is comparable to Quick Device Find in earlier versions of HP Web Jetadmin (Figure 10). Characteristics of Quick Device discoveries are: Discovers only one device at a time based on user supplied address Does not discover PC-connected devices Is not launched from the Device Discovery wizard Figure 10 Quick Device Discovery This feature is always visible in the Device Management view just beneath the navigation tree. Simply use IP hostname or IP address strings (ONLY) and select Go. The feature searches device addresses in the HP Web Jetadmin 10.0 database first then performs a network query. If a device is found at the address provided, it is added to the HP Web Jetadmin 10.0 All Devices list. This feature is different from Search or Advanced Search (found in device list tools) which parse all or selected strings within device lists. Quick Device Discovery only acts on address information SLP (Service Location Protocol) Multicast Discovery The SLP Multicast discovery requires minimal settings to launch and multicasts a query onto the network to find a specific device type. Characteristics of an SLP Multicast discovery are: Discovers only HP Jetdirect connected devices. Sends multicast packets to the HP Jetdirect specific multicast address: Packets contain a router hop-counter (IP time to live attribute) that is settable from within HP Web Jetadmin (default 4 hops). Packets expire when router hop-counter reaches zero. Fast discovery mechanism. Low traffic. In this case, SLP is used to find HP Jetdirect devices. This discovery mechanism finds HP Jetdirect devices on both local and remote subnets. It was implemented in early HP Web Jetadmin releases and is effective in finding devices both remote and local to the HP Web Jetadmin installation. It has a light footprint on the network. Page 8

9 IP Broadcast Discovery IP Broadcast discovery enables administrators to find devices when IP broadcast addressees are known. Characteristics of IP Broadcast discoveries are: Works on both PC-connected and Network devices. Sends SNMP queries over one or more IP broadcasts. Devices that reply are placed into nodeportion of discovery. Fast and thorough, especially on a local segment. Most modern networks block broadcast traffic. Settings are the same as network device. May not find PC connected devices without the SNMP Proxy Agent. Figure 11 Select IP broadcast address pane IP Broadcast discoveries send SNMP query packets in the form of IP broadcasts, to one or more IP network(s). One network-specific broadcast address exists for each IP subnet on an IP intranet and one all 1s broadcast can be used on any IP network (HP Web Jetadmin uses this as the default IP broadcast address). IP subnets are determined by the IP network number and the IP subnet mask. Administrators can calculate and enter any variety of IP Broadcast addresses into the Select IP broadcast address pane in the Device Discovery wizard (Figure 11). Calculators, available free on the Internet, are a great way to determine IP broadcast addresses. An all 1s IP broadcast address is used as the default. Broadcasting is typically blocked by routers due to traffic spike concerns. IP Range Discovery IP Range Discovery is probably the most powerful way to discover all or nearly all devices in an enterprise. The Select IP ranges interface is used to add, remove or edit IP range data (Figure 12). IP ranges can also be imported or exported from and to flat text files. A calculate feature is available that adds IP ranges based on the client host, server host or known IP address information. Large subnet protection is in force by default which will keep the application from spanning too many addresses unless absolutely necessary. Characteristics of IP Range discoveries are: Use in the discovery of both PC connected and network devices. IP ranges are simply two addresses that represent range begin and end points. Figure 12 Select IP ranges pane Multiple ranges cab be specified. Manually edit or import ranges from file. Descriptive tags help to identify ranges. Application sends 1 query to each address represented by the range. HP Web Jetadmin 10.0 pings the device ranges in bursts which limits the network footprint. Page 9

10 Calculator feature adds IP ranges based on: o Local client host o WJA server host o Device Can be very slow if not configured properly. Can draw security attention. IP Range Discovery is probably the most powerful way to discover all or nearly all devices in an enterprise. The Select IP ranges interface, shown in Figure 12 (above) is used to add, remove or edit IP range data. IP ranges can also be imported or exported from and to flat text files. A calculate feature is available that adds IP ranges based on the client host, server host or known IP address information. Large subnet protection is in force by default which will keep the application from spanning too many addresses unless absolutely necessary. Importing Ranges from a File: As stated earlier, many IP ranges can be imported via text files. In many cases, the administrator will work with hundreds and even thousands of IP ranges and have to manage the data in another application such as a word processor or spreadsheet. In these cases, a very simple file format can be used as the link between the administrator s favorite application and HP Web Jetadmin 10.0 IP Range Discovery. Here is a look at the file format used in importing (and exporting) IP Range data: =My Range =Your Range =Our Range =Their Range One range per line; begin and end addresses separated by a hyphen character; optional text description separated from the range data by an equal sign character. The file or the IP Range discovery feature has no known size limit. For more details on using the IP Range Discovery feature, see the section Setting Realistic IP Ranges under Other Discovery Details Specified Address Discovery Specified address discovery sends a query to each address entry listed within Discovery settings for this method. Characteristics of Specified address discovery are: Finds both PC connected and network devices. Based on user supplied addresses. IP address or hostnames are valid address forms. Fast and only hits addresses specified by the user. Accurate to the extent of base specified by the user. Addresses can be imported from text file. This discovery is powerful when the addresses of devices are known. It does require some maintenance as addresses change or when devices are added to or removed from the fleet. Device address types include IPv4 addresses, network resolvable IP Hostnames and network resolvable FQDNs. An address base can also be imported from a text file or exported to a text file for use in other applications or editors. Here is an example of a specified address file using the various types of address forms. Page 10

11 BP005a.yourco.com BP065 BP076.yourco.com Remember, all discoveries use the method, in this case Specified Address, to build a list of nodes which are later resolved into network or PC connected devices and placed in the HP Web Jetadmin 10.0 All Devices list. Active Directory Discovery HP Web Jetadmin 10.0 provides a new discovery feature that queries Microsoft Active Directory using an Active Directory starting point such as domain, OU or other Active Directory containers. Characteristics of an Active Directory discovery are: Finds both PC connected and networked devices. Requires a directory search start point (multiples possible). Searches within specified container or include all sub-containers. Allows filtering based on AD queue attributes Location and Description. Populates AD device attributes viewable in HP Web Jetadmin 10.0 filters and columns. HP Web Jetadmin 10.0 provides a new discovery feature that queries Microsoft Active Directory using an Active Directory starting point such as domain, OU or other Active Directory containers. Within HP Web Jetadmin settings, administrator navigates Active Directory starting point such as: LDAP://YourOrg.com/OU=US,OU=Printers... The administrator can choose to perform recursive queries meaning any sub-units below the specified path will be searched. Searching Current Level searches immediate child objects of the base object, excluding the base object. Searching All Levels searches the whole subtree, including the base object and all child objects. The administrator can also perform discovery on multiple Active Directory locations. And, the discovery can also be filtered on both location and description strings if these are published to the Active Directory. Figure 13 shows the Specify Active Directory options pane within the Device Discovery wizard. Active Directory and Network Device Figure 13 Specify Active Directory Options pane Discovery: The Active Directory discovery method scans the directory for shared Windows printers when it is used to find network connected devices. From the printer shares, the discovery is able to extract IP address information from the printer port name. One of two printer port names is supported in discovering devices using this method. These are: IP_<ip_addr> or <ip_addra>:<port> When either one of these names contains a valid IP address, a node discovery is Page 11

12 completed. If the port name does not match one of these two forms or if the IP address is not valid, the network device may not be discovered. Later, in the node resolve portion of discovery, these IP addresses are checked for valid devices which are added to the HP Web Jetadmin 10.0 All Devices list. Active Directory and PC Connected Device Discovery: The Active Directory discovery method for PC connected devices simply scans the directory for supported Windows hosts. When a qualified Windows host is found, its address detail is added to the node portion of discovery. Later, these nodes are queried to determine if the SNMP Proxy Agent is deployed on them or, in the case where Windows credentials were supplied, the discovery will attempt to find a qualified printer via a WMI query. Valid devices, if found, are placed in the HP Web Jetadmin 10 All devices list. Domain Discovery For PC Connected Discovery only Uses AD or non AD domain as a starting point Finds and uses Windows hosts to discover local printers Multiple domains can be specified Domain discovery method uses the Active Directory or Windows 2000 domain as a starting point to search for supported Windows hosts. All supported Windows hosts are placed into the node portion of the discovery and then queried for the SNMP Proxy Agent. If the proxy agent is not found on the host and if the user supplied Windows credentials, a WMI query is attempted. All discovered devices are placed into the HP Web Jetadmin 10.0 All Devices list. Using the Customize Feature Customize is found in most of the settings panes for each discovery method and is used to control a list of personalized favorites (Figure 14). Each user has the ability to select favorites from a global set of discovery settings, such as IP ranges, and then choose to display their favorites using the Favorites checkbox. This keeps them from having to see all discovery settings. Figure 14 Customize Discovery Settings Page 12

13 Discover and Synchronize Other Web Jetadmin Servers Discovery of other installations of HP Web Jetadmin 10.0 is launched in Application Management > Web Jetadmin Installations. Here, HP Web Jetadmin 10.0 instances are listed with controls for discovery, viewing, removing and even launching the remote instance. Discovery controls through a variety of methods allow finding instances on both local and remote subnets. Here are a few characteristics of HP Web Jetadmin 10.0 installation discovery: HP Web Jetadmin 10.0 can discover other instances of HP Web Jetadmin. Discovery is possible to versions as early as 6.5.xxxx. Three discovery features for finding other HP Web Jetadmin installations include WS Discovery, IP Broadcast, and IP Range. IP Range and IP Broadcast discoveries share stored settings data with other discovery features. HP Web Jetadmin applications are discovered via an always-on port 8000 UDP listener. HP Web Jetadmin instances can be launched directly from the discovery listing. The list can be modified by performing other discoveries or by manually removing instances. Once found, HP Web Jetadmin 10.0 installations are visible in the Web Jetadmin Installations workspace with a discovery progress display (Figure 15). Figure 15 Web Jetadmin Installations pane These installations are also viewable from the feature found in Tools > Data Synchronization from the HP Web Jetadmin 10.0 menu bar (Figure 16). This feature can be used to quick-discover individual HP Web Jetadmin installations and to invoke/schedule data synchronization from the discovered installation, to the HP Web Jetadmin 10.0 installation where the Synchronize feature is launched. Figure 15 Web Jetadmin Installations pane Synchronization activates a one way data Figure 16 Data Synchronization transfer from the discovered HP Web Jetadmin 10.0 installation to the HP Web Jetadmin 10.0 installation launching the feature. Many different data elements can be enabled as part of the data transfer. Serial number, port, model number, last discovered, last communication, HP Jetdirect model, IP hostname, IP address, and discovery date and time always transfer. This transfer is a one-time event that can be rescheduled. Page 13

14 Appendices 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 things to check when troubleshooting device discovery: 1. Can find one device through Quick Device Discovery but can t find lots of devices with other discovery settings. The IP Ranges might be too large so discovery may be running too long and never getting to the part of the network where devices exist. Try using a small range where devices are known to exist. IP Broadcasts are being blocked. Try using another method such as IP range or Specified Devices. SLP traffic is blocked. Try using another method such as IP range or Specified Devices. Check local Firewall, which may be blocking traffic on incoming or outgoing Ports. 2. Can t find the device through Quick Device Discovery. Can t find the device through any other means in HP Web Jetadmin EWS works, telnet works, ping works. The device s SNMP stack has been disabled. Look in the device s EWS interface and select Network and then look at the SNMP settings. Disable SNMPv1/v2 will keep HP Web Jetadmin 10.0 from discovering the device. The device might have had the public Get community name disabled. Learn the Get community name for that device and then use HP Web Jetadmin 10.0 global credentials to configure well known Get community names. 3. HP Web Jetadmin 10.0 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. 4. Have tried everything and cannot discover the device on my 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 10.0 will never find it. 5. PC Connected Device Discovery Does not Find Devices Make sure the SNMP Proxy Agent is installed on the remote hosts and that port 161 is not being blocked by a firewall. Make sure the WMI (Windows Management Instrumentation) service is stared 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. Page 14

15 Appendix B Discovery Traffic A range of discovery traffic taken from sample discoveries on an HP network. Note: traffic generated for each device discovered, all discovery settings at default values. SNMP query/response sequence vary depending on printer used in sample. Note: testing was performed on an HP internal network and may or may not reflect results observed on other networks. SLP Multicast network device SLP Multicast response = 2 packets, 768 bytes over 24.5Sec SNMP follow-up query-response = 6 packets, 1.9Kbytes over 60mSec IP Broadcast network device Each IP broadcast address = 3 SNMP packets, 255 bytes over 7Sec IP broadcast response = 3 SNMP packets, 468 bytes over 7Sec SNMP follow-up query-response = 34 packets, 5.4Kbytes over 109mSec IP Range network device ICMP Echo Request send & receive = 2 packets, 148bytes over 70ms Follow-up SNMP queries & responses from printer = 28 packets, 3.6Kbytes over 2.6Sec Specified Address network device SNMP queries & responses from printer = 38 packets, 6.1 Kbytes over 1.1 Sec Active Directory network device Follow-up SNMP queries & responses from printer = 34 packets, 4.2 Kbytes over 5 Sec IP Broadcast PC-connected device SNMP queries & responses from printer = 23 packets, 3.6 Kbytes over 27.5 Sec Page 15

16 Appendix C Setting Realistic IP Ranges IP Range discovery can perform to expectations when the range data has been correctly developed. It is very easy to configure ranges that are larger than needed and actually cause the discovery to take a long time and perhaps even yield little in the way of devices. For example, a class A range could easily be developed for the HP intranet but would literally take weeks to complete. For example, the class A range that represents HP s intranet is: This represents over 16 million address combinations. On most large networks, the majority of these addresses won t answer the HP Web Jetadmin 10.0 query and will cause timeouts to occur; these translate into very long discovery times. In reality, most other networks including HP s are divided up into subnets. Subnets can be used to describe a network IP addressing scheme and are sometimes referred to as IP maps. A subnet within a large network can be described with a network number and a subnet mask. A typical combination might look like this: Network number example: Subnet mask example: This is one subnet and has an IP range of through Up to 1,022 addresses are possible on this subnet. It may take HP Web Jetadmin 10.0 only about 10 minutes to discover devices on this network depending on the network, the number of devices on that network and the host on which HP Web Jetadmin 10.0 is installed. Note: IP address calculators are an easy way to analyze IP networks. Many free versions of IP calculators exist and can be obtained on the Internet. Setting ranges based on subnets or contiguous subnets We have discussed HP Web Jetadmin 10.0 IP Range discovery mechanism. We have also discussed how very large ranges can cause HP Web Jetadmin 10.0 discovery to take long periods of time to complete. We also discussed that many of today s IP networks are broken into smaller networks called subnets. These subnets reflect the actual portions of the network that are being used. These subnets, when put together into one list, represent an IP map. This type of a map can be obtained from an IT or Network Infrastructure team. It is also a good idea to work with these teams to discuss plans for implementing HP Web Jetadmin 10.0 discoveries. Hewlett-Packard strongly recommends that you discuss HP Web Jetadmin 10.0 discoveries with your information technology or network administration team. An example of IP range planning On our hypothetical network we have 20 subnets. All of these subnets use the same subnet mask of Here are the network numbers that represent our 20 subnets: , , , , , , , , , , , , , , , , , , , , , , , , , , From this information, we can formulate the following IP address ranges and import them into HP Web Jetadmin Page 16

17 We can take the formulation one step further and simplify things. Some of our IP ranges are contiguous. These contiguously addressed subnets are one after the other, in order, making it easy to combine them. The final result would look like this: We have reduced the number of IP ranges down to four. We can build this into a form that is easily imported into HP Web Jetadmin and also reflects descriptions. Here is an example of data that can be imported via a text file: =subnet range for western region =subnet range for central region =subnet range for branch office =subnet range for eastern region Of course, there would have been nothing wrong with leaving the 20 ranges as separate items. Consolidating ranges makes dealing with large quantities of data simpler but may not help when descriptions are needed for the purpose of cataloging ranges. IP Range Files import and export features As stated earlier, IP range data can be developed in other tools and imported through text files. In fact, HP Web Jetadmin 10.0 can export IP range data to text files. This makes it easier to deal with large numbers of IP ranges, manipulate complex data and archive data for use in multiple instances. Let s break down the file format for IP Range import/export: Characteristics of IP Range files: 1 range per line. Each IP address is separated by a hyphen character (-). Comment or description strings can be appended to the IP range by using a n equal character (=). Example of 1 IP range with a comment (where xxx represents an octet in the IP address): xxx.xxx.xxx.xxx-xxx.xxx.xxx.xxx=descriptive text string Page 17

18 Appendix D SNMP Proxy Agent SNMP Proxy Agent is a downloadable installer and is available at hp.com HP Web Jetadmin Software and Drivers downloads pages. This service, installed onto remote Windows hosts (workstations or servers), provides an SNMP proxy that facilitates discovery and communications of locally connected devices. This proxy used in conjunction with the workstation s SNMP service makes available: status, page count and many other details on devices connected via LPT or USB ports. SNMP Proxy Agent can be deployed onto remote hosts through any combination of desktop management applications or scripting methods. Important SNMP Proxy Agent details: A companion readme.txt file describes agent installation and other details..msi and.exe installer formats are available for download and can be run in silent mode to afford automated distribution through scripts or tools such as SMS. SNMP Proxy Agent discoveries support read-only device queries. NOTE: other HP Web Jetadmin 10.0 functionality such as alerting and configuration is not available at this time for these devices. Only one device per workstation is supported in discovery. Printers must have a DOT4 bi-di capable driver installed in order to be discovered. In most cases, the printer model name, engine page count, toner levels, serial number, and more are available. Many recent HP office-class devices support additional objects, while some of the personal printers may not support many objects at all. Required Intel Pentium or Celeron processor (Pentium II or higher recommended) 64 MB RAM (128 MB RAM or higher recommended) 10 MB available hard disk space Supported OS: Windows 2000 (SP 4) Windows XP (SP 2) Windows Server 2003 Enterprise Edition Required Operating System Settings and Components: Supported Printers: Administrative Access: Windows SNMP service must be installed and configured to allow queries from the WJA server. Community name should be set to public for read access Firewall settings should be appropriately modified to allow WJA to query the proxy agent (for example, UDP port 161 should be open for SNMP queries). The HP SNMP Proxy Agent supports a wide variety of HP printers as long as they are installed using a DOT4 bi-directional capable driver. Administrative rights on the remote Windows host are only required when installing the SNMP proxy agent. The agent remains open and administrative rights are not required for HP Web Jetadmin 10.0 to perform queries through this agent. Page 18

19 Appendix E Maintaining Accurate Address Information HP Web Jetadmin 10.0 has the ability to adjust IP addresses stored for each device. In many cases, IP addresses on devices will remain static and changes within the HP Web Jetadmin 10.0 all devices list won t be needed. In a few cases, device addresses may change due to device moves or when device addresses are assigned with DHCP. In these cases, HP Web Jetadmin 10.0 should be able to cope with the changes and quickly change its internal record of a device s IP address. HP Web Jetadmin will automatically change a devices IP address anytime it detects a change in that address. For instance, a device might have been configured with the IP address yesterday but today it has the IP address HP Web Jetadmin 10.0 will only realize changes when some communication has taken place with the new device address. IP Range discoveries may be performed from time to time if IP addresses are prone to changing. Page 19

20 Appendix F Global Discovery Settings Discovery Settings Discovery settings that exist under Tools, Options, Device Management, Discovery and generally affect discovery behavior and performance. These are typically set by administrators. Type of setting Detail Explanation General Number of routers to cross Value = decrementing router hop count time to live parameter on the SLP multicast packed used by HP Web Jetadmin discovery. Minimum = 1 Default = 4 Maximum = 15. Routers will drop the multicast packet when value reaches 0. Blocked Devices Listen for new devices Discover SNMPv3 Checkbox enables the passive discovery mechanism that listens on port 427 for SLP signals propagated at Jetdirect power-on. Default = off (unchecked) Checkbox enables SNMPv3 credential entry fields in HP Web Jetadmin discovery settings. When these credentials are added (at discovery settings or global credentials) HP Web Jetadmin will attempt SNMPv3 queries on devices. Default = off (unchecked) NOTE: SNMPv3 discoveries can be slow if not properly set. These should be targeted at only parts of the network that are known to have SNMPv3 enabled devices. The Blocked Devices list contains device addresses for which device discoveries are blocked. Devices are populated into this list in one of two ways. First, the device can be deleted from the All Device list with the Delete and Block option which adds the device to the Blocked Devices list. Second, devices can be added to (or removed from) the list in Tools > Options > Devices Lists > Blocked Devices. The device s presence in the Blocked Devices list will prevent HP Web Jetadmin from discovering it. Adding a device to the list through the Tools > Options > Device Lists > Blocked Devices interface will not cause it to be removed from the All Devices list. Other Related Network Settings Tools > Options > Application Management > Network contain most of the other settings that affect discovery. Setting Explanation Default SNMPv1 Value sets the number of milliseconds Web Jetadmin waits for a reply 400 Timeout from a network query SNMPv1. Default = 400 SNMPv3 Value sets the number of milliseconds Web Jetadmin waits for a reply 500 Timeout from a network query SNMPv3. SNMP Retries Value sets the number of retry queries HP Web Jetadmin will execute 4 when no response is detected Enable DNS Lookups Forces HP Web Jetadmin to query name services for each device discovered. Default = on (checked) This setting is sometimes disabled in environments where DNS responses are slow or are not functioning. Default = enabled IP Ranges Credentials Global store for IP Range settings used by network device discovery, PC connected device discovery and HP Web Jetadmin application discovery. In some cases, credentials like SNMP Get community names or SNMPv3 are being used. Use the Credentials interface to set well known device credentials. These will be tried during discovery when devices don t respond to queries that use default credentials. None or Blank None or blank Page 20

21 May 2007 Hewlett-Packard Development Company, L.P. The information contained in this document is subject to change without notice. HP makes no warranty of any kind with respect to this information. HP specifically disclaims the implied warranty of merchantability and fitness for a particular purpose. HP shall not be liable for any direct, indirect, incidental, consequential, or other damage alleged in conjunction with the furnishing or use of this information. Microsoft, Windows, and Windows NT/2000/XP are registered trademarks of Microsoft Corporation in the USA, and other countries. All other brand and product names are trademarks or registered trademarks of their respective companies. Page 21