openview-nnm

8/7/2019 openview-nnm

1/12

Page 1

HP OpenView NNM IntegrationWeb Jetadmin

HP Web Jetadmin Integration into

HP OpenView Network Node Manager

Overview

Among the many functions thatEnterprise Management Solutions

such as HP OpenView Network NodeManager provide to IT administrators,the ability to maintain, monitor, andtroubleshoot network nodes remainsa high priority. It is important toprovide accurate viewing of thenetwork and quick identification ofproblems so they can be resolvedbefore they escalate to a criticalstage.

Enterprise Management Solutions canmonitor the status and configurationofnetwork elements such as routers,

switches, servers, and printers,representingthe status and logicallayout of the network in a two or

three-dimensional map (see Figure 1).However, to effectively manageprinters, administrators require moredetailed printer information to

quickly resolve printer issues beforethey severely impact customerproductivity. Ideally, administratorsrequire the type of printer installation,configuration, maintenance,monitoring, and troubleshooting thata printer management solution suchHP Web Jetadmin can provide.

Fortunately, HP Web Jetadmin canintegrate into Enterprise ManagementSolutions such as HP OpenViewNetwork Node Manager. With theintegration of HP Web Jetadmin into

these Enterprise ManagementSolutions, Hewlett-Packard hasextended the reach of these solutions

to include complete printermanagement. From the same

interface, network administrators cannow access all of their EnterpriseManagement tools and the powerfulfunctionality of HP Web Jetadmin.

HP Web Jetadmin can also be used toassist in configuring printers toforward critical and warning events(traps) into the EnterpriseManagement Solutions. The eventscan appear in the event logs or alarmbrowsers to proactively troubleshootproblems and solve them before theyimpact end users.

Without the Enterprise Managementintegration, an administrator wouldneed to maintain two separateplatforms for network management,one for printers (HP Web Jetadmin),and one for the rest of the network(the Enterprise Managementplatform). This means twice the setup,configuration, and maintenance of anintegrated package, and the need tomonitor two separate user interfacesfor alarms.

Software bridges can be created forNetwork Node Manager, and morethan likely other Enterprise

Figure 1


2/12

Page 2


Management Solutions such as CAUnicenter TNG or Tivoli NetView, to

provide the hooks into HP WebJetadmin to view more detailedprinter information.

However, this paper will focus strictlyon creating and customizing bridgesand forwarding printer traps for HPOpenView Network Node Manager6.4 only.

For information regarding HP WebJetadmin integration into HP SystemsInsight Manager, please read thetechnical brief titled HP Web

Jetadmin Integration for HP SystemsInsight Manager, found on thefollowing HP Web site:

http://www.hp.com/go/wja_whitepapers

Creating a Bridge

HP Web Jetdmin integrates into theNetwork Node Manager frameworkthrough the use of a software bridge.The bridge provides a hook betweenthe functionality of Network NodeManager and HP Web Jetadmin,providing an easy technique for usersrunning Network Node Manager toswitch to an HP Web Jetamin view forany printer to gather more details.

A customized bridge can be easilycreated in Network Node Managerthat allows for the launching of an HPWeb Jetadmin Status page whenevera symbol is opened from a devicemap (see Figures 1 and 2).

To create a bridge, create a filenamed HPWJABridge.arf using astandard text editor such as MicrosoftNotepad, and place it under thefollowing subdirectory:

/Program Files/HP OpenView/registration/C

Appendix A contains a sample of abasic bridge as well a more advancedone. Merely supply the name and

port of the desired HP Web Jetadminserver where indicated.

Since HP Web Jetadmin supports allStandard Printer MIB compliant thirdparty printers as well as HP printers,the bridge in the example definesexpected printer attributes asisPrinter. Therefore, as long as theprinter appears as a printer icon in themap and contains the isPrinterattribute, no matter which vendor, theprinter can be configured to launch aseparate HP Web Jetadmin Statuswindow whenever the printer isopened from the Network NodeManager map. A raised box aroundthe icon indicates it has beenconfigured to launch HP WebJetadmin (see Figure 1).

The bridge can also be modified (seesecond example in Appendix A) toadd an entry under the Tools drop-down menu to launch HP WebJetadmin, as well as an option tolaunch an HP Web Jetadmin Status

Page for a device when right-clickingon the device in the map.

Bridge ConfigurationTo configure a device on the NetworkNode Manager map to use the bridge,right-click on the desired printer icon,then select Symbol Properties(seeFigure 3). Change the Status SourcetoSymboland selectHPWebJetadminActions: WJALaunchfrom theApplication Actionlist.Finally, select the Target Objectsbutton and add the printer. As longas the printer matches the bridgecriteria defined in the bridge file, theconfiguration should succeed.

If configuration fails, it is more thanlikely caused by a mismatch betweenthe printer attributes and the criteriadefined in the bridge file. To view theprinter attributes, right-click theprinter icon, and select ObjectProperties(see Figure 3). TheCapabilities option will provide a listof attributes that describe the object

Figure 2


3/12

Page 3


(see Figure 4). Make sure thatisPrinter is contained as a capability

for this object.

Once the configuration succeeds, aseparate HP Web Jetadmin Statuswindow will appear when any printeris opened from the Network NodeManager map (see Figure 5).

Bridge Operation

Generally, the status of a networkelement is reflected by its color onthe Network Node Manager map green for up, red for down (see Figure6). If a problem is detected on aprinter, the administrator can easilyswitch to the HP Web Jetadmin Statusview of the printer, which providesmuch more information than thestandard Network Node Managerinterface, by simply clicking on thedevice. A separate HP Web Jetadmindevice Status window will appear,providing the ability to perform manytasks to assist in diagnosing andfixing any issues that exist. Forexample, typical functionality thatHPWeb Jetadmin provides to solve

Figure 4

Figure 5

Figure 3


4/12

Page 4


printer issues includes (see Figure 7):

Status - display current status,front panel message,capabilities, properties, setprinter online/offline.

Configuration a multitude ofdevice, network, and securityparameters can be configured,including a fully functionalremote control panel for manyprinter models.

Diagnostics view additionaldevice information such as serialnumber, page count, error log,Novell NetWare queue status,etc.

Reset Options - power cycleprinter, cold reset printer tofactory defaults, reset NetWareconnections.

Update upgrade the firmwareversion for both HP Jetdirect andprinter.

Create Queue install a printqueue using the Standard PortMonitor for Windows.

Test Page test basicfunctionality by forcing the

printer to print an internalconfiguration page.

Print Jobs view most recentprint jobs to have completedprinting on the printer.

Disk Jobs view or delete anystored print jobs.

Alerts configure printer eventsto trigger e-mail messages todesired individuals.

Application Plug-ins additionalfunctionality, such as the abilityto manage fonts and macrosthrough the Device Storage

Manager, can be installed intoHP Web Jetadmin and accessedfor a printer.

NetWare create a NovellNetWare queue using queueserver mode or remote printermode.

Not all functionality will be availablefor all models of printers. To see a

Figure 6

Figure 7


5/12

Page 5


matrix that matches HP printers andfunctionality that applies to each,

read the technical brief titledSupported Printer Features in HPWeb Jetadmin.

Alarms

Network Node Manager containsalarm browsers that filter deviceevents based on acknowledgment,severity, time, source, message,and/or event type. TheAlarmCategorieswindow contains buttonscorresponding to each of the alarmcategories. While Network Node

Manager defines a set of defaultcategories, new categories can becreated, and the alarms assigned to acategory can be modified. The colorof the push button reflects the mostsevere unacknowledged alarm in thecategory.

Network Node Manager uses SNMP(Simple Network ManagementProtocol) to read and manage theconfiguration and status of thenetwork devices. The polling intervalcan be defined in Network Node

Manager to assist in accuratelycapturing devices in an error state.However, with polling, some errorsmay never be discovered since theymay not exist at the exact momentthe device is polled. Other errorsmay exist for an extended period oftime before they are discovered viapolling, causing severe down time.

Traps

Fortunately, through the use of HPWeb Jetadmin, printers can beinstructed to send real-time SNMPtraps whenever error conditions existon the printers. A trap is a brief

message explaining the type ofproblem and some relevant detailssuch as event type, description, etc.The events will then appear in theNetwork Node Manager alarmbrowser, which operators will use todrill down to the root cause of theproblem using the HP Web Jetadminbridge.

HP Web Jetadmin has its own Alertsmechanism which configures itself inthe trap destination list of the HPJetdirect device and sends e-mail

messages to desired recipients whenproblems occur on the printer.

HP Web Jetadmin can be used to alsoconfigure a printer to send trapsdirectly into Network Node Managerto be displayed in the alarm browsers.While viewing the Status page of adevice in HP Web Jetadmin, selectConfigurationfrom the drop-down

menu, then select Network. UnderSNMP Trap Destination Table, enterthe IP address and port (default 162)of the HP OpenView server (see Figure8).

Now, when warning or critical errors

occur on the printer, an SNMP trapwill be sent directly into NetworkNode Manager to be displayed in thealarm browsers. HP Web Jetadmincan also be used to configuremultiple printers simultaneously byselecting Configurationfrom theDevice Toolsdrop-down menu whileviewing either a group or selectingmultiple devices from the list ofAllDevices.

Note: Some traps can occur veryfrequently on printers, such as Toner

Low events. Be aware that NetworkNode Manager may receive a largenumber of traps. Fortunately, thefrequency of reporting the event canbe customized in Network NodeManager, as well as which events willappear in the alarm browser.

Figure 8


6/12

Page 6


Using HP Web Jetadmin to configureprinters to forward traps into NetworkNode Manager offers some distinctadvantages, particularly with respectto alarming. First of all, all alarmscan be viewed through the unifiedalarm views of Network NodeManager, eliminating the need tohave two user interfaces running atthe same time. Second, and perhapsmore importantly, the range ofautomatic actions is vastly greater inNetwork Node Manager. With HPWeb Jetadmin, the only automaticaction possible is e-mail. WithNetwork Node Manager, anadministrator can configure anyexecutable file, batch file or script torun in the event of a given alarm. Soinstead of relying on e-mailexclusively, an administrator canchoose to page someone, trigger ahelpdesk ticket through a ticketing

system such as Remedy or Peregrine,or use any other means of notificationthat is possible through executables,batch files, or scripts.

Configuring Network NodeManager to Recognize Traps

In order for Network Node Managerto recognize the traps sent to it fromdevices, the trap definitions must bedefined in the trapd.conf file. If HPJetdirect traps are not defined,Network Node Manager will still

display them because it will recognizethem as part of the ENTERPRISES

enterprise. However, the events willnot be displayed with informative textsuch as they would if definitions aredefined. For example, Figure 15depicts three different events, eachwith and without definitions defined.

The trapd.conf file containsdefinitions for the handling of SNMPtraps generated by SNMP agents. Itincludes information on how toformat the log and what action totake, if any, upon receiving an event.The formats are also used to present

messages in the alarm browser. Theprimary method for modifying thetrapd.conf definitions is through theOptions, Event Configurationitem ofNetwork Node Manager, although it ispossible (but not recommended) toedit the trapd.conf file with a texteditor.

Trap events can be created/edited byselecting Options, Event Configurationin Network Node Manager (see Figure9). Enterprises and events can becreated, and actions can be defined

for those events.

An enterprise must first be createdbefore events can be created. Tocreate an enterprise, select Edit,Enterprise, New (see Figure 10). Enterthe name of an enterprise e.g. net-printer. Assign an ID to theenterprise. In the case of HP printers,use the Object Identifier

.1.3.6.1.4.1.11.2.3.9.1

This generalDeviceStatus object is

sent in a UDP SNMPv1 Trap packet,along with a 5 digit-trap value each

Figure 10

Figure 9


7/12

Page 7


time an event occurs on the printer.Appendix B contains a table of

common 5-digit trap values sentwhen events occur on HP printers.

To create an event to be assigned tothis enterprise, highlight theenterprise from the list, then selectEdit, Events, New (see Figure 11). ANewEvent Wizardwill launch, allowing fordefining several parameters. On thefirst screen, underSpecific TrapNumber, enter the desired 5-digit trapnumber that corresponds to an eventfrom the table in Appendix B. Enteran Event Nameand Descriptionthat

matches the desired event.

The second screen allows forselecting sources (devices) to whichthe event will apply. The default is toselectAll Sources, but individualdevices can also be entered orselected from the map.

The third screen allows for definingwhich alarm browser will contain theevent, the severity of the event, andthe message that will appear in theevent log (see Figure 12). This same

message will appear in the alarmbrowser as well (see Figure 13).Additional examples of events andhow they are displayed in the alarmbrowser can be found in Appendix C.

The final screens will allow fordefining a command to be executedwhen the event occurs or for a popupmessage to appear, and forspecifying destinations to which

Figure 11

Figure 12

Figure 13


8/12

Page 8


events can be forwarded.Destinations include remote

managers, other management hosts,or a combination of both.

Once all configuration settings arecompleted, the settings will be writtento the trapd.conf file. When theevents occur on the printersconfigured to send traps to NetworkNode Manager, the desired alarmbrowser container will display theevent as defined (see Figure 13).

To determine more informationpertaining to the printer event

displayed in the alarm browser, or topotentially fix the issue that isoccurring on the printer, double-clickon the event in the alarm browser.The Network Node Manager map willappear, with the device containing theerror highlighted. Now double-clickon the highlighted device to launchHP Web Jetadmin.

Troubleshooting Alarms

If the printer events are not appearingin the alarm browser, there are several

troubleshooting steps that can betaken to determine why.

From a Command Prompt, create atelnet session to the desired printer todetermine if the IP address of themachine running Network NodeManager is contained in the TrapDestination List of the HP Jetdirectdevice (see Figure 14). If the IPaddress is present, confirm that theport is 162 (or matches the port towhich Network Node Manager islistening).

If the device is configured to sendtraps to the proper destination, usethe SNMP MIB Browser tool inNetwork Node Manager, found underthe Toolsdrop-down menu, todetermine if the HP Jetdirect device issending SNMPv1 traps (see Figure 15).Enter the IP address of the printerunderName or address, then enter the

following OID underMIB Object IDto

walk the tree:

.1.3.6.1.4.1.11.2.13.1.2

If the .5.1 parameter (or 5.2, 5.3,depending on which entry is the onematching Network Node Manager)has a value of 0, then it is configuredfor SNMPv1 traps. If the value is 1,then the HP Jetdiect device is sending

SNMPv2 traps, which will not be

parsed correctly by Network NodeManager using the net-printerenterprise. Use the telnet session todelete the entry if it is set to sendSNMPv2 traps, then add the entryagain using either telnet or HP WebJetadmin, which will default toSNMPv1.

Figure 15

Figure 14


9/12

Page 9


If the device is configured correctly tosend SNMPv1 traps, use a sniffer or

network trace software such asMicrosoft Network Monitor todetermine if the traps are indeedbeing sent by the printer. Traps willappear as UDP packets.

Finally, commands exist in NetworkNode Manager to display all receivedtraps, send traps, etc. Use theNetwork Node Manager Helpfunctions to learn more about nativetroubleshooting tools.

Summary

With the integration of HP WebJetadmin into Enterprise ManagementSolutions, Hewlett-Packard hasextended the reach of these solutionsto include complete printermanagement. From the sameinterface, network administrators cannow access all of their EnterpriseManagement tools and the powerfulfunctionality of HP Web Jetadmin. Inaddition, critical and caution eventscan appear in the event logs or alarmbrowsers of Enterprise ManagementSolutions to proactively troubleshootproblems and solve them before theyimpact end users.

Support/Services

The information contained within thisdocument is provided as is. Thesolutions provided are examplesonly, with no official testingconducted or support provided onthese solutions. However, forassistance pertaining to general HPWeb Jetadmin or HP OpenViewNetwork Node Manager issues,contact regional support centersfound at the following location:

www.hp.com , select Contact HP.Technical Support.

Copyright February, 2004Microsoft, Windows, and Windows NT/2000/XPare registered trademarks of MicrosoftCorporation in the USA, and other countries. Allother brand and product names are trademarksor registered trademarks of their respectivecompanies. The information contained in thisdocument is subject to change without notice.HP makes no warranty of any kind with respectto this information. HP specifically disclaimsthe implied warranty of merchantability andfitness for a particular purpose. HP shall not beliable for any direct, indirect, incidental,consequential, or other damage alleged inconjunction with the furnishing or use of thisinformation.


10/12

Page 10


Appendix A

Merely substitute the host name or IP address of the desired HP Web Jetadmin machine underWJA machinein the url.

This file as defined above will cause the device Status page of HP Web Jetadmin to be launched for a device whendouble-clicking on the device in the Network Node Manager map. Additionally, this file can be altered (below) to includeHP Web Jetadmin as an available item when right-clicking on a device (popup) or from the Toolsdrop-down menu.

Application "HPWebJetadminActions"

{

Action "WJALaunch"

{

SelectionRule (isPrinter);

MinSelected 1;

MaxSelected 1;

NameField "IP Address", "IP Hostname", "IPX Address", "Selection Name";

#ifdef NT

Command "iexplore http//WJA machine:8000/device/$OVwSelections";

#else

Command "iexplore http://$OVwSelections";

#endif}

}

Sample of a simple HPWJABridge.arf file

Application "HPWebJetadminActions"

{

Menubar "Tools"

{

"Launch WebJetAdmin" f.action "WJALaunch";

}

PopupItem "Launch WebJetAdmin"

Context (AllContexts)

TargetSymbolType ANY

f.action "WJALaunch";

Action "WJALaunch"

{

SelectionRule (isPrinter);

MinSelected 1;

MaxSelected 1;

NameField "IP Address", "IP Hostname", "IPX Address", "Selection Name";

#ifdef NT

Command "iexplore http//WJA machine:8000/device/$OVwSelections";

#else

Command "iexplore http://$OVwSelections";

#endif

}}

Sample of an advanced HPWJABridge.arf file


11/12

Page 11


Appendix B

Trap ID Description

10031 Checking Printer

35037 Page Punt (error 21)

35076 Memory Out (error 20)

40010 Toner Out

40019 Output Full

40021 Cover Open

40026 Tray Missing

40038 Toner Low

40050 Generic Error

40051 Fatal Error

40052 Scanner Failure

40059 Main Motor Failure

40079 Offline

40090 Envelope Connection Error

40124 Duplex Connection Error

41002 Tray 1 Load Paper




44001 Paper Jam - Input44002 Paper Jam - Output

44003 Paper Jam - Top Cover

44004 Paper Jam - Duplexer


12/12

Page 12


Appendix C

The three events below displayed with and without definitions in the trapd.conf file.

openview-nnm

Documents