IBM IP Edition Version 4 Release 2 Network Manager Network Visualization Setup Guide
Annonce
Annonce
Network Manager IP Edition
Version 4 Release 2
Network Visualization Setup Guide
IBM
R4.2 E4
Network Manager IP Edition
Version 4 Release 2
Network Visualization Setup Guide
IBM
R4.2 E4
Note
This edition applies to version 4.2 of IBM Tivoli Network Manager IP Edition (product number 5724-S45) and to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2006, 2017.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
About this publication . . . . . . . . v
What this publication contains .
Support and community information .
Conventions used in this publication .
Chapter 1. Administering the GUI framework . . . . . . . . . . . . . . 1
Process for planning and setting up the console .
Working with dashboards or pages .
Creating proportional layout dashboards .
Editing dashboard content and layout .
Creating navigation icons and folders .
Editing the properties of a dashboard, folder, or external URL .
Deleting custom dashboards and folders.
Restoring system dashboards, folders, and external URLs .
List of Network Manager widgets .
Event information for Network Manager widgets 15
Chapter 2. Administering network views . . . . . . . . . . . . . . . 17
Access configuration for network view collections 18
Creating network view containers .
Creating standard network views .
Creating dynamic network views .
Roles required to copy and move network views 63
Configuring connectivity types .
Enabling custom or unassigned views .
Enabling visualization of logical groups .
Customizing line thickness in topology maps .
Deploying pre-configured network views .
Making a pre-configured template available to operators .
Creating and deploying network views from templates automatically .
© Copyright IBM Corp. 2006, 2017
Chapter 3. Administering network view bookmarks . . . . . . . . . . . . . 87
About network view bookmarks .
Creating network view bookmarks .
Editing network view bookmarks .
Adding a network view to a bookmark .
Removing a network view from a bookmark .
Deleting a network view bookmark .
Chapter 4. Configuring tools and menus . . . . . . . . . . . . . . . 93
XML elements and attributes for defining context menus .
Creating an executable WebTools tool.
Changing the output of a WebTools tool .
Creating tools for context menus .
Adding reports to context menus .
Adding CGI scripts to context menus .
Configuring scope of the Show Connectivity
Creating tools that open the MIB browser .
XML elements and attributes for defining tools 106
Defining context filters for tools and menus .
XML attributes for defining context filters .
Defining user access for tools and menus .
XML attributes for defining security filters.
Defining variables for tools .
Chapter 5. Editing network topology 113
Topology editing and the discovery process .
Audit trail of manual changes to the topology 113
Adding devices to the topology .
Adding connections between devices .
Deleting manually added devices.
Removing connections between devices .
Chapter 6. Administering path views 121
Path trace troubleshooting table .
Interpreting detailed path trace output .
iii
Switching on path trace debugging .
Chapter 7. Configuring geographical views . . . . . . . . . . . . . . . 129
Scoping and filtering geographical views .
Enabling regional aggregation for geographical views .
Configuring event status for geographical views 131
Configuring the appearance of geographical views 132
Integrating geographic views with other widgets 132
URL parameters for geographical maps .
Chapter 8. Configuring non-English language settings for network visualization . . . . . . . . . . . . 139
Appendix. Network Manager glossary 141
Notices . . . . . . . . . . . . . . 145
Index . . . . . . . . . . . . . . . 149
iv
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
About this publication
IBM Tivoli Network Manager IP Edition provides detailed network discovery, device monitoring, topology visualization, and root cause analysis (RCA) capabilities. Network Manager can be extensively customized and configured to manage different networks. Network Manager is tightly integrated with IBM Tivoli
Netcool/OMNIbus. When installed together with the IBM Netcool Operations
Insight infrastructure and operations management solution, then Network Manager is a key component within that solution, where it is also tightly integrated with
Netcool/Impact, and IBM Operations Analytics - Log Analysis. Network Manager also provides extensive reporting features, and integration with other IBM products, such as IBM Tivoli Application Dependency Discovery Manager, IBM
Tivoli Business Service Manager and IBM Tivoli Monitoring.
The IBM Tivoli Network Manager IP Edition Network Visualization Setup Guide describes how to use Network Manager to visualize your discovered network.
Intended audience
This publication is intended for network operators who are responsible for monitoring the health of the network.
IBM Tivoli Network Manager IP Edition works in conjunction with IBM Tivoli
Netcool/OMNIbus; this publication assumes that you understand how IBM Tivoli
Netcool/OMNIbus works. For more information on IBM Tivoli Netcool/OMNIbus,
see the publications described in “Publications” on page vi.
What this publication contains
This publication contains the following sections: v
Chapter 1, “Administering the GUI framework,” on page 1
Describes how to use the functions of the Web console to administer pages, folders, views, widgets, and console preference profiles.
v
Chapter 2, “Administering network views,” on page 17
Describes how to create new views or change existing network views to help network operators visualize devices.
v
Chapter 4, “Configuring tools and menus,” on page 93
Describes how to create and edit context menus, configure user access to menu items, define the context in which menus are available, and create tools that can be run from the context menus.
v
Chapter 5, “Editing network topology,” on page 113
Describes how to edit the discovered network topology by performing the following actions: adding network devices, adding connections between network devices, removing devices from the domain, and removing connections between network devices.
© Copyright IBM Corp. 2006, 2017
v
Publications
This section lists publications in the Network Manager library and related documents. The section also describes how to access IBM publications online and how to order publications.
Your Network Manager library
The following documents are available in the Network Manager library: v IBM Tivoli Network Manager IP Edition Release Notes, GI11-9354-00
Gives important and late-breaking information about IBM Tivoli Network
Manager IP Edition. This publication is for deployers and administrators, and should be read first.
v
IBM Tivoli Network Manager Getting Started Guide, GI11-9353-00
This guide describes how to set up IBM Tivoli Network Manager IP Edition after you have installed the product. This guide describes how to start the product, make sure it is running correctly, and discover the network. Getting a good network discovery is central to using Network Manager successfully. This guide describes how to configure and monitor a first discovery, verify the results of the discovery, configure a production discovery, and how to keep the network topology up to date. Once you have an up-to-date network topology, this guide describes how to make the network topology available to Network Operators, and how to monitor the network. The essential tasks are covered in this short guide, with references to the more detailed, optional, or advanced tasks and reference material in the rest of the documentation set.
v IBM Tivoli Network Manager IP Edition Product Overview, GC27-2759-00
Gives an overview of IBM Tivoli Network Manager IP Edition. It describes the product architecture, components and functionality. This publication is for anyone interested in IBM Tivoli Network Manager IP Edition.
v IBM Tivoli Network Manager IP Edition Installation and Configuration Guide,
SC27-2760-00
Describes how to install IBM Tivoli Network Manager IP Edition. It also describes necessary and optional post-installation configuration tasks. This publication is for administrators who need to install and set up IBM Tivoli
Network Manager IP Edition.
v
IBM Tivoli Network Manager IP Edition Administration Guide, SC27-2761-00
Describes administration tasks for IBM Tivoli Network Manager IP Edition, such as how to administer processes, query databases and start and stop the product.
This publication is for administrators who are responsible for the maintenance and availability of IBM Tivoli Network Manager IP Edition.
v IBM Tivoli Network Manager IP Edition Discovery Guide, SC27-2762-00
Describes how to use IBM Tivoli Network Manager IP Edition to discover your network. This publication is for administrators who are responsible for configuring and running network discovery.
v IBM Tivoli Network Manager IP Edition Event Management Guide, SC27-2763-00
Describes how to use IBM Tivoli Network Manager IP Edition to poll network devices, to configure the enrichment of events from network devices, and to manage plug-ins to the Tivoli Netcool/OMNIbus Event Gateway, including configuration of the RCA plug-in for root-cause analysis purposes. This publication is for administrators who are responsible for configuring and running network polling, event enrichment, root-cause analysis, and Event
Gateway plug-ins.
vi
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
v IBM Tivoli Network Manager IP Edition Network Troubleshooting Guide,
GC27-2765-00
Describes how to use IBM Tivoli Network Manager IP Edition to troubleshoot network problems identified by the product. This publication is for network operators who are responsible for identifying or resolving network problems.
v IBM Tivoli Network Manager IP Edition Network Visualization Setup Guide,
SC27-2764-00
Describes how to configure the IBM Tivoli Network Manager IP Edition network visualization tools to give your network operators a customized working environment. This publication is for product administrators or team leaders who are responsible for facilitating the work of network operators.
v
IBM Tivoli Network Manager IP Edition Management Database Reference,
SC27-2767-00
Describes the schemas of the component databases in IBM Tivoli Network
Manager IP Edition. This publication is for advanced users who need to query the component databases directly.
v IBM Tivoli Network Manager IP Edition Topology Database Reference, SC27-2766-00
Describes the schemas of the database used for storing topology data in IBM
Tivoli Network Manager IP Edition. This publication is for advanced users who need to query the topology database directly.
v IBM Tivoli Network Manager IP Edition Language Reference, SC27-2768-00
Describes the system languages used by IBM Tivoli Network Manager IP
Edition, such as the Stitcher language, and the Object Query Language. This publication is for advanced users who need to customize the operation of IBM
Tivoli Network Manager IP Edition.
v IBM Tivoli Network Manager IP Edition Perl API Guide, SC27-2769-00
Describes the Perl modules that allow developers to write custom applications that interact with the IBM Tivoli Network Manager IP Edition. Examples of custom applications that developers can write include Polling and Discovery
Agents. This publication is for advanced Perl developers who need to write such custom applications.
v IBM Tivoli Monitoring for Tivoli Network Manager IP User's Guide, SC27-2770-00
Provides information about installing and using IBM Tivoli Monitoring for IBM
Tivoli Network Manager IP Edition. This publication is for system administrators who install and use IBM Tivoli Monitoring for IBM Tivoli
Network Manager IP Edition to monitor and manage IBM Tivoli Network
Manager IP Edition resources.
Prerequisite publications
To use the information in this publication effectively, you must have some prerequisite knowledge, which you can obtain from the following publications: v IBM Tivoli Netcool/OMNIbus Installation and Deployment Guide, SC23-9680
Includes installation and upgrade procedures for Tivoli Netcool/OMNIbus, and describes how to configure security and component communications. The publication also includes examples of Tivoli Netcool/OMNIbus architectures and describes how to implement them.
v IBM Tivoli Netcool/OMNIbus User's Guide, SC23-9683
Provides an overview of the desktop tools and describes the operator tasks related to event management using these tools.
v IBM Tivoli Netcool/OMNIbus Administration Guide, SC23-9681
About this publication
vii
Describes how to perform administrative tasks using the Tivoli
Netcool/OMNIbus Administrator GUI, command-line tools, and process control.
The publication also contains descriptions and examples of ObjectServer SQL syntax and automations.
v IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, SC23-9684
Contains introductory and reference information about probes and gateways, including probe rules file syntax and gateway commands.
v IBM Tivoli Netcool/OMNIbus Web GUI Administration and User's Guide SC23-9682
Describes how to perform administrative and event visualization tasks using the
Tivoli Netcool/OMNIbus Web GUI.
Accessing terminology online
The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology Web site at the following Web address: http://www.ibm.com/software/globalization/terminology
Accessing publications online
IBM posts publications for this and all other products, as they become available and whenever they are updated, to the IBM Knowledge Center Web site at: http://www.ibm.com/support/knowledgecenter/
Network Manager documentation is located under the Cloud & Smarter
Infrastructure
node on that Web site.
Note:
If you print PDF documents on other than letter-sized paper, set the option in the File > Print window that allows your PDF reading application to print letter-sized pages on your local paper.
Ordering publications
You can order many IBM publications online at the following Web site: http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss
You can also order by telephone by calling one of these numbers: v In the United States: 800-879-2755 v In Canada: 800-426-4968
In other countries, contact your software account representative to order IBM publications. To locate the telephone number of your local representative, perform the following steps:
1.
Go to the following Web site: http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss
2.
Select your country from the list and click Go. The Welcome to the IBM
Publications Center page is displayed for your country.
3.
On the left side of the page, click About this site to see an information page that includes the telephone number of your local representative.
viii
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Accessibility
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully.
Accessibility features
Network Manager includes the following major accessibility features: v Operations that use a screen reader.
Network Manager uses IBM Installation Manager to install the product. You can read about the accessibility features for IBM Installation Manager at http://www-01.ibm.com/support/knowledgecenter/SSDV2W/ im_family_welcome.html.
Network Manager uses the latest W3C Standard, WAI-ARIA 1.0
(http://www.w3.org/TR/wai-aria/), to ensure compliance to US Section 508
(http://www.access-board.gov/guidelines-and-standards/communications-and-it/ about-the-section-508-standards/section-508-standards), and Web Content
Accessibility Guidelines (WCAG) 2.0 (http://www.w3.org/TR/WCAG20/). To take advantage of accessibility features, use the latest release of your screen reader in combination with the latest web browser that is supported by this product.
The Network Manager online product documentation in IBM Knowledge Center is enabled for accessibility. The accessibility features of IBM Knowledge Center are described at https://www.ibm.com/support/knowledgecenter/v1/content/about/ releasenotes.html#accessibility.
Keyboard navigation
This product uses standard navigation keys.
Interface information
Network Manager provides the following features suitable for low vision users: v All non-text content used in the GUI has associated alternative text.
v Low-vision users can adjust the system display settings, including high contrast mode, and can control the font sizes using the browser settings.
v Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Network Manager provides the following features suitable for photosensitive epileptic users: v The Network Manager user interfaces do not have content that flashes more than two times in any one second period.
The Network Manager web user interface includes WAI-ARIA navigational landmarks that you can use to quickly navigate to functional areas in the application.
Extra steps to configure Internet Explorer for accessibility
If you are using Internet Explorer as your web browser, you might need to perform extra configuration steps to enable accessibility features.
About this publication
ix
To enable high contrast mode, complete the following steps:
1.
Click Tools > Internet Options > Accessibility.
2.
Select all the check boxes in the Formatting section.
If clicking View > Text Size > Largest does not increase the font size, click Ctrl + and Ctrl -.
Related accessibility information
In addition to standard IBM help desk and support websites, IBM has established a TTY telephone service for use by deaf or hard of hearing customers to access sales and support services:
TTY service
800-IBM-3383 (800-426-3383)
(within North America)
IBM and accessibility
For more information about the commitment that IBM has to accessibility, see IBM
Accessibility (www.ibm.com/able).
Tivoli technical training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site: http://www.ibm.com/software/tivoli/education
Support and community information
Use IBM Support, Service Management Connect, and Tivoli user groups to connect with IBM and get the help and information you need.
IBM Support
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need:
Online
Go to the IBM Software Support site at http://www.ibm.com/software/ support/probsub.html and follow the instructions.
IBM Support Assistant
The IBM Support Assistant (ISA) is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. The ISA provides quick access to support-related information and serviceability tools for problem determination. To install the ISA software, go to http://www.ibm.com/software/support/isa
Tivoli User Community
The Tivoli User Community is an independent, user-run membership organization that provides Tivoli users with information to assist them in the implementation of
Tivoli Software solutions. Through these groups, members can share information and learn from the knowledge and experience of other Tivoli users. Access the link
x
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
for the Tivoli Users Community at www.tivoli-ug.org.
Service Management Connect
Access Service Management Connect at https://www.ibm.com/developerworks/ servicemanagement/nsa/index.html. Use Service Management Connect in the following ways: v Become involved with transparent development, an ongoing, open engagement between other users and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code.
v Connect one-on-one with the experts to collaborate and network about Tivoli and the community.
v Read blogs to benefit from the expertise and experience of others.
v
Use wikis and forums to collaborate with the broader user community.
Conventions used in this publication
This publication uses several conventions for special terms and actions and operating system-dependent commands and paths.
Typeface conventions
This publication uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text
Italic
v Citations (examples: titles of publications, diskettes, and CDs v Words defined in text (example: a nonswitched line is called a
point-to-point line) v Emphasis of words and letters (words as words example: "Use the word
that to introduce a restrictive clause."; letters as letters example: "The
LUN address must start with the letter L.") v New terms in text (except in a definition list): a view is a frame in a workspace that contains data.
v Variables and values you must provide: ... where myname represents....
Monospace
v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v
Text that the user must type v Values for arguments or command options
Bold monospace
About this publication
xi
v Command names, and names of macros and utilities that you can type as commands v
Environment variable names in text v Keywords v Parameter names in text: API structure parameters, command parameters and arguments, and configuration parameters v Process names v Registry variable names in text v Script names
Operating system-dependent variables and paths
This publication uses environment variables without platform-specific prefixes and suffixes, unless the command applies only to specific platforms. For example, the directory where the Network Manager core components are installed is represented as NCHOME.
On UNIX systems, preface environment variables with the dollar sign $. For example, on UNIX, NCHOME is $NCHOME.
xii
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Chapter 1. Administering the GUI framework
Use the functions of the Dashboard Application Services Hub within Jazz for
Service Management to administer pages, folders, views, widgets, and console preference profiles.
For more detailed information about Dashboard Application Services Hub, see the
Jazz for Service Management Knowledge Center, at http://www-01.ibm.com/ support/knowledgecenter/SSEKCU/welcome.
Console layout
The layout of the console user interface has these major elements.
Figure 1. Console layout
▌1▐ Navigation bar
At the top of the navigation section, use the Search to quickly find particular tasks. Search results are dynamically returned and filtered as you type. A Favorites icon provides access to any day-to-day tasks that you may add to favorites. The rest of this area displays a set of navigation
© Copyright IBM Corp. 2006, 2017
1
icons used for accessing product-specific content. The icons shown in the navigation pane are only those to which you have access.
▌2▐ Configuration area
In this area, icons are provided for user functions, view selection, and console configuration, as follows: v The User icon is used for logging out and changing your password.
v The Views icon is used to change views. Views dictate which product tasks, dashboards or pages, are displayed and which pages or dashboards open automatically.
v The Configuration icon is used to access console administration and user management functions.
v The Help icon provides access to help contents for the console and any installed products and to find details of the console version, as well as details for installed products. You can also access the Dashboard
Application Services Hub community through the Help icon, where you will find multimedia tutorials and information about upcoming releases.
▌3▐ Taskbar
Displays tabs to move between open pages or dashboards. The taskbar allows you to work on different dashboards without closing a dashboard or losing unsaved data. For example, if you are working on a form on
Dashboard A, you can open an application on another dashboard to gather information about a particular resource. Then you can complete the form on Dashboard A without losing any unsaved data that you may have already entered. Multiple dashboards can be opened at one time, but only one of the dashboard or pages has focus (current page). If a large number of dashboards are open, you can use the list arrow on the right of the taskbar to show a list of the open dashboards. Depending on your role, the taskbar may also contains a number of additional administration icons for editing the current dashboard or creating new ones.
▌4▐ Content area
Displays the current dashboard that you are working on. The dashboard, contains one or more Web applications or widgets. Pages that contain multiple related widgets are generally called dashboards and invariably include a number of integrated widgets.
Setting up the console
For a new console installation, the console administrator needs to create the experience for users when they log into the console. This task involves working through the console content from the basic building blocks to the high level organization and presentation of these resources so that users can quickly find what their way around and perform their tasks efficiently.
To get started setting up the console, you should already be familiar with the concepts and characteristics of the layout. You should take time navigating through the console to become familiar with the widgets, dashboards, views, roles, and preference profiles that are provided. As you work with the console, you will create some of these resources to suit your organization's needs.
Understanding the structure of the console
Access to each level in the console organization is assigned based on the users' roles. Keep each role in mind when planning how to structure the console content.
2
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Content in the console is composed of widgets. Access to each dashboard, and to each widget on each dashboard, is assigned to users based on their defined role.
Each dashboard is accessed from the navigation bar, either from the console root or they can be grouped into folders. The hierarchical structure of the navigation affects how quickly users can find a dashboard and work with the widgets on that dashboard.
Folders and dashboards can be assembled into views that the user can select from the View icon in the navigation bar. Each view can include dashboards that are initially launched when the view is selected.
Finally, you can define a set of preferences, called a preference profile, that determines what views are available to each role, and whether the navigation pane should be displayed.
Process for planning and setting up the console
Setting up the console is an iterative process. While you should initially start with organizing dashboards, roles, and widgets and work your way up to setting up views and preference profiles, over time you will need to come back to any of these steps to make changes.
1.
Define your console users and what tasks they perform. Console users are assigned to roles, which are used to determine what tasks they can perform. As you assess the users' tasks, think about how these roles will be defined.
Consider how the community of users will be assigned to different roles and whether there are any existing roles that you can use, or if you need to create new roles.
Roles can be created without assigning access to any resources. This step can be performed later.
2.
Review the content. Users' tasks are performed using widgets on dashboards.
You need to understand what widgets are available and how they will be used to perform these tasks. For each widget, determine which roles should have access and which roles should be restricted.
3.
Create a navigation structure of dashboards and folders. Determine which dashboards are currently used to access the widgets. Are these dashboards sufficient for the roles that you have defined, or do you need to create new dashboards? For existing dashboards, do you need to add or remove any widgets or change the way they are arranged on the dashboard? Consider that multiple roles can access a dashboard with different access to the widgets on that dashboard.
Review the folders in the navigation and the dashboards that are contained in these folders. Do these folders help the users find their content? Do you need to edit existing folders or create new folders? Should you move any dashboards between folders? What folders or dashboards should be hidden for each role?
4.
Organize the content and navigation into views. Determine which navigation folders and dashboards have a related purpose for each role. You can define one or more views for each role, and even make a single view appear differently between roles based on access control. Each view can also include one or more dashboards that are launched when the view is selected. Each of these options is provided to help remove other content and dashboards that can distract users.
5.
Define the presentation for each role Determine which views should be available to users in a role. You can assign one preference profile per role.
Chapter 1. Administering the GUI framework
3
6.
Test the console for each role. Create a test user for each role. Log into the console as each user and verify the use cases.
v
The view selection list shows only the views to which the role has access and as defined by the preference profile.
v Each view shows only the navigation nodes and startup dashboards allowed for that role.
v Each folder shows only the dashboards allowed for that role.
v Each dashboard launched in the navigation bar shows only the widgets allowed for that role.
v If the role has Editor access to a dashboard, the Edit Page option is available in the Page Actions selection list. This option is not shown if the user's role does not have Editor access.
v
Each dashboard shows only the widgets allowed for that role.
v
The widget title bar provides an icon that provides access to two options, a Personalize option, and an Edit option. The Personalize option is available, if the user role has Privileged User access. The Edit option is available if the user role has Editor access. Otherwise, neither of these options are available.
Go back and make corrections as indicated by the results of your testing.
7.
Move the console to production use. Assign roles to actual users and notify the user community that the console server is ready for use.
Working with dashboards or pages
Console content is composed of dashboards, folders, and external URLs. Such content is accessed through icons and submenus in the navigation bar.
Field descriptions
This section describes the fields and controls in the main panel of Pages.
Selects all items displayed in the table for deletion. If you are displaying only a filtered set of items, only those items are selected. You can deselect specific items before actually deleting.
Deselects all items displayed in the table.
New Page
New Folder
Opens a panel for creating a new folder.
Delete
Immediately deletes all selected items in the list. Only Custom resource types can be deleted.
Filter
Type in this field to quickly find an item in the table. This field is useful when there are a large number of items to look through.
Select
Selects or deselects a single item in the table.
Name
Type
Unique Name
4
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Click > Pages to create, edit, and delete dashboards and folders for the console navigation. You can also edit external URLs that are launched from the navigation bar. You cannot create URLs in the console. Instead, URLs are created when an application is deployed to the console that includes the URL node in its descriptors.
You can create dashboards with any of the following layouts: v Proportional
With proportion layout, widgets can be positioned anywhere to create a non-scrolling dashboard. Proportional layout supports overlaying widgets.
Widgets proportionally resize based on the resolution of the screen being used.
v
Freeform
With freeform layout, widgets can be positioned anywhere on a dashboard, including over another widget. Freeform dashboards scroll horizontally or vertically, depending on the size of screen being used.
v Fluid
With fluid layout, widgets reorder their position on the dashboard depending on the type of screen being used. This layout type supports vertical scrolling only, that is, when a screen is narrow widgets are displayed vertically. This layout type is the most flexible layout in relation to mobile device screens, for example, tablets and smart phone screens. Fluid layout does not support the overlaying of widgets.
Creating proportional layout dashboards
To create a proportionally laid out dashboard, you must first set the properties of the dashboard, including the dashboard name and its location in the navigation bar. You must then select widgets for the dashboard. All dashboards that are created in the console have a resource type of “Custom”.
Important:
Manager access to the Pages page is required in order to be able to create and delete dashboards or folders.
To create a proportional layout dashboard for testing purposes:
1.
To display the Create New Page page: v
In the taskbar, click .
v In the navigation bar, click click New Page.
> Pages and in the Dashboards page,
A Page Settings page is displayed.
2.
In the Page name field, provide a descriptive name for the dashboard and in the Page location field indicate where you want the dashboard to be displayed in the navigation pane. Consider the content on the dashboard and how users will find that content by looking for the dashboard name in the navigation pane.
3.
Select the Proportional option for the dashboard layout.
4.
Optional: Click the Optional Setting label and associate one or more roles with the new dashboard and set the level of access for each role.
Chapter 1. Administering the GUI framework
5
5.
Click OK. The taskbar tab is updated with the name of the new dashboard and a window is displayed that includes a widget palette from which you can select widgets for your new dashboard.
6.
The widget palette can contain widgets or widget catalogs. Widget catalogs are used to organize widgets into logical groups in environments where many widgets are available to be added to a dashboard. You can use the search field to filter the number of items displayed, or you can use the navigation arrows to scroll through the items. To remove a search filter, clear the search field and click Search. You can hover over a widget in the palette to view more information about it.
7.
To add content to your dashboard, drag items from the content palette to the content area below the palette, using the grid lines to assist you in positioning each widget.
Tip:
As you add items you can configure display settings through the icon, for example, you can change skin and a widget's position on the dashboard, that is, whether it is displayed in front of or behind other content.
You can also resize a widget.
8.
To resize a widget, click anywhere near one of its borders to display resizing handles. Use the handles to resize the widget. In this mode, you can also click near the center of the widget and drag it to any position on the dashboard.
9.
Continue to add widgets until the dashboard is complete.
10.
Click Save to commit your changes.
The new proportional layout dashboard is displayed. Users with “editor” access to the dashboard can subsequently edit the dashboard to add more content, rearrange existing content, as well as replace and remove content.
Make sure that the roles with access to this dashboard also have access to the widgets that are on the dashboard. You can also edit the new dashboard to customize its settings, for example, its dashboard persistence settings or text direction settings.
Editing dashboard content and layout
Console content is composed of dashboards, folders, and external URLs. Such content is accessed through icons and submenus in the navigation bar.
v Console Settings > Pages to create, edit, and delete dashboards and folders for the console navigation. You can also edit external URLs that are launched from the navigation bar. You cannot create URLs in the console. Instead, URLs are created when an application is deployed to the console that includes the URL node in its descriptors.
You can create dashboards with any of the following layouts:
Proportional
With proportion layout, widgets can be positioned anywhere to create a non-scrolling dashboard. Proportional layout supports overlaying widgets. Widgets proportionally resize based on the resolution of the screen being used.
Freeform
With freeform layout, widgets can be positioned anywhere on a dashboard, including over another widget. Freeform dashboards scroll horizontally or vertically, depending on the size of screen being used.
Fluid
With fluid layout, widgets reorder their position on the dashboard
6
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
depending on the type of screen being used. This layout type supports vertical scrolling only, that is, when a screen is narrow widgets are displayed vertically. This layout type is the most flexible layout in relation to mobile device screens, for example, tablets and smart phone screens. Fluid layout does not support the overlaying of widgets.
v This section describes the fields and controls in the main panel of Pages.
Select all
Selects all items displayed in the table for deletion. If you are displaying only a filtered set of items, only those items are selected. You can deselect specific items before actually deleting.
Deselect all
Deselects all items displayed in the table.
New Page
Opens a panel for creating a new page.
New Folder
Opens a panel for creating a new folder.
Delete
Immediately deletes all selected items in the list. Only Custom resource types can be deleted.
Filter
Type in this field to quickly find an item in the table. This field is useful when there are a large number of items to look through.
Select
Selects or deselects a single item in the table.
Name
Displays the title of the page as it is shown in the navigation.
Type
Displays the type of page.
Unique Name
Displays the string used by the system to uniquely identify the page or folder.
Related reference
:
“List of Network Manager widgets” on page 11
You can use Network Manager widgets for creating pages.
Access to online help
Online help is topic-oriented, procedural, or reference information that you can access from the product installation, to assist you in the use of the product and to complete tasks.
You can search and browse within the online help to troubleshoot and find solutions for tasks you want to perform. Access to online help, as users work with the product, helps users to expand their knowledge about the product. You can access the online help from either the top-level online help or from the context-sensitive online help.
v Top-level online help. This online help displays a table of contents view of all available online help topics, for all products that are installed into your instance of Dashboard Application Services Hub.
v Context-sensitive online help. This online help links directly to documentation about the current panel. From this panel help topic, you can browse throughout the online help. After a product installation, this online help is disabled by default as the containing widget title bars are also disabled by default.
Chapter 1. Administering the GUI framework
7
Accessing the top-level online help
The top-level online help displays a table of contents view of all online help topics.
Access to the top-level help is enabled by default. Within the Contents tab of the top-level help, you can expand, collapse, and select topics to browse around all topics within the online help. Complete the following steps to access the top-level online help.
1.
Within the Dashboard Application Services Hub navigation bar, select the Help icon . The Help menu displays.
2.
From the Help menu, select InfoCenter. The Help System window opens.
3.
Within the Help System window, select Using Network Manager.
The top-level online help for Network Manager is displayed.
v Within the Contents tab of the top-level help, expand, collapse, and select topics to browse around all topics within the online help.
v Enter some text in the Search field to find any related online help.
v Use the available icons in the Help System toolbar to print or bookmark topics, or to move forwards and backwards between topics.
Enabling access to context-sensitive online help
An administrator can enable access to context-sensitive online help. This online help enables users to directly access documentation that is related to the current panel. From this panel help topic, users can browse throughout the online help.
After a product installation, this context-sensitive online help is disabled by default as the containing widget title bars are also disabled by default. If an administrator enables context-sensitive online help, users can directly access documentation that is related to the current panel. After access to context-sensitive online help is enabled, you can browse through all documentation topics within the online help.
Complete the following steps to enable access to context-sensitive online help.
This access to context-sensitive online help might not work for some pages as the
GUI might pre-date Dashboard Application Services Hub, or there might be no context-sensitive online help for the page.
1.
As the administrator user itnmadmin, display the view where you want to enable access to the online help. For example, if you want users to be able to access in-context online help for the Network Hop View, open the Network
Hop View. Click the Incident icon and select Network Availability > Network
Hop View
.
2.
In the views title bar, click the Page Actions icon .
3.
Select Edit Page. The view changes to show a view toolbar with a series of buttons and a widget palette.
4.
Within a view, there can be one or more widgets. Select the widget for which you want to enable access to the context-sensitive online help.
5.
In the view toolbar, select Widget > Skin > Default. The widget title bar for the widget is displayed and the Help icon is available within the widget title bar.
6.
In the view toolbar, select Save and Exit.
The widget title bar that contains the Help icon displays and access to context-sensitive online help for the selected widget is enabled for all users.
8
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
v
To access context-sensitive online help, click the Help icon widget title bar.
within the v To enable access to context-sensitive online help for another widget, repeat all the steps.
v To browse to other topics within the online help, either expand the icons in the navigation pane or enter text in the Search field.
v To disable access to context-sensitive online help for a widget, go to the view toolbar and select Widget > Skin > Default no title
Creating navigation icons and folders
Navigation icons are used as top-level folders to logically group nodes in the navigation bar. All navigation icons that are created in the console have a resource type of “Custom”.
1.
In the navigation bar, click > Pages. A Page Settings page is displayed.
2.
Click New Folder. The properties panel for the new folder is displayed.
3.
Complete the fields in the properties panel.
a.
Provide a folder name. Optionally, you can use the String Translation button to change the support for translation of the name.
b.
Accept the default location provided or click Location to specify where you want to new folder to be located in the left navigation bar. When you click
Location
, you can simply click and drag the new folder to any area in the directory tree.
c.
If you chose to position the folder at the top level, you must select a navigation icon for it. If you located the folder under another folder, then you are not able to associate a navigation icon with the folder. For top level folders that are displayed as navigation items, their folder name is displayed as tooltip when a user moves the cursor over the icon.
4.
Click Save to save your changes and return to the Pages page.
The new folder is displayed in the summary table on the Pages page. Folders marked as empty, are not displayed in the navigation bar. Once a folder contains dashboard content, if it is a top-level folder, its icon is added to the navigation bar, otherwise it is listed as a subfolder in the location that you specified. Add other nodes to the folder by editing their location properties.
Editing the properties of a dashboard, folder, or external URL
You can edit the properties of custom and system navigation nodes, which include navigation icons, folders, dashboards, and external URLs.
Properties of a node include its display name and its location in the navigation.
You can also indicate whether multiple or only single instances of a dashboard can be launched in the console.
When changes are made to a system node, the updated system node is saved as
System - Customized . You cannot delete a system node. Instead, you can restore the system node, which deletes the custom copy of it.
You can perform the following tasks when you edit a node's properties.
v Define who can access a dashboard or external URL and the level of access
Chapter 1. Administering the GUI framework
9
v Determine which view should include the node. When the view is selected, the dashboard, folder, or URL is included in the navigation bar for that view.
v
Change the name that is displayed in the navigation bar for a node.
v Change the location of a node in the navigation bar. For example, you can group dashboards into folders.
Attention:
You cannot create URLs in the console. Instead, URLs are created when an application is deployed to the console that includes the URL node in its descriptors.
1.
Click > Pages in the navigation bar. Pages is opened displaying navigation nodes in a summary table.
2.
Locate the node that you want to edit in the table provided. Use the filter in the table to type in the node name and quickly display it.
3.
Click the link for the node provided in the Name column. The properties panel for the node is displayed.
4.
Make your changes to the node's dashboard, folder, and external URL properties.
5.
Click Save when you have finished.
The changes you made are reflected in the navigation bar.
Deleting custom dashboards and folders
You can delete only dashboards with the resource type of Custom. These are nodes created using the console.
System nodes that have been customized can be restored.
Attention:
Before deleting a dashboard or folder, consider whether any users are actively using the resource and any impacts this might have on services. If necessary, notify users in advance of any plans for changes that could affect their work.
Important:
Manager access to the Pages page is required in order to be able to create and delete dashboards or folders.
1.
Click > Pages in the navigation bar. Pages is opened displaying console navigation nodes in a summary table.
2.
Locate the node that you want to delete in the table provided. Use the filter in the table to type in the node name and quickly display it.
3.
Check the box in the Select column for the node. You can select more than one custom dashboard or folder for deletion.
4.
Click Delete. A message is displayed at the top prompting you to confirm the deletion.
5.
Click OK.
The dashboard or folder is deleted and removed from the navigation bar.
10
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Restoring system dashboards, folders, and external URLs
System nodes are always preserved with their original settings. After making changes to a system node, the changes are saved in a customized copy of the dashboard, folder, or URL. When you restore a system node, the customized copy is deleted and the original system node is restored in its place.
To delete the customized copy and restore the system node, follow these steps.
1.
Click
Pages
in the navigation bar. Pages is opened displaying navigation nodes in a summary table.
2.
Locate the node that you want to edit in the table provided. Use the filter in the table to type in the node name and quickly display it.
3.
Click the link for the node provided in the Name column. The properties panel for the node is displayed.
4.
Scroll to the bottom of the panel and click Restore.
5.
Click OK to save your changes.
You are returned to the main panel of Pages. The resource type of the node is displayed as System.
Network Manager widgets
Use this reference information to help you configure customized Network Manager pages.
The following topics provide more information on Network Manager widgets.
List of Network Manager widgets
You can use Network Manager widgets for creating pages.
The following Network Manager widgets are available to add to a page.
v Configure NCIM Database Access v Configure Poll Definitions v Configure Poll Policies v Management Database Access v
Network Discovery Configuration v Network Discovery Status v Network Hop View v Network Views v Path Views v Path View Administration v SNMP MIB Browser v SNMP MIB Graph v Structure Browser v Reporting (configures Tivoli
®
Common Reporting)
You might also see widgets from other products;.for example, the Tivoli
Netcool/OMNIbus Web GUI Event Viewer.
Chapter 1. Administering the GUI framework
11
Editable widget parameters
Use this information to understand which parameters are associated with each
Network Manager widget and how each of these parameters affects the appearance of the widget.
To modify widget parameters, refer to the information about customizing a
Dashboard Application Services Hub widget in the Jazz for Service Management information center at http://www-01.ibm.com/support/knowledgecenter/
SSEKCU/welcome.
Important:
The Network Views, Hop View, and Structure Browser widgets refresh themselves. There is no need to set a global refresh on these widgets.
The editable parameters for the Network Manager widgets are as follows.
“Monitor Configuration Poll Policy” on page 13
“Monitor Configuration Template” on page 13
“Management Database Access” on page 13
“Structure Browser” on page 13
Database Configuration
There are no editable parameters for this widget.
Discovery Configuration
There are no editable parameters for this widget.
Discovery Status
There are no editable parameters for this widget.
MIB Browser
MIB Browser
Domain
Name of the domain that the widget presents as default
Object ID
SNMP Object ID of the node for which MIB information is requested
Host
Name of the host that has where the Helper Server is running
Show Results Only?
Indicates whether only the results of the MIB query are displayed.
The default value is False.
12
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Monitor Configuration Poll Policy
There are no editable parameters for this widget.
Monitor Configuration Template
There are no editable parameters for this widget.
Management Database Access
Management Database Access
Domain
Name of the domain that the widget presents as default
Query
SQL query
Service
Name of management database on which the query is run
Show Results Only?
Indicates whether only the results of the query are displayed. The default value is False.
Structure Browser
Structure Browser
Entity ID
Entity ID of the device whose structure is being requested.
View Mode
Specifies which mode the widget loads: tree or table.
Note:
Table mode is only available when the Structure Browser is displayed as a widget.
Table Mode
Select the type of information to display within the table.
Topology HopView
Topology HopView
Domain
Name of the domain that the widget presents as default
Seed device
Pivot device around which the Network Hop View must be displayed
Hops
Number of hops to display from the pivot device
Connectivity
Type of connectivity to display in the network map; options are IP
Subnets, Layer1, Layer 2, Layer 3, PIM, and IPMRoute
Default value: IP Subnets
Layout
Layout style of the network map; options are Symmetric,
Hierarchical, Orthogonal, and Circular
Default value: Symmetric
Chapter 1. Administering the GUI framework
13
Show End Nodes?
Indicates whether to display end nodes in the map. The default value is False.
NetworkViews
Topology Network Views
Network Views Properties
Show Network Views Tree
Indicates whether to display the network view navigation tree.
Choose Default Tab
Indicates whether to show the Bookmarks or Libraries tab as the default tab.
Libraries Treetable Properties
Map ID
ID of a specific network view to be displayed in the treetable.
Bookmarks Treetable Properties
Width
Specifies the width of the columns in the Bookmarks treetable.
Hidden Columns
Provides the option to hide the Max column, which shows the maximum alert status for all devices within a network view.
Locked Columns
Provides the option to lock the Max column.
Sort Column
Specifies which column to sort on.
Sort Order
Specifies the sort order.
Path Views
Topology Path Views
Path View Properties
Show Path Views Tree
Indicates whether to display the path views navigation tree.
Path View ID
ID of the path view to be displayed.
Treetable Properties
Width
Indicates the width of the column.
Hidden Columns
Indicates whether a column should be hidden. Master columns can not be hidden.
Locked Columns
Prohibits scrolling. Master columns can not be locked.
14
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Sort Column
Specifies how the master column is to be sorted.
Sort Order
Indicates whether columns should be sorted in ascending or descending order. Parent rows are sorted first, then child rows.
Related information
:
Customizing a widget
Depending on how a widget was configured when it was created and any shared settings applied by your administrator, you can customize a widget's setting.
Event information for Network Manager widgets
Refer to this table to get information about the publish events and subscribe events for Network Manager widgets. Use this event information when you create a new custom widget and you want to wire your custom widget with an existing
Network Manager widget.
Table 1. Event information for Network Manager widgets
Widget name
Dashboard Network Views
Event type
Publish event
Event name
NodeClickedOn
Network Hop View Publish event
Subscribe event
Subscribe event
Subscribe event
NodeClickedOn
NodeClickedOn showEntity
Showdevice
Event description
Left-clicking a node on the widgets topology canvas publishes a
NodeClickedOn event that contains the
Network Manager ViewId.
Left-clicking a node on the widget's topology canvas publishes a
NodeClickedOn event that contains the
Network Manager entityId .
Internally, this NodeClickedOn event that containsentityId converts to a showDevice event (which contains
NmosObjInst , NmosEntityId, and so on) and displays the device as a node on the widget's topology canvas based on the entityId
Similar to the description for the
Network Hop View subscribe event, for NodeClickedOn.
Similar to the description for the
Network Hop View subscribe event, for NodeClickedOn.
Chapter 1. Administering the GUI framework
15
Table 1. Event information for Network Manager widgets (continued)
Widget name
Network View
Network Views
Path Views GUI
SNMP MIB Grapher
SNMP MIB Browser
Structure Browser
Event type
Subscribe event
Publish event
Publish event
Event name
NodeClickedOn showEvents showEntity
Event description
Subscribes to a NodeClickedOn event and displays device structure based on the events entityId attribute.
Right-clicking a node on the widget's topology canvas and choosing Show
Events
publishes a showEvents event that contains Transient Events Filter
name and the Network Manager
ViewId.
Right-clicking a node on the widget's topology canvas and choosing Show
Device Structure
publishes a showEntity event that contains the
Network Manager Entity Id.
Not applicable. This widget does not publish or subscribe to events.
Not applicable. This widget does not publish or subscribe to events.
Not applicable. This widget does not publish or subscribe to events.
Not applicable. This widget does not publish or subscribe to events.
Subscribe event NodeClickedOn
Subscribe event showEntity
Subscribes to a NodeClickedOn event and displays device structure based on the events Entity Id attribute.
Subscribes to a showEntity event and displays device structure based on the
Entity Id.
Publish event showPerformance Within the Structure Browser, when you open a node and choose the Show
Interface tab, the showPerformance event publishes the deviceId and the
interfaceId.
16
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Chapter 2. Administering network views
Network Views shows logical groupings of devices that you may need to monitor within your network. Create new views or change existing views to help network operators visualize devices.
About network views
Use this information to understand what a network view is, the different types of network view, and the types of user access to network view collections.
Use a network view to create a custom grouping of any set of devices, sub-nets,
VLANs or other device collections for monitoring.
Network views can also be created based on device events. For example, you can create a network view that displays all devices on which a Critical severity event has occurred.
Standard network views
Create a standard network view to group any set of devices, sub-nets, VLANs or other device collections for monitoring. Standard network views are also referred to as network views.
For example, if you need to monitor the status of two specific sub-nets, you can group them in a standard network view. Once created, this network view appears in the Navigation Panel, with a name and in a position in the navigation tree that you specify.
For example you can create a new My Views container node in the navigation tree, name your new network view My Subnets and place this new view in the My Views container.
As the network changes and the topology is updated following discoveries, the content of the network view changes accordingly. For example, if new devices are added to the subnet, then these devices are automatically added to the network view after they have been discovered.
Usage considerations
Standard network view are useful for operators who monitor a part of the large network and need to focus on the devices, subnets or other device collections within their part of the network.
Create a standard network view if: v You want to create views of particular device collections only, rather than all device collections of a specific type.
v You want to create a view that contains more than one device collection, rather than one view for each device collection.
Related tasks
:
“Creating standard network views” on page 22
Network Manager has two types of views: standard and dynamic. You can create
© Copyright IBM Corp. 2006, 2017
17
these standard views.
Dynamic network views
Dynamic network views are based on the devices or collections that you specify and based on all the network topology data. Dynamic network views are also referred to as dynamic views
If you create a dynamic view of VLANs, multiple VLAN network views are created, one for each VLAN. The result is therefore a node in the Navigation Panel for each VLAN in the network.
As the network changes and the topology is updated following discoveries, the
VLAN nodes in the Navigation Panel might appear or disappear. For example, if any VLANs are removed from the network, then after another discovery, the corresponding VLAN network views automatically disappear.
Usage considerations
The dynamic view option is useful for keeping track of all the devices and device collections in your network. This option is therefore of greater use to an administrator who needs to keep track of device changes across the entire network.
This option is also useful for operators of smaller networks who monitor an entire network.
Do not create a dynamic view if: v
You want to create views of particular device collections only, rather than all device collections of a specific type.
v You want to create a view that contains more than one device collection, rather than one view for each device collection.
If you want to achieve either of the above results, create a standard network view.
Related tasks
:
“Creating dynamic network views” on page 47
Network Manager has two types of views: standard and dynamic. You can create these dynamic views.
Access configuration for network view collections
Use groups and role assignments to administer read-write and read-only access to network view collections, and administer privileges to copy and move network views between network view collections.
“Types of network view collection” on page 19
“Types of user access to network view collections” on page 19
Network view collections
A network view collection is a grouping of network views accessible to a single user, a restricted set of users, or all users. You configure user access to network view collections by assigning roles to users and assigning users to groups.
18
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Types of network view collection
TopoViz categorizes network view collections as follows:
Group views
Network views that are assigned to the group or groups to a user belongs.
For example, divide users into geographical groups. Access to network views can then be restricted based on membership of the groups.
User views
Network views created by a user. Only the user and certain administrators can see these views.
Global views
Network views that are accessible to all users regardless of the group or groups to which they belong.
Types of user access to network view collections
User access to network views falls into the following two categories:
Read-write access
Enables the user to create, edit, delete, and partition network views. A user with this type of access can also copy and move network views between group, user and global view collections. Administrator access also enables users to display network views. To give users read-write access, you must assign the user the netcool_rw role, in addition to the Network Views administrative roles.
Read-only access
Enables the user to only display network views.
Example
The following table shows an example of assignment of roles to enable read-write or read-only access for different users within the “London” and “New York” groups.
The user “bob” is a member of both the “London” and “New York” groups and has read-write access across both groups. In addition to the group views, user can access their own user views and the global views.
Chapter 2. Administering network views
19
Table 2. Configuring user access to network view collections
Group
Accessible view collections
London Views
London
Users
ben
Roles
ncp_networkview
(London) betty netcool_ro ncp_networkview
(London) netcool_rw
Global Views betty Views
London Views
Global Views barbara ncp_networkview_admin_user ncp_networkview barbara Views
(London) netcool_rw ncp_networkview_admin_user
London Views
Global Views
New
York bob ncp_networkview_admin_group ncp_networkview
(London and New
York) netcool_rw ncp_networkview_admin_all_users ncp_networkview_admin_group ncp_networkview_admin_global ben Views, betty
Views, barbara
Views bob Views jerry Views, judy
Views, jonas
Views jerry
(New
York)
London Views
New York Views
Global Views jerry Views
New York Views
Global Views judy
(New
York) jonas
(New
York) ncp_networkview netcool_rw ncp_networkview_admin_user ncp_networkview_admin_group ncp_networkview netcool_rw ncp_networkview_admin_user ncp_networkview netcool_ro judy View
New York Views
Global Views
New York Views
Global Views
Access
Level
read-only read-write read-only read-write read-only read-write read-write read-only read-write read-only read-only
20
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Creating network view containers
Create a container to group together network views and store them in a single node in the Network View navigation panel.
To create a network view container:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Container.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click OK.
The new container node is displayed in the Network View Tree.
Now, create new view within the container, or move existing views to the container.
Related tasks
:
Chapter 2. Administering network views
21
Create network views to show only those parts of the network that you need to monitor. There are two types of network views: standard views and dynamic views.
“Copying or moving views” on page 61
Move network views if you want to make private views available on a group-wide or global basis. Copy network views into your private collection if you want to change a group or global view without any impact on the original view.
Creating network views
Create network views to show only those parts of the network that you need to monitor. There are two types of network views: standard views and dynamic views.
Both standard views and dynamic views provide a custom grouping of any set of devices, sub-nets, VLANs or other device collections for monitoring.
Certain types of network view can be created based on device events. For example, you can create a network view that displays all devices on which a Critical severity event has occurred. To create network views based on device events, you must create a network view with an event filter.
Creating standard network views
Network Manager has two types of views: standard and dynamic. You can create these standard views.
Certain types of network view can be created based on device events. For example, you can create a filtered network view that displays all devices on which a Critical severity event has occurred.
Creating dependency network views
Dependency network views show devices that are dependent on specified independent entities. For example, within a radio access network (RAN), base stations are modeled as being dependent on base station controllers. You can create a dependency network view to display all of the base stations dependent on one or more base station controllers.
If you want to store the view in a custom container, you must create the container before you begin this task.
To create a dependency network view:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin
22
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Dependency.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. Complete the tab as follows:
Domain
Select your network domain.
Class
This drop-down lists the classes of independent entity in your network.
Select a class from the list. For example, to create a network view that shows all the devices that are dependent on specified RAN base station controllers, select RAN Base Station Controller.
Connectivity
Select Default. The network view is displayed using the most appropriate connectivity for the type of collection you selected. You also have the option of specifying one of the other following connectivity options:
Layer 1
Displays all physical connections.
Chapter 2. Administering network views
23
Layer 2
Displays all switched connections between devices in the topology. A layer 2 view typically shows switch and hub connections.
Layer 3
Shows routers and the connections between routers. Switches are not normally displayed.
Note:
If switches have active connections involving layer 3 interfaces, they are included in this layout.
The connections between devices are displayed as follows: v Connections between two layer 3 interfaces are shown as normal.
v
Connections between a layer 3 and a layer 2 interface are shown as being between the layer 3 interface and the subnet to which the layer 2 interface belongs.
v Connections between two layer 2 interfaces are not shown.
IP subnets
Shows all devices within a subnet connected to a subnet cloud.
This layout helps to simplify the network map and also helps to make subnet membership clear. If you want to see all connections, select one of the following options: v Layer 1 for transmission layer connections.
v Layer 2 for data link connections.
v Layer 3 to show all routers and connections between them.
OSPF
Displays connections based on discovered OSPF information that includes router roles, area membership, and connectivity.
Fix Pack 3
Probe
Displays the probe topology, linking probe sources to probe targets.
Converged Topology
Displays the lowest layer links between devices based on all layer 1, 2 and 3 topology data available.
PIM
Displays connections based on PIM adjacency information.
IPMRoute
Displays connections based on IP Multicast upstream and downstream routing information.
Microwave
Shows microwave connections only.
Logical RAN
Shows logical RAN connectivity. RAN entities are usually connected by L1 or L2 connections, but this logical connectivity allows an overview of the main RAN entities to be seen.
Connections are usually implicit in the discovered data. For example, a base station controller is connected at some level to the base stations it manages. Logical RAN connectivity shows this relationship without any intermediate devices, such as multiplexers.
24
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
No connections
Does not present any of the discovered connections for the nodes shown in the view.
LTE Control Plane
Displays a topology view of the LTE control plane.
LTE User Plane
Displays a topology view of the LTE user plane.
Available independent entities
Select the independent entities for which you want to display dependent devices and click Select
independent entities
list.
to move them to the Selected
5.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Creating network views of device collections
To monitor collections of devices, such as subnets, VPNs, and MPLS VPNs, in a part of a large network, create a standard network view of a device collection.
Standard views of device collections are changed automatically as the topology changes after a discovery.
If you want to store the view in a custom container, you must create the container before you begin this task.
You can create the following device collections: v Border Gateway Protocol (BGP) Autonomous Systems (AS), clusters, and networks v Data Centers v Element Management System (EMS) systems v Generic collections v Geographic locations v Geographic regions v Global Virtual Local Area Networks (VLANs) v Hot Standby Routing Protocol (HSRP) groups v
Internet Group Membership Protocol (IGMP) groups v Internet Protocol (IP) paths v IPM Route Multicast Distribution Trees (MDT) v ITNM Services v Logical collections v LTE pools v LTE public land mobile networks (PLMNs) v LTE tracking area collections v MPLS Traffic Engineered (TE) tunnels v Open Shortest Path First (OSPF) areas and routing domains v Port Groups v Protocol Independent Multicast (PIM) groups
Chapter 2. Administering network views
25
v Radio Access Network (RAN) circuit core, GSM cells, location areas, packet core, routing areas, and UTRAN cells v
Stacks v Subnets v Virtual Private Networks (VPNs) v VLAN Ports v VLAN Trunking Protocol (VTP) domains v VTP domains
To create a standard network view of one or more device collections in your network:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Collection.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
26
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. Complete the tab as follows:
Domain
Select your network domain.
Type
Select the required device collection. The Available Collections list is automatically populated based on your selection.
Connectivity
Select Default. The network view is displayed using the most appropriate connectivity for the type of collection you selected. You also have the option of specifying one of the other following connectivity options:
Layer 1
Displays all physical connections.
Layer 2
Displays all switched connections between devices in the topology. A layer 2 view typically shows switch and hub connections.
Layer 3
Shows routers and the connections between routers. Switches are not normally displayed.
Note:
If switches have active connections involving layer 3 interfaces, they are included in this layout.
The connections between devices are displayed as follows: v Connections between two layer 3 interfaces are shown as normal.
v Connections between a layer 3 and a layer 2 interface are shown as being between the layer 3 interface and the subnet to which the layer 2 interface belongs.
v Connections between two layer 2 interfaces are not shown.
IP subnets
Shows all devices within a subnet connected to a subnet cloud.
This layout helps to simplify the network map and also helps to make subnet membership clear. If you want to see all connections, select one of the following options: v Layer 1 for transmission layer connections.
v Layer 2 for data link connections.
v Layer 3 to show all routers and connections between them.
OSPF
Displays connections based on discovered OSPF information that includes router roles, area membership, and connectivity.
Fix Pack 3
Probe
Displays the probe topology, linking probe sources to probe targets.
Chapter 2. Administering network views
27
Converged Topology
Displays the lowest layer links between devices based on all layer 1, 2 and 3 topology data available.
PIM
Displays connections based on PIM adjacency information.
IPMRoute
Displays connections based on IP Multicast upstream and downstream routing information.
Microwave
Shows microwave connections only.
Logical RAN
Shows logical RAN connectivity. RAN entities are usually connected by L1 or L2 connections, but this logical connectivity allows an overview of the main RAN entities to be seen.
Connections are usually implicit in the discovered data. For example, a base station controller is connected at some level to the base stations it manages. Logical RAN connectivity shows this relationship without any intermediate devices, such as multiplexers.
No connections
Does not present any of the discovered connections for the nodes shown in the view.
LTE Control Plane
Displays a topology view of the LTE control plane.
LTE User Plane
Displays a topology view of the LTE user plane.
SubGraph
If the visualization of logical groups has been enabled by the administrator, this menu is available. Select Enable to display entities in logical groups surrounded by a boundary (cloud), which can be expanded and collapsed. Select Disable to display entities in logical groups connected to a ring, which cannot be expanded or collapsed.
Available Collections
Select the device collections that you want to display in the network view and click Select list.
to move them to the Selected Collections
5.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Related tasks
:
“Creating dynamic views of subnets” on page 52
To create network views for each of the subnets in your network, create a dynamic
view of the subnets.
“Creating dynamic views of MPLS VPNs” on page 54
To create a view of the customer VPNs in your network, and have the option of showing customer-edge (CE) devices, create a dynamic view of MPLS VPNs.
28
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Creating network views of MPLS VPNs
To have the option of showing or hiding CE (customer edge) devices, create a network view of MPLS VPNs.
You can also create an MPLS VPN view by creating a network view of device collections. However, you do not have the option to show or hide CE devices.
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select MPLS VPN.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. Complete the tab as follows:
Chapter 2. Administering network views
29
Domain
Select your network domain.
CE Devices
Select the Hide or Show.
Available MPLS VPNs
Select the MPLS VLANs that you want to display in the network view and click Select to move them to the Selected MPLS VPNs list.
5.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Creating network views of VPLS VLANS
To monitor Virtual Private LAN Service Virtual Private Networks (VPLS VPNs), you can create network views of specific VPNs.
VPLS VPN network views are created automatically. You can also create them manually. To create a network view of a particular VPLS VPN, complete the following steps.
1.
Click the Incident icon and select Network Availability > Network Views.
2.
In Network Views, within the Libraries tab, click New View
3.
Complete the General tab as follows:
.
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select VPLS VPN.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
30
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Background Image
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. Complete the tab as follows:
Domain
Select your network domain.
CE Devices
Select Hide or Show.
Available VPLS VPNs
Select the VPLS VLANs that you want to display in the network view and click Select to move them to the Selected VPLS VPNs list.
5.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Creating custom network views
The custom view groups any set of devices, sub-nets, VLANs or other device collections in a domain for monitoring. Create a custom view to manually add devices. Custom views are empty when they are first created. Devices can be added from any network view in the domain for which the custom view was created.
Custom views do not use SQL filters. The view is updated as you add and remove devices.
Note:
When you add an unassigned device to a custom view, the Unassigned view is automatically updated to remove the device.
An administrator can set the value of the topoviz.customview.enable property in the $NMGUI_HOME/profile/etc/tnm/ file to enable or disable custom views. This property is also used to enable or disable Unassigned views.
Complete these steps to create a custom view.
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click the New View .
3.
Complete the General tab as follows:
Chapter 2. Administering network views
31
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Custom.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Add devices, including unassigned devices, to the custom view.
32
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Adding devices to a custom view:
You can group any set of devices, subnets, VLANs, or other device collections in one domain in a custom view.
After you create a custom view, the view is empty. Devices can be added to a custom view from any network view in the domain for which the custom view was created. The devices are copied, that is, they also remain in their original view.
If you add an unassigned device to a custom view, the device is automatically removed from the unassigned view.
Complete these steps to add one or more devices to a custom view.
1.
From an existing view, select one or more devices.
2.
Right-click the selected device or devices and select Add To View from the context menu.
3.
From the Add View window, under Add devices to custom view, specify a value for these fields:To and View.
4.
First, choose a view from the To drop-down menu. This designates the category of view, for example itnmadmin views, to add the device to.
5.
Next, click the View Tree button. A tree is displayed that contains the custom views that are available for the Type you selected. The custom views in the tree are highlighted in bold and italics.
6.
Select a custom view from the tree, and then click OK.
Note:
You must click OK below the tree, before clicking OK for Add selected
nodes to
. If you do not click OK below the tree, an error message is displayed.
7.
Click OK to add the selected devices to the custom view.
Removing devices from a custom view:
Remove one or more devices from a custom view if you no longer want the device to be assigned to the custom view.
Network Manager automatically updates network views to add or remove devices.
The custom view is the only view that is not automatically updated. If you want to remove a device from a custom view, you must remove the device. Complete these steps to remove one or more devices from a custom view.
Note:
If an unassigned view exists for a domain, any devices removed from the custom view are automatically added to the unassigned view if they do not exist in any other network view.
1.
Navigate to the custom view from which you want to remove one or more devices.
2.
From the custom view, select the devices.
3.
Right-click to access the context menu and then select Remove from view.
4.
When the confirmation window displays, click Yes to remove the selected devices from the custom view.
Chapter 2. Administering network views
33
Creating network views for unassigned devices
Create a network view for unassigned devices. The Unassigned view groups all devices in a domain that are not currently assigned to a network view. The view is updated dynamically as devices are added and removed from views in the domain.
The Unassigned view acts as a placeholder for network devices that do not belong to other views. From the Unassigned view, an operator can assign devices to a network view.
Unassigned views do not use SQL filters because they are automatically created by querying the network for unassigned devices. The view is updated dynamically as devices are added and removed from views in the domain.
An administrator can set the value of the topoviz.customview.enable property in the etc/tnm/topoviz.properties file to enable or disable unassigned views. This property is also used to enable or disable custom views.
Complete these steps to create an Unassigned view.
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Unassigned.
Layout
Select Grid or Tabular.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
34
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
The Unassigned view is created when devices that are not in another view are automatically added to the unassigned view.
You can select an unassigned device and right-click to add the device to a network view.
Creating filtered views
Use a filtered view to view parts of the network based on topology database filters; for example, a network view showing all Cisco devices on a given subnet.
If you want to store the view in a custom container, you must create the container before you begin this task.
1.
Click the Incident icon and select Network Availability > Network Views.
2.
Click the Libraries tabe and click New View
3.
Complete the General tab as follows:
.
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Filtered.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Chapter 2. Administering network views
35
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Set up the filter. You have the following options: v Click the Filter tab, and select a domain. Select the attribute table that you want to use in the filter and type an SQL WHERE clause in the Filter field.
v Click the Filter tab and click Edit to use the Filter Builder GUI. The
Filter Builder has basic and advanced modes:
– In basic mode, select a field, comparator, and value from the lists. Use the radio buttons to create Boolean relationships that combine multiple filters.
To add more filters, click Add new row .
– In advanced mode, type the SQL WHERE clause into the field. Prefix each column name from the table that you query with the table alias t..
For example, t.entityName like 'rtr%'
The SQL syntax differs depending on which database you use to store topology.
See the documentation for your database type.
5.
From the End nodes list, specify whether you want end nodes, such as printers and workstations, to be displayed in the view.
6.
From the Connectivity list, select the required connectivity:
Layer 1
Displays all physical connections.
Layer 2
Displays all switched connections between devices in the topology. A layer 2 view typically shows switch and hub connections.
Layer 3
Shows routers and the connections between routers. Switches are not normally displayed.
Note:
If switches have active connections involving layer 3 interfaces, they are included in this layout.
The connections between devices are displayed as follows: v Connections between two layer 3 interfaces are shown as normal.
36
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
v Connections between a layer 3 and a layer 2 interface are shown as being between the layer 3 interface and the subnet to which the layer
2 interface belongs.
v Connections between two layer 2 interfaces are not shown.
IP subnets
Shows all devices within a subnet connected to a subnet cloud. This layout helps to simplify the network map and also helps to make subnet membership clear. If you want to see all connections, select one of the following options: v Layer 1 for transmission layer connections.
v Layer 2 for data link connections.
v Layer 3 to show all routers and connections between them.
OSPF
Displays connections based on discovered OSPF information that includes router roles, area membership, and connectivity.
Fix Pack 3
Probe
Displays the probe topology, linking probe sources to probe targets.
Converged Topology
Displays the lowest layer links between devices based on all layer 1, 2 and 3 topology data available.
PIM
Displays connections based on PIM adjacency information.
IPMRoute
Displays connections based on IP Multicast upstream and downstream routing information.
Microwave
Shows microwave connections only.
Logical RAN
Shows logical RAN connectivity. RAN entities are usually connected by
L1 or L2 connections, but this logical connectivity allows an overview of the main RAN entities to be seen. Connections are usually implicit in the discovered data. For example, a base station controller is connected at some level to the base stations it manages. Logical RAN connectivity shows this relationship without any intermediate devices, such as multiplexers.
No connections
Does not present any of the discovered connections for the nodes shown in the view.
LTE Control Plane
Displays a topology view of the LTE control plane.
LTE User Plane
Displays a topology view of the LTE user plane.
7.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Sample filters
The following examples show the different ways to build a typical filter. The filter retrieves all Cisco devices on subnet 172.20.10.
Chapter 2. Administering network views
37
To build a filter by typing SQL WHERE statements:
1.
On the Filter tab, from the Table list, select ipEndPoint. In the Value field, type subnet like '172.20.10.%'
.
2.
Click Add new row .
3.
From the Table list, select chassis. In the Value field, type className like
'Cisco'
.
4.
Click OK.
To build a filter by using the Filter Builder:
1.
On the Filter tab, from the Table list, select ipEndPoint. Click . The Filter
Builder is displayed.
2.
On the Basic tab, select subnet from the Field list.
3.
From the Comparator list, select =.
4.
In the Value field, type 172.10.10.6 and click OK.
5.
On the Filter tab, from the Table list, select chassis. Click . The Filter
Builder is displayed.
6.
Click Add new row .
7.
From the Field list, select className.
8.
From the Comparator list, select =.
9.
In the Value field, type Cisco.
10.
Click OK.
Example topology filter: main node filter:
This example shows you how to create a network view that filters based on main node IP addresses only.
Before you begin this task, you need to follow the instructions described in the task "Creating filtered views". When you reach the step in which you set up the filter for the network view, perform the following steps.
In this example you will create a network view that filters on main node IP addresses that meet the following criteria: any IP address that has 172.18, 172.19, or
172.20 as the first two octets.
1.
Click the Filter tab.
2.
From the Domain list, select your network domain.
3.
In the Table column, select mainNodeDetails.
4.
Open the Filter Builder, by clicking Open Filter Builder .
5.
In the Filter Builder, under Basic, use the lists and fields to build the required query: First create the part of the query that filters for any IP address that has
172.18 as the first two octets.
a.
From the Field list select ipAddress.
b.
From the Comparator list select like.
c.
In the Value field type 172.18% The percent sign (%) is a wildcard.
6.
Next, create the part of the query that filters for any IP address that has 172.19
as the first two octets.
a.
Click Add new row to add a new row to the Filter table.
38
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
b.
From the Field list select ipAddress.
c.
From the Comparator list select like.
d.
In the Value field type 172.19%
7.
Next, create the part of the query that filters for any IP address that has 172.20
as the first two octets.
a.
Click Add new row to add a new row to the Filter table.
b.
From the Field list select ipAddress.
c.
From the Comparator list select like.
d.
In the Value field type 172.20%
8.
Ensure that the Boolean relationship used to combine the three filters that you just defined is Any.
9.
Click OK to complete the definition of the filter.
Now, complete the remaining steps in the task "Creating a filtered network view".
Example topology filter: all Cisco devices on a subnet:
When creating a filtered network view, create a topology filter to filter the parts of the topology to show in the network view. For example, as part of the filtered network view you can create a filter to show all Cisco devices on a given subnet.
This task shows you how to create an example topology filter for a filtered network view.
Before you begin this task, you need to follow the instructions described in the task "Creating filtered views". When you reach the step in which you set up the filter for the network view, perform the following steps.
1.
Click the Filter tab.
2.
From the Domain list, select your network domain.
3.
Set up the subnet part of the filter. In the Table column, select the ipEndPoint
NCIM topology table.
4.
Open the Filter Builder, by clicking Open Filter Builder .
5.
In the Filter Builder, under Basic, use the lists and fields to build the required query: a.
From the Field list select subnet.
b.
From the Comparator list select like.
c.
In the Value field type a subnet identifier. For example, to specify the subnet 172.20.100.0, type the text 172.20.100%. The percent sign (%) is a wildcard.
d.
Click OK to complete the definition of the subnet part of the filter. The
Filter
column value for ipEndPoint now reads as follows: subnet like
'172.20.100%'.
6.
Set up the part of the filter that filters by device type. Click Add new row to add a new row to the Filter table.
7.
In the Table column, select the chassis NCIM topology table.
8.
Open the Filter Builder, by clicking Open Filter Builder .
9.
In the Filter Builder, under Basic, use the lists and fields to build the required query:
Chapter 2. Administering network views
39
a.
From the Field list select className.
b.
From the Comparator list select like.
c.
In the Value list type Cisco%.
d.
Click OK to complete the definition of the device type part of the filter.
The Filter column value for chassis now reads as follows: className like
'Cisco%'.
10.
Ensure that the Boolean relationship used to combine the two filters that you just defined is All.
Now, complete the remaining steps in the task "Creating a filtered network view".
Example event filter: all devices with Critical events:
When creating a filtered network view, create an event filter to filter topology based on events. For example, as part of the filtered network view you can create a filter to show all devices with events of Critical severity.
This task shows you how to create an example event filter for a filtered network view.
Before you begin this task, you need to follow the instructions described in the task "Creating a filtered network view". When you reach the step in which you set up the filter for the network view, perform the following steps.
1.
Click the Filter tab.
2.
From the Domain list, select your network domain.
3.
In the Table column, select the activeEvent table.
4.
Open the Filter Builder, by clicking Open Filter Builder .
5.
In the Filter Builder, under Basic, use the lists and fields to build the required query: a.
From the Field list select Severity.
b.
From the Comparator list Select =.
c.
From the Value list select Critical.
d.
Click OK to complete the definition of the filter. The Filter column value for the activeEvent table now reads as follows: Severity = Critical.
Note:
The activeEvent table contains a subset of fields from the Tivoli
Netcool/OMNIbus alerts.status table. For information on the fields in the alerts.status table, see the IBM Tivoli Netcool/OMNIbus Administration Guide.
Now, complete the remaining steps in the task "Creating a filtered network view".
Creating filtered views using variables
Use a variable in a filtered view to create complex views. For example, create a view of all devices with events older than one hour.
If you want to store the view in a custom container, you must create the container before you begin this task.
You can use a variable in the filter. The variable is replaced by the appropriate value retrieved from the server. The variable name must be in the form
{%variable}
.
40
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Restriction:
The only variable supported is {%serverTime}. The {%serverTime} variable is replaced with the current time on the Network Manager server, expressed as a
UNIX epoch time (seconds after midnight on 1 January 1970 UTC).
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Filtered.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Set up the filter: a.
Click the Filter tab.
b.
From the Domain list, select your network domain.
Chapter 2. Administering network views
41
c.
In the Table column, select the database table that contains the variable you want to use. For the {%serverTime} variable, select the activeEvent table.
d.
In the Filter column, type an SQL WHERE clause that includes the variable you want to use. For example, to create a view that contains devices with events older than one hour, use the following clause:
{%serverTime} – FirstOccurrence > 3600
5.
From the End nodes list, specify whether you want end nodes, such as printers and workstations, to be displayed in the view.
6.
From the Connectivity list, select the required connectivity:
Layer 1
Displays all physical connections.
Layer 2
Displays all switched connections between devices in the topology. A layer 2 view typically shows switch and hub connections.
Layer 3
Shows routers and the connections between routers. Switches are not normally displayed.
Note:
If switches have active connections involving layer 3 interfaces, they are included in this layout.
The connections between devices are displayed as follows: v Connections between two layer 3 interfaces are shown as normal.
v Connections between a layer 3 and a layer 2 interface are shown as being between the layer 3 interface and the subnet to which the layer
2 interface belongs.
v Connections between two layer 2 interfaces are not shown.
IP subnets
Shows all devices within a subnet connected to a subnet cloud. This layout helps to simplify the network map and also helps to make subnet membership clear. If you want to see all connections, select one of the following options: v Layer 1 for transmission layer connections.
v Layer 2 for data link connections.
v Layer 3 to show all routers and connections between them.
OSPF
Displays connections based on discovered OSPF information that includes router roles, area membership, and connectivity.
Fix Pack 3
Probe
Displays the probe topology, linking probe sources to probe targets.
Converged Topology
Displays the lowest layer links between devices based on all layer 1, 2 and 3 topology data available.
PIM
Displays connections based on PIM adjacency information.
IPMRoute
Displays connections based on IP Multicast upstream and downstream routing information.
Microwave
Shows microwave connections only.
42
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Logical RAN
Shows logical RAN connectivity. RAN entities are usually connected by
L1 or L2 connections, but this logical connectivity allows an overview of the main RAN entities to be seen. Connections are usually implicit in the discovered data. For example, a base station controller is connected at some level to the base stations it manages. Logical RAN connectivity shows this relationship without any intermediate devices, such as multiplexers.
No connections
Does not present any of the discovered connections for the nodes shown in the view.
LTE Control Plane
Displays a topology view of the LTE control plane.
LTE User Plane
Displays a topology view of the LTE user plane.
7.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Creating IP filtered views
You can create network views for IP-addressable entities based on IP filter criteria.
For example, you can create a network view for all IP-addressable entities that either have a specific IP address or contain a specific fragment of an IP address.
You can specify multiple IP filters.
If you want to store the view in a custom container, you must create the container before you begin this task.
To create an IP-filtered network view:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select IP Filter.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Chapter 2. Administering network views
43
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. From the Domain list, select your network domain.
5.
In the Address Patterns field, specify an IP address pattern that you want to match. An IP filtered network view filters based on the accessible IP address for any IP addressable entity within the selected domain. IP addressable entities include main node devices, such as switches and routers, but also include device components such as interfaces, loopback interfaces, and VLANs. An IP filtered network view therefore does not only filter on main node IP addresses; instead it returns all main nodes that meet the following criteria: v Main nodes, where the accessible IP address of the main node matches the range specified in the IP filter. Examples of main nodes returned using this criterion include switches where the IP address of the switch corresponds to the accessible IP address.
v
Main nodes, where at least one interface or other IP addressable component within the main node matches the range specified in the IP filter. Examples of main nodes returned using this criterion include routers where the device typically contains many IP interfaces routing traffic. The management address of the device is often on a separate management network. As the device might be named by its management address this returned address might not match the filter specified; for example, an IP filter view of with a filter criterion such as 1.1.1.0/24 returns a device with the name 2.2.2.2.
If you want to filter on main node IP addresses only, you can create a filtered network view.
Tip:
You can specify as many IP address patterns as you want. The resulting network view shows the union of all IP address retrieved by the different address patterns.
6.
From the End nodes list, specify whether you want end nodes, such as printers and workstations, to be displayed in the view.
44
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
7.
From the Connectivity list, select the required connectivity. The Connectivity list displays some of the options listed below:
Layer 1
Displays all physical connections.
Layer 2
Displays all switched connections between devices in the topology. A layer 2 view typically shows switch and hub connections.
Layer 3
Shows routers and the connections between routers. Switches are not normally displayed.
Note:
If switches have active connections involving layer 3 interfaces, they are included in this layout.
The connections between devices are displayed as follows: v Connections between two layer 3 interfaces are shown as normal.
v Connections between a layer 3 and a layer 2 interface are shown as being between the layer 3 interface and the subnet to which the layer
2 interface belongs.
v Connections between two layer 2 interfaces are not shown.
IP subnets
Shows all devices within a subnet connected to a subnet cloud. This layout helps to simplify the network map and also helps to make subnet membership clear. If you want to see all connections, select one of the following options: v Layer 1 for transmission layer connections.
v Layer 2 for data link connections.
v Layer 3 to show all routers and connections between them.
OSPF
Displays connections based on discovered OSPF information that includes router roles, area membership, and connectivity.
Fix Pack 3
Probe
Displays the probe topology, linking probe sources to probe targets.
Converged Topology
Displays the lowest layer links between devices based on all layer 1, 2 and 3 topology data available.
PIM
Displays connections based on PIM adjacency information.
IPMRoute
Displays connections based on IP Multicast upstream and downstream routing information.
Microwave
Shows microwave connections only.
Logical RAN
Shows logical RAN connectivity. RAN entities are usually connected by
L1 or L2 connections, but this logical connectivity allows an overview of the main RAN entities to be seen. Connections are usually implicit in the discovered data. For example, a base station controller is connected at some level to the base stations it manages. Logical RAN connectivity shows this relationship without any intermediate devices, such as multiplexers.
Chapter 2. Administering network views
45
No connections
Does not present any of the discovered connections for the nodes shown in the view.
LTE Control Plane
Displays a topology view of the LTE control plane.
LTE User Plane
Displays a topology view of the LTE user plane.
8.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Sample IP address patterns
To match all IP addresses that begin with 192.168, type the address pattern 192.168.
To match IP addresses that begin with 172.18, 172.19, and 172.20, type the address pattern 172.18-20.
Related tasks
:
“Example topology filter: main node filter” on page 38
This example shows you how to create a network view that filters based on main node IP addresses only.
IP filter syntax:
Use this reference information to understand how to model the syntax of an IP filter.
When searching for specific IP addresses, you can use ranges for the last octet. You can also assume wildcards for the last octet.
See the following examples to understand the use of ranges and wildcards.
The following examples show different options for using ranges and wildcards to filter for IP addresses: v 172.18-20 matches any IP address that has 172.18, 172.19, or 172.20 as the first two octets.
v 172.20.36-38 matches any IP address that has 172.20.36, 172.20.37, or 172.20.38
as the first three octets.
v 192.168
matches all IP addresses that have the value of 192.168 as the first two octets.
Note:
When used in the last octet, the asterisk (*) wildcard is optional. For example, entering 192.168 and 192.168.* produce the same results. However, the asterisk can be used to filter within octets, for example 192.0.2.1* only matches addresses that have 192.0.2.1* as their first characters.
46
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Creating standard cross-domain network views
You can create standard network views of different types, that show devices from all discovered domains.
If you want to store the view in a custom container, you must create the container before you begin this task.
Before creating a cross-domain network view, you must configure and run cross-domain discoveries for each domain that you want to aggregate.
To create standard network views across domains, complete the following steps:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select a standard network view type. Because the resulting network view will contain all devices from all discovered networks, consider the size of the network views so as not to create unnecessary load on the server.
Fill in the other fields as appropriate for that type of network view.
4.
Click the Filter tab. Complete the tab as follows:
Domain
Select the AGGREGATION domain.
Fill in the other fields as appropriate for that type of network view.
5.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Creating dynamic network views
Network Manager has two types of views: standard and dynamic. You can create these dynamic views.
Certain types of network view can be created based on device events. For example, you can create a dynamic distinct network view that categorizes devices by location, and within each location, categorizes the devices by the event severity on each device.
Chapter 2. Administering network views
47
Creating dynamic views of device collections
To view and keep track of changes to device collections in your network, create dynamic views of device collections. Use dynamic network views to monitor changes to the network. If the topology has changed after a discovery, the nodes in the Navigation Panel are updated automatically.
Use a dynamic network view to monitor which devices have been added to the network, and which devices have been removed. If the topology has changed after a discovery, the nodes in the Navigation Panel are updated automatically.
If you want to store the view in a custom container, you must create the container before you begin this task.
You can create the following device collections: v Border Gateway Protocol (BGP) Autonomous Systems (AS), clusters, and networks v Data Centers v Element Management System (EMS) systems v Generic collections v Geographic locations v Geographic regions v Global Virtual Local Area Networks (VLANs) v Hot Standby Routing Protocol (HSRP) groups v Internet Group Membership Protocol (IGMP) groups v Internet Protocol (IP) paths v
IPM Route Multicast Distribution Trees (MDT) v ITNM Services v Logical collections v LTE pools v LTE public land mobile networks (PLMNs) v LTE tracking area collections v MPLS Traffic Engineered (TE) tunnels v Open Shortest Path First (OSPF) areas and routing domains v Port Groups v
Protocol Independent Multicast (PIM) groups v Radio Access Network (RAN) circuit core, GSM cells, location areas, packet core, routing areas, and UTRAN cells v Stacks v Subnets v Virtual Private Networks (VPNs) v VLAN Ports v VLAN Trunking Protocol (VTP) domains v VTP domains
The following table describes specific requirements for which a dynamic view of device collections is not suitable. In each case, follow the alternative course of action:
48
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Table 3. Strategies for creating dynamic views of device collections
Requirement
You want a dynamic view of subnets and want to avoid creating large numbers of view of class C subnets.
Action
Create a dynamic view of subnets.
Typically, networks contain large numbers of class C subnets, which result in large numbers of views. By creating a dynamic view of subnets, you can restrict the number of views to class A and class B subnets.
Create a dynamic view of MPLS VPNs.
You want a dynamic view of MPLS VPNs but want to restrict the views to customer
VPNs only, and want the option of showing customer-edge (CE) devices in those views.
For MPLS VPNs, a dynamic view of device collections results in views for both the customer VPNs and the MPLS core network.
Additionally, the customer VPNs do not show customer edge (CE) devices.
To create a dynamic view of one or more device collections in your network:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Dynamic Views – Collection.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, to browse for an icon.
click Browse
Background Image
Click Browse for the view.
to browse for an image to use as the background
Chapter 2. Administering network views
49
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. Complete the tab as follows
Domain
Select your network domain.
Type
Select the required device collection. The Preview list is automatically populated based on your selection.
Connectivity
Select Default. The network view is displayed using the most appropriate connectivity for the type of collection you selected. You also have the option of specifying one of the other following connectivity options:
Layer 1
Displays all physical connections.
Layer 2
Displays all switched connections between devices in the topology. A layer 2 view typically shows switch and hub connections.
Layer 3
Shows routers and the connections between routers. Switches are not normally displayed.
Note:
If switches have active connections involving layer 3 interfaces, they are included in this layout.
The connections between devices are displayed as follows: v Connections between two layer 3 interfaces are shown as normal.
v Connections between a layer 3 and a layer 2 interface are shown as being between the layer 3 interface and the subnet to which the layer 2 interface belongs.
v Connections between two layer 2 interfaces are not shown.
IP subnets
Shows all devices within a subnet connected to a subnet cloud.
This layout helps to simplify the network map and also helps to make subnet membership clear. If you want to see all connections, select one of the following options: v Layer 1 for transmission layer connections.
v Layer 2 for data link connections.
v Layer 3 to show all routers and connections between them.
OSPF
Displays connections based on discovered OSPF information that includes router roles, area membership, and connectivity.
50
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Fix Pack 3
Probe
Displays the probe topology, linking probe sources to probe targets.
Converged Topology
Displays the lowest layer links between devices based on all layer 1, 2 and 3 topology data available.
PIM
Displays connections based on PIM adjacency information.
IPMRoute
Displays connections based on IP Multicast upstream and downstream routing information.
Microwave
Shows microwave connections only.
Logical RAN
Shows logical RAN connectivity. RAN entities are usually connected by L1 or L2 connections, but this logical connectivity allows an overview of the main RAN entities to be seen.
Connections are usually implicit in the discovered data. For example, a base station controller is connected at some level to the base stations it manages. Logical RAN connectivity shows this relationship without any intermediate devices, such as multiplexers.
No connections
Does not present any of the discovered connections for the nodes shown in the view.
LTE Control Plane
Displays a topology view of the LTE control plane.
LTE User Plane
Displays a topology view of the LTE user plane.
SubGraph
If the visualization of logical groups has been enabled by the administrator, this menu is available. Select Enable to display entities in logical groups surrounded by a boundary (cloud), which can be expanded and collapsed. Select Disable to display entities in logical groups connected to a ring, which cannot be expanded or collapsed.
Subtree Structure
For selected dynamic network view device collections, this option enables you to view the network view as a hierarchical structure. The flag takes one of the following values: Hierarchical (present the collections in a hierarchy), or Flat (present the collections in a flat list).
Note:
The schema allows collections of any type to exist in a hierarchy, but this option is expected to be most useful for geographic location and geographic region collections. Note also that the geographic hierarchy will not appear automatically; the ability to display a geographic hierarchy requires stitcher customization to identify the relevant parts of the postal address where a device is located. You will need to perform this stitcher customization for your deployment, or possibly for each country that you display in the network views.
Chapter 2. Administering network views
51
5.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Related tasks
:
“Creating dynamic views of subnets”
To create network views for each of the subnets in your network, create a dynamic
view of the subnets.
“Creating dynamic views of MPLS VPNs” on page 54
To create a view of the customer VPNs in your network, and have the option of showing customer-edge (CE) devices, create a dynamic view of MPLS VPNs.
Creating dynamic views of subnets
To create network views for each of the subnets in your network, create a dynamic
view of the subnets.
If you want to store the view in a custom container, you must create the container before you begin this task.
Typically, networks contain large numbers of class C subnets, which result in large numbers of views. By creating a dynamic view of subnets, you can restrict the number of views to class A and class B subnets.
Tip:
If you want to create network views that contain more than one subnet, then do not create a dynamic view. Instead, create a standard network view for device collections.
To create a dynamic view of the subnets in your network:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Dynamic Views – Subnet.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
52
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. Select your network domain from the Domain list.
5.
Select the required option from the Subnet list:
Option
A & B
A, B & C
Description
Creates network views for each of the class
A and class B subnets in your network
Creates network views for each of the class
A , class B, and class C subnets in your network.
Typically, this option automatically creates a large number of subnet network views because most networks contain many class C subnets.
The Preview list is automatically populated based on your selection.
6.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Related tasks
:
“Creating dynamic views of subnets” on page 52
To create network views for each of the subnets in your network, create a dynamic
view of the subnets.
“Creating dynamic views of MPLS VPNs” on page 54
To create a view of the customer VPNs in your network, and have the option of showing customer-edge (CE) devices, create a dynamic view of MPLS VPNs.
“Creating dynamic views of device collections” on page 48
To view and keep track of changes to device collections in your network, create dynamic views of device collections. Use dynamic network views to monitor changes to the network. If the topology has changed after a discovery, the nodes in the Navigation Panel are updated automatically.
Chapter 2. Administering network views
53
“Creating network views of device collections” on page 25
To monitor collections of devices, such as subnets, VPNs, and MPLS VPNs, in a part of a large network, create a standard network view of a device collection.
Standard views of device collections are changed automatically as the topology changes after a discovery.
Creating dynamic views of MPLS VPNs
To create a view of the customer VPNs in your network, and have the option of showing customer-edge (CE) devices, create a dynamic view of MPLS VPNs.
If you want to store the view in a custom container, you must create the container before you begin this task.
Restriction:
The dynamic view of MPLS VPNs does not create a network view for the MPLS core network. To create a view for the core network, create a dynamic view of device collections.
Tip:
If you want to create a view that contains more than one customer VPN, do not create a dynamic view. Instead, create a network view of MPLS VLANs.
To create a dynamic view of the customer VPNs in your network:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Dynamic Views – MPLS – VPN.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
54
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Background Image
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. Complete the tab as follows:
Domain
Select your network domain.
CE Devices
Select Hide or Show. The Preview list is automatically populated based on your selection.
5.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Related tasks
:
“Creating dynamic views of device collections” on page 48
To view and keep track of changes to device collections in your network, create dynamic views of device collections. Use dynamic network views to monitor changes to the network. If the topology has changed after a discovery, the nodes in the Navigation Panel are updated automatically.
“Creating network views of device collections” on page 25
To monitor collections of devices, such as subnets, VPNs, and MPLS VPNs, in a part of a large network, create a standard network view of a device collection.
Standard views of device collections are changed automatically as the topology changes after a discovery.
“Creating dynamic views of subnets” on page 52
To create network views for each of the subnets in your network, create a dynamic
view of the subnets.
Creating distinct dynamic views
To create a network view that has custom categories and subcategories, create a
distinct dynamic view.
For example, you can use the distinct dynamic view to categorize devices by location and within each location organize by the network administrator who is responsible for maintaining the devices. For example, you can use this option to categorize devices by location, and within each location, list the different device classes, such as Cisco 2600 devices or 3ComSuperStack devices.
To create an IP-filtered network view:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
Chapter 2. Administering network views
55
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Dynamic Views – Distinct.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. From the Domain list, select your network domain.
5.
In the Fields list, select the topology database tables and fields that correspond to the categories and subcategories that you want to define. Make sure you define the categories and subcategories in the correct order.
a.
Click Add....
b.
From the Table list, select the required database table. The Field list is automatically populated based on your selection.
c.
Select the required field from the Field list.
d.
56
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
See “Sample topology database fields for categories” on page 58 for more
information on how to specify the fields. As you select fields, the Preview list is updated to show the relationships between the categories that you selected.
6.
From the End nodes list, specify whether you want end nodes, such as printers and workstations, to be displayed in the view.
7.
From the Connectivity list, select the required connectivity:
Layer 1
Displays all physical connections.
Layer 2
Displays all switched connections between devices in the topology. A layer 2 view typically shows switch and hub connections.
Layer 3
Shows routers and the connections between routers. Switches are not normally displayed.
Note:
If switches have active connections involving layer 3 interfaces, they are included in this layout.
The connections between devices are displayed as follows: v Connections between two layer 3 interfaces are shown as normal.
v Connections between a layer 3 and a layer 2 interface are shown as being between the layer 3 interface and the subnet to which the layer
2 interface belongs.
v Connections between two layer 2 interfaces are not shown.
IP subnets
Shows all devices within a subnet connected to a subnet cloud. This layout helps to simplify the network map and also helps to make subnet membership clear. If you want to see all connections, select one of the following options: v Layer 1 for transmission layer connections.
v Layer 2 for data link connections.
v Layer 3 to show all routers and connections between them.
OSPF
Displays connections based on discovered OSPF information that includes router roles, area membership, and connectivity.
Fix Pack 3
Probe
Displays the probe topology, linking probe sources to probe targets.
Converged Topology
Displays the lowest layer links between devices based on all layer 1, 2 and 3 topology data available.
PIM
Displays connections based on PIM adjacency information.
IPMRoute
Displays connections based on IP Multicast upstream and downstream routing information.
Microwave
Shows microwave connections only.
Logical RAN
Shows logical RAN connectivity. RAN entities are usually connected by
L1 or L2 connections, but this logical connectivity allows an overview of the main RAN entities to be seen. Connections are usually implicit in
Chapter 2. Administering network views
57
the discovered data. For example, a base station controller is connected at some level to the base stations it manages. Logical RAN connectivity shows this relationship without any intermediate devices, such as multiplexers.
No connections
Does not present any of the discovered connections for the nodes shown in the view.
LTE Control Plane
Displays a topology view of the LTE control plane.
LTE User Plane
Displays a topology view of the LTE user plane.
8.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Sample topology database fields for categories
The following example helps you complete the fields in step 5 on page 56.
To categorize devices by location, and within each location categorize by the responsible network administrator, define the following categories, in the following order:
1.
Location of the device: This data is held in the sysLocation field of the chassis database table.
2.
Contact person associated with the device: This data is held in the sysContact field of the chassis database table.
This order ensures that location is the main category and contact person is the subcategory.
Creating template-based dynamic views
Use a template-based dynamic view to generate a pre-configured set of dynamic views that are predefined by the network administrator.
If you want to store the view in a custom container, you must create the container before you begin this task.
The required templates must have been defined and stored in the
$NMGUI_HOME/profile/etc/tnm/dynamictemplates/ directory. If a template is not stored in this directory, it cannot be selected for generating dynamic views.
A template is a set of preconfigured views that are defined in an XML file. The network administrator can preconfigure different sets of views for different network operators by defining these preconfigured views in separate templates.
The network operators select the template that is relevant to them and generate the views.
To create a template-based dynamic view:
1.
Click the Incident icon and select Network Availability > Network Views.
2.
Click the Libraries tab and click New View
3.
Complete the General tab as follows:
.
58
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select Dynamic Views - Template.
Layout
Select Orthogonal, Circular, Symmetric, Hierarchical, or Tabular layout.
Map Icon
If you want a different icon than the default icon to represent the view, click Browse to browse for an icon.
Tree Icon
If you want a different icon than the default icon to represent the view, click Browse
Background Image
to browse for an icon.
Click Browse for the view.
to browse for an image to use as the background
Background Style
Specify whether the background image is to be centered or tiled.
Line Status
Specify how the lines that represent the links between devices should be rendered.
You can choose not to display any status, or to display the system default. Alternatively, lines can be colored based on the associated
Event Viewer event with the highest severity, and can appear with an additional severity icon.
4.
Click the Filter tab. From the Domain list, select your network domain.
5.
From Template, select the template that want to use to generate the dynamic view. The Preview list is automatically populated with the list of network views based on your selection.
6.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Chapter 2. Administering network views
59
Creating dynamic cross-domain network views
You can create dynamic network views of different types, that show devices from all discovered domains.
If you want to store the view in a custom container, you must create the container before you begin this task.
Before creating a cross-domain network view, you must configure and run cross-domain discoveries for each domain that you want to aggregate.
To create dynamic network views across domains, complete the following steps:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Click New View .
3.
Complete the General tab as follows:
Name
Type a name for the network view, dynamic view, or network view container.
Important:
It is best practice to use network view names containing
Latin characters only. Network views names containing non-Latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new version of
Network Manager.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
Type
Select a dynamic network view type. Because the resulting network view will contain all devices from all discovered networks, consider the size of the network views so as not to create unnecessary load on the server.
Fill in the other fields as appropriate for that type of network view.
4.
Click the Filter tab. Complete the tab as follows:
Domain
Select the AGGREGATION domain.
Fill in the other fields as appropriate for that type of network view.
5.
Click OK. The new view is added to the navigation tree in the Navigation
Panel. If you added the view to a container, expand the container node to see the new view in the tree.
Example: Small network or Proof of Concept (POC)
If you want to check whether two or more domains have been discovered and joined together as you expect, you could recreate all the network views that are usually created automatically after a discovery finishes. Do this only if you are sure that the total of the resulting network views will not have an adverse performance impact. For example, you might want to do this while testing cross-domain discovery, on a non-production system. To create all the usual network views, complete the following steps:
1.
Create a new network view of type Dynamic Views - Template.
2.
Select the domain AGGREGATION.
3.
Select the template IP Default.
60
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Changing network views
You can change any of the properties of an existing view.
To edit a view, complete the following steps:
1.
In the navigation panel, navigate to the view you want to edit and click theEdit
view
button. A dialog box is displayed.
2.
Edit the properties of the view. When you have finished, click OK to apply your changes.
3.
Click Save .
Deleting network views
Delete existing network views if they are no longer required.
To delete an existing view:
1.
Click the Incident icon and select Network Availability > Network Views.
2.
Navigate to the required network view and select the view. Then click Delete
View
. The Delete View dialog is displayed.
3.
Select one of the following options:
Option
Delete view and all its sub-views
Delete view and move sub-views to new parent
Description
Deletes both the selected view and any subviews that it might have.
Deletes only the selected view and moves any sub-views to the node that you select from the list. To move the subviews to the top level of the hierarchy, select NONE.
4.
Click Delete > OK.
Copying or moving views
Move network views if you want to make private views available on a group-wide or global basis. Copy network views into your private collection if you want to change a group or global view without any impact on the original view.
To copy or move views to a container, you must be a member of that contain, or you must have administration rights for the container.
To move a view, you must have the appropriate administration rights. If you do not have the administration rights to move a view, you can only copy a view. For many of these operations you must have read-write access.
To copy or move a view:
1.
Click the Incident icon and select Network Availability > Network Views.
Chapter 2. Administering network views
61
2.
Navigate to the required view, select the view, and click Copy or Move View
.
3.
Under Action, select an option: v Copy : Creates a copy of the view in the selected target.
v Move : Moves the view to the selected target.
4.
Complete the other fields as follows:
To
Select the view collection to which you want to copy or move the view.
Parent
Select the node under which the view appears in the hierarchy in the
Navigation Tree. To display the view on the top level, select NONE.
5.
Click OK.
Possible copy and move actions
The following table describes the copy and move operations that you can perform, and shows source and target view collections for these copy and move operations.
Table 4. Copying and Moving Network Views between Network View Collections
Source Target Result
Own user view collection
Own user view collection
Within same user view collection
Places the network view in a required position within the user view collection
Group view collection Makes a private network view available on a group-wide basis
Own user view collection
Global view collection
Group view collection Own user view collection
Makes a private network view available on a global basis
Enables you to copy a group view into your own user view collection and modify the view there
Group view collection Within same group view collection
Group view collection Another group view collection
Places the network view in a required position within the group view collection
Enables sharing of network views between groups
Group view collection Global view collection Makes a network view formerly available only to users within a single group available on a global basis
Global view collection Own user view collection
Enables you to copy a global view into your own user view collection and modify the view there
Global view collection Group view collection Enables you to copy a global view into a group view collection where group members can display the view and modify it if they have read-write access
Global view collection Another point within the Global view collection
Places the network view in a required position within the global view collection
Related reference
:
“Access configuration for network view collections” on page 18
Use groups and role assignments to administer read-write and read-only access to network view collections, and administer privileges to copy and move network
62
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
views between network view collections.
Roles required to copy and move network views
To enable users to copy and move network views between network view collections you must assign the users to certain roles and groups.
The ability to copy and move network views between view collections varies depending on which roles are assigned to a user and which group or groups of which the user is a member.
The following table describes that you must assign to users so that they can copy and move views.
Table 5. Roles for copying and moving network views between network view collections
Operation From
Copy or move
Own user view collection
To
Within same user view collection
Roles required
ncp_networkview ncp_networkview_admin_user
Group membership required
None
Copy Own user view collection
Group view collection netcool_rw ncp_networkview ncp_networkview_admin_group
Must be member of the target group
Move view collection
Own user view collection
Group view collection netcool_rw ncp_networkview ncp_networkview_admin_user
Must be member of the target group ncp_networkview_admin_group
Copy
Move
Copy
Move
Own user view collection
Own user view collection
Group view collection
Group view collection
Global view collection netcool_rw ncp_networkview ncp_networkview_admin_global
Global view collection netcool_rw ncp_networkview ncp_networkview_admin_user ncp_networkview_admin_global
Own user view collection netcool_rw ncp_networkview ncp_networkview_admin_user
Group view collection netcool_rw ncp_networkview ncp_networkview_admin_user ncp_networkview_admin_group netcool_rw
None
None
Must be member of the source group
Must be member of the source group
Chapter 2. Administering network views
63
Table 5. Roles for copying and moving network views between network view collections (continued)
Operation From
Copy or move
Copy
Group view collection
Group view collection
To
Within same group view collection or to another group view collection
Global view collection
Roles required
ncp_networkview ncp_networkview_admin_group netcool_rw ncp_networkview ncp_networkview_admin_global
Group membership required
Must be member of the source and target groups
Must be member of the source group
Move Group view collection
Global view collection netcool_rw ncp_networkview ncp_networkview_admin_global
Must be member of the source group ncp_networkview_admin_group
Copy Global view collection
Own user view collection netcool_rw ncp_networkview ncp_networkview_admin_user
None
Move Global view collection
Own user view collection netcool_rw ncp_networkview ncp_networkview_admin_user ncp_networkview_admin_global
None
Copy or move
Copy
Move
Global view collection
Global view collection
Global view collection
Another point within the Global view collection
Group view collection netcool_rw ncp_networkview ncp_networkview_admin_global netcool_rw ncp_networkview ncp_networkview_admin_group
Group view collection netcool_rw ncp_networkview ncp_networkview_admin_global ncp_networkview_admin_group netcool_rw
None
Must be member of the target group
Must be member of the target group
64
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Configuring connectivity types
You can create or edit connectivity types for use in the Hop View and the Network
Views.
You can display different types of connectivity in the Network Hop View and the
Network Views. For example, you can display Layer 1, Layer 2, Layer 3, or IP subnets connectivity. You can also define your own connectivity types.
To configure a connectivity type, complete the following steps:
1.
On the server where the Network Manager Web components are installed, back up and edit the appropriate file: v For US English, edit the file $NMGUI_HOME/profile/etc/tnm/locale/ ncp_layertypes.properties
.
v
For other languages, edit the file $NMGUI_HOME/profile/etc/tnm/locale/ ncp_layertypes_lang_country.properties
, where lang is the two-latter language code, and country is the two-letter country code.
For example, to define a new layer type in Brazilian Portuguese, edit the file ncp_layertypes_pt_BR.properties
.
2.
Add a line to create a new connectivity type, or edit or delete the line for an existing connectivity type. To create a new layer of type "Pseudo Wire": connectivity.77:Pseudo Wire
In this example, the number 77 is the value of the entityType field from the ncim.entityType
topology database that corresponds to Pseudo Wire Topology.
You can choose a different entityType, as long as it has a metaClass of
Topology. Pseudo Wire is the name that will be displayed in the Connectivity menu.
Important:
Do not delete or modify the default connectivity types Layer 1,
Layer 2. Layer 3, IP Subnets, or Converged Topology.
3.
Save and close the file.
Enabling custom or unassigned views
Enable custom and unassigned views if you want to create a custom or unassigned view type. You must create a custom view if you want to manually add a collection of devices to a view. Create an unassigned view to automatically collect all unassigned devices for a domain in the unassigned view.
Complete these steps to enable custom and unassigned views.
1.
Back up the $NMGUI_HOME/profile/etc/tnm/topoviz.properties file.
2.
Add or edit the following property: topoviz.customview.enable. Set the value to true to enable both custom and unassigned views.
Note:
Set the value to false to disable custom and unassigned views.
3.
Save and close the $NMGUI_HOME/profile/etc/tnm/topoviz.properties file.
4.
Ensure that the addToView.xml and removeFromView.xml files are present in the
$NMGUI_HOME/profile/etc/tnm/tools/ directory. If they are not present, copy them from the $NMGUI_HOME/profile/etc/tnm/tools/default/ directory.
5.
Ensure that the following lines are present in the $NMGUI_HOME/profile/etc/ tnm/menus/ncp_topoviz_device_menu.xml
file:
Chapter 2. Administering network views
65
<tool id="addToView"/>
<tool id="removeFromView"/>
Enabling visualization of logical groups
If you enable this feature, logical groups such as subnets can be expanded and collapsed in the Network Views.
If the SubGraph property of a Network View is disabled, membership of logical groups is shown by dashed lines connecting entities to a blank oval, which represents the logical group. If the SubGraph property of a Network View is enabled, entities in logical groups are shown surrounded by a rectangular border, which can be collapsed into a cloud.
The SubGraph property can only be set on Network Views of type Collection.
The SubGraph property of a Network View can be enabled or disabled when creating or editing a network view. The option to enable or disable the SubGraph property only appears in the GUI if the visualization of logical groups has first been enabled by an administrator.
To enable the visualization of logical groups, complete the following tasks.
1.
Back up the /opt/ibm/netcool/gui/precision_gui/profile/etc/tnm/ topoviz.properties
file.
2.
Add or edit the following line: topoviz.collection.subgraph.enable=true.
3.
Save and close the file.
Customizing line thickness in topology maps
You can customize the thickness of the lines connecting network entities based on the speed of the connection between them.
1.
Back up and edit the file: $NMGUI_HOME/profile/etc/tnm/topoviz.properties
2.
Edit the following properties to enable the display of link capacity:
topoviz.hopview.showlinkcapacity
Set to true to enable link capacity display for the Network Hop View.
Set to false to disable.
topoviz.networkview.showlinkcapacity
Set to true to enable link capacity display for the Network Views. Set to false to disable.
3.
Edit the following properties to specify the thickness of the lines for different connection speeds:
topoviz.pipe.1.threshold
Specify the first connection speed threshold above which the line thickness changes. Connection speed is measured in bits/sec. You can use the following International System of Units multipliers: k, M, G, T,
P, E.
topoviz.pipe.1.thickness = 2
Specify the thickness of a line, the connection speed of which is above the first threshold. The line thickness is specified in multiples of the default line thickness.
topoviz.pipe.2.threshold
Specify the second connection speed threshold above which the line
66
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
thickness changes. Connection speed is measured in bits/sec. You can use the following International System of Units multipliers: k, M, G, T,
P, E.
topoviz.pipe.2.thickness
Specify the thickness of a line, the connection speed of which is above the second threshold. The line thickness is specified in multiples of the default line thickness.
topoviz.pipe.n.threshold
Specify the nth connection speed threshold above which the line thickness changes, where n is 3, 4, or 5, in order. You can specify up to
5 thresholds. Connection speed is measured in bits/sec. You can use the following International System of Units multipliers: k, M, G, T, P, E.
topoviz.pipe.n.thickness
Specify the thickness of a line, the connection speed of which is above the nth threshold, where n is the value that you specified in the previous property. The line thickness is specified in multiples of the default line thickness.
4.
Restart the Dashboard Application Services Hub for the changes to take effect.
The following example specifies that connections with a capacity over 2 GBits/sec are drawn with lines that are twice as thick as the default: topoviz.pipe.1.threshold = 2G topoviz.pipe.1.thickness = 2
Deploying pre-configured network views
To configure network views for use by network operators, create a template that specifies pre-configured network views. The template can be deployed either by the operators, or globally for specific sets of operators.
The network views in the template can be created in two ways: v Network operators generate the network views from the Network Views GUI by create a new template-based dynamic network view and specifying the template.
v You generate the network views specified in the template and assign the generated views to a specific user or group.
Making a pre-configured template available to operators
Provide a template of pre-configured network views to network operators so that they can use the template to generate dynamic network views from the Network
Views GUI themselves.
To provide the template:
1.
Define the template in an XML file. Give the XML file the following name:
template_name.xml
, where template_name is the name of the template on which network operators base their dynamic network views.
2.
Save the template to the /opt/ibm/netcool/gui/precision_gui/profile/etc/ tnm/dynamictemplates directory.
Related concepts
:
“About network view templates” on page 69
A network view template is a set of preconfigured network views that is defined in an XML file. Network administrators use templates to automatically generate network views.
Chapter 2. Administering network views
67
Creating and deploying network views from templates automatically
Create network views from templates and assign them to groups or users automatically using auto-provision scripts.
To deploy the templates, you must create an auto-provision script. This script performs the following tasks: v Creates a top-level dynamic view node in the Network Views Navigation Panel, using a specified name v Generates a set of network views using a specified template, and puts the template in the top-level dynamic view node in the Navigation Panel v Assigns the network views generated to a specified user or user group.
v
Uses a specified domain.
Every 60 seconds the $NMGUI_HOME/profile/etc/tnm/autoprovision/ directory is monitored for new auto-provision scripts. When a new auto-provision script is found, the script is read and processed, and the dynamic network view referenced in the script is created and assigned to the specified user or user groups.
When a script is processed, the suffix .processed is added to the file name, whether or not any network views were created. Files which end in .processed are not processed again. If you want to rerun a script, remove the .processed from the end of the file name, so that the file name ends in .xml.
To deploy preconfigured network views automatically:
1.
Define the template as an XML file and save the template to the
$NMGUI_HOME/profile/etc/tnm/dynamictemplates/ directory.
2.
Create the auto-provision script in XML and copy it into the
$NMGUI_HOME/profile/etc/tnm/autoprovision/
directory. See “Sample auto-provision script” for an example. The script is automatically processed
within 60 seconds and the specified network views are created in the specified domain for the specified users and groups.
3.
If a network topology exists for the specified domain, the new network views are automatically populated with devices. If no discovery has been run, the network views are populated when a discovery has been run in the appropriate domain.
Restriction:
If the domain referenced in the auto-provision script does not exist at the time that the script is processed, no network views are created. You need to first create the domain, and then create the network views. This is true even if you create a script that references all domains using a wildcard "*".
Sample auto-provision script
The following sample auto-provision script creates a view called NCOMS View and creates a set of views underneath using the dynamic view template ipdefault.
These views are assigned to the itnmadmin user and use the domain NCOMS.
<autoProvision name="NCOMS View" domain="NCOMS" accessLevel="user" accessId="itnmadmin">
<dynamicViewTemplate id="ipdefault" />
</autoProvision>
68
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Network view templates
Read about network view templates and use this reference information to create new network view templates for Network Manager.
About network view templates
A network view template is a set of preconfigured network views that is defined in an XML file. Network administrators use templates to automatically generate network views.
The XML files that are used to define the templates are stored in the
$NMGUI_HOME/profile/etc/tnm/dynamictemplates/ directory.
Network administrators create templates based on the needs of network operators.
The templates can be made available to operators in the following ways:
By saving the templates to a specified location
The operator can then choose to generate the preconfigured set of network views from the Network Views GUI, as one of the options available when creating a network view.
By assigning the templates to specified users or user groups
The administrator deploys the preconfigured views defined in one or more templates and assigns these views to a specific user, group or at a global level. Depending on how the templates have been assigned, operators find the preconfigured views automatically available in their Network Views
Navigation Panel.
Related tasks
:
“Creating template-based dynamic views” on page 58
Use a template-based dynamic view to generate a pre-configured set of dynamic views that are predefined by the network administrator.
“Making a pre-configured template available to operators” on page 67
Provide a template of pre-configured network views to network operators so that they can use the template to generate dynamic network views from the Network
Views GUI themselves.
“Creating and deploying network views from templates automatically” on page 68
Create network views from templates and assign them to groups or users automatically using auto-provision scripts.
Related reference
:
“Description of IP network view template” on page 70
The IP network view template ip_default.xml defines dynamic network views for a wide range of IP network classes and collections.
Default network view templates
Network Manager is shipped with templates containing dynamic views for each item available on the network.
Chapter 2. Administering network views
69
IP network view template:
Network Manager is shipped with the IP network view template, ip_default.xml.
This template consists of dynamic network views for each item available on the IP network.
Description of IP network view template:
The IP network view template ip_default.xml defines dynamic network views for a wide range of IP network classes and collections.
Note:
Do not use the ip_default.xml template if you have large or very large networks. The ip_default.xml template is intended mainly for educational purposes to demonstrate how the topology can be displayed. Running this template against a large or very large production topology could have a serious impact on the memory and performance of your Network Manager installation, particularly on displaying and using network views. If you have large or very large networks, create network view templates that enable operators to generate a limited set of network views or create network views manually. For more information on creating network views and network view templates, see the IBM
Tivoli Network Manager IP Edition Network Visualization Setup Guide. For more information about network sizes, see the section on deployment scenarios in the
IBM Tivoli Network Manager IP Edition Product Overview.
Dynamic views are created for the following items: v Alert views. The following alert views are presented:
– All devices with PingFailRootCause events
– All devices with SnmpLinkInDiscards events
– Alert views based on event severities
– Monitoring views: network views resulting from Network Manager polling and used by the adaptive polling scenarios v ASMs running on devices. An ASM agent running on a device corresponds to a commercial server or database product running on that device. These network views group devices within a network based on the commercial server or database products running on those devices.
v BGP networks v Customer MPLS VPNs v
Device classes v HSRP groups v IGMP v IPMROUTE v NAT address spaces v OSPF routing domains v Subnets v VLANs v VPLS v VTP domains
No dynamic view is created for an item if no item of that type exists on the network. For example, if your network has no HSRP groups, then no dynamic view is generated for HSRP groups.
70
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
IP network view template XML code:
This template example uses all of the elements available from the IP template hierarchy. It includes network views based on user-defined filters and dynamic views.
Example
The following sample template XML file is provided for illustration purposes and uses all of the elements available from the template hierarchy.
<dynamicViewTemplate id="complete_template" label="Complete Template" manager="PrecisionIP">
<!-"Classic" Class Partition -->
<!-- VPLS -->
<container id="vpls" label="VPLS">
<dynamicMplsVpn id="vpls_vpns" label="VPLS VPNs" ceDevices="true"/>
</container>
<!-- IP Multicast Routing View -->
<dynamicCollection id="ipMRoutingMdts" label="Multicast Routing MDTs" entityType="46" connectivity=”ipMRoute”/>
<!-- IGMP View -->
<dynamicCollection id="igmpGroups" label="IGMP Groups" entityType="121"/>
<dynamicDistinct id="device_classes" label="Device Classes" connectivity="ipsubnets" endNodes="false">
<tableField table="chassis" field="className" />
</dynamicDistinct>
<!-BGP Networks -->
<collection id="bgp_networks" label="BGP Networks" entityType="30">
<entity name="BGP Networks" />
</collection>
<!-- PIM Network -->
<collection id="pim_network" label="PIM Network" entityType="42">
<entity name="PIM Network"/>
</collection>
<!-- Unassigned view-->
<unassigned id="unassigned_view" label="Unassigned_View" />
<!-- Custom view (previously known as a manual view)-->
<custom id="custom_view" label="Custom_View" connectivity="ipsubnets"/>
<!-VLAN Port Collections -->
<dynamicCollection id="vlan_port_collection" label="Vlan Ports" entityType="113" connectivity="layer2" />
<!-HSRP Groups -->
<dynamicCollection id="hsrp_groups" label="HSRP Groups" entityType="18" />
<!-OSPF Routing Domains -->
<dynamicCollection id="ospf_routing_domains" label="OSPF Routing Domains" entityType="21" />
<!-VTP Domains -->
<dynamicCollection id="vtp_domains" label="VTP Domains" entityType="24" />
<!-Subnets -->
<dynamicSubnet id="subnets" label="Subnets" classes="ab" />
<!-MPLS -->
<container label="mpls" label="MPLS">
<collection id="mpls_core" label="MPLS Core" entityType="17">
<entity name="VPN_CONTAINER_MPLS Core" />
</collection>
<dynamicMplsVpn id="mpls_vpns" label="MPLS VPNs" ceDevices="false" />
</container>
<!-- MPLS TE -->
<dynamicCollection id="mpls_te" label="MPLS TE" entityType="36"/>
<!-- Static MPLS -->
<mplsVpn id="mpls_vpn" label="Static MPLS VPN" ceDevices="true">
<entity name="VPN_CONTAINER_1104"/>
</mplsVpn>
<!-NAT Address Spaces -->
<dynamicDistinct id="nat_address_spaces" label="NAT Address Spaces" connectivity="ipsubnets" endNodes="false">
<tableField table="ipEndPoint" field="addressSpace" />
</dynamicDistinct>
<!-Discovered ASMs -->
<dynamicDistinct id="discovered_asms" label="Discovered ASMs" connectivity="ipsubnets" endNodes="false">
<tableField table="netcoolAsmsRunning" field="ASMName" />
</dynamicDistinct>
<!-- Wildcard IP Filter -->
<ipFilter id="ipfilter1" label="Filtered IPs 1" endNodes="true">
<addressPattern pattern="192.*.*.*"/>
</ipFilter>
<!-- Ranged IP Filter -->
<ipFilter id="ipfilter2" label="Filtered IPs 2">
<addressPattern pattern="192.168.3-4"/>
</ipFilter>
Chapter 2. Administering network views
71
<!-- Filtered for two class names -->
<filtered id="filtered1" label="Network Devices/Linux Machines" endnodes="true" condition="or">
<filter table="chassis" filter="className = ’NetworkDevice’"/>
<filter table="chassis" filter="className = ’Linux’"/>
</filtered>
<!-- Filtered for particular network devices -->
<filtered id="filtered2" label="Network Devices: Main Node < 2000" endnodes="true" condition="and">
<filter table="chassis" filter="className = ’NetworkDevice’"/>
<filter table="chassis" filter="mainNodeEntityId < 2000"/>
</filtered>
<!-- Devices that have been manually added with the topology editor -->
<!-- connectivity defaults to IP subnets -->
<filtered id="ManuallyAdded" label="Manually Added Devices" endNodes="true">
<filter schema="ncim" table="entity" filter="manual = 1" />
</filtered>
<!-- All routers -->
<filtered id="AllRouters" label="All Routers" connectivity="layer3">
<filter schema="ncim" table="classMembers" filter="classId in (select classId from {%schema_ncim}entityClass where classType=’Router’)" />
</filtered>
<!-- All switches -->
<filtered id="AllSwitches" label="All Switches" connectivity="layer2">
<filter schema="ncim" table="classMembers" filter="classId in (select classId from {%schema_ncim}entityClass where classType=’Switch’)" />
</filtered>
<!-- default event filtered type views based on severities -->
<container id="alert_views" label="Alert views">
<container id="acknowledged_alerts" label="Acknowledged Alerts">
<filtered id="Critical" label="Critical" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="Severity=5 and Acknowledged=1"/>
</filtered>
<filtered id="Major" label="Major" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="Severity=4 and Acknowledged=1"/>
</filtered>
<filtered id="Minor" label="Minor" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="Severity=3 and Acknowledged=1"/>
</filtered>
</container>
<container id="Unacknowledged_alerts" label="Unacknowledged Alerts">
<filtered id="Critical" label="Critical" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="Severity=5 and Acknowledged=0"/>
</filtered>
<filtered id="Major" label="Major" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="Severity=4 and Acknowledged=0"/>
</filtered>
<filtered id="Minor" label="Minor" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="Severity=3 and Acknowledged=0"/>
</filtered>
</container>
<!-- Filter using the current time as a variable -->
<filtered id="OldCriticalPingFail" label="Critical Ping Fail Events at least 1 hour old" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="EventId = ’NmosPingFail’ and Severity=5 and {%serverTime} - FirstOccurrence >= 3600"/>
</filtered>
<!-- default event filtered type view -->
<filtered id="ping_fail_root_cause" label="PingFailRootCause" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="EventId=’NmosPingFail’ and NmosCauseType=’Root Cause’"/>
</filtered>
<filtered id="snmppollfail" label="SNMP Poll Fail" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="EventId=’NmosSnmpPollFail’" />
</filtered>
<!-- default event filtered type view -->
<filtered id="SnmpLinkInDiscards" label="SnmpLinkInDiscards" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="EventId=’NmosSnmpLinkInDiscards’"/>
</filtered>
<!-- Monitoring views -->
<container id="Monitoring_views" label="Monitoring Views">
<filtered id="InitialPingFail" label="Initial Ping Fail Events" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="EventId = ’NmosPingFail’ and Tally <= 18"/>
</filtered>
<filtered id="HighDiscardRate" label="Devices that have at least one interface event for HighDiscardRate" connectivity="ipsubnets" endNodes="true">
<filter schema="ncmonitor" table="activeEvent" filter="EventId = ’Poll-HighDiscardRate’"/>
</filtered>
</container>
</container>
</dynamicViewTemplate>
72
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
LTE network view template:
Network Manager is shipped with the LTE network view template, lte_default.xml
. This template consists of dynamic network views for each item available on the LTE network.
Description of LTE network view template:
The LTE network view template lte_default.xml defines dynamic network views for a wide range of LTE network classes and collections.
Views are created for the following items: v Control Plane by Tracking Area: Lists network views containing sections of the control plane associated with a given tracking area. Each of these network views is given the name of the associated tracking area.
v EPC network: Lists all devices in the evolved packet core (EPC) network.
v EPC Control Plane: Provides a fully connected network view showing all control plane devices in the Evolved Packet Core section of the LTE network.
v EPC by Vendor: Lists all vendors for devices in the evolved packet core (EPC) network. Clicking a vendor name lists the devices of that vendor type in the
EPC.
v EPC User Plane: Provides a fully connected network view showing all user plane devices in the Evolved Packet Core section of the LTE network.
v E-UTRAN network: Lists all eNodeB devices in the evolved UMTS Terrestrial
Radio Access network (EUTRAN).
v E-UTRAN by Vendor: Lists all vendors for the eNodeB devices in the evolved
UMTS Terrestrial Radio Access network (EUTRAN). Clicking a vendor name lists the eNodeB devices of that vendor type in the EUTRAN v LTE Network Geography: Shows devices in the LTE hierarchy grouped geographically. The geographical groupings vary depending on how the geographical locations and regions are defined in your system.
v LTE Pools: Shows all pools in the LTE hierarchy. If you have no LTE pools then this node does not appear. Because the LTE Pools view is a dynamic distinct view, it will contain child views for whatever types of LTE pools exist in the
NCIM topology database; for example, MME pools, PGW pools, SGW pools.
v PLMN: Lists all public land mobile networks (PLMN) in the LTE hierarchy.
v
Tracking Areas: Lists all tracking areas in the LTE hierarchy.
v User Plane by Tracking Area: Lists network views containing sections of the user plane associated with a given tracking area. Each of these network views is given the name of the associated tracking area.
v Vendor: Lists all vendors in the LTE hierarchy. Clicking a vendor name lists network views corresponding to the device types from that vendor in the LTE hierarchy.
No dynamic view is created for an item if no item of that type exists on the network. For example, if your network has no LTE pools, then no dynamic view is generated for LTE pools.
Chapter 2. Administering network views
73
LTE network view template XML code:
This template example uses all of the elements available from the LTE template hierarchy. It includes network views based on user-defined filters and dynamic views.
Example
The following sample template XML file is provided for illustration purposes and uses all of the elements available from the template hierarchy.
<dynamicViewTemplate id="lte_default" label="LTE Default" manager="PrecisionIP" >
<container id="lte_network_drilldown" label = "LTE Network Drilldown" layout="tabular">
<filtered id="eutran" label="E-UTRAN" endNodes="true" connectivity="noconnections">
<filter schema="ncim" table="entityClass" filter="classType = ’ENODEB’"/>
</filtered>
<dynamicDistinct id="eutranByVendor" label="E-UTRAN by Vendor" endNodes="true" connectivity="noconnections">
<tableField table="enbFunction" field="vendorName"/>
</dynamicDistinct>
<filtered id="epc" label="EPC" condition="OR" endNodes="true" connectivity="noconnections">
<filter schema="ncim" table="entityClass" filter="classType = ’EIR’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’MME’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’HSS’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’PCRF’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’PGW’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’SGW’"/>
</filtered>
<dynamicDistinct id="epcByVendor" label="EPC by Vendor" endNodes="true" connectivity="noconnections">
<tableField table="epcLteFunction" field="vendorName"/>
</dynamicDistinct>
<dynamicCollection id="plmn" label="PLMN" entityType="158" useCollectionHierarchy="true" connectivity="noconnections"/>
<dynamicCollection id="tracking_areas" label="Tracking Areas" entityType="153" useCollectionHierarchy="false" endNodes="true" connectivity="noconnections"/>
<dynamicDistinct id="vendor" label="Vendor" endNodes="true" connectivity="noconnections">
<tableField table="lteFunction" field="vendorName"/>
<tableField table="lteFunction" field="lteFunctionType"/>
</dynamicDistinct>
</container>
<dynamicCollection id="lte_network_geography" label="LTE Network Geography" entityType="112" connectivity="lteuserplane" useCollectionHierarchy="true" subgraph="true" endNodes="true" />
<!-- entityType 112 is Geographic Region -->
<container id="lte_network_topology" label = "LTE Network Topology">
<dynamicCollection id="controlplane" label="Control Plane by Tracking Area" entityType="163" connectivity="ltecontrolplane" useCollectionHierarchy="true" subgraph="true" endNodes="true"/>
<dynamicCollection id="userplane" label="User Plane by Tracking Area" entityType="164" connectivity="lteuserplane" useCollectionHierarchy="true" subgraph="true" endNodes="true"/>
<filtered id="epc_control_plane" label="EPC Control Plane" connectivity="ltecontrolplane" condition="OR" endNodes="true">
<filter schema="ncim" table="entityClass" filter="classType = ’EIR’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’MME’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’HSS’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’PCRF’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’PGW’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’SGW’"/>
</filtered>
<filtered id="epc_user_plane" label="EPC User Plane" connectivity="lteuserplane" condition="OR" endNodes="true">
<filter schema="ncim" table="entityClass" filter="classType = ’PGW’"/>
<filter schema="ncim" table="entityClass" filter="classType = ’SGW’"/>
</filtered>
</container>
<dynamicDistinct id="lte_pools" label="LTE Pools" connectivity="ltecontrolplane" endNodes="true">
<tableField table="ltePoolDevices" field="ltePoolType"/>
74
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
<tableField table="ltePoolDevices" field="ltePoolName"/>
</dynamicDistinct>
</dynamicViewTemplate>
Network view template elements
Use this information to understand the elements that are used to create an XML template for a network view.
The following table describes the elements that are used to create a template.
Note:
Each element can take the attributes id and label, in addition to the attributes listed in the table.
Table 6. Elements in the template XML
Element Description
addressPattern collection
Specifies an address pattern to filter device IP addresses.
Generates a network view of a device collection.
Attributes
pattern entityType subgraph container dynamicCollection
Generates a container to group network views. Containers can also group other containers.
Generates a dynamic view of a device collection.
entityType connectivity dynamicDistinct dynamicMplsVpn dynamicSubnet dynamicViewTemplate entity filter filtered ipFilter manual subgraph
Generates a distinct dynamic view.
connectivity
Generates a dynamic view of MPLS
VPNs.
endNodes ceDevices
Generates a subnet dynamic view.
classes
Defines a template.
manager name Specifies a device collection to display in the network view.
Specifies a custom filter on the chosen table and fields within it.
The filter is performed on an inner join between the "entity" table and the specified table.
schema table filter
Generates a network view of a device collection, filtered based on other tables and fields.
endNodes connectivity
Generates a network view of a device collection, filtered by the IP address of each. A device must pass at least one child addressPattern filter to be shown.
Generates an empty manual view.
condition endNodes connectivity
Chapter 2. Administering network views
75
Table 6. Elements in the template XML (continued)
Element
mplsVpn tableField
Description
Generates a network view of MPLS
VPNs.
Specifies a topology database table and field to use as a category.
Attributes
ceDevices table field unassigned Generates an empty unassigned view.
Network view template attributes
Use this information to understand the attributes that are used to create an XML template for a network view.
The following table describes the attributes that are used to create a template.
Note:
Attribute values must be enclosed within quotation marks; for example, id="device_classes" .
Table 7. Attributes in the template XML
Element
ceDevices classes condition
Description
Specifies whether to display customer-edge
(CE) routers in a dynamic view of MPLS VPNs.
Options are the following: v false : do not display CE routers v true : display CE routers
Specifies which types of subnets to display in a subnet dynamic view. Options are the following: v ab : class A and B subnets v abc : class A, B, and C subnets
The operator to combine multiple filters.
Options are the following: v and v or
The default option is the "and" operator.
76
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Table 7. Attributes in the template XML (continued)
Element
connectivity
Description
Specifies the type of connectivity to use to display the network views. Options include: v ipmroute v ipsubnets v layer1 v layer2 v layer3 v ltecontrolplane v lteuserplane v noconnections v ospf v pim endNodes entityType
Note:
If you do not want to see connections between devices, then the option is connectivity="noconnections" . However, in this case a tabular view showing the devices in a list might be a better choice than one of the graphical views. You can specify a tabular layout using the layout attribute, described further down in this table.
Boolean flag that specifies whether to display end nodes, such as workstations and printers, in the network view. Options are as follows: v false: do not display end nodes (default) v true: display end nodes
Specifies the type of the device collection to display.
field filter
For example, to display VLANs, set this attribute to 16, which is the entityType field value for VLANs in the topology database.
Specifies a topology database field to use in a distinct dynamic view.
SQL filter to use. Any strings within the SQL filter must be coded within single quotation marks. It is necessary to use XML escape sequences for certain symbols. Examples of filters are: v "className = 'NetworkDevice'" v "mainNodeEntityId > 2000"
Note:
If filtering using entityId, you must specify the corresponding table attribute as entity.The filter string can use variables in the form {%variable}. For example, the following filter shows events that are older than an hour:
<filter schema="ncmonitor" table="activeEvent" filter="{%serverTime} -
FirstOccurrence > 3600"> . In Network
Manager 3.9, the only supported variable is
{%serverTime} .
Chapter 2. Administering network views
77
Table 7. Attributes in the template XML (continued)
Element
id label
Description
Contains a template identifier. If you deploy pre-configured views automatically using a template, use the id identifier to use in the auto-provision script in the dynamicViewTemplate attribute.
Contains the label used to identify a template in the Network Views GUI.
The operator sees this label in the New View dialog box when the operator creates a template-based dynamic view.
layout manager
Specifies the layout to use to display the network views: Options are as follows: v circular v grid v hierarchical v orthogonal v symmetric v tabular
Contains the name of the network management system that manages the devices to be visualized in the generated network views; for example, PrecisionIP for Network Manager.
mapIcon name pattern
Used to represent views in the Topology
Display Panel. The default map icon takes the form of a cloud. This attribute takes the following form: mapIcon="icon.svg"
Where icon is the name of the icon to use to represent the view in the Topology Display
Panel.
Note:
You can specify as a map icon any of the
.svg icons in the directory $NMGUI_HOME/ profile/etc/tnm/resource/ . You only need to specify the filename of the icon , as this filename is automatically appended to the directory path.
Contains the name of the device collection to display. You can also use this attribute to specify the name of a container node and of dynamic views.
Specifies a filter pattern for IP addresses; for example, 192.*.*.8, or 192.168.3–4.
78
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Table 7. Attributes in the template XML (continued)
Element
subgraph schema table
Description
Provides the option, within the network view, to display entities in logical groups surrounded by a boundary (cloud), which can be expanded and collapsed. This attribute can take the following values: v subgraph = "false" : enable display of entities in logical groups surrounded by a boundary (cloud).
v subgraph = "true" : enable display of entities in logical groups connected to a ring, which cannot be expanded or collapsed.
Specifies a database schema within the NCIM database. By default the value of the schema attribute is set to ncim. You do not need to specify the schema attribute if you want to reference a table in the ncim schema. However, if you want to reference a table in a different schema, then you must set the value of the schema attribute. For example, to reference the activeEvent table in the ncmonitor schema, set schema = ncmonitor .
Specifies a topology database table to use in a distinct dynamic view.
treeIcon useCollectionHierarchy
Used to represent views in the Navigation
Panel. The default tree icon takes the form of a cloud. This attribute takes the following form: treeIcon="icon.png"
Where icon is the name of the icon to use to represent the view in the Navigation Panel.
Note:
You can specify as a tree icon any of the
.png icons in the directory $NMGUI_HOME/ profile/etc/tnm/resource/ . You only need to specify the filename of the icon , as this filename is automatically appended to the directory path.
For selected dynamic network view device collections, this option enables you to view the network view as a hierarchical structure. The flag takes one of the following values:
Hierarchical
(present the collections in a hierarchy), or Flat (present the collections in a flat list).
Chapter 2. Administering network views
79
Entity types
The entityType table contains all the entity types that are available in the NCIM topology database.
The following table lists the entity types available in the topology database.
8
9
10
Table 8. Network Manager entities
0
1
2
Entity type
3
4
5
6
7
11
12
13
14
15
16
17
Entity type name Category NCIM table Description
Unknown
Chassis
Interface
Element
Element
Element physicalChassis networkInterface
Logical Interface Element networkInterface Interfaces with entityType 3 are inferred but are not directly accessible. Hot Standby Routing
Protocol (HSRP) virtual IP interfaces are an example of logical interfaces.
VLAN port on a main node device.
Local VLAN
Module
Daughter Card
Fan
Backplane
Sensor
Virtual Router
CPU
Subnet
Element
Element localVlan physicalCard Card within a switch or router. The term module is used to avoid confusion with the term card which is used in layer 1 networks.
Power
® supply unit within a main node device.
PSU Element physicalPower
Supply
Logical Collection Collection
Slot
Element
Element physicalFan
Examples of logical collections include MPLS
VPNs, global VLANs and subnets. NCIM can also model OSPF areas.
The child of a network card.
Fan component within a main node device.
Element physicalBackplane Backplane component within a main node device.
Backplanes usually contain slot entities.
Element physicalSlot
Element physicalSensor
Element virtualRouter
Slot component within a main node device. Slots usually contain module entities.
Sensor component within a main node device.
Represents a instance of a virtual router within a chassis device.
Element cpu
Collection subnet
Represents Central Processing Units (CPUs).
Logical collection that lists the IP address in a class A, B, or C subnet.
Global VLAN
VPN
Collection globalVlan
Collection networkVpn
Main node device.
Interfaces with entityType 2 can be discovered and polled.
Collection of VLAN entities across multiple chassis devices that combine to form a virtual network.
Logical collection of IP address collected within a
VPN.
80
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
38
40
41
22
23
24
25
32
33
34
28
29
30
31
Table 8. Network Manager entities (continued)
Entity type
18
19
20
21
26
27
35
36
37
42
43
Entity type name Category NCIM table Description
HSRP Group
Stack
VRF
Collection hsrpGroup Represents an Hot Standby Routing Protocol
(HSRP) group logical collection. The Cisco HRSP implements a virtual router with its own IP and
MAC addresses. This virtual router forms an
HSRP group that consists of a number of real interfaces, only one of which is active at any given time. The active interface forwards IP traffic that is sent to the virtual router, and the other interfaces in the group stand by ready to become active if the active interface fails.
Element Collection of chassis devices as defined by the
Entity MIB.
Represents a VPN routing and forwarding table.
Element vpnRoute
Forwarding
Collection ospfRoutingDomain Represents an OSPF routing domain.
OSPF Routing
Domain
OSPF Service
OSPF Area
VTP Domain
Other
BGP Service
BGP AS
BGP Route
BGP Cluster
BGP Network
ISIS Service ospfService physicalOther bgpRouteAttribute bgpNetwork
ISIS Level Element
OSPF Pseudo-Node Element
ITNM Service Collection itnmService
MPLS TE Service
MPLS TE Tunnel
MPLS TE Resource Element mplsTETunnel
MPLS LSP
IP Connection
PIM Service
PIM Network
IPMRoute Service
Service
Collection ospfArea
Collection vtpDomain
Element
Service bgpService
Collection bgpAutonomous
System
Attribute
Collection bgpCluster
Service
Collection
Service
Element
Element
Element
Service mplsTEService mplsTETunnel
Resource mplsLSP ipConnection pimService
Collection pimNetwork
Service ipMRouteService
Represents an OSPF service running on a device.
Represents an OSPF area.
Represents a VLAN trunking protocol domain.
Stores attributes of a component whose entity type the discovery was unable to determine. This occurs if the physical entity class is known, but does not match any of the supported values.
Represents a BGP service.
Represents a BGP autonomous system.
Represents a BGP route.
Represents a BGP cluster.
Represents a BGP network.
Represents an ISIS service.
Represents the ISIS level.
Represents an OSPF pseudo-node.
The base type for other services such as ISIS
Service.
Represents a Multi Protocol Label Switching
Traffic Engineered (MPLS TE) service
Represents an MPLS TE tunnel
Represents an MPLS TE resource
Represents an MPLS Label Switch Path (LSP)
Represents a connection using TCP/IP.
Represents a Protocol Independent Multicast
(PIM) service.
Represents a PIM network.
Represents an IP Multicast Routing service.
Chapter 2. Administering network views
81
Table 8. Network Manager entities (continued)
Entity type
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
67
68
Entity type name
IPMRoute
Upstream
IPMRoute
Downstream
IPMRouteMdt
IPMRouteSource
IPMRouteGroup
IP Path
IP End point
VLAN Trunk End point
Frame Relay End point
OSPF End point
ATM End point
VPWS End point
BGP End Point
ISIS End Point
MPLS Tunnel End
Point
TCP/UDP End
Point
PIM End Point
IPMRoute End
Point
IGMP End Point
Network Service
Entity End Point
LAG End Point
Probe End point
Category NCIM table Description
Protocol
Endpoint
Protocol
Endpoint
Protocol
Endpoint
Protocol
Endpoint
Protocol
Endpoint
Element ipMRouteUpstream Stores the upstream (RPF) route statistics for each device or Multicast Distribution Tree (MDT).
Element Stores the downstream route statistics per device or MDT.
Collection ipMRouteMdt
Element
Element ipMRouteSource ipMRouteGroup
Stores the Collection entities representing the
MDTs for each Multicast Source or Group.
Represents Multicast Sources, as contained by the
MDT.
Represents Multicast Groups, as contained by the
MDT.
Collection ipPath
Protocol
Endpoint ipEndPoint
Protocol
Endpoint
Represents a network path between IP devices.
Represents a logical IP end point that is implemented by a physical interface.
vlanTrunkEndPoint Represents a logical VLAN trunk end point that is implemented by a physical interface.
Protocol
Endpoint
Protocol
Endpoint
Protocol
Endpoint
Protocol
Endpoint frameRelay
EndPoint ospfEndPoint atmEndPoint vpwsEndPoint
Represents a logical Frame Relay end point that is implemented by a physical interface.
Represents a logical OSPF end point that is implemented by a physical interface.
Represents a logical ATM end point that is implemented by a physical interface.
Represents a logical VPWS end point that is implemented by a physical interface.
Protocol
Endpoint
Protocol
Endpoint
Protocol
Endpoint
Protocol
Endpoint
Protocol
Endpoint bgpEndPoint mplsTETunnelEnd
Point pimEndpoint
Represents a logical BGP end point that is implemented by a physical interface.
Represents a logical ISIS end point that is implemented by a physical interface.
Represents a logical MPLS tunnel end point that is implemented by a physical interface.
Represents a logical TCP/UDP end point that is implemented by a physical interface.
Represents the Protocol Independent Multicast
(PIM) end points discovered in the network and their associated attributes.
ipMRouteEndPoint Stores information on the IP Multicast Routing
Protocol End Points.
igmpEndPoint Stores information on the Internet Group
Membership Protocol (IGMP) End Points.
networkService
Entity
EndPoint lagEndPoint
Helps model relationships related to the management of frame relay links.
probeEndPoint
Represents a logical Link Aggregation Group
(LAG) end point that is implemented by a physical interface.
Fix Pack 3 Represents the source or target end point of a probe operation, implemented by a physical interface.
82
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Table 8. Network Manager entities (continued)
71
72
73
74
75
77
78
79
80
81
82
Entity type
70
83
84
85
86
87
90
91
92
110
111
112
113
120
Entity type name Category NCIM table Description
Topology
Layer 1 Topology
Layer 2 Topology
Layer 3 Meshed
Topology
Converged
Topology (Layer 1 -
Layer 3)
Topology
Topology
MPLS TE Topology Topology
Pseudo Wire
Topology
OSPF Topology
BGP Topology
IP Path Topology
PIM Topology
Local VLAN
Topology
Topology
Topology
Topology
Topology
Topology
Topology
Topology
Topology
Topology ipPath
Grouping of connections which belong to a topology.
Grouping of connections which belong to a Layer
1 topology.
Grouping of connections which belong to a Layer
2 topology.
Grouping of connections which belong to a Layer
3 meshed topology.
Based on data available in NCIM, groups together connections at the lowest layer for which data is available.
Grouping of connections which belong to an
MPLS TE topology.
Grouping of connections which belong to a
Pseudo Wire topology.
Represents an OSPF topology.
Represents a BGP topology.
Represents an IP path.
Represents PIM topologies.
Represents local VLAN topologies.
IPMRoute Topology Topology
VPLS Pseudo Wire
Topology
Topology
Virtualization
Topology
Topology
Microwave
Topology
RAN Topology
Topology
Topology
LTE Control Plane Topology
Represents an IP Multicast Routing topology.
Respresents a VPLS Pseudo Wire Topology.
Represents a virtualization topology.
Represents a microwave topology.
LTE User Plane Topology
Represents a radio access network topology.
Represents the devices and connectivity that make up the LTE control plane.
Represents the devices and connectivity that make up the LTE user plane.
Probe Topology Topology
Generic Collection Collection genericCollection
Geographic
Location
Represents the probe source/target connectivity.
A collection that is not of any other type.
Element geographicLocation Represents a geographic location.
Geographic Region Collection geographicRegion Represents a geographic region.
VLAN Ports Collection vlanCollection Represents a collection of the ports on a given named VLAN or, if no name is provided, on a given VLAN identifier.
IGMP Service Service igmpService Represents an Internet Group Management
Protocol (IGMP) service.
Chapter 2. Administering network views
83
126
127
128
130
131
132
133
134
135
136
137
138
139
150
Table 8. Network Manager entities (continued)
Entity type
121
122
123
124
125
151
152
153
Entity type name Category NCIM table Description
IGMP Groups
VSI (Virtual Switch
Instance)
Collection igmpGroup Stores multicast group collections for which there are associated Internet Group Membership
Protocol (IGMP) end points in the igmpEndPoint table.
Element virtualSwitch
Instance
Represents a virtual switch instance (VSI) configured on a Provider Edge (PE) device that is associated with a Virtual Private LAN Service
(VPLS) Virtual Private Network (VPN) instance.
Represents a data center.
Element
Collection virtualCluster
Service
Represents a cluster of virtual machines.
virtualMgmtService Represents a virtual management service.
Data Center
Virtual Cluster
Virtual
Management
Service
Hypervisor
Port Group
EMS System
RAN GSM Cell
Element hypervisor
Collection portGroup
Element emsSystem
Element ranGSMCell
Represents a hypervisor.
Represents a port group.
Represents an EMS system accessed by a collector.
Represents a GSM cell.
RAN UTRAN Cell Element ranUtranCell
RAN Sector Element ranSector
RAN NodeB Local
Cell
Represents a UTRAN cell.
Represents a RAN sector.
Element ranNodeBLocalCell Represents a NodeB Local Cell.
RAN Location Area Collection ranLocationArea
RAN Routing Area Collection ranRoutingArea
RAN Packet Core Collection
RAN Circuit Core Collection
RAN Radio Core
RAN Transceiver
LTE Sector
Collection ranRadioCore
Collection ranTransceiver
Element eUtranSector
LTE Cell
MME Function
Tracking Area
Element
Element eUtranCell mmeFunction
Collection trackingArea
Represents a RAN Location Area.
Represents a RAN Routing Area.
Represents RAN packet switch core entity.
Represents a RAN circuit switched core entity.
Represents a RAN radio core entity.
Represents a RAN transceiver.
Represents a geographic area of radio coverage and is implemented and supported by physical radio equipment. An LTE sector implements one or more LTE cells.
Represents a geographical area of radio coverage and is implemented and supported by physical radio equipment, such as towers, amplifiers, and antennas.
The Mobility Management Entity (MME) is the main signalling control element in the core network and is the key control node for enabling user equipment access to the core network. The role of the MME is implemented within a network hardware node and is modelled by
NCIM using the mmeFunction entity type.
Multiple mmeFunction instances can be implemented within a single network hardware node.
Represents an LTE tracking area.
84
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Table 8. Network Manager entities (continued)
Entity type
154
NCIM table
sgwFunction
155 PGW Function Element pgwFunction
156
157
158
159
160
Entity type name
SGW Function
ENB Function
LTE Pool
PLMN
HSS Function
PCRF Function
Category
Element
Element enbFunction
Collection ltePool
Element plmn
Element hssFunction
Element pcrfFunction
Description
The Serving Gateway (SGW) resides in the user plane where it forwards and routes packets to and from the eNodeB and packet data network gateway (PGW). The role of the SGW is implemented within a network hardware node and is modelled by NCIM using the sgwFunction entity type. Multiple sgwFunction instances can be implemented within a single network hardware node.
The Packet Data Network Gateway (PGW) provides user plane connectivity to packet data networks. The role of the PGW is implemented within a network hardware node and is modelled by NCIM using the pgwFunction entity type.
Multiple pgwFunction instances can be implemented within a single network hardware node.
The eNodeB device manages the radio air interface communication with users of the LTE network. Each eNodeB device controls one or more cells, which are geographic areas of radio coverage. The role of the eNodeB is implemented within a network hardware node and is modelled by NCIM using the enbFunction entity type.
Multiple enbFunction instances may be implemented within a single network hardware node.
Generic modelling mechanism for groups of pooled LTE entities, and currently used to model
MME pools, PGW pools, and SGW pools. As an example, in order to model an MME pool, the relationship between the ltePool entity and associated mmeFunction entities is modelled using the collects table.
Models a Public Land Mobile Network (PLMN).
A PLMN is a network that provides land mobile telecommunications services to the public. Each operator providing mobile services has its own
PLMN.
Models the LTE Home Subscriber Service (HSS).
The HSS manages subscriber identities, service profiles, authentication, authorization, and quality of service (QoS), and acts as the master repository for subscriber profiles, device profiles and state information.
Models the LTE Policy and Charging Rules
Function (PCRF). The PCRF manages the policy and charging for uplink and downlink service flows and the permitted EPS bearer QoS.
Chapter 2. Administering network views
85
Table 8. Network Manager entities (continued)
Entity type
161
163
164
170
171
190
191
192
Entity type name Category NCIM table Description
EIR Function
LTE Control Plane
LTE User Plane
Aggregated Link
Element
Collection
Collection eirFunction controlPlane
ViewCollection userPlane
ViewCollection
Models the LTE Equipment Identity Register
(EIR). The EIR keeps track of mobile devices which should either be banned from using the network or monitored. When a mobile phone is stolen its identity it is added to the EIR blacklist and the result is that this phone will never be able to attach to the network for service. Usually each network has its own EIR which is often combined with the HSS node. It is possible for multiple operators to share a common EIR which enables the blacklisted information to be more easily and widely available.
Supports the dynamic collection views under LTE
Network Topology
> Control Plane by Tracking
Area
in the Network Views. Each instance of this entity type collects the eNodeBs in the corresponding tracking area, together with the devices that these eNodeBs are connected to on the control plane.
Supports the dynamic collection views under LTE
Network Topology
> User Plane by Tracking
Area
in the Network Views. Each instance of this entity type collects the eNodeBs in the corresponding tracking area, together with the devices that these eNodeBs are connected to on the user plane.
Collection aggregatedLink Represents a network link between Link
Aggregation Groups (LAGs)
Element aggregationGroup Represents a Link Aggregation Group (LAG).
Link Aggregation
Group
Probe Service Service probeService
Probe
Probe Collection
Collection probe
Collection probeCollection
Fix Pack 3 Represents the service that provides probes on a device.
Fix Pack 3 Represents configured network probes and their attributes.
Fix Pack 3 Provides a collection facility for probes or probe collections.
86
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Chapter 3. Administering network view bookmarks
Network view bookmarks group together just those network views that you or your team need to monitor. Create new bookmarks or change existing bookmarks to help network operators visualize just those devices that they need to monitor.
About network view bookmarks
Network view bookmarks group together selected network views.
Each network view bookmark contains selected network views in a tree structure that is inherited from the network view libraries. If you add a parent network view to a bookmark, you automatically also get all the children networks views in the bookmark. If you want only certain child network views you can do this by adding just those child network views to the bookmark.
For example, a NOC administrator is creating a network view bookmark to assign to his NOC. The parent network view Subnet contains six subnet network views,
A through F. The administrator adds subnets A, B, and C to the bookmark, but does not add subnets D, E, and F, because his NOC is not responsible for monitoring subnets D through F.
Note:
In this example, the system automatically adds the parent network view
Subnets
to the bookmark. The Bookmarks treetable displays system-added views, such as the Subnets view in this example, with an asterisk to the left of the network view name. Manually added views, such as views A, B, and C in this example, are displayed without an asterisk to the left of the view name.
Read-write and read-only permissions for bookmarks can be set on individual user and on a group basis. By default this can be done by an administrator. Permissions for a bookmark can also be set globally; global permission apply to everyone else, that is, all users who have neither individual user permissions for the bookmark, nor are members of any of the groups that have group permissions for the bookmark. In addition, individual operators can create their own bookmarks.
The maximum alert status of all entities in a network view is reported in the network view bookmark tree for all bookmarks.
Creating network view bookmarks
Create a network view bookmark to group together just those network views that you or your team need to monitor.
To create a network view bookmark:
1.
Click the Incident icon and select Network Availability > Network Views.
2.
Within Network Views, in the Bookmarks tab, click Create Bookmark
3.
Complete the Bookmark Properties window as follows:
.
Name
To create a new bookmark, type the name of the bookmark. To change the name of an existing bookmark, type the new name of the bookmark over the current name.
© Copyright IBM Corp. 2006, 2017
87
Note:
Bookmark names cannot be blank and must be unique per user account.
Set as Default
Click here to set this bookmark as the default bookmark which displays on each visit to the Network Views > Bookmarks tab.
Bookmark permissions sections
If you have the ncp_bookmark_admin role, then you can modify permissions for the current bookmark using the panel sections below. If you do not have this role then you can only view the permissions for the current bookmark. By default the itnmadmin user has this role.
Also, any user that is a member of the administrator group
Network_Manager_IP_Admin has this role.
User Permissions
In this part of the panel you can set individual user permissions for the current bookmark.
New permission
Click here to set a new permission for a specific user.
Options are read-only or read-write. Clicking this button adds a row to the User Permissions table. In the
User
column, click and select from the drop-down list to select a user. In the Permissions column, click and select from the drop-down list to set a permission for this user.
Delete permission
Select one or more rows in the User Permissions table and then click this button to remove permissions for the selected user or users.
Group Permissions
In this part of the panel you can set user group permissions for the current bookmark.
New permission
Click here to set a new permission for a user group.
Options are read-only or read-write. Clicking this button adds a row to the Group Permissions table. In the Group column, click and select from the drop-down list to select a user group. In the Permissions column, click and select from the drop-down list to set a permission for this user group.
Delete permission
Select one or more rows in the Group Permissions table and then click this button to remove a permissions for the selected user group or groups.
Global Permissions
Click here and select from the drop-down list to set global permissions for the current bookmark. Options are none, read-only or read-write. The global permission setting on a given bookmark applies to all other users; that is all users who meet both of the following criteria:
88
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
v They are not mentioned in the User Permissions section.
v
They are not members of any of the groups in the Group
Permissions
section.
4.
Click OK. The new network view bookmark is added to the bookmarks drop-down list. Open the bookmarks drop-down list to see the new bookmark.
Note:
If you set this bookmark as the default bookmark, then it appears at the top of the list. Otherwise it appears in the list in alphabetical order.
Editing network view bookmarks
You can edit bookmarks properties and also change the network views contained in a bookmark.
Editing bookmark properties
You can edit the bookmark name, change the default bookmark settings, or, view or edit the bookmark permissions.
To edit bookmark properties:
1.
Click the Incident icon and select Network Availability > Network Views >
Bookmarks
.
2.
Click Edit Bookmark .
3.
Complete the Bookmark Properties window as follows:
Name
To create a new bookmark, type the name of the bookmark. To change the name of an existing bookmark, type the new name of the bookmark over the current name.
Note:
Bookmark names cannot be blank and must be unique per user account.
Set as Default
Click here to set this bookmark as the default bookmark which displays on each visit to the Network Views > Bookmarks tab.
Bookmark permissions sections
If you have the ncp_bookmark_admin role, then you can modify permissions for the current bookmark using the panel sections below. If you do not have this role then you can only view the permissions for the current bookmark. By default the itnmadmin user has this role.
Also, any user that is a member of the administrator group
Network_Manager_IP_Admin has this role.
User Permissions
In this part of the panel you can set individual user permissions for the current bookmark.
New permission
Click here to set a new permission for a specific user.
Options are read-only or read-write. Clicking this button adds a row to the User Permissions table. In the
User
column, click and select from the drop-down list
Chapter 3. Administering network view bookmarks
89
to select a user. In the Permissions column, click and select from the drop-down list to set a permission for this user.
Delete permission
Select one or more rows in the User Permissions table and then click this button to remove permissions for the selected user or users.
Group Permissions
In this part of the panel you can set user group permissions for the current bookmark.
New permission
Click here to set a new permission for a user group.
Options are read-only or read-write. Clicking this button adds a row to the Group Permissions table. In the Group column, click and select from the drop-down list to select a user group. In the Permissions column, click and select from the drop-down list to set a permission for this user group.
Delete permission
Select one or more rows in the Group Permissions table and then click this button to remove a permissions for the selected user group or groups.
Global Permissions
Click here and select from the drop-down list to set global permissions for the current bookmark. Options are none, read-only or read-write. The global permission setting on a given bookmark applies to all other users; that is all users who meet both of the following criteria: v They are not mentioned in the User Permissions section.
v They are not members of any of the groups in the Group
Permissions
section.
4.
Click OK.
Adding a network view to a bookmark
Add a network view to a bookmark by right-clicking the desired network view in the network view libraries tree.
To add network views to a bookmark:
1.
Click the Incident icon and select Network Availability > Network Views >
Libraries
.
2.
Select a single network view as follows: a.
From the network view library drop-down list above the network view tree, select the network view library that contains the network view to add to the bookmark.
b.
In the network view tree navigate to the desired network view.
3.
Right-click the desired network view and click Add to Bookmark, then in the submenu, click the name of the bookmark to add the network view to. Only the bookmarks that you have permission to read and write to appear in the list.
For example, if you want to add the selected network views to an existing
90
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
bookmark named Bookmark1, then click Add to Bookmark > Bookmark1.
Network views are added to the bookmark in the following way: v
If you selected a parent network view, then the parent network view and all of its child network views are added to the bookmark. If the parent network view is a dynamic network view, then as child network views are added to or removed from the parent following network discovery, the views are added to or removed from the bookmark automatically.
v If you selected one or more child network views whether of a standard or dynamic parent network view then only the network views you selected are added to the bookmark. In addition, individually selected child network views of dynamic parent network views will be automatically removed from the bookmark if the child network view is removed following network discovery.
v Whichever view you add to a bookmark, the system automatically adds its parent, the parent's parent, and so on until it gets to the top of the tree.
Note:
Manually added network views appear without an asterisk to the left of the view name. System-added network views appear with an asterisk to the left of the view name. For example, if you added a parent network view to the bookmark, then the parent network view and all of its child network views are added to the bookmark. Asterisks are shown as follows: v The parent network view was manually added, and therefore appears without an asterisk.
v The child network views were added by the system, and therefore appear with an asterisk.
Removing a network view from a bookmark
Remove a network view from a bookmark by right-clicking a network view in the network view bookmarks tree.
To remove network views from a bookmark:
1.
Click the Incident icon and select Network Availability > Network Views >
Bookmarks
.
2.
Select a single network view as follows: a.
From the network view bookmarks drop-down list above the network view tree, select the network view bookmark that contains the network view to remove from the bookmark.
b.
In the network view bookmarks tree, navigate to the desired network view.
Restriction:
You can only remove network views from the bookmark that were manually added to the bookmark earlier, as follows: v The network views that you can remove appear without an asterisk to the left of the view name. These are manually added views.
v The network views that you cannot remove appear with an asterisk to the left of the view name. These are views added by the system. System-added views are parents or children of manually added views.
3.
Right-click the desired network view and click Remove view from bookmark.
Restriction:
You can only remove a view from a bookmark if you have read-write permission on that bookmark, or you have the ncp_bookmark_admin role.
The selected view is removed from the bookmark.
Chapter 3. Administering network view bookmarks
91
Note:
If a view is removed that is part of a hierarchy of other views that were previously added then that view will not be physically removed from the tree but will be marked with an asterisk (*).
Deleting a network view bookmark
Deleting a network view bookmark completely removes that bookmark from the system.
To delete a network view bookmark:
1.
Click the Incident icon and select Network Availability > Network Views >
Bookmarks
.
2.
From the network view bookmarks drop-down list, select the bookmark that you want to delete.
3.
Click Delete Bookmark .
Restriction:
You can only delete a bookmark if you have read-write permission on that bookmark, or you have the ncp_bookmark_admin role.
The bookmark is removed from your system.
92
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Chapter 4. Configuring tools and menus
You can create and edit context menus, configure user access to menu items, define the context in which menus are available, and create tools that can be run from the context menus.
About context menus
Context menus are opened by right-clicking on devices, events, subnets, links, or components within the device structure browser, for example network ports. You can run tools from context menus. You apply filters to menus and tools.
As an administrator, you can create context menus that enable operators to run tools on devices, events, subnets, links, or components within the device structure browser. You can configure which users can access the tools, and where the tools, menus and menu hierarchies can be used from.
About filters
Filters are pieces of XML code that form part of an XML menu definition or an
XML tool definition. There are two types of filter: context filters and security filters.
Filter characteristics are inherited by submenu and tools. For example if the My
Tools...
menu has context or security restrictions, then these restrictions are applied to all menus and tools within the My Tools... menu.
If no filter is present then the menu or tool will always appear in the context menu.
Related tasks
:
“Defining context filters for tools and menus” on page 108
You can specify the types of views in which a menu or tool is available, and which devices it can be run on, using context filters.
“Defining user access for tools and menus” on page 110
You can specify the users, roles, and groups authorized to display a tool or menu using security filters.
About tools
Tools are defined in XML files in the $NMGUI_HOME/profile/etc/tnm/tools/ directory. You can associate URL tools with a menu option.
Related tasks
:
“Creating tools for context menus” on page 99
You can create tools for operators to use and add them to context menus on a network map.
© Copyright IBM Corp. 2006, 2017
93
Configuring context menus
You can add a menu item to, or edit the menu items in, the context menus that are displayed when you right-click a device or subnet from a topology map.
You can associate tools with menu items to enable network operators to right-click a device, link or subnet and run a script or a third-party Web application. Tools can also be invoked from components in the device structure browser, such as network ports, via the Tools menu. Any new menu items you define appear after the default menu items.
To add or edit an item in a context menu for a device, event, subnet, link or component within the device structure browser, complete the following steps.
1.
Edit an XML file in the $NMGUI_HOME/profile/etc/tnm/menus/ directory.
2.
Configure the elements and attributes of the menu definition to define the name, filters, label, and other properties of the menu item. Use the reference information about the XML elements and attributes available for menu items and the example provided to help you define the menu item.
3.
Add the menu item that you have defined to the appropriate menu type in the
$NMGUI_HOME/profile/etc/tnm/topoviz.properties
file:
Menus launched from devices
topoviz.menu.device = menu-id
Menus launched from subnets
topoviz.menu.subview = menu-id
Where menu-id is an identifier that points to the top level of a menu hierarchy defined in an XML file in the $NMGUI_HOME/profile/etc/tnm/menus/ directory.
Subnets require a separate menu because the tools executed on subnets are executed for all nodes contained within the subnet.
The following example defines a menu item for devices with the identifier
“mytools”: topoviz.menu.device = mytools
XML elements and attributes for defining context menus
Understand the different XML elements and attributes that define context menu items.
Sample menu item definition
The following example shows the format of an XML file that defines a menu item.
Elements are highlighted in bold for clarity.
<ncp_menu id="mytools" label="My Tools" key="key">
<context>
<!-- This section of the xml file is a context filter. -->
<!-- Context filters specify the device and view conditions -->
<!-- under which this menu is displayed. -->
</context>
<security>
<!-- This section of the xml file is a security filter. -->
<!-- Security filters specify the users, roles and groups -->
<!-- authorized to display this menu. -->
</security>
<definition>
<tool id="ncp_dns"/>
<separator/>
94
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
<menu id="ncp_cisco"/>
<menu id="ncp_juniper"/>
</definition>
</ncp_menu>
XML elements and attributes
The following table describes the elements and attributes used to define context menus, with reference to the above example.
Table 9. Elements and Attributes in the menu XML definition file
Element or attribute
ncp_menu context security id label key tool
Type
Element
Element
Element
Attribute
Attribute
Attribute
Element
Description
Introduces the definition of a menu.
Defines the views and devices that the menu items is available from. Use the reference information about defining context filters to define this attribute.
Defines the users, groups and roles that are allowed to view the menu item. Use the reference information about defining user access filters to define this attribute.
Contains an alphanumeric identifier for this menu.
Contains the actual text of the menu option that appears in the context menu.
Used as a lookup into the $NMGUI_HOME/profile/etc/tnm/ locale/ncp_menus(_xx_XX).properties
file. This allows you to specify translations of the menu label for users with different locale settings.
Inserts a tool with the specified id into the menu.
separator menu
Element
Element
In this example, a tool with the id ncp_dns is inserted into the menu. The associated menu text for this tool is DNS
Lookup
.
The ncp_dns tool is defined in a separate XML file stored in
$NMGUI_HOME/profile/etc/tnm/tools/ .
Inserts a separator into the menu.
Inserts a submenu with the specified id into the menu.
In this example, two submenus are defined: v The ncp_cisco submenu. The associated menu text for this submenu is Cisco Tools....
v The ncp_juniper submenu. The associated menu text for this submenu is Juniper Tools....
Each of these submenus is defined in a separate .xml file stored in $NMGUI_HOME/profile/etc/tnm/menus/. These .xml
files are formatted according to the rules defined in this section.
Chapter 4. Configuring tools and menus
95
Configuring WebTools
The itnmadmin user can configure WebTools by modifying values in the related configuration files.
WebTools is one of the ready-to-use right-click tools that are provided by Network
Manager. Use WebTools to perform diagnostic and information retrieval actions on network devices that are shown in network views. The itnmadmin user can modify how users use WebTools.
About WebTools
The itnmadmin user can configure WebTools to extract values from one WebTools command output, and then use the values as parameter-values for the next command.
To reuse values from a WebTools command, you must update the definition files for the WebTools tool. There is one set of definition files per tool. The definition files consist of a template file that acts as a wrapper, and a processor file.
Update the WebTools tool definition files.
v Within $NCHOME/core/precision/scripts/webtools/etc/templates/ update the template file. The standard template file that is included in the product is called ncp_wt_border.tmpl
.
v Within $NCHOME/core/precision/scripts/webtools/etc/processors/ update the processor file. The standard processor files that are included in the product are called advtraceroute_exec.proc, default_exec.proc, default_telnet.proc, and notitle_exec.proc
.
Enter the following command, this command tells the ncp_webtool.cgi script to load the DNSLookup.xml file and use 8.8.8.8 as the query parameter and do whatever is defined within the DNSLookup.xml file.
Run the command ncp_perl ../bin/ncp_webtool.cgi toolid=DNSLookup query=8.8.8.8
The DNSLookup.xml file and other .xml files give the following types of definitions.
Lists the named parameter to accept and their types.
The template file to use.
The data processor file to use.
The order in which things within the tool must be run.
The tools within WebTools can be one of two types.
v A helper tool. This tool uses the Network Manager SSH Telnet stack to access a device and run a series of commands against the device as defined by the tool definition. Use the CiscoShowRoute.xml file as an example of a helper tool. The
CiscoShowRoute.xml
file sets term length zero to avoid pagination and not does not include the output of the query in the results visible=0. Then, the file runs show ip route and supplies the parameters that are called vrf, vrfname, target , in that order and if the parameters are specified. You can also run the helper tools from the command line.
<commands>
<command visible="0" allow_early_match="1" response_time="5000">term length 0</command>
<command visible="1" allow_early_match="1" response_time="5000">show ip route ##vrf## ##vrfname##
##target##</command>
</commands>
96
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
v An executable tool. This tool runs a command on the Network Manager backend server and passes named parameters to it. For this example, the DNSLookup.xml
file runs the executable file and passes in the type and query parameters, which are also defined in the file, into the script in that order.
<command>
<executable>${NCWTHOME}/bin/ncp_wt_nslookup.pl</executable>
<argument>type</argument>
<argument>query</argument>
</command>
Limiting menus from WebTools
The itnmadmin user can modify the list of WebTools menu items visible to a specific role.
1.
Within $ITNMHOME/gui/precision_gui/profile/etc/tnm/menus, open the configuration file for the WebTools menu item that you want to modify. For example, for the Topology Management menu item, open the ncp_topo_mgmt_menu.xml
configuration file.
2.
Within the configuration file, for the role name parameter, enter the role name.
v Display the Topology Management menu item if users are assigned the ncp_topo_mgmt role and you are in the hop view.
[root@CO9128108199 menus]# more ncp_topo_mgmt_menu.xml
<?xml version="1.0" ?>
<ncp_menu id="ncp_topo_mgmt_menu" key="ncp_topo_mgmt_menu" label="Topology Management">
<definition>
<tool id="addDevice"/>
<tool id="deleteDevice"/>
<tool id="addConnection"/>
<tool id="removeConnection"/>
</definition>
<context>
<attribute id="clientType">
<equals value="ncp_hopview" />
</attribute>
</context>
<security>
<role name="ncp_topo_mgmt"/>
</security>
</ncp_menu> v Display the Apply Policy menu item if users are assigned the ncmPolicyCheck role and they select one device for which there is a record in the networkConfigMgr table and the device ncmKey is not empty. The entityId lookup is implicit in this example.
[root@CO9128108199 tools]# more itncm_apply_policy.xml
<?xml version="1.0"?>
<ncp_tool id="itncm_apply_policy" key="itncm_apply_policy" label="Apply Policy" type="url" runOnList="true" runForEach="false">
<url value="ITNCMWizard/jsp/servlet/ITNCMWizardApplyPolicy.jsp" target="_blank" method="GET">
<parameter name="ui.action" valueType="text" text="run" />
<parameter name="ui.name" valueType="text" text="Apply Policy" />
<parameter name="wizardType" valueType="text" text="apply_policy" />
<parameter name="applicationType" valueType="text" text="device" />
<parameter name="applicationKeys" valueType="ncim" table="entity" column="entityid" />
</url>
<context>
<parameter name="applicationNames" valueType="ncim" table="entity" column="entityName" />
<attribute id="deviceCount">
Chapter 4. Configuring tools and menus
97
<equals value="1" />
</attribute>
<attribute id="ncmKey" valueType="ncim" table="networkConfigMgr" column="ncmKey">
<notequals value="" />
</attribute>
</context>
<security>
<role name="ncmPolicyCheck" />
</security>
</ncp_tool>
Creating an executable WebTools tool
The itnmadmin user can create a standard WebTools tool.
An executable WebTools tool uses a task on the Network Manager backend server and the Network Manager administrator user itnmadmin must login to the server to define the new tool. After the itnmadmin user creates a standard WebTools tool, the tool becomes available for use in the WebTools menu to users with relevant roles. The itnmadmin user must complete the following steps to create a standard
WebTools tool.
1.
Within $NCHOME/core/precision/scripts/webtools/etc/, create a WebTools configuration xml file for your new executable WebTools tool. To see existing
WebTools configuration xml files, enter the $ ls command within
$NCHOME/core/precision/scripts/webtools/etc/
. For example,
$ cd $NCHOME/precision/scripts/webtools/etc/
$ ls
AdvancedPing.xml
AdvancedSubnetPing.xml
CiscoLSPPing.xml
CiscoLSPTraceroute.xml
AdvancedTraceroute.xml
CiscoMBGPInfo.xml
CiscoBGPInfo.xml
CiscoMPLSInfo.xml
CiscoIGMPInfo.xml
CiscoISISInfo.xml
CiscoMPLSTEInfo.xml
CiscoMPLSTELinkMgmtInfo.xml
CiscoMRouteInfo.xml
CiscoOSPFInfo.xml
CiscoPIMInfo.xml
CiscoPing.xml
CiscoRoutingInfo.xml
CiscoShowCDPNeighbors.xml
CiscoInterfaceList.xml
CiscoMPLSTESpecificInfo.xml
CiscoShowEtherChannelSummary.xml
2.
Create a set of definition files for the new WebTools tool. There is one set of definition files per tool, which consists of a template file that acts as a wrapper, and a processor file. The template file and processor file govern output, format, and content.
v Either create a template file within $NCHOME/core/precision/scripts/ webtools/etc/templates/ , or use the standard template file that is included in the product, which is called ncp_wt_border.tmpl.
v Either create a processor file within $NCHOME/core/precision/scripts/ webtools/etc/processors/ or use one of the standard processor files that are included in the product, which are called advtraceroute_exec.proc, default_exec.proc
, default_telnet.proc, and notitle_exec.proc.
3.
Update your WebTools configuration xml file with details for the template file and processor file to be used.
4.
Determine where your new tool menu item appears in the existing menu hierarchy on the Network Manager GUI server.
a.
Within /space/IBM/netcool/gui/precision_gui/profile/etc/tnm/tools create the WebTools tool definition file, for example MyNewScriptTool.xml.
Within the new tool definition file, supply the parameters to run the tool, as defined by the WebTools configuration file in the Network Manager backend server, for example the ncp_webtool.cgi configuration file.
b.
Within /space/IBM/netcool/gui/precision_gui/profile/etc/tnm/menus modify the GUI menu definition file, for example MyNewTool.xml.
98
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
The WebTools engine takes the new list of commands and uses the default IBM code and scripts to get the information.
Changing the output of a WebTools tool
The itnmadmin user can change the output options for a WebTool tool.
After the itnmadmin user configures a new WebTool tool, or determines a change is needed to the output for an existing WebTools tool, the itnmadmin can configure the output options of the tool. The itnmadmin user must complete the following steps to configure the output options of a WebTool tool.
1.
Create a set of definition files for the WebTools tool. There is one set of definition files per tool, which consists of a template file that acts as a wrapper, and a processor file. The template file and processor file govern output, format, and content.
v
Create a template file within $NCHOME/core/precision/scripts/webtools/ etc/templates/
.
v Create a processor file within $NCHOME/core/precision/scripts/webtools/ etc/processors/ .
2.
Within the .xml configuration files for the WebTools tool, remove references to older definition files and add references to the new definition files.
Creating tools for context menus
You can create tools for operators to use and add them to context menus on a network map.
Related concepts
:
Tools are defined in XML files in the $NMGUI_HOME/profile/etc/tnm/tools/ directory. You can associate URL tools with a menu option.
Adding reports to context menus
You can add existing reports to context menus. Operators can run the reports from devices in any network map.
There are several reports available by in the context menu by default. You can add additional reports to the context menu.
To add a report to a context menu, complete the following steps.
1.
On the server where the Dashboard Application Services Hub is installed, create or edit a tool definition XML file in the following directory:
$NMGUI_HOME/profile/etc/tnm/tools/
. Create a separate file for each menu item and give each file a meaningful name.
2.
In the tool definition file, define the parameters for the report. Some parameters, such as the domain and entity name, are retrieved from the environment and embedded in the report URL. Default values are used for report parameters that are not defined. If no default values exist, you are prompted for a value. The following example tool definition defines a tool called ifInDiscards, which launches a generic trend analysis report using the poll policy ifInDiscards.
<?xml version="1.0"?>
<ncp_tool id="ncp_ifindiscards_report" key="ncp_ifindiscards_report" label="IfInDiscards Report" type="url">
<url value="../../../tarf/servlet/component" target="_blank" windowFeatures="ScrollBars=yes,
Resizable=yes,Width=1280,Height=1024" method="GET">
Chapter 4. Configuring tools and menus
99
<parameter name="b_action" valueType="text" text="cognosViewer"/>
<parameter name="ui.action" valueType="text" text="run"/>
<parameter name="ui.object" valueType="text" text="/content/package[@name=’Network Manager’]
/folder[@name=’Performance Reports’]/report[@name=’Generic Trend Analysis’]"/>
<parameter name="ui.name" valueType="text" text="ifInDiscards Usage"/>
<parameter name="run.outputFormat" valueType="text" text="HTML"/>
<parameter name="run.prompt" valueType="text" text="false"/>
<parameter name="p_Domain" valueType="domainName" />
<parameter name="p_PollDefinition" valueType="text" text="ifInDiscards"/>
<parameter name="p_Hostname" valueType="ncim" table="entityData" column="entityName" runOnMainNode="true"/>
</url>
</ncp_tool>
3.
Edit the file $NMGUI_HOME/profile/etc/tnm/menus/ncp_reports.xml and add a menu entry that references the tool definition file. The following example defines context menu options for several reports, including the ncp_ifindiscards_report defined in the previous example, under a menu titled
Reports
.
<ncp_menu id="ncp_reports_menu" key="ncp_reports_menu" label="Reports">
<definition>
<tool id="ncp_bandwidth_in_report"/>
<tool id="ncp_bandwidth_out_report"/>
<tool id="ncp_availability_report"/>
<tool id="ncp_ifindiscards_report"/>
<tool id="ncp_memory_usage_report"/>
<tool id="ncp_cpu_usage_report"/>
<tool id="ncp_cisco_device_dashboard"/>
<tool id="ncp_monitored_policies_report"/>
</definition>
</ncp_menu>
You can define which reports are available to run on which kinds of devices by using context filters.
URL tools
A URL tool opens a new browser window and applies a specified URL.
Examples of URL tools that you can configure to extend the right-click tools include the following: v Third-party applications.
v Custom CGI scripts.
v Web sites: Use an absolute URL, for example http://www.any_company.com.
URL tools are defined in an XML file that is located in the $NMGUI_HOME/profile/ etc/tnm/tools/ directory.
You can specify the features of the window in which the tool opens. You can specify window features either by specifying the most common features using a parameter per feature, or by specifying any feature using a common parameter.
Example
The following example shows a URL tool that traces a route from the server to a selected device or component, and shows the format of the XML file used to define the URL tool. Elements and attributes are highlighted in bold for explanatory purposes only.
100
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
<ncp_tool id="server_traceroute" label="Trace route from server" type="url" runforeach="false" runonlist="true"
key="key">
<url value="/webtop/cgi-bin/traceroute.cgi" target="_blank">
<parameter name="host" valueType="ncim" table="chassis" column="accessIPaddress" runOnMainNode="true"/>
</url>
<context>
<!-- This section of the xml file is a context filter. -->
<!-- Context filters specify the device and view conditions -->
<!-- under which this tool is displayed.-->
</context>
<security>
<!-- This section of the xml file is a security filter. -->
<!-- Security filters specify the users, roles and groups -->
<!-- authorized to display this tool. -->
</security>
</ncp_tool>
Sample URL tool
Use this example information to understand the XML attributes and elements that are used to define a URL tool.
The following XML code shows the use of the parameter attribute.
<ncp_tool id="url_tool_id" label="My URL Tool" type="url"
<url value="/mytool/doSomething.do" target="_blank">
<parameter name="domain" valueType="domainName"/>
<parameter name="webtopds" valueType="webtopDataSource"/>
<parameter name="host" valueType="ncim" table="chassis" column="accessIPaddress" runOnMainNode="true"/>
<parameter name="retries" valueType="text" text="3"/>
<parameter name="userId" valueType="cookie" cookieName="userId"/>
</url>
<context>
......
</context>
<security>
......
</security>
</ncp_tool>
This example, when executed against a device, produces a URL that has the following form: https://server:port/ibm/console/mytool/doSomething.do?domain=NCOMS
&webtopDataSource=NCOMS&host=1.2.3.4&retries=3&userId=fred
Sample Window features for URL tools
Use these examples to help you specify the features of the window in which a
URL tool opens.
In the following examples, attributes are highlighted in bold for explanatory purposes only.
Example 1
The following example shows how to specify the most common features using a parameter per feature.
<ncp_tool id="url_tool_id" label="My URL Tool" type="url"
<url value="/mytool/doSomething.do" target="_blank" width="500" height="500"
status="no" resizable="no">
</url>
......
</ncp_tool>
Chapter 4. Configuring tools and menus
101
Example 2
The following example shows how to specify any window feature using a common windowFeatures parameter.
<ncp_tool id="url_tool_id" label="My URL Tool" type="url"
<url value="/mytool/doSomething.do" target="_blank" windowFeatures="width=500, height=500, menubar=no, toolbar=no, location=no, status=no, resizable=no">
</url>
......
</ncp_tool>
Adding CGI scripts to context menus
To make additional tools available when network operators right-click a device, extend the context menu to include a custom CGI script. User-defined tools are accessed by right-clicking a device.
Restriction:
You cannot launch a user-defined tool on a device of type Subnet.
You must store all CGI scripts in NCHOME/omnibus_webgui/etc/cgi-bin
You must register CGI tools in the Tivoli Netcool/OMNIbus Web GUI.
CGI script parameters
When you write a CGI script for use in an extended context menu, you must use the script parameters to reference the device from which the script is called.
To reference the device, use the following fixed parameters, which are automatically passed to user-defined scripts by TopoViz.
Attention:
The parameters are provided only when no parameters are specified in the URL tool definition. Otherwise, the parameters passed to the CGI script are as specified in the tool.
$selected_rows.ServerName
This value defines the name of the ObjectServer that corresponds to the current Network Manager domain. This value is defined in the ncp.domains
table when the topology database is created.
$selected_rows.NmosObjInst
This value is a unique identifier for the device. It is equivalent to the
ObjectId field in the mainNodeDetails table of the topology database.
$selected_rows.Node
This value is from the ObjectServer. The value is usually equivalent to the
IpAddress field in the mainNodeDetails table of the topology database.
These values refer to the device that was selected when the context menu was used. Topoviz uses an HTTP Get request to call the script and passes the above parameters in the URL. The URL is encoded into x-www-form-urlencoded format.
Non-alphanumeric characters are converted into the 3-character string %xy, where
xy is the two digit hexadecimal representation of the lower 8-bits of the character.
Example
If a script named traceroute.cgi is run on the host 192.168.21.35, and the script is passed the following variables: v
ServerName=Primary_01
102
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
v
NmosObjInst=1477
v
Node=192.168.0.7
A new browser window is opened with the following URL: https://192.168.21.35:16316/ibm/console/webtop/cgi-bin/traceroute.cgi?
%24selected_rows.ServerName%3DPrimary_01%26%24selected_rows.NmosObjInst
%3D1477%26%24selected_rows.Node%3D192.168.0.7
CGI support
Use the initialization parameters to control the behavior of CGIServlet.
CGIServlet
CGI scripts run on a Web server and use the Common Gateway Interface (CGI) to perform tasks. The support for CGI in Dashboard Application Services Hub is provided by CGIServlet, extracted from Apache Tomcat. The Tomcat CGI support is largely compatible with the Apache HTTP Server but there are some limitations
(such as only one cgi-bin directory). To change the configuration, edit web.xml in the directory where the CGI application is installed.
Servlet initialization parameters
Several initialization parameters are available for configuring the behavior of the
CGIServlet.
cgiPathPrefix
The CGI search path will start at the Web application root directory +
File.separator + this prefix. Default setting: cgiPathPrefix is Web-INF/cgi.
debug
Determines the level of debugging detail for messages that are logged by the servlet. Default setting: 0.
executable
This is type of the program to be used to run the script. Default setting: perl .
parameterEncoding
Names the parameter encoding to be used with the CGI servlet. Default setting: System.getProperty("file.encoding","UTF-8").
passShellEnvironment
Determines whether shell environment variables, if there are any, shall be passed to the CGI script. Default setting: false.
Registering tools in the Tivoli Netcool/OMNIbus Web GUI
After you have created the CGI script, and defined the appropriate tool, you must register the tool in the Web GUI so that you can use the tool in Topoviz.
The Tivoli Netcool/OMNIbus Web GUI was known as Netcool/Webtop in versions
2.2 and below. Registering your tool makes it available in Topoviz only.
From the CGI Registration window you can configure settings and properties for the tool. See the IBM Tivoli Netcool/OMNIbus Web GUI Administration and User's
Guide for more details.
To register a tool in the Web GUI:
1.
Click Content. From the Menus & Tools list, select CGI Registration >
Register
. The CGI Registration page is displayed.
Chapter 4. Configuring tools and menus
103
2.
Type the name of the tool and the file name of the script.
To make the tool available in the Web GUI, you must add the tool to the main Web
GUI client.
Making tools available in the Tivoli Netcool/OMNIbus Web GUI
In addition to registering the tool in the Web GUI, you must also make the tool available in the main Web GUI client.
The Tivoli Netcool/OMNIbus Web GUI was known as Netcool/Webtop in versions
2.2 and below.
From the Tools Editor window you can configure settings and properties for the tool. See the IBM Tivoli Netcool/OMNIbus Web GUI Administration and User's Guide for more details.
To create a tool in the Web GUI:
1.
Click the Content tab. From the Menus & Tools list, select Tools. The Tools
Editor page is displayed.
2.
Click Create. The Create New Tool page is displayed.
3.
Type the name and type of the tool.
Configuring scope of the Show Connectivity Information tool
You can specify which interface types to display when the Show Connectivity
Information
tool is run on a device in Network Hop View or Network Views. By default, all interface types are displayed.
Before performing this task you must determine the appropriate interface types
IDs. You can do this by performing the following SQL query on the NCIM topology database.
SELECT * FROM ncim.enumerations where enumGroup = ’ifType’;
The Show Connectivity Information tool displays a table of devices and interfaces connected to a selected device. By default all interface types on the selected device are included in this table. You can specify interface types to include in or exclude from this table.
1.
Open the $NMGUI_HOME/profile/etc/tnm/topoviz.properties configuration file.
2.
Specify interface types to display in the Show Connectivity Information tool by either including interface types or excluding interface types.
a.
Include interface types by typing a line similar to the following example anywhere in the topoviz.properties file.
topoviz.connectivity.includes=2,36
In this example, the Show Connectivity Information tool displays interface types 2 and 36 only.
b.
Exclude interface types by typing a line similar to the following example anywhere in the topoviz.properties file.
topoviz.connectivity.excludes=1
In this example, the Show Connectivity Information tool displays all interface types except for interface type 1.
104
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Note:
You must not use both includes and excludes parameters in the topoviz.properties
file as this may produce unexpected results in the Show
Connectivity Information
tool.
3.
Save and close the topoviz.properties file.
Creating tools that open the MIB browser
To provide additional diagnostic information for network operators, create custom tools that open the MIB browser from an Event Viewer or from a topology map, and display information in the MIB browser.
For example, you can create a tool that opens the MIB browser in an Event Viewer, performs an SNMP Walk query on all the interfaces of the affected device, and automatically displays this interface MIB data in the MIB browser.
MIB browser modes
Custom tools can open the MIB browser in one of two modes, full mode or
results-only mode.
Full mode
The complete MIB browser page is displayed, with the MIB tree, MIB
Variable Information panel, and the SNMP Query Results panels
Results-only mode
The results of the MIB browser query are displayed in the SNMP Query
Results panel, as a single page.
Creating a custom tool
To provide additional information for network operators from an Event Viewer or topology map, create a custom tool that displays information in the MIB browser.
1.
Decide which data you want the MIB browser to display, and how you want the MIB browser to display the data.
2.
Determine the URL that opens the MIB browser with the required content and format. The URL must have the following format: https://host:port/ibm/console/ncp_mibbrowser/Launch.do
Where: v host is the IP address of the host on which the Dashboard Application
Services Hubserver is running.
v
port is the port to access on the host. The default value is 16316.
A URL in this format starts the MIB browser with the Domain option set to the first value in the list, and with no Host or Value options set in the SNMP
Query
toolbar.
3.
Write a CGI script that constructs the URL in response to a right-click in an
Event Viewer or in a topology map.
4.
To define and store the tool for use in Topoviz, register the tool in the Tivoli
Netcool/OMNIbus Web GUI. The Tivoli Netcool/OMNIbus Web GUI was known as Netcool/Webtop in versions 2.2 and below.
5.
To define and store the tool for use in the Web GUI, create the tool in the Web
GUI.
6.
To make the tool available as a right-click option in a context menu, create a menu entry in the Web GUI.
Chapter 4. Configuring tools and menus
105
Optional parameters for MIB browser URLs
When you define a URL that starts the MIB browser, you can supply a number of additional optional parameters.
domain
The name of the IBM Tivoli Network Manager IP Edition domain to use to obtain the MIB and SNMP data. The value of this parameter is used to set the Domain option menu in the Configuration Toolbar.
Tip:
To write a tool that opens the MIB browser from an Event Viewer, you can specify the name of the ObjectServer instead of the IBM Tivoli
Network Manager IP Edition. To do this, specify the parameter
$selected_rows.ServerName where ServerName is the field in the Event
Viewer event that specifies the name of the ObjectServer.
host
The IP address of the target device to be queried for SNMP data. This value is used to populate the Host field in the SNMP Query Toolbar.
variable
The MIB object to query. This value can be the OID of the MIB object, for example 1.3.6.1.2.1.1.3 or it can be the name of the MIB object, for example sysUpTime. This value is used to populate the OID field in the SNMP
Query Toolbar
.
resultsOnly
Specifies whether the MIB browser is started in full mode or results-only mode. Specify one of the following options: v true : The MIB browser opens in results-only mode.
v false : The MIB browser is opened in full mode.
If you supply the domain, host, and variable parameters, the MIB browser is started, automatically performs the SNMP query specified by these parameters and displays the results in the SNMP Query Results area. The type of SNMP query varies depending on the value of the variable parameter
XML elements and attributes for defining tools
Use these XML elements and attributes to define URL tools and tools that open reports.
The following table describes the XML elements and attributes used to define URL tools and tools that open reports.
Table 10. Elements and Attributes used to define URL tools and tools that open reports
Element or attribute Type
context Attribute excludeBaseContext Attribute excludeBaseURI id
Attribute
Attribute
Description
Specifies the context filters for the tool.
Determines if the default base context should be excluded, but retains the protocol server port portion of the base URI. For example, to exclude the
/ibm/console from the base URI, set the value to true. The default value is false .
Determines if the default base URI should be excluded, which includes everything up to and including https://server:port/ibm/console. The default value is false.
Contains an alphanumeric identifier for this tool.
106
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Table 10. Elements and Attributes used to define URL tools and tools that open reports (continued)
Element or attribute Type
key
Attribute label name ncp_tool omitDefault
Parameters parameter runforeach runonlist security type target
Attribute
Attribute
Element
Attribute
Element
Attribute
Attribute
Attribute
Attribute
Attribute
Description
Used as a lookup into the $NMGUI_HOME/profile/etc/tnm/locale/ ncp_tools(_xx_XX).properties
file. This attribute allows you to specify translations of the tool label for users with different locale settings.
Contains the actual text of the menu option for this tool that appears in the menu.
Specify a name to be used for the parameter.
Introduces the definition of a tool.
As an attribute of the <url> element, prevents any default parameters from being added to the URL if it is set to true. Set this attribute to true if your tool has no <parameter> tags and you do not want any default parameters added. If your tools has some <parameter> tags, this attribute has no effect.
Specifies parameters to pass to the URL. You can configure multiple parameters using the following parameter types. Each of these parameter types is formulated using a different valueType attribute: v Value of an NCIM topology database field. The data retrieved must be associated with an entity.
v Name of the Network Manager domain containing the device or devices against which the tool is executing.
v Name of the Tivoli Netcool/OMNIbus Web GUI data source mapped to the
Network Manager domain containing the device or devices against which the tool is executing.
v
Value of a Web browser cookie.
v Plain text. Use this parameter type to specify tool-specific parameters, such as the number of hops to pass to the tool that launches the Hop View, or the number of retries.
If set to the value true, then this tool is run once for each selected node.
If set to the value true, then this tool is run once only. The selected nodes are passed to the tool as a comma-separated list.
Specified the security filters for the tool.
The following types of tool are supported: v url : use this option to define a URL tool.
This attribute is standard HTML syntax and specifies the name of the window to open the tool into. Possible values include: v _blank : Opens the tool in a new window v _self : Opens the tool in the current window url value
Element
Attribute
You can also specify a window name.
Specifies the URL to open when a user selects this tool.
Specifies the value of the URL for the <url> element. You can use variables here that you have defined in the $NMGUI_HOME/profile/etc/tnm/ tnm.properties
file. For example, you could reference two variables called tnm.myserveraddress and tnm.myserverport using a URL similar to the following: url="https://{%prop:tnm.myserveraddress}:{%prop:tnm.
myserverport}/rest_of_url"
Chapter 4. Configuring tools and menus
107
Table 10. Elements and Attributes used to define URL tools and tools that open reports (continued)
Element or attribute Type
valueType
Attribute
Description
Indicates how the Network Manager Web application from which the tool is called obtains the value of the parameter. This attribute can take the following values: v domainName : obtains the name of the Network Manager domain containing the device or devices against which the tool is executing.
v webtopDataSource : obtains the name of the Tivoli Netcool/OMNIbus Web
GUI data source mapped to the Network Manager domain containing the device or devices against which the tool is executing.
v ncim : retrieves the value of a field in the NCIM topology database. Use the table and column parameters to specify the topology database field. Set the runOnMainNode attribute to true in order to use the entityId field associated with the main node containing a selected interface.
v cookie : obtains the value of the cookie specified using the cookieName attribute.
v text : specified text attribute is added as a parameter value.
Defining context filters for tools and menus
You can specify the types of views in which a menu or tool is available, and which devices it can be run on, using context filters.
To define a context filter for a menu or tool, complete the following steps.
1.
Edit the XML file in the $NMGUI_HOME/profile/etc/tnm/menus/ directory that defines the menu or tool to which you want to apply the filter.
2.
Optional: Edit the <context> element to define the filter. Use the reference information about the XML elements and attributes available for context filters and the example provided to help you define the context filter. If the <context> element is not used, the tool or menu is available for all devices, subject to any restrictions imposed by the optional security element.
Related concepts
:
Filters are pieces of XML code that form part of an XML menu definition or an
XML tool definition. There are two types of filter: context filters and security filters.
XML attributes for defining context filters
Understand the different XML elements and attributes that define context filters.
Sample context filter
The following example shows the format of a context filter:
<context>
<attribute id="class">
<matches regexp=".*Cisco*"/>
</attribute>
<attribute id="clientType">
<equals value="ncp_networkview"/>
</attribute>
<attribute id="managed">
</attribute>
<attribute id="entityType">
<equals value="1"/>
</attribute>
108
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
<attribute id="viewType">
<equals value="1"/>
</attribute>
</context>
If the menu is to be displayed, the context must match each of the id attributes. In this example, the tool or menu is displayed if the following expression is true: class = ".*Cisco*" AND clientType = "ncp_networkview" AND managed = true AND entityType = "1" AND viewType = "1"
This means that this tool is available only in filtered (viewType = "1") Network
Views, and can be run only against managed, main node devices.
XML attributes of a context filter
The following table describes the XML elements, attributes, and operators available for the definition of a context filter.
Table 11. Elements, attributes, and operators in the context filter XML definition section
Element or
Attribute
childViewType
Type Description
The childViewType attribute filters for a view type, where the selected view is contained within another view.
class clientType entityType equals managed
Value
Value
Value
Operator
Value
Possible values are: v 0 - Container v 1 - Filtered v 2 - Collection v 3 - MPLS VPN v 4 - IP Filter v 5 - Unassigned v 6 - Custom v 7 - VPLS VPN v 8 - Dependency v 100 - Dynamic Collection v 101 - Dynamic Subnet v
102 - Dynamic MPLS VPN v
103 - Dynamic Distinct v 104 - Dynamic Template v 107 - Dynamic MPLS VPN
Corresponds to the ClassName of the device on which the right-click is performed
Web application from which the tool may be run. Possible values are: v ncp_hopview v ncp_networkview v ncp_structurebrowser
The type of device (entityType) that the tool can be run against.
Performs a simple = comparison between attributes
Indicates whether the tool can only be run against devices that are in the managed state. Possible values are: v true v false
Chapter 4. Configuring tools and menus
109
Table 11. Elements, attributes, and operators in the context filter XML definition section (continued)
Element or
Attribute
matches notequals viewType
Type
Operator
Operator
Value
Description
Performs a regular expression comparison between attributes
Performs a simple not= comparison between attributes
Defines the type of view in which the tool can appear and be used. Refers to the view that contains the selected device.
Possible values are: v 0 - Container v 1 - Filtered v 2 - Collection v 3 - MPLS VPN v 4 - IP Filter v 5 - Unassigned v 6 - Custom v 7 - VPLS VPN v 8 - Dependency v 100 - Dynamic Collection v 101 - Dynamic Subnet v 102 - Dynamic MPLS VPN v 103 - Dynamic Distinct v
104 - Dynamic Template v 107 - Dynamic MPLS VPN
Defining user access for tools and menus
You can specify the users, roles, and groups authorized to display a tool or menu using security filters.
To define a security filter for a tool or menu, complete the following steps.
1.
Edit the XML file in the $NMGUI_HOME/profile/etc/tnm/menus/ directory that defines the menu or tool to which you want to apply the filter.
2.
Edit the <security> element to define the filter. Use the reference information about the XML elements and attributes available for security filters and the example provided to help you define the security filter.
Related concepts
:
Filters are pieces of XML code that form part of an XML menu definition or an
XML tool definition. There are two types of filter: context filters and security filters.
110
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
XML attributes for defining security filters
Understand the different XML attributes of the <security> element that define security filters.
Example
The following example shows a security filter:
<security>
<user name="bob"/>
<user name="mary"/>
<group name="Network Manager IP Desktop"/>
<role name="ncp_networkview"/>
</security>
If the menu or tool is to be displayed, the context must match at least one of the following attribute assignments: v User bob v User mary v Any user with the role ncp_networkview v Any user in the group Network Manager IP Desktop
Elements and attributes of a security filter
The following table describes the XML elements, attributes, and operators available for the definition of a security filter.
Table 12. Elements, attributes, and operators in the security filter XML definition section
Element or attribute
user
Type Description
group role
Attribute
Attribute
Attribute
Assigns the tool or menu to a specific user
Assigns the tool or menu to a specific group
Assigns the tool or menu to a specific role
Defining variables for tools
You can define variables for use in tools in the tnm.properties file.
If you want to use variables in tools and do not want to hardcode them in each tool, you can define them in the tnm.properties file. You can reference the variables in any tool definition.
For example, right-click tools that launch into other applications must be configured with the server and port details of the application.
To define variables for use in tools, complete the following steps:
1.
Back up and edit the $NMGUI_HOME/profile/etc/tnm/tnm.properties file.
2.
Add or edit an entry similar to the following example: tnm.bhm.server=myserver.mydomain.com
tnm.bhm.port=40443
Note:
Variables must begin with the string tnm. in the tnm.properties file.
3.
In the tool definition XML file, reference these variables as in the following example:
Chapter 4. Configuring tools and menus
111
url="https://{%prop:tnm.bhm.server}:{%prop:tnm.bhm.port}/rest_of_url"
112
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Chapter 5. Editing network topology
Edit the discovered network topology to manually add and remove devices and connections.
About topology editing
You can edit the discovered network topology by performing the following actions: adding network devices, adding connections between network devices, removing and deleting devices from the domain, and removing connections between network devices. The topology can only be edited in the Network Hop View.
For information on how to configure the Network Hop View to differentiate between manually added network devices and discovered network devices, see the
IBM Tivoli Network Manager IP Edition Administration Guide.
Topology editing and the discovery process
Following a discovery, the Topology manager, ncp_model, inspects relevant tables in the NCIM topology database to determine which manual topology changes were made, and then makes sure not to overwrite those manual changes.
All manual changes to the topology are recorded in the NCIM topology database entityActions and connectActions tables.
For information on how to examine the audit log for manually added devices and connections, see the description of the entityActions and connectActions tables in the IBM Tivoli Network Manager IP Edition Topology Database Reference.
Audit trail of manual changes to the topology
All manual changes to the topology will be recorded in the NCIM topology database entityActions and connectActions tables. These tables facilitate an audit trail for manual topology changes as well as allow for the undo or reversal of a manual action.
For information on how to examine the audit log for manually added devices and connections, see the description of the entityActions and connectActions tables in the IBM Tivoli Network Manager IP Edition Topology Database Reference.
Adding devices to the topology
You can manually add main node device entities to the discovered network topology. You might want to do this because there is no access to a specific network device, or because device support (discovery agents) is not available for certain device types.
You use the Add Device Wizard to manually add a device to the topology. This wizard updates the NCIM topology database entityData, chassis, and ipEndPoint tables. For more information on these NCIM topology database tables, see the IBM
Tivoli Network Manager IP Edition Topology Database Reference.
© Copyright IBM Corp. 2006, 2017
113
Note:
Devices that are added manually can be displayed in the Network Views.
Go to Network Availability > Network Views and select Manually Added
Devices
from the Network View tree.
To launch the wizard, complete these steps.
1.
Click the Incident icon and select Network Availability > Network Hop View.
2.
Ensure that the topology map displayed contains at least one of the devices to which you want to add a connection. For information about how to display a topology map in the Network Hop View, see the IBM Tivoli Network Manager IP
Edition Network Troubleshooting Guide.
3.
In the Network Hop View, right-click a device or the background area of the topology map, and click Topology Management > Add Device. The Add
Device Wizard Entity Details window opens.
4.
Complete the Entity Details window as follows. The fields in this window populate the NCIM entityData table for the device that you are adding.
domain
The domain to which the device is being added. This value is retrieved from the domain of the Hop View from which the Add Device Wizard was launched.
entityName
IP address or DNS name for this device. For example, an IP address such as 172.20.1.7, or a DNS name, such as company-abc.net.
Restriction:
Fix Pack 2
Device names can include square brackets [] in the device name, but not at the end of the device name.
Restriction:
This name must be unique for all entities within the current domain. If a device with the same entity name already exists in this domain then the wizard requires you to specify a different entity name. This applies whether the device is manually added or discovered. In this case, do one of the following: v Enter a different entity name.
v Cancel the wizard, and select a different domain. Try to add the device to this new domain, by going back to step 2 of this procedure.
entityType
Type of entity. This value is set to chassis. This means that you can only add a chassis, or main node device.
displayLabel
Label to display for this device in a network view or network hop view.
description
Textual description of this device
reason
Reason for adding this device to the topology.
5.
Click Next. Complete the Chassis Details window as follows. The fields in this window populate the NCIM chassis table for the device that you are adding.
className
The name of a class of devices. The master className field is in the entityClass table.If you specified className then this field lists the classes available in the NCIM database entityClass table. Select a class from this list to classify the device.
114
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
sysObjectId
The vendor's authoritative identification of the network management subsystem contained in the entity. If you specified sysObjectId then type a valid sysObjectId value for this device.
sysName
An administratively-assigned name for this managed node. By convention, this is the fully-qualified domain name of the node. If the name is unknown, the value is the zero-length string.
sysDescr
A textual description of the entity. This value must include the full name and version identification of the system hardware type, software operating-system, and networking software.
sysLocation
The physical location of this node, for example “telephone closet, 3rd floor.” If the location is unknown, the value is the zero-length string.
sysContact
The textual identification of the contact person for this managed node, and information on how to contact this person. If no contact information is known, the value is the zero-length string.
ipForwarding
Indication of whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by this entity but not addressed to this entity. IP gateways forward datagrams, whereas IP hosts do not, unless the source is routed through the host. Takes one of the following values: v forwarding v not-forwarding
serialNumber
The serial number of the entity.
modelName
The model name of the entity.
accessIPAddress
The IP address through which this entity was discovered and will be monitored.
Note:
For non-IP entities, such as layer 1 optical devices, this field is null.
If you specify a value for accessIPAddress then you must also specify a value for accessProtocol. The value specified for accessIPAddress must be valid within the Internet protocol specified for accessProtocol. For example, if you set accessProtocol to IPv4, then you must specify an
IPv4 address.
accessProtocol
The Internet protocol used by the chassis. If you specify a value for
accessProtocol
then you must also specify a value for accessIPAddress.
Chapter 5. Editing network topology
115
DNSName
DNS name for the IP address associated with this IP end point. The value specified in this field is used to populate the NCIM ipEndPoint table for the device that you are adding.
Note:
The DNSName field in the NCIM ipEndPoint table is only updated if you have specified a value for both the accessProtocol and
accessIPAddress
fields in this window.
6.
Click Next. The Add Device Wizard checks the chassis details entered.
v If no errors are returned, then the Confirm Details window opens.
v If there are any errors, then you are prompted to correct them before proceeding.
7.
In the Confirm Details window, review the information that you specified and click Finish. The Add Device Wizard checks the entity details entered. If the operation was successful then a window opens indicating that the device was successfully added to the domain. Click Add Like option to add more devices with identical data except for the entityName and displayName fields. The topology map in the Network Hop View is updated to display the newly added device.
Note:
If the Network Hop View is refreshed before a connection is added to the manually added device, then the manually added device will disappear from the network hop view as it has no connections.
Adding connections between devices
You can manually add connections between devices in the discovered network topology. You can add these connections between manually added devices or between discovered devices or between a mix of the two. This enables you to add connections that the Discovery engine was unable to discover.
You use the Add Connection Wizard to manually add a connections between devices. All connections added are stored in the NCIM topology database as bidirectional.
To launch the wizard, complete these steps.
1.
Click the Incident icon and select Network Availability > Network Hop
View
.
2.
Ensure that the displayed topology map contains at least one of the devices to which you want to add a connection. For information on how to display a topology map in the Network Hop View, see the IBM Tivoli Network Manager
IP Edition Network Troubleshooting Guide.
3.
In the Network Hop View, select one device or two devices. Then right-click to display the context menu and click Topology Management > Add
Connection.
from the context menu. Based on your device selections, you can perform one of the following actions:
You selected one device
You can connect this device to a device that is not displayed in the current hop view.
You selected two devices
You can connect these two devices to each other.
116
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Note:
If you select more than two devices then the Topology Management >
Add Connection.
option is not available in the context menu.
The Add Connection Wizard Device Selection window opens.
4.
Complete the Device Selection window as follows. The fields in this window populate the NCIM connects table for the connection that you are adding.
From Device
IP address of the device that is the notional start of the connection.
To Device
IP address of the device that is the notional end of the connection. If you selected one device only then this field contains the text <Click
Next to select device>
.
Swap Devices
Allows you to switch the notional start and notional end of the connection.
5.
Click Next. The next window displayed depends upon whether you initially selected one or two devices in the Network Hop View.
v If you selected one device, then the Entity Search window opens. Use the
Entity Search window to locate the To Device, the device at the notional end of the connection.
v If you selected two devices then the Connection Details window opens. Go
6.
Complete the Entity Search window as follows.
v Use the Basic tab to search by IP address or device name.
Domain
Select the domain in which you want to search.
Note:
If you opened the Entity Search window from the Path Views
GUI, then you cannot change domain. This is done to prevent cross-domain path traces.
IP Address
Specify the IP address of the device. You can specify all of the address, or only the first part of the address. You are unable to use wildcard characters like the percent character (%) or the asterisk (*) in the search facility within Path Views and Path View
Administration, however you can use these character types as wildcards in the search facility for other widgets.
Device Name
Specify the name of the device. You can specify all of the name, or only the first part of the name. You are unable to use wildcard characters like the percent character (%) or the asterisk (*) in the search facility within Path Views and Path View Administration, however you can use these character types as wildcards in the search facility for other widgets. Device names are not case-sensitive. If you specify both an IP address and a device name, the IP address takes precedence.
v Use the Advanced tab to search by device attributes.
Domain
Select the domain in which you want to search.
Chapter 5. Editing network topology
117
Note:
If you opened the Entity Search window from the Path Views
GUI, then you cannot change domain. This is done to prevent cross-domain path traces.
Table
Select the database table that you want to search. The mainNodeDetails table lists network devices.
Field
Select the field whose value you want to search. The selection available for this field is automatically populated based on the chosen database.
Comparator
Select a comparator.
Value
Required. Type the value that you want to search for. You are unable to use wildcard characters like the percent character (%) or the asterisk (*) in the search facility within Path Views and Path
View Administration, however you can use these character types as wildcards in the search facility for other widgets.
7.
Complete the Connection Details window as follows.
From Device
IP address of the device that is the notional start of the connection.
From Interface
If interfaces exist on this device, then these are presented in the From
Interface
list. If an interface list exists, then you can make the connection at the interface or device level for this device.
To Device
IP address of the device that is the notional end of the connection. If you selected one device only then this field contains the text <Click
Next to select device>
.
To Interface
If interfaces exist on this device, then these are presented in the To
Interface
list. If an interface list exists, then you can make the connection at the interface or device level for this device.
Connectivity
Defaults to the connectivity setting in the Network Hop View.
Note:
If the topology map in the Network Hop View is set to IP
Subnets then the Connectivity setting in this window defaults to
Layer 2, the first item in the list.
Speed
The speed for this connection. This must be an integer value.
Reason
Reason for adding this connection to the topology.
8.
Click Next. The Confirm Details window is displayed.
9.
Review the information that you specified and click Finish. The Add
Connection Wizard checks that a connection between the specified interfaces on the two devices does not already exist. If such a connection already exists, then a screen is displayed indicating that the wizard is unable to create this connection.
10.
If one of the following conditions holds, then the Success window requires you to recenter the topology map before you can display the new connection.
Click Recenter & Close to do this.
118
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
v Neither of the devices selected for connection were seed devices in the original network hop view and one of the selected devices was not on the current network hop view.
v The connectivity specified for the connection is not the same as the connectivity on the original network hop view.
Deleting manually added devices
You can delete manually added devices from the topology. This action completely removes all data associated with the deleted devices from the NCIM topology database.
You use the Delete Device Wizard to delete manually added devices from the topology. All data associated with the manually added device is removed from the
NCIM topology database.
Note:
If you want to remove a discovered device from the domain, you must use the RemoveNode.pl script. For more information on the RemoveNode.pl script, see the IBM Tivoli Network Manager IP Edition Administration Guide.
Complete the following steps to launch the wizard and delete manually added devices from the topology.
1.
Click the Incident icon and select Network Availability > Network Hop View.
2.
Within the Network Hop View, display a topology map. The displayed topology map must contain at least one of the devices which you want to delete. For information on how to display a topology map in the Network Hop
View, see the IBM Tivoli Network Manager IP Edition Network Troubleshooting
Guide.
3.
In the Network Hop View, select one or more manually added devices to delete. Then right-click to display the context menu and click Topology
Management
> Delete Device from the context menu.
Note:
You can distinguish manually added devices from discovered devices by noting which devices have the associated manually added device icon
The Delete Device Wizard Device Selection window opens.
4.
Complete the Device Selection window as follows.
.
Please select the devices you would like to permanently delete
Lists all manually added device selected in the topology map. If you also selected discovered devices, these are ignored and are not shown in this list. You can change the selection here by deselecting devices as required.
5.
Click Next. The Confirm Device Deletion window is displayed.
6.
Review the information on the Confirm Device Deletion window and click
Finish
. The Success window is displayed indicating that the specified devices have been deleted from the topology.
Chapter 5. Editing network topology
119
Removing connections between devices
You can manually remove connections between devices in the network topology.
1.
Click the Incident icon and select Network Availability > Network Hop View.
2.
Ensure the displayed topology map contains the connection that you want to delete. For information on how to display a topology map in the Network Hop
View, see the IBM Tivoli Network Manager IP Edition Network Troubleshooting
Guide.
3.
In the Network Hop View, select the connection to remove. Then right-click to display the context menu and click Topology Management > Remove
Connection
from the context menu. The header at the top of the context menu displays the connection that is selected for removal.
Note:
You can only remove one connection, or one link in a multilink connection, at a time.
v If the selected connection is made up of multiple links, then you must first click the link you want to remove, and then from the submenu that is displayed, click Topology Management > Remove Connection.
v If you selected two or more different connections, then only the first connection that you selected is presented for removal.
The Confirm Connection Removal window opens.
4.
Complete the Device Selection window as follows.
Connection
Displays the device and interface details at either end of the connection.
If the connection endpoint at either end is the device itself, then no interface data is shown.
Layer
Displays the connection layer for this connection.
Reason
Specify a reason for removing these devices from the domain.
5.
Click Confirm. The Success window is displayed confirming that the connection has been removed.
120
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Chapter 6. Administering path views
Path views display devices and links that make up a network path between two selected devices. Create new path views or change existing path views to help network operators visualize network paths.
Note:
You can only trace a path across a single domain. All devices specified in the Trace Network Path window must be in the same domain.
About path views
During the discovery process, system paths such as MPLS TE paths and Virtual
Circuits are discovered and displayed as path views. In addition, you can trace IP paths on an ad hoc basis to view a snapshot of a network path at a specific moment. Once saved, you can monitor these paths regularly.
Types of path
Read about the differences between system paths and user-defined paths.
System paths
System paths are MPLS TE paths and Virtual Circuits. These are automatically added during the discovery process and cannot be edited or deleted.
User-defined paths
You can create IP paths from the Path Views GUI or from the Path View
Administration GUI, using the Trace IPv4 network path window to define the path trace. You can also select a device in the Network Views , Network Hop View , or
Event Viewer
, and launch the Trace IPv4 network path window with that device already defined as the start point of a path. If you select two devices before launching the Trace IPv4 network path window from these interfaces, the end point will also be populated.
You can specify a device to be included on the path between a start and end device by using the Via field, and you also have the option to trace a return path back to you start device. By using the 'ping-verify each hop' option, you can ping each device encountered on the route between two selected devices. This is especially useful in troubleshooting the network path once a failure has occurred.
While paths are usually traced inside a network domain, you can trace a path between an interface inside your domain and one outside, an option that is referred to as an 'out-of-band' trace.
You can retrace user-defined IP paths on demand by selecting the path and pressing the retrace button. The 'elapsed time' column displays the time that has elapsed since the path was last traced.
Note:
Network Manager path views also include the concept of a full path and a
partial path.
© Copyright IBM Corp. 2006, 2017
121
In some cases, when creating a user-defined path, it is not possible to trace the full path between start and end devices. This can occur when path trace prerequisites are not met; for example, one of the devices along the path might not provide
SNMP access. Another reason why it might not be possible to trace the full path is that one of the devices along the path does not provide routing information. If
Network Manager is unable to trace a full path, then it will create a partial path made up of a subset of the nodes along the path. Partial paths are highlighted in the Path View Administration GUI by means of a warning icon in the Trace Status column.
Path trace prerequisites
You run a path trace to generate path views. A path trace can fail because any of the devices involved in the path do not satisfy path trace prerequisites. Use this information to ensure that all path trace prerequisites are met.
Prerequisites
The devices involved in the path must meet the following requirements:
SNMP access
v All devices specified when running the path trace must provide SNMP access so that the path trace operation can access relevant MIB variables in the device. For one-way paths, the source device (specified in the
From
field in the Trace IPv4 Network Path window) and the devices along the route (specified in the Via field) must allow SNMP access. For return paths, the source device, the devices along the route, and the target device (specified in the To field) must allow SNMP access.
v All routers identified by the path trace operation as next hop devices along the path must allow SNMP access.
Routing information
v All devices specified when running the path trace must provide basic routing information. For one-way paths, the source device (specified in the From field) and the devices along the route (specified in the Via field) must at a minimum store information on the next hop device. For return paths, the source device, the devices along the route, and the target device (specified in the To field) must store information on the next hop device.
v
All routers identified by the path trace operation as next hop devices along the path must support the following MIB variables:
General MIB variables
– sysName
– ifName
– ifType
– ifConnectorPresent
– ipAdEntIfIndex
Routers identified by the path trace operation as next hop devices along the path must, in addition, support either of the following sets of MIB variables that govern routing:
122
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Classless Inter-Domain Routing (CIDR) MIB variables
This set of routing variables is made up of the following MIB variables:
– ipCidrRouteNumber
– ipCidrRouteIfIndex
– ipCidrRouteDest
– ipCidrRouteMask
– ipCidrRouteType
– ipCidrRouteMetric1
– ipCidrRouteNextHop
– ipCidrRouteProto
IP route MIB variables
This set of routing variables is made up of the following MIB variables:
– ipRouteIfIndex
– ipRouteDest
– ipRouteMask
– ipRouteType
– ipRouteMetric1
– ipRouteNextHop
– ipRouteProto
Creating path views
To create a path view, launch the Trace Network Path window, enter valid devices as start and end points of your path, and then launch the path trace.
Before you can work with network paths, the administrator must have successfully completed the first network discovery, and network views must be configured for your user ID.
A full list of network paths that have been defined is displayed in the Path View
Administration and in the Path Views GUI windows in list format. From here, you can create new path views. The paths are displayed per user, and the user required can be selected from the drop-down list.
Restriction:
Network path monitoring is not available for IPV6 addresses.
Note:
You can only create or edit IP path views. MPLS TE paths are populated during discovery and cannot be edited or retraced. MPLS TE paths are displayed by default under the itnmadmin views. This can be altered by editing the
$NMGUI_HOME/profile/etc/tnm/topoviz.properties
file and changing the values for the following attributes: v topoviz.pathview.accesslevel
v topoviz.pathview.accessid
Note:
You can only trace a path across a single domain. All devices specified in the Trace Network Path window must be in the same domain.
Chapter 6. Administering path views
123
You can also create a path view by running the itnm_pathTool.pl Perl script from the command line. For more information, see the IBM Tivoli Network Manager IP
Edition Administration Guide.
To create a path view, complete the following steps.
1.
Go to one of the following windows.
a.
Click the Administration icon and select Network > Path View
Administration
.
b.
Click the Incident icon and select Network Availability > Path Views.
The Path View Administration GUI or the Path Views GUI opens. Within the
Path View Administration GUI, all monitored paths display in table format.
2.
Click Create and trace a path within Path View Administration , or click New
Path
within Path Views. The Trace Network Path window displays.
3.
In the Trace Network Path window, complete the trace criteria fields:
Domain
Select a network domain in which to trace a path.
Name
Type a name describing the network path. This name is displayed in the tree view of network paths in the Path View window, as well as in the table of network paths that are being monitored in the Path View
Administration window.
Start
Enter the device that will be the start point of the network path to be monitored. Use the Browse button to open the Entity Search dialog, which helps you to find a device.
End
Enter the device that will be the end point of the network path to be monitored here. Use the Browse button to open the Entity Search dialog, which helps you to find a device.
Via
Click Swap to switch end and start device. As network paths are dynamic, the trace results could be different.
Enter a specific device to be included in the route of the network path to be monitored . Use the Browse button to open the Entity Search dialog, which helps you to find a device.
Get return path
Select this option to trace the return path as well. As network paths are dynamic, the return path could be different.
When selected, this options runs a trace from your Start device to your
End device and back to you Start device. During the trace, the End device is treated as a Via device, and therefore the Via option is unavailable when this option has been specified.
Perform out-of-band trace
Select this option when tracing IP addresses that are utilised for out-of-band access. Selecting this option forces the trace to set the next-hop IP address for a device to the access IP address value stored for this device in the NCIM topology database. Note that specifying this option reduces the accuracy of the tool because the utility does not resolve the next-hop ingress interface and physical port if an out-of-band access IP address is used.
Note:
You can only specify an out-of-band End device. The Start and
Via
devices cannot be outside the domain.
124
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Ping-verify each hop
Select this option to ping each device encountered on the route between two selected devices. You can use this option to troubleshoot the network path once a failure has occurred.
Save and trace
Click this button to save the path view and trace the path between the devices entered. If the trace fails, an error message is displayed.
If the path was not successfully traced, then you get a path trace error, indicating the reason that the path could not be traced. To see more detailed path trace output, click the error at the top of the Trace Network Path window. Detailed path trace output opens in a second window. To troubleshoot the path trace, refer to the related information on troubleshooting path views.
Troubleshooting path views
If the path was not successfully traced, then you get a path trace error, indicating the reason that the path could not be traced.
Path trace troubleshooting table
Use this troubleshooting table to determine the type of error that you are encountering and to determine the possible reason for the error and actions to take that might resolve the error.
The following table provides possible reasons and corrective actions for each type of path trace error.
Table 13. Path trace troubleshooting table
Type of error
Internal Network Manager error
Invalid input parameters
Network devices not responding
Possible reason
Internal database failure.
Input parameters specified in the Trace an IPv4 Path window are invalid. For example, the IP address is incorrectly formatted, or does not exist in the specified domain.
An IP address in the path did not respond to ping verification.
Note:
This message is only generated if Ping-verify
each hop
is selected in the
Trace IPv4 Network Path window.
Possible corrective actions
Switch on path trace debugging and review the logs.
Correct the parameters specified in the Trace an
IPv4 Path window and retrace the path.
Check whether the device is can be pinged. Configure the network or device as required.
Example of an error of this type
Failed to create a path due to an internal database error. For more details check the log file
$NMGUI_HOME/profile/logs/ tnm/ncp_topoviz.X.log
, where X is a number such as 1, or 2, and consult documentation on how to turn on further path tool logging.
The parameter is not a valid IPv4 address or IP forwarding has been disabled for the address.
Cannot continue with the path trace.
ip_address_or_device_name
address did not respond to ping verification. Cannot continue with trace.
Chapter 6. Administering path views
125
Table 13. Path trace troubleshooting table (continued)
Type of error
Path trace error
Path trace prerequisites not met
Required Network Manager process not running
Timeout error
Possible reason
Internal path trace error.
For one or more of the devices along the path,
SNMP access or routing information has not been configured.
Some Network Manager processes are not running.
Path trace timeouts are too short. For example, one of the devices along the path was unable to provide the necessary SNMP routing data within the specified timeout. For example, the device might be set to non-forwarding mode.
Possible corrective actions
Switch on path trace debugging and review the logs.
Check that there is SNMP access to devices along the path. If necessary, correct the SNMP community string settings for this device in the Discovery
Configuration GUI.
Check, and if necessary, correct the MIB settings for this device using the SNMP
MIB Browser.
Check that all relevant
Network Manager processes are running. In particular, check that the processes Topology manager, ncp_model, and
WebTools, ncp_webtool, are running and that the NCIM topology database is accessible.
Increase the length of path trace timeouts by adjusting the relevant configuration file property.
Example of an error of this type
An error occurred during the trace of this path. For more details check the log file $NMGUI_HOME/profile/ logs/tnm/ ncp_topoviz.X.log
,, where
X is a number such as 1, or
2, and consult documentation on how to turn on further path tool logging.
The path start point
ip_address_or_device_name, does not satisfy prerequisites. Cannot continue the path trace. The ipCidrRouteNumber MIB variable is not retrievable from the device and therefore the path trace script itnm_pathTool.pl
cannot determine an IP route.
OQL WebTools request failed. Check that all ncp processes are running. For more details check the log file $NMGUI_HOME/profile/ logs/tnm/ ncp_topoviz.X.log
,, where
X is a number such as 1, or
2, and consult documentation on how to turn on further path tool logging.
A timeout occurred. The path trace is taking longer than the configured OQL timeout and might still be running. Increase the oql.response.poll.timeout in
$NMGUI_HOME/profile/etc/ tnm/tnm.properties
to wait longer for the path trace result.
126
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Interpreting detailed path trace output
In the case of a path trace error you can access detailed path trace output by clicking on the error message that is displayed in the Trace Network Path window.
Scroll down to the end of the path trace output and look for lines that contain the text WARNING and ERROR. These lines contain the most precise information on the nature and cause of the problem.
Note:
You can obtain the most detailed output by switching on path trace debugging and tracing the path again.
Setting path trace timeouts
There are three timeouts associated with the path trace. You can modify the path trace timeouts; for example, you can make the timeouts longer if you want to give the path trace more time to retrieve device information.
The path trace timeouts are associated with the following Network Manager processes. The path trace interacts with all of these system components when constructing a path: v OQL Service Provider (ncp_oql) timeout: the default value for this timeout is two minutes.
v Webtools (ncp_webtools) timeout: the default value for this timeout is five minutes.
v GUI timeout: the default value for this timeout is 10 minutes.
Setting the OQL Service Provider timeout
Set the OQL Service Provider timeout by modifying the appropriate configuration file.
To change the OQL Service Provider timeout:
1.
Edit the following configuration file: $NMGUI_HOME/profile/etc/tnm/ tnm.properties
.
2.
Find the line that contains the property: tnm.oql.response.poll.timeout. This property is set to a default value of 320,000 milliseconds (five minutes and 20 seconds).
3.
Modify this value as appropriate.
4.
Save the file $NMGUI_HOME/profile/etc/tnm/tnm.properties.
Setting the WebTools timeout
Set the WebTools timeout by modifying the appropriate configuration file.
To change the WebTools timeout:
1.
Edit the following configuration file: $NCHOME/precision/scripts/webtools/ etc/PathToolGUI.xml
.
2.
Find the line that has the following form: <tool id="PathToolGUI" type="executable" timeout="300"> . The timeout parameter is set by default to
300 seconds (five minutes).
3.
Modify this value as appropriate.
4.
Save the file $NCHOME/precision/scripts/webtools/etc/PathToolGUI.xml.
Chapter 6. Administering path views
127
Setting the GUI timeout
Set the GUI timeout by modifying the appropriate configuration file. This timeout applies to both the Path View Administration GUI and the Path Views GUI.
The GUI timeout applies to paths that are being traced and hence are in an In
Progress state. If the timeout expires and the path is still an In Progress state, then the Trace Status for that path is set to Unknown. In this state, it is possible to retrace the path.
To change the GUI timeout:
1.
Edit the following configuration file: $NMGUI_HOME/profile/etc/tnm/ monitorconfig.properties
.
2.
Find the line that contains the property: monitorconfig.pathtrace.timeout.
This property is set to a default value of 600 seconds (10 minutes).
3.
Modify this value as appropriate.
4.
Save the file $NMGUI_HOME/profile/etc/tnm/monitorconfig.properties.
Switching on path trace debugging
To get more detailed path trace output in the logs and in the Path Views GUI and
Path View Administration GUI, switch on path trace debugging.
1.
Open the $NMGUI_HOME/profile/etc/tnm/tnm.properties configuration file and identify the line that contains the following paramteter: tnm.pathtool.script.debug
2.
Set this parameter as follows: tnm.pathtool.script.debug=true
Based on this setting the path trace provides the most detailed output. Look for this output in one of the following places depending on how you ran the path trace:
Table 14.
If you ran the path trace run from...
GUI (Path Views GUI or Path View
Administration GUI
Command line using the itnm_pathTool.pl
script
Then display the detailed path trace output by...
Clicking an error message in the Trace
Network Path window.
Viewing the $NMGUI_HOME/profile/logs/tnm/ ncp_topoviz.num.log
file, where num is a number such as 1, or 2
128
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Chapter 7. Configuring geographical views
Fix Pack 2
Geographical views display devices that are enriched with geographical information. Before you use geographical views, you must enable and configure them.
Enabling geographical views
Fix Pack 2
Before you can configure geographical views, you must ensure that there are devices to display, and give access to the appropriate users.
Before you can enable geographical views, you must configure and run a geographical discovery.
You must give users who need to use geographical views the ncp_gis user role.
Without this role, the options to open geographical views are not visible.
You must give users who need to administer geographical views the ncp_gis_admin user role. Without this role, the options to edit portlet layout preferences are not visible.
To enable geographical views, complete the following tasks:
1.
Create a group, or edit an existing group to which you want to add the appropriate roles, and add the ncp_gis or ncp_gis_admin role to the group.
2.
Assign the group to the users who need to use or administer geographical views.
Scoping and filtering geographical views
Fix Pack 2
To improve visibility and performance, you might want to limit the devices that are displayed in geographical views.
The number of items rendered on a geographical map depends on how many devices, locations, and links are in scope to be displayed, and how many of those in-scope items you choose to filter out. To keep the total items that are included in a view down to a number that allows for clear navigation and good performance, use the scoping methods described in this task. If you want to reduce the number of in-scope items that are displayed for a particular view, use the filtering methods described in this task.
If you open a geographical view that contains more than the default limit of 1,000 items on a map, you are prompted to filter the view to reduce the number of items that are displayed. Devices, links, and locations all count towards the total. The rendering limit is controlled by the deviceRenderLimit property in the
$JazzSM_HOME/profile/installedApps/JazzSMNode01Cell/isc.ear/ncp_gis.war/
© Copyright IBM Corp. 2006, 2017
129
resources/config.json
file. If you increase this limit, you might encounter problems when you render geographical maps.
1.
To scope the GIS Device Map to a particular set of devices, select the devices in a topology view, right click and select Show on Map.
2.
To scope the GIS Device Map to a particular Network View, add the Network
Views widget and the GIS Device Map to a page. When you select a Network
View, the GIS Device Map updates to display all devices with location information in that Network View.
3.
To open the GIS Device Map scoped to a particular network view by using a
URL, construct a URL similar to the following: https://server:port/ibm/console/ncp_gis/NetKitMapWidget.jsp?viewId=760
In the preceding example, 760 is the numeric ID of a network view.
4.
To scope the GIS Device Map to a particular geographical area, construct a URL similar to the following: https://server:port/ibm/console/ncp_gis/NetKitMapWidget.jsp?
bounds=((northern latitude,western longitude),
(southern latitude,eastern longitude))
Where the latitudes and longitudes define the corners of a geographical area.
For example: https://server:port/ibm/console/ncp_gis/NetKitMapWidget.jsp?
bounds=%28%2851.50,-0.15%29,%2851.45,-0.09%29%29
5.
To filter the items that are shown in the map, click the Map Configuration icon in the upper left of the GIS Device Map. Select the Topology Filtering tab in the
Map Configuration window.
a.
Select domains in the Domain section to include and exclude devices by domain.
b.
Select device classes in the Device Class section to include and exclude devices by class.
c.
Select the option in the Connectivity section to display or hide links between devices or locations.
d.
Select the option in the Connectivity section to enable or disable links within locations.
e.
Select network layers in the Connectivity section to include and exclude links on a particular network layer.
Enabling regional aggregation for geographical views
Fix Pack 3
You can group locations into cities, group cities into states, and group states into countries. This grouping is called regional aggregation.
Regional aggregation has the following advantages: v The number of markers that are placed on the geographical maps is reduced.
v You can view large geographical areas, for example, connectivity from data center to data center or from country to country.
The geographical view can be scoped by a network view, a defined set of geographic bounds, a specific set of devices, specific domains, or all devices across all domains. Events for devices and locations are also aggregated. The region displays the highest status level of any of the subregions.
130
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Links between regions represent the aggregate links from region to region, region to location, or region to device.
To enable regional aggregation for geographical views, complete the following steps.
1.
Ensure that the following fields in the ACMEGeoLocation (or equivalent) database table are correctly populated for all devices that you want to include in geographical views:
IP,ADDRESS,CITY,STATE,COUNTRY,LATITUDE,LONGITUDE
The default regional aggregation is address -> city -> state -> country. This logic is defined in the following stitcher: $NCHOME/precision/disco/stitchers/
DNCIM/PopulateDNCIM_CustomGeography.stch
Restriction:
The character sequence -> is reserved for regional aggregation.
Device and location names must not contain this sequence.
2.
Open the GIS Device Map and click the Topology Rendering tab. Enable the
Aggregate Locations to Regions
option.
You can also enable or disable regional aggregation by using the URL parameters for geographical maps.
Devices and locations are grouped automatically to the highest regional hierarchy available in the geographical view. Double-click a region to drill into that region and show the next logical level of the hierarchy.
Related reference
:
“URL parameters for geographical maps” on page 133
You can use URL parameters to open geographical maps with specific configurations.
Configuring event status for geographical views
Fix Pack 2
You can configure the intervals at which geographical views update event status.
To configure event status, complete the following steps.
1.
Configure the interval at which device status is queried from Tivoli
Netcool/OMNIbus. Set the interval by changing the mapStatusRefreshInterval property in the $JazzSM_HOME/profile/installedApps/JazzSMNode01Cell/ isc.ear/ncp_gis.war/resources/config.json
file. The value is in seconds. The default is 20 seconds. When you configure this property, consider the Tivoli
Netcool/OMNIbus refresh rate and the Network Manager poll policy cycle.
2.
Configure the interval at which the status indicator is refreshed when it is visible on a device, link, or location. Change the gridStatusRefreshInterval property in the $JazzSM_HOME/profile/installedApps/JazzSMNode01Cell/ isc.ear/ncp_gis.war/resources/config.json
file. You do not normally need to modify this interval. If you set the mapStatusRefreshInterval to a higher value than the default, you might want to modify this interval.
Chapter 7. Configuring geographical views
131
Configuring the appearance of geographical views
You can hide the IP address of devices, and configure the severity colors of links.
To configure the appearance of geographical views, complete the following steps.
1.
To hide the IP address of devices on geographic maps, modify the following file on the Dashboard Application Services Hub server: $JazzSM_HOME/profile/ installedApps/JazzSMNode01Cell/isc.ear/ncp_gis.war/resources/config.json
and set the property rendering.obsfucateMarkerNames to true. The IP address is replaced with asterisks ****. If you right click the device or location, the IP address is visible.
2.
To configure the colors that are used to represent the status of events on links, change the colors and icons in the following file: $JazzSM_HOME/profile/ installedApps/JazzSMNode01Cell/isc.ear/ncp_gis.war/resources/ config.json
. For example, to overwrite the unknown state icon with the clear icon, copy the clear.png file over the unknown.png file in the
$JazzSM_HOME/profile/installedApps/JazzSMNode01Cell/isc.ear/ncp_gis.war/ resources/common_assets/status_icons/ directory.
Integrating geographic views with other widgets
Fix Pack 2
You can change the devices that are displayed in the GIS Device Map by integrating it with another widget.
The GIS Device Map listens for NodeClickedOn events. If it receives a
NodeClickedOn event that contains the correct parameters, the GIS Device Map displays the corresponding devices.
To remove the integration between the GIS Device Map and another widget, for example, between the GIS Device Map and the Event Viewer in the GIS Device
Health View, edit the widget and disable the publishing of the NodeClickedOn event.
To integrate the GIS Device Map with another widget, complete the following steps:
1.
Ensure that the widget that you want to integrate sends a NodeClickedOn event with the following parameters: v Only one of the following required parameters: viewId, bounds, deviceId, locationId .
v One or more of the following optional parameters: config.filter.domain, config.filter.class
, config.filter.layer, config.enableLinks, config.enableLinkStatus
, config.enableTopologyStatus, config.minTopologyStatus
, config.minLinkStatus.
2.
Add the integrating widget to a dashboard.
3.
Add the GIS Device Map to the same dashboard.
132
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
URL parameters for geographical maps
Fix Pack 2
You can use URL parameters to open geographical maps with specific configurations.
Parameters for scoping geographical maps
The following URL parameters can be used to define the scope of the geographical maps.
Table 15. URL parameters for scoping geographical maps
Parameter
None bounds
Description
Displays all geographically enriched devices, locations, and links in all domains.
Displays geographically enriched devices and links within a defined area.
The area is defined as the rectangle between the north-west and south-east points.
Example
https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp
https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
bounds=((northern latitude,western
longitude),
(southern latitude,
eastern longitude)) deviceId
The values must be in the following format: ((northern latitude,western
longitude),
(southern latitude,eastern
longitude)) https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
bounds=%28%2851.50,-0.15%29,
%2851.45,-0.09%29%29
The regular expression for the allowed values is:
(\\()(\\()([+-]?\\d*\\.\\d+)(?![-
+0-9\\.])(,)
([+-]?\\d*\\.\\d+)(?![-+0-9\\
.])(\\))(,)
(\\()([+-]?\\d*\\.\\d+)(?![-+0-9\\
.])(,)
([+-]?\\d*\\.\\d+)(?![-+0-9\\.])
(\\))(\\))
Displays specific geographically enriched devices.
The deviceId parameter must be a comma-separated list of positive numeric value device IDs.
https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
deviceId=19078,19062,19067
The regular expression for the allowed values is:
([1-9][0-9]*,[ ])*[1-9][0-9]*
Chapter 7. Configuring geographical views
133
Table 15. URL parameters for scoping geographical maps (continued)
Parameter
getAllLocations
Description
Fix Pack 3 Controls regional aggregation. Displays all aggregated locations within the top level. For example, if the top level is Country, displays Regions. Locations that do not contain any in-scope entities, for example, because entities have been excluded by domain or class, are not shown.
getLocationsWithinBounds
Fix Pack 3 Controls regional aggregation. Displays all aggregated locations within the top level, within the specified map boundaries. For example, if the top level is Country, displays Regions. Locations that do not contain any in-scope entities, for example, because entities have been excluded by domain or class, are not shown.
Example
https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
getAllLocations https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
getLocationsWithinBounds=%28
%2851.50,
-0.15%29,%2851.45,-0.09%29%29
The area is defined as the rectangle between the north-west and south-east points.
The values must be in the following format: ((northern latitude,western
longitude),
(southern latitude,eastern
longitude)) getLocationsByViewId
The regular expression for the allowed values is:
(\\()(\\()([+-]?\\d*\\.\\d+)(?![-
+0-9\\.])(,)
([+-]?\\d*\\.\\d+)(?![-+0-9\\
.])(\\))(,)
(\\()([+-]?\\d*\\.\\d+)(?![-+0-9\\
.])(,)
([+-]?\\d*\\.\\d+)(?![-+0-9\\.])
(\\))(\\))
Fix Pack 3
Controls regional aggregation. Displays all aggregated locations within the top level, for the given network view ID and all views that it contains. For example, if the top level is Country, displays
Regions. Locations that do not contain any in-scope entities, for example, because entities have been excluded by domain or class, are not shown.
https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
getLocationsByViewId
134
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Table 15. URL parameters for scoping geographical maps (continued)
Parameter
getLocationsByDeviceIds locationId
Description Example
Fix Pack 3 Controls regional aggregation. Displays all aggregated locations within the top level, for the given device IDs (recursively traversing the view tree). For example, if the top level is Country, displays Regions. Locations that do not contain any in-scope entities, for example, because entities have been excluded by domain or class, are not shown.
Displays geographically enriched locations.
The value must be a positive numeric value representing a valid location collection entityId.
https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
getLocationsByDeviceIds https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
locationId=47672 viewId
The regular expression for the allowed values is: (\\d+)
Displays all geographically enriched devices and links within the specified network view.
https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
viewId=760
Valid values are: v NCP_VIEW_$viewId v $viewId https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
viewId=NCP_VIEW_760
Where viewId is a positive numeric value only, and a valid Id of a network view..
The regular expression for the allowed values is:
(((NCP_VIEW_)(\\d+))|(\\d+))
URL parameters for filtering geographical maps
The following URL parameters can be used to filter the contents of the geographical map.
Table 16. URL parameters for filtering geographical maps
Parameter Description
config.filter.domain
Scopes the view to the specified domains.
Example
The following example displays network entities in the specified domain:
The value must be a comma-separated list of positive numeric value domain IDs.
The regular expression for the allowed values is: ([1-9][0-9]*,[
])*[1-9][0-9]* https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
config.filter.domain=5
Chapter 7. Configuring geographical views
135
Table 16. URL parameters for filtering geographical maps (continued)
Parameter
config.filter.class
Description
Scopes the view to devices that match the specified class type.
config.filter.layer
The value must be a comma-separated list of positive numeric value entity class type IDs.
The regular expression for the allowed values is: ([1-9][0-9]*,[
])*[1-9][0-9]*
Scopes the view to links that match the defined topology layer type.
The value must be a comma-separated list of positive numeric value topology layer type
IDs.
config.enableLinks
config.enableLinkStatus
config.enableTopologyStatus
Example
The following example displays
CiscoCat35xx class devices only: https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
config.filter.class=110
The following example displays devices on only Layer 2: https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
config.filter.layer=72
The regular expression for the allowed values is: ([1-9][0-9]*,[
])*[1-9][0-9]*
Scopes the view to exclude or include all links from the view.
The following example excludes links:
This value can be true or false.
The regular expression for the allowed values is: ((true)|(false)) https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
config.enableLinks=false
Scopes the view to exclude or include link status from the view.
The following example displays links without severity colors:
This value can be true or false.
The regular expression for the allowed values is: ((true)|(false)) https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
config.enableLinkStatus
=false
Scopes the view to exclude or include device and location status from the view.
The following example displays devices and locations without any severity icons.
This value can be true or false.
The regular expression for the allowed values is: ((true)|(false)) https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
config.enableTopology
Status=false
136
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Table 16. URL parameters for filtering geographical maps (continued)
Parameter
config.minTopologyStatus
Description
Scopes the view to show only status for devices and locations with events of a status greater than the specified value.
v
The value must be one of the following:
0 : Clear or Higher v 1: Indeterminate or Higher v 2: Warning or Higher v 3: Minor or Higher v 4: Major or Higher v 5: Critical only
Example
The following example displays device and location status of Warning or higher: https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
config.minTopology
Status=2 config.minLinkStatus
v
The regular expression for the allowed values is: [0-5]
Scopes the view to show only status for links with events of a status greater than the specified value.
The value must be one of the following:
0 : Clear or Higher v 1: Indeterminate or Higher v 2: Warning or Higher v 3: Minor or Higher v 4: Major or Higher v 5: Critical only
The regular expression for the allowed values is: [0-5]
The following example displays link status of Critical or higher: https://server:port
/ibm/console/ncp_gis/
NetKitMapWidget.jsp?
config.minTopology
Status=5
Related tasks
:
“Enabling regional aggregation for geographical views” on page 130
You can group locations into cities, group cities into states, and group states into countries. This grouping is called regional aggregation.
Chapter 7. Configuring geographical views
137
138
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Chapter 8. Configuring non-English language settings for network visualization
If you want to display device labels or default network view names in languages other than English, you must perform some configuration steps.
© Copyright IBM Corp. 2006, 2017
139
140
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Appendix. Network Manager glossary
Use this information to understand terminology relevant to the Network Manager product.
The following list provides explanations for Network Manager terminology.
AOC files
Files used by the Active Object Class manager, ncp_class to classify network devices following a discovery. Device classification is defined in
AOC files by using a set of filters on the object ID and other device MIB parameters.
active object class (AOC)
An element in the predefined hierarchical topology of network devices used by the Active Object Class manager, ncp_class, to classify discovered devices following a discovery.
agent
bookmark
class hierarchy
Predefined hierarchical topology of network devices used by the Active
Object Class manager, ncp_class, to classify discovered devices following a discovery.
configuration files
Each Network Manager process has one or more configuration files used to control process behaviour by setting values in the process databases.
Configuration files can also be made domain-specific.
discovery agent
Piece of code that runs during a discovery and retrieves detailed information from discovered devices.
Discovery Configuration GUI
GUI used to configure discovery parameters.
Discovery engine (ncp_disco)
Network Manager process that performs network discovery.
discovery phase
A network discovery is divided into four phases: Interrogating devices,
Resolving addresses, Downloading connections, and Correlating connectivity.
discovery seed
One or more devices from which the discovery starts.
discovery scope
The boundaries of a discovery, expressed as one or more subnets and netmasks.
Discovery Status GUI
GUI used to launch and monitor a running discovery.
discovery stitcher
Piece of code used during the discovery process. There are various
© Copyright IBM Corp. 2006, 2017
141
discovery stitchers, and they can be grouped into two types: data collection stitchers, which transfer data between databases during the data collection phases of a discovery, and data processing stitchers, which build the network topology during the data processing phase.
dNCIM database
The dNCIM is a relational database embedded into the Discovery engine, ncp_disco, and it stores the containment model that is derived from the fullTopology database (and created by stitchers). This is the version of the topology that is sent to the Topology manager, ncp_model. The dNCIM database performs the same function as the scratchTopology database did in previous versions of Network Manager.
domain
entity
A topology database concept. All devices and device components discovered by Network Manager are entities. Also device collections such as VPNs and VLANs, as well as pieces of topology that form a complex connection, are entities.
event enrichment
The process of adding topology information to the event.
Event Gateway (ncp_g_event)
Network Manager process that performs event enrichment.
Event Gateway stitcher
Stitchers that perform topology lookup as part of the event enrichment process.
failover
In your Network Manager environment, a failover architecture can be used to configure your system for high availability, minimizing the impact of computer or network failure.
Failover plug-in
Receives Network Manager health check events from the Event Gateway and passes these events to the Virtual Domain process, which decides whether or not to initiate failover based on the event.
Fault Finding View
Composite GUI view consisting of an Event Viewer widget above and a
Network Hop View widget below. Use the Fault Finding View to monitor network events.
full discovery
A discovery run with a large scope, intended to discover all of the network devices that you want to manage. Full discoveries are usually just called discoveries, unless they are being contrasted with partial discoveries. See
message broker
Component that manages communication between Network Manager processes. The message broker used byNetwork Manager is called Really
Small Message Broker. To ensure correct operation of Network Manager,
Really Small Message Broker must be running at all times.
NCIM database
Relational database that stores topology data, as well as administrative data such as data associated with poll policies and definitions, and performance data from devices.
142
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
ncp_disco
ncp_g_event
ncp_model
ncp_poller
network domain
A collection of network entities to be discovered and managed. A single
Network Manager installation can manage multiple network domains.
Network Health View
Composite GUI view consisting of a Network Views widget above and an
Event Viewer
widget below. Use the Network Health View to display events on network devices.
Network Hop View
Network visualization GUI. Use the Network Hop View to search the network for a specific device and display a specified network device. You can also use the Network Hop View as a starting point for network troubleshooting. Formerly known as the Hop View.
Network Polling GUI
Administrator GUI. Enables definition of poll policies and poll definitions.
Network Views
Network visualization GUI that shows hierarchically organized views of a discovered network. Use the Network Views to view the results of a discovery and to troubleshoot network problems.
network view bookmark
Network view bookmarks group together just those network views that you or your team need to monitor. Create new bookmarks or change existing bookmarks to help network operators visualize just those devices that they need to monitor.
OQL databases
Network Manager processes store configuration, management and operational information in OQL databases.
OQL language
Version of the Structured Query Language (SQL) that has been designed for use in Network Manager. Network Manager processes create and interact with their databases using OQL.
partial discovery
A subsequent rediscovery of a section of the previously discovered network. The section of the network is usually defined using a discovery scope consisting of either an address range, a single device, or a group of devices. A partial discovery relies on the results of the last full discovery, and can only be run if the Discovery engine, ncp_disco, has not been
stopped since the last full discovery. See also, full discovery.
Path Views
Network visualization GUI that displays devices and links that make up a
Appendix. Network Manager glossary
143
network path between two selected devices. Create new path views or change existing path views to help network operators visualize network paths.
performance data
Performance data can be gathered using performance reports. These reports allow you to view any historical performance data that has been collected by the monitoring system for diagnostic purposes.
Polling engine (ncp_poller)
Network Manager process that polls target devices and interfaces. The
Polling engine also collects performance data from polled devices.
poll definition
Defines how to poll a network device or interface and further filter the target devices or interfaces.
poll policy
Defines which devices to poll. Also defines other attributes of a poll such as poll frequency.
Probe for Tivoli Netcool/OMNIbus (nco_p_ncpmonitor)
Acquires and processes the events that are generated by Network Manager polls and processes, and forwards these events to the ObjectServer.
RCA plug-in
Based on data in the event and based on the discovered topology, attempts to identify events that are caused by or cause other events using rules coded in RCA stitchers.
RCA stitcher
Stitchers that process a trigger event as it passes through the RCA plug-in.
root cause analysis (RCA)
The process of determining the root cause of one or more device alerts.
SNMP MIB Browser
GUI that retrieves MIB variable information from network devices to support diagnosis of network problems.
SNMP MIB Grapher
GUI that displays a real-time graph of MIB variables for a device and usse the graph for fault analysis and resolution of network problems.
stitcher
Code used in the following processes: discovery, event enrichment, and
root cause analysis. See also, discovery stitcher, Event Gateway stitcher,
Structure Browser
GUI that enables you to investigate the health of device components in order to isolate faults within a network device.
Topology Manager (ncp_model)
Stores the topology data following a discovery and sends the topology data to the NCIM topology database where it can be queried using SQL.
WebTools
Specialized data retrieval tools that retrieve data from network devices and can be launched from the network visualization GUIs, Network Views and
Network Hop View, or by specifying a URL in a web browser.
144
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Notices
This information applies to the PDF documentation set for IBM Tivoli Network
Manager IP Edition.
This information was developed for products and services offered in the U.S.A.
IBM
® may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web
© Copyright IBM Corp. 2006, 2017
145
sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
958/NH04
IBM Centre, St Leonards
601 Pacific Hwy
St Leonards, NSW, 2069
Australia
IBM Corporation
896471/H128B
76 Upper Ground
London
SE1 9PZ
United Kingdom
IBM Corporation
JBF1/SOM1 294
Route 100
Somers, NY, 10589-0100
United States of America
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the
146
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Trademarks
The terms in Table 17 are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
Table 17. IBM trademarks
AIX
®
BNT
ClearQuest
®
Cognos
DB2
®
®
Informix
® iSeries
Lotus
®
Lotus
Netcool
®
NetView
®
DB2 Universal
Database developerWorks
®
OMEGAMON
®
DS8000
Enterprise
Storage Server
®
IBM
Passport Advantage
PowerPC
PowerVM
®
PR/SM
™
System p
System z
®
Tivoli
WebSphere
® z/OS
® z/VM
® zSeries
Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Notices
147
Java
™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Privacy policy considerations
IBM Software products, including software as a service solutions, ("Software
Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific information about this offering's use of cookies is set forth below.
This Software Offering may collect IP addresses, user names and passwords for the purpose of performing network discovery. Failure to enable the collection of this information would likely eliminate important functionality provided by this
Software Offering. You as customer should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.
For more information about the use of various technologies, including cookies, for these purposes, See IBM's Privacy Policy at http://www.ibm.com/privacy and
IBM's Online Privacy Statement at http://www.ibm.com/privacy/details the section entitled "Cookies, Web Beacons and Other Technologies" and the "IBM
Software Products and Software-as-a-Service Privacy Statement" at http://www.ibm.com/software/info/product-privacy.
148
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
Index
A
adding
connections between devices 116
administering
attributes
audit trail
manual changes to topology 113
disabling custom views 65 disabling unassigned views 65
E
editing
education
see Tivoli technical training x
elements
enabling custom views 65 enabling unassigned views 65
environment variables, notation xi
event filter
example
of main node filter 38 of topology filter 38
B
bookmark
bookmarks
F
filter
topology filter example 38, 39
C
connections between devices
connectivity types, creating 65
context menus
creating
custom views
I
G
L
line speed 66 line thickness, customizing 66 logical groups, enabling in Network
D
default network view bookmark
deleting
manually added devices from the topology 119
dependency network views
devices
adding connections between 116
deleting manually added devices 119
removing connections between 120
M
main node filter
manual changes to topology
menus
N
© Copyright IBM Corp. 2006, 2017 network view
network view bookmark
network view bookmarks 87 administering 87 creating 87
network views
Network Views
enabling visualization of logical groups 66
filtered views
O
online publications vi ordering publications vi
P
path trace timeouts
prerequisites
R
removing
connections between devices 120
network view from a bookmark 91
S
service x service management connect x
setting
network view bookmark as default 89
setting path trace timeouts 127
SMC x support x support information x
T
templates
149
templates (continued)
timeouts for path trace
tools, user-defined context menus
device types
topology filter
U
unassigned views
user-defined tools
example script 102 script parameters 102
V
VPLS
VPNs
W
web console
Web GUI
widgets
X
xml
150
IBM Tivoli Network Manager IP Edition: Network Visualization Setup Guide
IBM®
Printed in the Republic of Ireland
Download
Offentligt link opdateret
Det offentlige link til din chat er blevet opdateret. You may view and manage your chat links after registration here.
Dokument offentligt link
Annonce