Resources MIB are blocked because the PC might also support those OIDs. HP SNMP Proxy
Agent directs on top of the SNMP service. HP SNMP Proxy Agent redirects objects intended for
the device to the device and objects intended for the PC to the PC. For security reasons, HP
SNMP Proxy Agent must block configuration SNMP Set Request packets that might apply to the
PC, such as those found in MIB-II and Host Resources MIB. Items under Networking fail because
they are set on the PC. The following are examples of the configuration items that are blocked:
• SNMP Trap Table
• System Contact
• System Location
• Set Community Name
• Get Community Name
• The devices that HP WS Pro Proxy Agent discover do not have restrictions between configuration
items applying to the PC or printer because the PC does not support the Web Services calls.
Alerts
It is possible to monitor device alerts through the proxies. However, the number of alerts that can be
monitored are limited to only the alerts that polling supports. HP Web Jetadmin cannot process traps
through the proxies. Therefore, the alerts in the General category that use traps are not supported.
Reports
If the proxy discovers devices that display supply levels and page counts, the devices can be added
to Data Collections and reports can be generated on the data that is collected.
PROXY COMPARISON
Recall earlier it was stated that the level of support for each device depends on the following
variables:
• Which proxy discovered the device
• How the feature is exposed on the device
• How HP Web Jetadmin is defined to retrieve or configure the feature
HP Web Jetadmin can use a variety of techniques to retrieve or configure information, such as SNMP,
DSMP, XDM, LEDM, and WS*. HP Web Jetadmin uses only one technique to support each feature on
a specific device. If a device supports LEDM and a feature is exposed via LEDM, HP Web Jetadmin
supports the feature using only LEDM for that device. Even if the device also exposes the feature
through SNMP, HP Web Jetadmin uses the preferred technique of LEDM. This plays an important role
in what each proxy supports on a given device.
If HP SNMP Proxy Agent discovers the device, it exposes only the features that HP Web Jetadmin uses
SNMP to support on that device. If HP WS Pro Proxy Agent discovers a device, it exposes only the
features that HP Web Jetadmin uses LEDM to support on that device.
For example, the HP LaserJet 400 M401 device supports both SNMP and LEDM. Each feature is
supported using only one technique. If a feature is exposed through LEDM, HP Web Jetadmin uses
LEDM, regardless of whether the feature is also exposed through SNMP. It does not matter which
proxy discovers the device. HP Web Jetadmin uses only LEDM for those features. This means that if
HP SNMP Proxy Agent discovers the device, most features are not supported because HP Web
Jetadmin must use LEDM.
Komentarze do niniejszej Instrukcji