NNMi9-1x HowToUse LabGuide

Network Management Center Technical Enablement

HP Software Field Excellence

Network Node Manager (NNMi) 9.1x:

How to Use, Level 320 Lab Guide

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Network Node Manager (NNMi) 9.1x: How to Use, Level 320

Copyright Information

© Copyright 2010 - 2013 Hewlett-Packard Development Company, L.P.

This content is provided for use throughout the Learning Solution duration and is the copyrighted work of HP. This content is provided for the sole use of the person accessing the Learning Solution and may not be used by any other person and may not be reproduced, recorded, repurposed, distributed or modified without the written permission of HP.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Network Node Manager (NNMi) 9.1x: How to Use, Level 320

Lab Guide

IMPORTANT, PLEASE READ!

TO: HP Internal Employees and Partners

FROM: Network Management Center Technical Enablement Team

1. Exercises in this document are based on content originally created for the HP Software Education courses NNMi120-91 (NNMi Essentials, Revision B) and NNMi200-91(NNMi Advanced, Revision A) training environments. They have been modified to make them work within the HP Software Field Excellence training infrastructure.

2. Reference the environment name “WBT - NNMi 9.1x_Series 300” when sending scheduling requests to [email protected]

3. Reference the above environment name when sending feedback regarding this document or training environment operation to [email protected]

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

mailto:[email protected]

mailto:[email protected]

For HP Internal and Partners Use Only. 2010 - 2013 Hewlett-Packard Development Company, L.P. 2-1

Lab 2 – NNMi Console Exercises

1. Connect to your NNMi lab environment.

2. On your Access VM, launch Mozilla Firefox or Internet Explorer, and log in to the NNMi console as user oper2 with password nnm.

3. What is the name of the initial view displayed in the Content Pane?

4. How often will this initial view refresh?

5. What information is available in the Analysis pane when you click on a node?

6. What options are available when you select a node (single left click) and select the Actions menu or bring up the right-click pop-up menu?

7. Select the Node Group Overview in the Topology Maps area on the left. Click on the All Sites node group.

a. Determine how the group got its status.

b. List the members of the group.

c. Display a map of the group.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Lab 2 – NNMi Console Network Node Manager (NNMi) 9.1x: How to Use, Level 320


8. Select Network Overview in the Topology Maps area on the left.

a. Double click ROUTER-01 in the map. Briefly glance through the types of information available on the tabs. (Again, much more information will be presented in the upcoming modules.).

b. Notice the information for ROUTER-01 in the Analysis pane.

c. Click the Network Overview breadcrumb.

d. Click on a connection endpoint (the small shapes around each node) and see how the information displayed differs from the information displayed for ROUTER-01.

What does the connection endpoint on a Layer 3 map represent?

e. Click on a connection line and look at the information in the Analysis pane.

What does the connection line on a Layer 3 map represent and what is the status?

9. Open the Inventory workspace, Nodes view.

What is shown in the resulting table?

10. Open the record for the Node Details for the node ROUTER-01 by double clicking on its row. Briefly review the types of information on each tab. Add Main Router as Notes for this node. Close the Details page.

11. Open each of the other Inventory views to see what is available.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Network Node Manager (NNMi) 9.1x: How to Use, Level 320 Lab 2 – NNMi Console


12. Open the Incident Browsing workspace and the Custom Incidents view, and mouse over the column headers to see what they mean. Note: Set the time selector, which defaults to Last Day, to All to view all past incidents as well.

13. Open each of the other workspaces to see the types of information available. We will be using these in detail throughout this course.

14. Verify the license, version, and number of objects from within the console.

Describe what each user role may access in the console 1. Open a second copy of the management console and log in as oper1 with

password nnm.

Note. Mozilla Fire Fox shares session information between open windows; Internet Explorer does not. Therefore, we recommend that each “user” logs into a different browser when comparing user settings.

a. How can you tell quickly which login you are using?

b. Which Workspaces are available to the different roles? Are the Views the same?

c. In the Inventory workspace, open the Nodes view for both users. Select a node. How do the Actions and Tools menus compare between the logins?

d. If you open Node Details, are there differences?

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



e. In the Incident Browsing workspace, open Open Root Cause Incidents. Select an incident. How do the Actions and Tools menus compare?

f. Open the Incident Details page. From each user, attempt to assign the incident to the administrator.

g. Sign out and close both operator consoles.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Solutions 1. Connect to your NNMi lab environment.


Answer:

a. Open your web browser.

b. If needed, browse to http://fullyQualifiedHost/nnm.

c. If needed, you may want to set this as your home page in the browser.

d. Sign in using the login oper2 and password nnm that have been configured in the lab environment.

3. What is the name of the initial view displayed in the Content Pane?

Answer:

The Topology Maps workspace opens and shows the last view in the list, All Sites. This is a customization in the lab environment.

4. How often will this initial view refresh?

Answer:

The All Sites view is configured to refresh every 60 seconds.

5. What information is available in the Analysis pane when you click on a node?

Answer:

The name of the node, its status, and a wealth of other information about the node.

6. What options are available when you select a node (single left click) and select the Actions menu or bring up the right-click pop-up menu?

Answer:

You may open a map of the neighbors of the node, analyze a path, access various troubleshooting tools, and perform other operations.

7. Select the Node Group Overview in the Topology Maps area on the left. Click on the All Sites node group.

a. Determine how the group got its status.

Answer:

With the group selected, select Actions → Node Group Details→ Status Details.

Are any nodes not Normal? Click on the status indicator (Critical, Major, etc.) and see which nodes have problems.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Close the status display.

b. List the members of the group.

Answer:

With the group selected, select Actions → Node Group Details→ Show Members.

Close the list by clicking the Close icon in the View Toolbar.

c. Display a map of the group.

Answer:

With the group selected, select Actions → Maps→ Node Group Map. (This is the map that was displayed by default when you started NNMi.)

Close the map by clicking the Close icon in the View Toolbar.

8. Select Network Overview in the Topology Maps area on the left.

Answer:

a. Double click ROUTER-01 in the map. Briefly glance through the types of information available on the tabs. (Again, much more information will be presented in the upcoming modules.).

b. Notice the information for ROUTER-01 in the Analysis pane.

c. Click the Network Overview breadcrumb.

d. Click on a connection endpoint (the small shapes around each node) and

see how the information displayed differs from the information displayed for ROUTER-01.

Answer:

The Analysis pane will display information about the IP address which is the connection endpoint in a Layer 3 map.

e. Click on a connection line and look at the information in the Analysis pane.

Answer:

The Analysis pane will display information about the IP subnet which is represented by the connection line in a Layer 3 map. Because the connections on a Layer 3 represent subnets, which are not monitored in NNMi, the connections on a Layer3 map appear as No Status.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



9. Open the Inventory workspace, Nodes view.

Answer:

A table of nodes displays in the console.

10. Open the record for the Node Details for the node ROUTER-01 by double clicking on its row. Briefly review the types of information on each tab. Close the Details page.

Answer:

a. Double Click on the row for ROUTER-01.

b. Review the types of data in the Basics section.

c. Note the Discovery State under the General tab.

d. You can type "Main router" in the Notes field.

e. Review the information on each of the tabs.

f. Close the Node Details page using the Save and Close icon to retain your Notes.

11. Open each of the other Inventory views to see what is available.

12. Open the Incident Browsing workspace and the Custom Incidents view, and mouse over the column headers to see what they mean. Note: Set the time selector, which defaults to Last Day, to All to view all past incidents as well.

Answer:

• A number of column names are self-explanatory such as Severity, Priority, Name, First Occurrence, Origin Occurrence Time, Created Time and Last Modified.

• We’ll look at other columns such as Category, Correlation Nature, Duplicate Count, Correlation Notes and Family in more detail when reviewing incident management and incident configuration.

Other columns include:

• Lifecycle State is used as the incident progresses toward resolution (note the “funnel” icon indicating an active filter)

• Last Occurrence shows the most recent time the incident happened • Assigned To is used for operator assignment of incidents • Source Node indicates which system caused the incident • Source Object shows which component on the source node • Originator indicates how the incident was generated, whether due to an

SNMP trap, NNMi event analysis or other mechanism • Message describes the incident • Notes are user-added comments

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



• RCA Active indicates whether NNMi is still analyzing the cause of this issue

13. Open each of the other workspaces to see the types of information available. We will be using these in detail throughout this course and follow-on courses.

14. Verify the license, version, and number of objects from within the console.

Answer:

a. Select Help → System Information.

b. Click View Licensing Information.

c. Review the number of node licenses used (Consumption).

d. Close the License window.

e. Select the Database tab.

f. Review the number of objects in the database.

g. Close the System Information window.

Describe what each user role may access in the console 1. Open a second copy of the management console and log in as oper1 with

password nnm.

Note. Mozilla Fire Fox shares session information between open windows; Internet Explorer does not. Therefore, we recommend that each “user” logs into a different browser when comparing user settings.

a. How can you tell quickly which login you are using?

Answer:

The user name and role appear in the upper right corner of the console.

b. Which Workspaces are available to the different roles? Are the Views the same?

Answer:

Both have access to Incident Management and Incident Browsing, Topology Maps, Monitoring, Troubleshooting, and Inventory workspaces, with all the same views.

The Management Mode workspace is only available to oper2, the level 2 operator.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



c. In the Inventory workspace, open the Nodes view for both users. Select a node. How do the Actions and Tools menus compare between the logins?

Answer:

oper1, the level 1 operator, sees only Graphs, Monitoring Settings, Ping (from server), Show All Incidents, Show All Open Incidents, Show Members, Show Details, and Traceroute (from server).

oper2, the level 2 operator, also sees Browse MIB, Configuration Poll, List Supported MIBs, Management Mode, Show Attached End Nodes, and Status Poll.

On the Tools menus the level 1 operator sees Find Node, NNMi Status, and Restore All Default View Settings. The level 2 operator also sees Find Attached Switch Port, MIB Browser, Status Distribution Graphs, and Visio Export.

d. If you open Node Details, are there differences?

Answer:

No differences; all details are shown for both accounts.

e. In the Incident Browsing workspace, open Open Root Cause Incidents. Select an incident. How do the Actions and Tools menus compare?

Answer:

The Actions menu is the same for both users. On the Tools menu the level 1 operator sees only Find Node, Restore All Default View Settings, and NNMi Status.

f. Open the Incident Details page. From each user, attempt to assign the incident to the administrator.

Answer:

Level 1 Operators are not permitted to set the assign field in the incident detail form. Only the Level 2 Operator has the Quick Find capability on that field.

(Note that Level 1 Operator can assign from the Actions menu.)

g. Sign out and close both operator consoles.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.


Lab 3 - Managing IncidentsNetwork Node Manager (NNMi) 9.1x: How to Use, Level 320

Exercises Describe incident lifecycle, assignments and ownership, states

1. What are the states in the incident lifecycle?

2. What are the states in incident ownership?

View network incidents After your instructor executes “Switch-01-Down” scenario an incident will appear in the Open Key Incidents table.

1. In the Incident Management workspace, open Open Key Incidents. Note: Since this is a demo database, entries are dated. Set the time selector, which defaults to Last Week, to All. You will need to do this for each incident view.

2. Mouse-aver the column headers to see what they mean.

3. Mouse-aver the icons in the columns to see what they mean.

View incident details 1. Open one of the incidents to look at its details. What tabs are there?

2. In the Incident Browsing workspace, look in the Custom Incidents view. Open an incident with a Correlation Nature (CN) of Root Cause and review the Correlated Children. Open a Secondary Root Cause and review the Correlated Parents.

3. Open an incident in the Category Fault and look at the Custom Attributes.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Lab 3 - Managing Incidents Network Node Manager (NNMi) 9.1x: How to Use, Level 320


Sort and filter incidents 1. Open the Incident Browsing → All Incidents view. (Set the time selector to All.)

2. Click the Severity column header to sort the incidents. Click again to reverse the sort.

3. Force the most recent incidents to the top of the list.

4. View only incidents for Routers.

Assign and reassign incidents 1. Open the Incident Management → Unassigned Open Key Incidents view. (Set

the time selector to All.)

2. Select several incidents and take ownership of them. What happens to the incident list?

3. Open the My Open Incidents view. Are the incidents there?

Progress an incident through the lifecycle 1. Select the incident in the My Open Incidents view. What lifecycle state is it in?

2. Move the incident to the next state using the menu.

3. Move the incident to the next state using Incident Details.

4. Close the incident using the menu.

5. Review the incident in the Closed Key Incidents view.

6. Can you re-open a closed incident?

Annotate incident 1. Open your incident in My Open Incidents which is In Progress.

2. Add text to the Notes field to say that you need to order new hardware. Click Save and Close.

3. Scroll the console right to see the notes field.

4. Filter the Notes field to show all incidents related to “hardware”

5. Remove the filter.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Network Node Manager (NNMi) 9.1x: How to Use, Level 320 Lab 3 - Managing Incidents


Delete an incident 1. Open the Open Key Incidents view. (Set the time selector to All.)

2. List only the incidents with Normal severity. (Use another value if you have no Normal incidents.)

a. The Severity column already has a filter. Right-click the Severity column and select Modify Filter.

b. The current filter displays incidents that are not Normal. Click Equals so that it displays only Normal incidents. Click OK.

3. Delete an incident.

4. Can you get a deleted incident back?

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Solutions Describe incident lifecycle, assignments and ownership, states

1. What are the states in the incident lifecycle ?

Answer:

Registered, In Progress, Completed, Closed and Dampened and

2. What are the states in incident ownership?

Answer:

Unassigned or Assigned To <owner>

View network incidents After your instructor executes “Switch-01-Down” scenario an incident will appear in the Open Key Incidents table.

1. In the Incident Management workspace, open Open Key Incidents. Note: Since this is a demo database, entries are dated well in the past. Set the time selector, which defaults to Last Week, to All. You will need to do this for each incident view.

2. Mouse-aver the column headers to see what they mean.

3. Mouse-aver the icons in the columns to see what they mean.

View incident details 1. Open one of the incidents to look at its details. What tabs are there?

Answer:

In addition to the Basics and Notes, there are tabs for General, Correlated Parents and Children, Custom Attributes, Diagnostics, and Registration.

Close the details form.

2. In the Incident Browsing workspace, look in the Custom Incidents view. Open an incident with a Correlation Nature (CN) of Root Cause and review the Correlated Children. Open a Secondary Root Cause and review the Correlated Parents.

Answer:

You can sort the list by clicking on the CN column. A good bet is to filter on the message string containing “Aggregator.”

Remove your filter.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



3. Open an incident in the Category Fault and look at the Custom Attributes.

Answer:

a) In the Incident Browsing workspace, select Open Key Incidents by Category.

b) Sort on Category, or filter on Fault. Remember to set the time to All for the demo db).

c) Open a Fault incident and click the Custom Attributes tab.

d) Close the incident window and remove your filter.

Sort and filter incidents 1. Open the Incident Browsing → All Incidents view. (Set the time selector to All.)

2. Click the Severity column header to sort the incidents. Click again to reverse the sort.

3. Force the most recent incidents to the top of the list.

Answer:

Click the Last Occurrence column header twice.

4. View only incidents for Routers.

Answer:

Since there is a default Node Group that contains all routers, use the <Set node group filter> drop-down list to select Routers.

Reset the filter to <Set node group filter> when you are done.

Assign and reassign incidents 1. Open the Incident Management → Unassigned Open Key Incidents view. (Set

the time selector to All.)

2. Select several incidents and take ownership of them. What happens to the incident list?

Answer:

a. Shift select multiple rows and Actions → Assign → Own Incident.

3. Open the My Open Incidents view. Are the incidents there?

Answer:

(Set the time selector to All.)

Yes, the incidents have moved to this list.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Progress an incident through the lifecycle 1. Select the incident in the My Open Incidents view. What lifecycle state is it in?

Answer:

You can mouse-aver the lifecycle icon or Open the Incident Details to see that it is Registered. That means it has an owner – you – and it has not yet been resolved.

2. Move the incident to the next state using the menu.

Answer:

Select the incident's checkbox and select Actions → Change Lifecycle → In Progress.

Note the icon change.

3. Move the incident to the next state using Incident Details.

Answer:

a. Open the incident.

b. In the Lifecycle State drop-down list, select Completed.

c. Click Save and Close.

d. Note the icon change.

4. Close the incident using the menu.

Answer:

Select the incident's checkbox and select Actions → Change Lifecycle → Close.

The incident is removed from the My Open Incidents view.

5. Review the incident in the Closed Key Incidents view.

Answer:

Select the Incident Browsing → Closed Key Incidents view.

(Set time selector to All.)

6. Can you re-open a closed incident?

Answer:

Yes. Select the incident and select Actions → Change Lifecycle → In Progress. The incident moves back to the My Open Incidents view.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Annotate incident 7. Open your incident in My Open Incidents which is In Progress.

8. Add text to the Notes field to say that you need to order new hardware. Click Save and Close.

9. Scroll the console right to see the notes field.

10. Filter the Notes field to show all incidents related to “hardware”

Answer:

Right-click the Notes header and select Filter by: Contains string. Type hardware.

11. Remove the filter.

Answer:

Right-click the Notes header and select Filter by: Remove filter.

Delete an incident 12. Open the Open Key Incidents view. (Set the time selector to All.)

13. List only the incidents with Normal severity. (Use another value if you have no Normal incidents.)

c. The Severity column already has a filter. Right-click the Severity column and select Modify Filter.

d. The current filter displays incidents that are not Normal. Click Equals so that it displays only Normal incidents. Click OK.

14. Delete an incident.

Answer:

Select the incident checkbox next to a Normal incident and click the Delete icon or select Actions → Delete. Click OK.

15. Can you get a deleted incident back?

Answer:

No.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.


Lab 4 - Troubleshooting Network IssuesNetwork Node Manager (NNMi) 9.1x: How to Use,

Level 320 Exercises Note: After executing failure simulation scenarios, allow several minutes for incidents to

appear in the open key incidents table. There may be delays between when incidents are generated and when they appear in the incident browser.

Simulate a network failure 1. Open the Scenarios folder on your access VM Desktop.

2. Double-click on the RouterDown.bat script to execute it.

3. While NNMi detects and analyzes the simulated failure symptoms, complete the initial exercises below.

Review Available Topology Maps 1. Open the Topology Maps workspace.

2. Open the Node Group Overview map. What types of symbols are shown here?

3. Select the Non-SNMP Devices node group symbol. Is there a difference between double-clicking a symbol, using the Open icon on the toolbar, and using the Actions → Maps → Node Group Map menu? How about Actions → Node Group Details → Show Members?

4. Navigate to the Network Overview topology map.

5. What happens when you double-click or Open a node icon from this view?

6. How do you view all the nodes physically connected to one of the highly-connected nodes?

7. Open the Routers map.

8. You should have 2 routers with a yellow status. How can you find out what’s wrong with it?

9. On the Incidents tab of the router with a yellow status, Open the most recent interface (or connection) incident.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Lab 4 - Troubleshooting Network Issues Network Node Manager (NNMi) 9.1x: How to Use, Level 320


Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Network Node Manager (NNMi) 9.1x: How to Use, Level 320 Lab 4 - Troubleshooting Network Issues


10. From the Incident details, Open the Source Object record. Note how the Hosted On Node is the node you started from. Surfing available information is no longer a linear sequence.

11. Close the detail forms.

12. Notice carefully which groups have maps in the Topology Maps workspace. Open Inventory → Node Groups in a new window. You can click back to the Topology Maps workspace to compare. Which Node Groups do not have top-level maps available?

13. How can you see maps of those groups?

Cross-launch from an incident to a graphical visualization 1. Verify that NNMi has detected the simulated network failure by navigating to

the All Sites topology map and refreshing the map’s status until you see that ROUTER-05 is in Critical status and that ROUTER-06 and ROUTER-01 are in Minor status.

2. Select a Node Down incident in Open Key Incidents. (You may have to remove filters that you created in previous steps.)

3. Launch a Layer 2 Neighbor view of the system involved in the incident.

4. Clear the simulated network failure by executing the RouterUp.bat script from the Scenarios folder on your access VM Desktop.

Managing Redundant Router Groups 1. Search all incidents for an incident with “Redundancy” in the message.

2. Can you launch to a visualization that shows the members of the redundancy group?

3. How could you track down redundancy group issues?

Managing Aggregated Links 1. How can you see a list of link aggregation groups?

2. How can you see the member interfaces in a group?

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



3. Filter all incidents for messages containing part or all of the string “Aggregator.”

4. Open an Aggregation incident. How can you see the members from here?

List nodes, interfaces, and addresses in the network 1. In which workspace would you view complete lists of objects e.g. VLANs?

2. How can you see which nodes are members of a node group in an Inventory → Nodes view?

3. Can you view the nodes that are members of a node group in the Inventory workspace Node Groups view?

4. How are the views in the Monitoring workspace different from the views in the Inventory workspace?

5. Open the Inventory workspace Interfaces view and verify that the view is sorted by interface status in ascending order.

6. Open the view in a new window using the Show View in New Window toolbar icon.

7. In the console, open the Monitoring workspace Non-Normal Interfaces view. Why don’t all the non-normal interfaces in the inventory list appear here?

8. Can you make the Inventory → Interfaces view look like the Monitoring → Non-Normal Interfaces view?

9. You may close the extra Inventory → Interfaces window. Simulate a major network failure

1. Verify that NNMi has cleared the simulated router down failure by navigating to the Incident Management Open Key Incidents table view and refreshing the view’s status until all incidents are cleared.

2. Open the Scenarios folder on your access VM Desktop.

3. Double-click on the NetworkSubsetDown.bat script to execute it.

4. While NNMi detects and analyzes the simulated failure symptoms, complete additional exercises below.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



View object details 1. Double-click the switch-01 row in the Inventory Nodes table view.

a. What is the status of switch-01?

b. When did the node become Normal?

c. What is the status of each address and interface?

d. What is the status of the SNMP agent?

e. Does the device have outstanding incidents?

f. What conclusions has NNMi drawn from this information?

Check the status and configuration of a device Ensure the collected information for the node is up-to-date by initiating a configuration poll.

Launch and interpret neighbor maps 1. Which devices could be affected if switch-01 failed?

2. Click the squares (Layer 2) or hexagons (Layer 3) around the nodes in each type of neighbor view. How does the information vary in the ‘Analysis Pane?’

3. Click the lines in each type of neighbor view. How does the information vary? (Especially notice the thick line on the L2 Neighbor view between switch-01 and switch-04.)

4. Click nodes, connectors, and lines in each neighbor view to see the type of information available in the ‘Analysis Pane’.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



5. In the database history, there are incidents relating to a temporary failure on ROUTER-03. It is not currently failing, but you can view the history. Look at the details for a node directly connected to the node with the failure. What status do its interfaces show? Does it have any related incidents?

6. How can you find out more about interfaces connected to the failed node?

7. Close the neighbor map views and any detail forms.

Identifying the root cause of a major network outage. 1. Verify that NNMi has detected the simulated major network failure by

navigating to the Network Overview topology map and refreshing the map’s status until you see that ROUTER-03, ROUTER-05 and switch-01 are in Critical status and that other nodes in the shadow of the ROUTER-03 and ROUTER-05 failures are in Unknown status.

2. From the Network Overview topology map, what appears to be the root cause of the network outage?

3. Open the Open Key Incidents view.

4. If needed, wait for incidents to appear.

5. Select an incident and select Actions → Maps → Layer 2 Neighbor View.

6. What incidents were generated?

7. Why does switch-01have a Critical status instead of Unknown like switch-02 and the other switches?

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Invoke troubleshooting tools 1. The t1-centos-01 node shows an Unknown status. Can you ping the device?

2. How often is the device polled?

3. Close all windows other than the main console window.

4. Clear the simulated network failure by executing the NetworkSubsetUp.bat script from the Scenarios folder on your access VM Desktop.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Solutions Review Available Topology Maps

1. Open the Topology Maps workspace.

2. Open the Node Group Overview map. What types of symbols are shown here?

Answer:

The hexagon symbols represent node groups, some of which are defaults and some of which were created by our demo administrator.

3. Select the Non-SNMP Devices node group symbol. Is there a difference between double-clicking a symbol, using the Open icon on the toolbar, and using the Actions → Maps → Node Group Map menu? How about Actions → Node Group Details → Show Members?

Answer:

Double-clicking displays a graphical set of nodes in the Content Pane, as does Actions → Maps → Node Group Map.

Open shows the Node Group details form.

Actions → Node Group Details → Show Members displays a list of devices in the Content Pane.

4. Navigate to the Network Overview topology map.

5. What happens when you double-click or Open a node icon from this view?

Answer:

Both display the node details form.

Close the node details form.

6. How do you view all the nodes physically connected to one of the highly-connected nodes?

Answer:

Select the node and select Actions → Maps → Layer 2 Neighbor View. The originating node is highlighted in the neighbor view. Try displaying a Layer 2 Neighbor View on switch-01 and notice how it differs from the Layer 3 view.

Close the neighbor view.

7. Open the Routers map.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



8. You should have 2 routers with a yellow status. How could you find out what’s wrong with it?

Answer:

Double-click a router with yellow status to open the details form.

Select the Incidents tab, Status tab, and Conclusions tab to get a picture of the situation with the node.

9. On the Incidents tab of the router with a yellow status, Open the most recent interface or connection incident.

Answer:

Double-click the incident in the table under the Incidents tab to open the incident details form.

10. From the Incident details, Open the Source Object record. Note how the Hosted On Node is the node you started from. Surfing available information is no longer a linear sequence.

Answer:

In the Analysis pane Details tab, click the blue link for the Source Object. You could also click the drop-down menu to the right of the Source Object box in the Basics area and select Open.

11. Close the detail forms.

12. Notice carefully which groups have maps in the Topology Maps workspace. Open Inventory → Node Groups in a new window. You can click back to the Topology Maps workspace to compare. Which Node Groups do not have top-level maps available?

Answer:

Navigate to Inventory → Node Groups in your main NNMi Console window. Use the Show View in New Window icon in the Content Pane icon toolbar to open the Node Groups table in a new window.

In your main NNMi Console window, click on Topology Maps in the workspace navigation pane to show the top level maps. Several groups do not have top level maps in the Topology Maps workspace, including Important Nodes, Microsoft Windows Systems, and Non-SNMP Devices.

13. How can you see maps of those groups?

Answer:

Select the group in the Node Groups table, and select Actions → Maps → Node Group Map.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



You can also see the list of node groups in the Topology Maps → Node Group Overview map. Double-clicking one of the containers opens a node group map.

Cross-launch from an incident to a graphical visualization 1. Verify that NNMi has detected the simulated network failure by navigating to

the All Sites topology map and refreshing the map’s status until you see that ROUTER-05 is in Critical status and that ROUTER-06 and ROUTER-01 are in Minor status.

2. Select a Node Down incident in Open Key Incidents. (You may have to remove filters that you created in previous steps.)

3. Launch a Layer 2 Neighbor view of the system involved in the incident.

Answer:

a. Select the incident.

b. Select Actions → Node Actions → Maps → Layer 2 Neighbor View.

4. Clear the simulated network failure by executing the RouterUp.bat script from the Scenarios folder on your access VM Desktop.

Managing Redundant Router Groups 1. Search all incidents for an incident with “Redundancy” in the message. (Note

that case matters.)

Answer:

a. Navigate to Incident Browsing All Incidents.

b. Set the time selector to All.

c. Right click on the Message column header and select Filter Create filter….

d. Click on the contains radio button and type “Redundancy” (to match the correct case) as the filter string. (Alternatively, you could specify “*edundancy” or simply “edundancy” to find both “Redundancy” and “redundancy.”)

e. Click OK.

f. Be sure to remove the filter or restore default filters before navigating away from this table view.

2. Can you launch to a visualization that shows the members of the redundancy group?

Answer:

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



No. Redundancy groups are not node groups and do not display in an identifiable manner o Layer 3 Neighbor maps.

3. How could you track down redundancy group issues?

Answer:

Open Monitoring → Router Redundancy Groups and Open the virtual IP represented by the group.

Managing Aggregated Links 1. How can you see a list of link aggregation groups?

Answer:

Open Inventory → Interfaces and select the interface group selector to Link Aggregation Interfaces.

2. How can you see the member interfaces in a group?

Answer:

a. Open one of the interfaces listed in the Link Aggregation group.

b. Select the Link Aggregation tab in the Interface Details form.

3. Filter all incidents for messages containing part or all of the string “Aggregator.”

Answer:

a. Navigate to Incident Browsing All Incidents.

b. Set the time selector to All.

c. Right click on the Message column header and select Filter Create filter….

d. Click on the contains radio button and type “ggreg”.

e. Click OK.

f. Be sure to remove the filter or restore default filters before navigating away from this table view.

4. Open an Aggregation incident. How can you see the members from here?

Answer:

Pull down the menu to the right of the Source Object and select either Show Analysis to view details, including members, in the Analysis Pane or Open to view the Connection details form in the Content Pane. Members appear under the Link Aggregation tab in the Connection details form.

List nodes, interfaces, and addresses in the network 1. In which workspace would you view complete lists of objects e.g. VLANs?

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Answer:

The Inventory workspace views list all nodes, interfaces, VLANs, addresses, and subnets, among other views.

2. How can you see which nodes are members of a node group in an Inventory → Nodes view?

Answer:

To see the list of nodes in a node group, open the Nodes view and select a node group instead of <Empty Group filter> at the top.

3. Can you view the nodes that are members of a node group in the Inventory workspace Node Groups view?

Answer:

Yes, select the group and select Actions → Node Group Details → Show Members.

4. How are the views in the Monitoring workspace different from the views in the Inventory workspace?

Answer:

The Inventory workspace generally addresses questions about "what's out there?" The Monitoring workspace is more useful when you want to know "what's wrong?"

5. Open the Inventory workspace Interfaces view and verify that the view is sorted by interface status in ascending order.

6. Open the view in a new window using the Show View in New Window toolbar icon.

7. In the console, open the Monitoring workspace Non-Normal Interfaces view. Why don’t all the non-normal interfaces in the inventory list appear here?

Answer:

Right-click on the Status column and Filter → Modify Filter. Notice that the “non-normal” filter actually includes only Warning, Minor, Major, and Critical. The other non-normal interfaces in the database are No Status or Unknown so they do not appear in this list.

8. Can you make the Inventory → Interfaces view look like the Monitoring → Non-Normal Interfaces view?

Answer:

a. In the Inventory view, right-click the Status column and select Filter → Create Filter. You can create a filter for all interfaces not equal to Normal, or you can duplicate the filter shown in the Monitoring view.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



b. Remove the filter.

9. You may close the extra Inventory → Interfaces window.

Simulate a major network failure 1. Verify that NNMi has cleared the simulated router down failure by navigating

to the Incident Management Open Key Incidents table view and refreshing the view’s status until all incidents are cleared.

2. Open the Scenarios folder on your access VM Desktop.

3. Double-click on the NetworkSubsetDown.bat script to execute it.

4. While NNMi detects and analyzes the simulated failure symptoms, complete additional exercises below.

View object details 1. Double-click the switch-01 icon in the All Sites map.

a. What is its status?

Answer:

It is Normal. The Status is visible on the Nodes list, in the Node Summary area of the Analysis Pane and in the Basics area of the Node details page.

b. When did the node become Normal?

Answer:

Select the Status tab and review the Status History, or look at the Status Last Modified value under the Details tab of the Analysis Pane.

c. What is the status of each address and interface?

Answer:

Look at the Interfaces tab and the IP Addresses tab of the node details form.

d. What is the status of the SNMP agent?

Answer:

Look in the Basics → SNMP Agent State section of the node details form.

e. Does the device have outstanding incidents?

Answer:

Select the Incidents tab. Look or filter for any incidents not in a Closed lifecycle state. (If you filter, remove the filter before closing the node details form.)

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



You can also look at the summary of Incidents under the Node Summary in the Analysis pane. Look for the number of Open incidents.

f. What conclusions has NNMi drawn from this information?

Answer:

Select the Conclusions tab.

Check the status and configuration of a device Ensure the collected information for the node is up-to-date.

Answer:

IFrom the Node Details page or the Nodes table view, select Actions → Polling → Status Poll for switch-01. You may also want to do a Configuration Poll.

Launch and interpret neighbor maps 1. Which devices could be affected if switch-01 failed?

Answer:

a. Select switch-01, then select Actions Maps Layer 2 Neighbor View.

b. Set the Number of Hops to 2.

c. Select switch-01, then select Actions Maps Layer 3 Neighbor View.

d. Set the Number of Hops to 2. How and why does this differ from the Layer 2 view?

2. Click the squares (Layer 2) or hexagons (Layer 3) around the nodes in each type of neighbor view. How does the information vary in the ‘Analysis Pane’.

Answer:

In the Layer 2 Neighbor view, they are interfaces and provide interface information. In the Layer 3 view, they are IP addresses.

3. Click the lines in each type of neighbor view. How does the information vary? (Especially notice the thick line on the Layer 2 Neighbor view between switch-01 and switch-04.)

Answer:

On the Layer 2 Neighbor view, lines represent connections with status and details. Thick lines indicate aggregated links and show bandwidth and availability.

On the Layer 3 view, lines represent subnets and do not carry status, but have details if you open them. Note that switch-01 and switch-04 are not shown as logically connected in the Layer 3 view.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



4. Click nodes, connectors, and lines in each neighbor view to see the type of information available in the Analysis Pane.

5. In the database history, there are incidents relating to a temporary failure on ROUTER-03. It is not currently failing, but you can view the history. Look at the details for a node directly connected to the node with the failure. What status do its interfaces show? Does it have any related incidents?

Answer:

For details, double click the neighboring node in a Layer 2 map view. View the Interfaces tab and the Incidents tab. In a production environment, the interface connected to a down node would show Operational Status Down.

6. How can you find out more about interfaces connected to the failed node?

Answer:

Click the interface icon on the neighboring node.

7. Close the neighbor map views and any detail forms.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Identifying the root cause of a major network outage. 1. Verify that NNMi has detected the simulated major network failure by

navigating to the Network Overview topology map and refreshing the map’s status until you see that ROUTER-03, ROUTER-05 and switch-01 are in Critical status and that other nodes in the shadow of the ROUTER-03 and ROUTER-05 failures are in Unknown status.

2. From the Network Overview topology map, what appears to be the root cause of the network outage?

Answer:

After several minutes the network overview map should resemble below. ROUTER-03 and ROUTER-05 are critical and most of the devices to the other side of them are unknown. This indicates that the ROUTER-03 and ROUTER-05 failures are the root causes for this network outage.

3. Open the Open key Incidents view.

4. If needed, wait for incidents to appear.

5. What incidents were generated?

Answer:

Node down incidents were generated for ROUTER-03 and switch-01, and a node or connection down incident was generated for ROUTER-05.

6. Select the incident and select Actions → Maps → Layer 2 Neighbors.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



7. Why does switch-01have a Critical status instead of Unknown like switch-02 and the other switches?

Answer:

The Critical status and node down incident for switch-01 are the result of switch-01 being in the Important Nodes node group.

Invoke troubleshooting tools 1. The t1-centos-01 node shows Unknown status. Can you ping the device?

Answer:

a. Select the device either in the graphical view or in the table, and select Actions → Node Access → Ping (from server). Ping reports that the node is unreachable.

2. How often is the device polled?

Answer:

a. Select the device either in the graphical view or in the table, and select Actions → Configuration Details → Monitoring Settings.

3. Close all windows other than the main console window.

4. Clear the simulated network failure by executing the NetworkSubsetUp.bat script from the Scenarios folder on your access VM Desktop.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

For HP Internal and Partners Use Only. 2010 - 2013 Hewlett-Packard Development Company, L.P.. 5-1

Lab 5 - Troubleshoot Using MIBs Exercises Display MIB data with SNMP line graphs


2. Open the Topology Map for All Sites.

3. Click on the link between ‘rswitch-01’ and ‘ROUTER-01’. Click the Connection tab in the ‘Analysis Pane’ to see the name of the connected interface on ‘ROUTER-01’.

4. Select rswitch-01. What graphs are available under Actions → Graphs?

5. Based on the device profile for rswitch-01, see which vendor graphs are available.

6. Select node ROUTER-01 and start a graph of the bytes sent and received for the device.

7. How many interfaces’ data is displayed by default?

8. Mouse-over each interface in the legend to determine the 2 interfaces with the most traffic.

9. Make the grapher show only the lines for those 2 interfaces which should include the lines for the interface to rswitch-01.

10. Change the polling interval to 5 seconds.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Lab 5 - Troubleshoot Using MIBs Network Node Manager (NNMi) 9.1x : How to Use, Level 320


11. Close the graph window.

12. Change the grapher defaults to poll every 30 seconds and display 5 lines.

13. Open the Interface Octets graph for ROUTER-01 and compare it with your first graph to see how the new defaults affect the layout.


Use the MIB Browser to access information 1. Select rswitch-01 from the view and use the Actions → Browse MIB to access

the following information: (Tools → MIB Browser requires you to type in the node name.)

a. What is the system name?

b. How many interfaces are there?

c. What information is available for each interface?

d. What are the multiple “listings” for these variables? Explain their relationship to the MIB structure.

e. List all the variables for interface 1.

f. What are the shown values for ifOperStatus?

g. What MIBs are supported by this ProCurve switch?

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Network Node Manager (NNMi) 9.1x : How to Use, Level 320 Lab 5 - Troubleshoot Using MIBs


h. Notice that the MIB names are links. What happens when you click on IP-MIB?

i. Find the numeric OID in the list for ipAdEntAddr. Copy it to the clipboard.

j. Paste the OID into the MIB Browser and click Walk. (Note: if you select the whole cell when you copy, you’ll need to delete leading and trailing spaces after you paste.)

The MIB Browser translates the numeric OID to the text name because the MIB is loaded. If the MIB were not loaded, the numeric OID would be shown along with the value.

2. Close the MIB Browser.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Solutions Display MIB data with SNMP line graphs


2. Open the Topology Map for All Sites.

3. Click on the link between ‘rswitch-01’ and ‘ROUTER-01’. Click the Connection tab in the ‘Analysis Pane’ to see the name of the connected interface on ‘ROUTER-01’.

Answer:

Fa0/0

4. Select rswitch-01. What graphs are available under Actions → Graphs?

Answer:

There are groups for MIB II, RMON, Host Resources, Web requests, and vendor-specific queries.

5. Based on the device profile for rswitch-01, see which vendor graphs are available.

Answer:

The profile is for HP ProCurve. The graphs available are CPU Utilization and Memory.

6. Select node ROUTER-01 and start a graph of the bytes sent and received for the device.

Answer:

a. The number of bytes is available in the MIB objects ifInOctets and ifOutOctets.

b. On the graph menu, select MIB II → Interface Octets.

7. How many interfaces’ data is displayed by default?

Answer:

20 interfaces are listed in the legend at the top.

8. Mouse-over each interface in the legend to determine the 2 interfaces with the most traffic.

Answer:

Fa0/0 and Se0/0

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



9. Make the grapher show only the lines for those 2 interfaces which should include the lines for the interface to rswitch-01.

Answer:

a. Select File → Select Lines.

b. Uncheck all boxes other than the ones you want displayed.

c. Click OK.

10. Change the polling interval to 5 seconds.

Answer:

a. In the Polling Interval (s) box, delete the 1.

a. Notice how the shape of the graph’s line changes.


12. Change the grapher defaults to poll every 30 seconds and display 5 lines.

Answer:

• Navigate to the Configuration workspace.

• Select User Interface Configuration.

• Navigate to the Default Line Graph Settings tab.

• Provide the default settings for all Line Graphs (see the Default Line Graph Settings table).

• Click Save and Close to the User Interface Configuration form.

13. Open the Interface Octets graph for ROUTER-01 and compare it with your first graph to see how the new defaults affect the layout.

Answer:

• Check the box for the node and select Actions → Graphs → MIB II → Interface Octets.

• Note the number of interfaces on the legend.

• Note the update frequency of the graph.


Use the MIB Browser to access information. 1. Select rswitch-01 from the view and use the Actions → MIB information →

Browse MIB to access the following information: (Tools → MIB Browser requires you to type in the node name.)

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



a. What is the system name?

Answer:

The browser starts with MIB II.system selected. To see the data from that area of the MIB, click the Walk (>) button.

The sysName is mainswitch.

b. How many interfaces are there?

Answer:

The MIB Object ID for the interfaces is: .iso.org.dod.internet.mgmt.mib-2.interfaces.

The value for ifNumber is 58.

c. What information is available for each interface?

Answer:

By expanding the ifTable, you can see the list of variables that are available for each interface.

d. What are the multiple “listings” for these variables? Explain their relationship to the MIB structure.

Answer:

Each “listing” is called a MIB Instance. These instances are actually individual occurrences of the same MIB variable. In this case, there are entries, or instances, that will be present for each physical interface and each software component of each interface. The result is that when you evaluate information from the MIB regarding interfaces, you will need to know which instance is being referenced in order to know what the information is describing.

Some items will have only one occurrence of the variable. For those, the instance number is zero.

e. List all the variables for interface 1.

Answer:

• Expand ifIndex.

• Select the line for interface 1.

• Select View → MIB Table.

f. What are the shown values for ifOperStatus?

Answer:

• Select the ifOperStatus line in the list.

• Select View → QuickView.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



• See the enumerated values in the window. Values are 1 or 2.

• Close the QuickView.

g. What MIBs are supported by this ProCurve switch?

Answer:

Select Tools → List Supported MIBs.

h. Notice that the MIB names are links. What happens when you click on IP-MIB?

Answer:

The console shows the list of variables for that MIB.

i. Find the numeric OID in the list for ipAdEntAddr. Copy it to the clipboard.

j. Paste the OID into the MIB Browser and click Walk. (Note: if you select the whole cell when you copy, you’ll need to delete leading and trailing spaces after you paste.)

The MIB Browser translates the numeric OID to the text name because the MIB is loaded. If the MIB were not loaded, the numeric OID would be shown along with the value.

2. Close the MIB Browser.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.


Lab 19 - Administering NNMi Exercises

1. On your Access VM, launch Mozilla Firefox or Internet Explorer, and log in to the NNMi console as user admin with password nnm.

Concepts 1. What is the difference between NNMi processes and NNMi Services?

2. Verify the status of the processes and services from within the console.

3. From the command prompt on the NNMi server, type ovstatus –c. What do you see?

4. From the NNMi server command prompt, type ovstatus –v ovjboss. What do you see?

Audit account activity 1. While logged in as an administrator, select Tools → Sign In/Out Audit Log.

2. Review the information.

a. What users have signed in/sign out of the NNMi console?

b. What is the Client Host IP address for users that have signed into NNMi?

3. Close the window.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Lab 19 - Administering NNMi Network Node Manager (NNMi) 9.1x : How to Use, Level 320


Manage the Database 1. Archive and remove all incidents more than 1 week old.

2. Review the archived incidents.

3. Export configuration settings, make a change, and then import your original settings.

4. Perform an online backup.

NOTE: Backups can take a long time, even for a small database.

5. (Optional) Make changes to your system (such as deleting nodes or incidents) and restore the backup.

6. Review the available tools through the man pages in Help → Documentation Library.

7. Locate the Release Notes from your NNMi install location and review the known defects at the time of release.

Launch NNMi from External Portal In this series of exercises, you will use a very simple web page that launches various NNMi views.

1. From the console, select Help → NNMi Documentation Library → Integrate NNMi Elsewhere with URLs. This page contains the abstract syntax for all the URLs, which is not as useful as examples. Click the http://<host>:<port>/nnm/integrationurlsamples.jsp link in the first paragraph.

2. The section at the top is like a table of contents for the rest of the file. You can jump to areas with sample links you can cut and paste to build a web page of your own.

3. An outline for a web page has been provided for you on you Access VM at C:\Depot\MyWebPage\mywebpage.html. Double-click to open in a browser to see the appearance. The links are not yet functional.

4. Edit mywebpage.html using Notepad or Wordpad. You might want to set the View → Options to wrap text to the window size.

a. Modify the links to launch on your NNMi server. Save the file and test the links.

What does the first link launch?

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Network Node Manager (NNMi) 9.1x : How to Use, Level 320 Lab 19 - Administering NNMi


What does the second link launch?

What does the third link launch?

b. Change the first link to automatically login as oper1 (password:nnm). Test your updated link and verify you are logged in with the correct user.

c. Change the second link to show CoreRouters rather than Windows systems.

OPTIONAL

d. Add a link launching a Layer 2 Neighbor view of Router-03 in the sandbox, out to 3 hops. Use networklinks.jpg as your link image.

Hint: Use the URL Samples page to help.

e. Add a link to trace the route from the NNMi server to switch-01. Use backbone.jpg as your link image.

f. Close all your own URLs and reopen the regular console.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



Solutions 59B Concepts

1. What is the difference between NNMi processes and NNMi Services?

Answer:

Processes run at the OS level. Services run within the ovjboss process.

2. Verify the status of the processes and services from within the console.

Answer:

Select Tools → NNM Status. Close the window when you’re done.

3. From the command prompt, type ovstatus –c. What do you see?

Answer:

The output is the same as the first part of Tools → NNM Status.

4. From the command prompt, type ovstatus –v ovjboss. What do you see?

Answer:

The output is the same as the second part of Tools → NNM Status.

Audit account activity 1. While logged in as an administrator, select Tools → Sign In/Out Audit Log.

2. Review the information.

Answer:

a. What users have signed in/sign out of the NNMi console?

You should have entries for the users, admin, oper1 and oper2

b. What is the Client Host IP address for users that have signed into NNMi?

10.10.15.140 which is the IP address of your Access VM

3. Close the window.

Manage the Database 1. Archive and remove all incidents more than 1 week old.

Answer: nnmtrimincidents.ovpl -trimAndArchive -age 1 -incr weeks -u admin -p nnm

2. Review the archived incidents.

Answer:

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



The file is saved in $NnmDataDir$NNM/tmp/incidegzntArchive.txt.gz, which can be unzipped using gzip –d and then viewed as a text file.

A spreadsheet program, if available on your system, is the best way to view the incident listing (delimited by tabs).

3. Export configuration settings, make a change, and then import your original settings.

Answer:

• Make a directory to hold your settings called labsettings.

• From the command prompt, run: nnmconfigexport.ovpl -c all -f labsettings -u admin -p nnm

• Review the files in the directory where you ran the command.

• Add a new communication region from the console.

• Remove all discovery seeds from the console.

• Import your original settings by running the import command: nnmconfigimport.ovpl -f labsettings -u admin -p nnm

• Be patient. Not only is it importing your settings, it must verify all group membership of all objects in the database.

• Review regions and seeds. Verify that your recent changes were discarded. (Note that the discovery seeds are duplicates because you did not delete the corresponding nodes.)

4. Perform an online backup.

Note: backups can take a long time, even for a small database.

Answer:

• Locate or create a temp directory on your system.

• From the command prompt, type nnmbackup.ovpl -type online -target <tempDir>

• Review the results in your temp directory.

5. (Optional) Make changes to your system (such as deleting nodes or incidents) and restore the backup.

Answer:

After making changes, run nnmrestore.ovpl –force –source <tempDir\nnm-bak-timestamp>, then ovstart. You will have to sign into the console again.

6. Review the available tools through the manpages in Help → Documentation Library.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



7. Locate the Release Notes from your NNMi install location and review the known defects at the time of release.

60BLaunch NNMi from External Portal In this series of exercises, you will create a very simple web page that launches various NNMi views.

1. From the console, select Help → NNMi Documentation Library → Integrate NNMi Elsewhere with URLs. This page contains the abstract syntax for all the URLs, which is not as useful as examples. Click the http://<host>:<port>/nnm/integrationurlsamples.jsp link in the first paragraph.

2. The section at the top is like a table of contents for the rest of the file. You can jump to areas with sample links you can cut and paste to build a web page of your own.

3. An outline for a web page has been provided for you on you Access VM at C:\Depot\MyWebPage\mywebpage.html. Double-click to open in a browser to see the appearance. The links are not yet functional.

4. Edit mywebpage.html using Notepad or Wordpad.

a. Modify the links to launch on your NNMi server. Save the file and test the links.

Answer:

• Change all occurrences of href=<yourhost.domain.com> to refer to your actual fully qualified hostname, including the :<PORT> if necessary in your environment. (What happens if you use a simple hostname instead of the FQDN?)

• Save the HTML file.

• From the folder view, double-click the HTML file.

• Test the links on the web page.

The first link launches the NNMi console.

The second link launches a node group map of Microsoft Windows Systems.

The third link launches a line graph showing Utilization for 3 interfaces on ROUTER-01.

• Close the extra NNM windows.

b. Change the first link to automatically login as oper1 (password:nnm). Test your updated link and verify you are logged in with the correct user.

Answer:

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.



• Append &j_username=oper1&j_password=nnm to the href link.

• Save the file and refresh the browser page. Test the link.

c. Change the second link to show CoreRouters rather than Windows systems.

Answer:

• Change the name=Microsoft+Windows+Servers to name=CoreRouters.

• Save the file and refresh the browser page. Test the link.

•

OPTIONAL: d. Add a link launching a Layer 2 Neighbor view of Router-03 in the

sandbox, out to 3 hops. Use networklinks.jpg as your link image.

Hint: Use the URL Samples page to help.

Answer:

• On the URL Samples page click the link for Neighbor Views.

• Click the string for Layer2Neighbors. Edit the URL to refer to Router-03.

• Set the hops to 3.

• Test the URL, then copy it into your HTML file.

• Save the file and refresh the browser page.

• Test the link.

e. Add a link to trace the route from the NNMi server to switch-01. Use backbone.jpg as your link image.

Answer:

• On the URL Samples page click the link for Tools.

• Click the string for traceroute with node name, and change the URL to point to switch-01.

• Test the URL, then copy it into your HTML file.

• Save the file and refresh the browser page.

• Test the link.

f. Close all your own URLs and reopen the regular console.

Reus

ed w

ith p

erm

issi

on o

f HP

Softw

are

Educ

atio

n. D

o N

ot D

istri

bute

to C

usto

mer

s.

Documents

NNMi9-1x HowToUse LabGuide