InCharge Network Protocol Manager for OSPF User's Guide Version 1 - Cisco · Crystal Decisions...

Network Protocol Managerfor OSPF

User’s GuideVersion 1.1

jlmiller

Text Box

OL-7719-01

Copyright ©1996-2004 by System Management ARTS Incorporated. All rights reserved.The Software and all intellectual property rights related thereto constitute trade secrets and proprietary data of SMARTS and any third party from whom SMARTS has received marketing rights, and nothing herein shall be construed to convey any title or ownership rights to you. Your right to copy the software and this documentation is limited by law. Making unauthorized copies, adaptations, or compilation works is prohibited and constitutes a punishable violation of the law. Use of the software is governed by its accompanying license agreement. The documentation is provided “as is” without warranty of any kind. In no event shall System Management ARTS Incorporated (“SMARTS”) be liable for any loss of profits, loss of business, loss of use of data, interruption of business, or for indirect, special, incidental, or consequential damages of any kind, arising from any error in this documentation.The InCharge products mentioned in this document are covered by one or more of the following U.S. patents or pending patent applications: 5,528,516, 5,661,668, 6,249,755, 10,124,881 and 60,284,860.“InCharge,” the InCharge logo, “SMARTS,” the SMARTS logo, “Graphical Visualization,” “Authentic Problem,” “Codebook Correlation Technology,” “Instant Results Technology,” “InCharge Viewlet,” and “Dashboard Viewlet” are trademarks or registered trademarks of System Management ARTS Incorporated. All other brand or product names are trademarks or registered trademarks of their respective companies or organizations.

Third-Party Software. The Software may include software of third parties from whom SMARTS has received marketing rights and is subject to some or all of the following additional terms and conditions:

Bundled SoftwareSun Microsystems, Inc., Java(TM) Interface Classes, Java API for XML Parsing, Version 1.1. "Java" and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. SMARTS is independent of Sun Microsystems, Inc.

W3C IPR SoftwareCopyright © 2001-2003 World Wide Web Consortium (http://www.w3.org), (Massachusetts Institute of Technology (http://www.lcs.mit.edu), Institut National de Recherche en Informatique et en Automatique (http://www.inria.fr), Keio University (http://www.keio.ac.jp)). All rights reserved (http://www.w3.org/Consortium/Legal/). Note: The original version of the W3C Software Copyright Notice and License can be found at http://www.w3.org/Consortium/Legal/copyright-software-19980720.

The Apache Software License, Version 1.1Copyright ©1999-2003 The Apache Software Foundation. All rights reserved. Redistribution and use of Apache source and binary forms, with or without modification, are permitted provided that the following conditions are met:1. Redistributions of Apache source code must retain the above copyright notice, this list of conditions and the Apache disclaimer as

written below. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the Apache disclaimer as written

below in the documentation and/or other materials provided with the distribution.3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:

"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4. The names “The Jakarta Project”, “Tomcat”, "Xalan", "Xerces", and "Apache Software Foundation" must not be used to endorse or promote products derived from Apache software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this Apache software may not be called "Apache," nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

APACHE DISCLAIMER: THIS APACHE SOFTWARE FOUNDATION SOFTWARE IS PROVIDED "AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.This Apache software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright © 1999, Lotus Development Corporation., http://www.lotus.com. For information on the Apache Software Foundation, please see http://www.apache.org.

FLEXlm Software© 1994 - 2003, Macrovision Corporation. All rights reserved. "FLEXlm" is a registered trademark of Macrovision Corporation. For product and legal information, see http://www.macrovision.com/solutions/esd/flexlm/flexlm.shtml.

JfreeChart – Java library for GIF generationThe Software is a “work that uses the library” as defined in GNU Lesser General Public License Version 2.1, February 1999 Copyright © 1991, 1999 Free Software Foundation, Inc., and is provided “AS IS” WITHOUT WARRANTY OF ANY KIND EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR

CORRECTION. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED IN THE ABOVE-REFERENCED LICENSE BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARITES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. JfreeChart library (included herein as .jar files) is provided in accordance with, and its use is covered by the GNU Lesser General Public License Version 2.1, which is set forth at http://www.object-refinery.com/lgpl.html/.

BMC – product libraryThe Software contains technology (product library or libraries) owned by BMC Software, Inc. (“BMC Technology”). BMC Software, Inc., its affiliates and licensors (including SMARTS) hereby disclaim all representations, warranties and liability for the BMC Technology.

Crystal Decisions ProductsThe Software may contain certain software and related user documentation (e.g., Crystal Enterprise Professional, Crystal Reports Professional and/or Crystal Analysis Professional) that are owned by Crystal Decisions, Inc., 895 Emerson Street, Palo Alto, CA 94301 (“Crystal Decisions”). All such software products are the technology of Crystal Decisions. The use of all Crystal Decisions software products is subject to a separate license agreement included with the Software electronically, in written materials, or both. YOU MAY NOT USE THE CRYSTAL DECISIONS SOFTWARE UNLESS AND UNTIL YOU READ, ACKNOWLEDGE AND ACCEPT THE TERMS AND CONDITIONS OF THE CRYSTAL DECISIONS’ SOFTWARE LICENSE AGREEMENT. IF YOU DO NOT ACCEPT THE TERMS AND CONDITIONS OF THE CRYSTAL DECISIONS’ SOFTWARE LICENSE, YOU MAY RETURN, WITHIN THIRTY (30) DAYS OF PURCHASE, THE MEDIA PACKAGE AND ALL ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS) RELATED TO THE CRYSTAL DECISIONS’ TECHNOLOGY, TO SMARTS FOR A FULL REFUND; OR YOU MAY WRITE, CRYSTAL WARRANTIES, P.O. BOX 67427, SCOTTS VALLEY, CA 95067, U.S.A.GNU eTeks PJA Toolkit Copyright © 2000-2001 Emmanuel PUYBARET/eTeks [email protected]. All Rights Reserved.The eTeks PJA Toolkit is resident on the CD on which the Software was delivered to you. Additional information is available at eTEks’ web site: http://www.eteks.com. The eTeks PJA Toolkit program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License (GPL) as published by the Free Software Foundation; version 2 of the License. The full text of the applicable GNU GPL is available for viewing at http://www.gnu.org/copyleft/gpl.txt. You may also request a copy of the GPL from the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. The eTeks PJA Toolkit program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. For a period of three years from the date of your license for the Software, you are entitled to receive under the terms of Sections 1 and 2 of the GPL, for a charge no more than SMARTS’ cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code for the GNU eTeks PJA Toolkit provided to you hereunder by requesting such code from SMARTS in writing: Attn: Customer Support, SMARTS, 44 South Broadway, White Plains, New York 10601.

IBM Runtime for AIX The Software contains the IBM Runtime Environment for AIX(R), Java™ 2 Technology Edition Runtime Modules © Copyright IBM Corporation 1999, 2000 All Rights Reserved.

HP-UX Runtime Environment for the Java™ 2 PlatformThe Software contains the HP-UX Runtime for the Java™ 2 Platform, distributed pursuant to and governed by Hewlett-Packard Co. ("HP") software license terms set forth in detail at: http://www.hp.com. Please check the Software to determine the version of Java runtime distributed to you.

DataDirect TechnologiesPortions of this software are copyrighted by DataDirect Technologies, 1991-2002.

NetBSD Copyright © 2001 Christopher G. Demetriou. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes software developed for the NetBSD Project. See http://www.netbsd.org/ for information about NetBSD.4. The name of the author may not be used to endorse or promote products derived from this software without specific prior written

permission.THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

Last Update: 10/1/04

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. <<Id: LICENSE, v 1.2 2000/06/14 15:57:33 cgd Exp>>

RSA Data Security, Inc.Copyright © 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved. License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function. License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work. RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind. These notices must be retained in any copies of any part of this documentation and/or software.

AESCopyright © 2003, Dr Brian Gladman <[email protected]>, Worcester, UK. All rights reserved.License Terms:The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that:1. distributions of this source code include the above copyright notice, this list of conditions and the following disclaimer;2. distributions in binary form include the above copyright notice, this list of conditions and the following disclaimer in the documentation

and/or other associated materials;3. the copyright holder's name is not used to endorse products built using this software without specific written permission.ALTERNATIVELY, provided that this notice is retained in full, this product may be distributed under the terms of the GNU General Public License (GPL), in which case the provisions of the GPL apply INSTEAD OF those given above. Disclaimer: This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not limited to, correctness and/or fitness for purpose. Issue Date: 26/08/2003

InCharge Network Protocol Manager for OSPF User’s Guide v

Contents

Preface ix

Intended Audience ixPrerequisites ixDocument Organization xDocumentation Conventions xiInCharge Network Protocol Suite Installation Directory xii

InCharge Network Protocol Suite Products xiiAdditional Resources xii

InCharge Commands xiiDocumentation xiii

Technical Support xiii

1 Introduction 1

Availability Monitoring 2SNMP Polling 2SNMP Trap and Syslog Processing 2

Availability Notifications 3

2 OSPF Elements and Their Failures 5

OSPF Elements, Relationships, and Connections 5Summary of Root-Cause Problems and Symptomatic Events 6OSPFArea 10

Attributes for OSPFArea 11Root-Cause Problems for OSPFArea 11Symptomatic Events for OSPFArea 11

OSPFAreaConfiguration 11Attributes for OSPFAreaConfiguration 12Root-Cause Problems for OSPFAreaConfiguration 12

Contents

vi InCharge Network Protocol Manager for OSPF User’s Guide

Symptomatic Events for OSPFAreaConfiguration 12OSPFService 12

Attributes for OSPFService 13Root-Cause Problems for OSPFService 13Symptomatic Events for OSPFService 13

OSPFNetwork 14Attributes for OSPFNetwork 14Root-Cause Problems for OSPFNetwork 15Symptomatic Events for OSPFNetwork 16

OSPFInterface 16Attributes for OSPFInterface 16Root-Cause Problems for OSPFInterface 19Symptomatic Events for OSPFInterface 19

OSPFVirtualInterface 20Attributes for OSPFVirtualInterface 20Root-Cause Problems for OSPFVirtualInterface 20Symptomatic Events for OSPFVirtualInterface 21

OSPFNeighborEndpoint 21Attributes for OSPFNeighborEndpoint 22Root-Cause Problems for OSPFNeighborEndpoint 23Symptomatic Events for OSPFNeighborEndpoint 23

OSPFVirtualNeighborEndpoint 24Attributes for OSPFVirtualNeighborEndpoint 24Root-Cause Problems for OSPFVirtualNeighborEndpoint 24Symptomatic Events for OSPFVirtualNeighborEndpoint 24

OSPFNeighborRelationship 24Attributes for OSPFNeighborRelationship 25Root-Cause Problems for OSPFNeighborRelationship 25Symptomatic Events for OSPFNeighborRelationship 25

OSPFVirtualLink 25Attributes for OSPFVirtualLink 26Root-Cause Problems for OSPFVirtualLink 26Symptomatic Events for OSPFVirtualLink 26

OSPF Redundancy Groups 27Creating a System Redundancy Group 27

InCharge Network Protocol Manager for OSPF User’s Guide vii

Symptomatic Events for a System Redundancy Group 27Underlying Transport Network Failures 28

3 OSPF Cross-Domain Impact Correlation Analysis 29

OSPF Impact Analysis Overview 29OSPF Impact Analysis Model 31OSPF Impact Analysis Examples 32

Example of Physical Interface Down 32Example of Physical Interface Disabled 33Example of Cable Down 35Example of TrunkCable Down 36

4 Viewing OSPF Notifications, Maps, and Containment 39

Viewing OSPF Notifications 39Opening an OSPF Notification Properties Dialog Box 40OSPF Notification Properties 40

Viewing OSPF Topology in Maps 41Opening an OSPF Topology Map 42OSPF Topology Map Graphical Representations 42OSPF Map Labels 44OSPF Map Views 44

Viewing OSPF Containment 49Opening an OSPF Containment Dialog 49OSPF Containment Tab Pages 50OSPF Containment Use as a Troubleshooting Aid 51

5 Customizing OSPF Polling 53

Polling Groups and Settings 53Polling Groups 54Polling Settings 54

Threshold Groups and Settings 57Opening the Polling and Thresholds Console 57

Layout of the Polling and Thresholds Console 58Polling and Thresholds Console Toolbar Buttons 59

Contents

viii InCharge Network Protocol Manager for OSPF User’s Guide

Working With Polling Groups and Settings 60How Managed Elements Are Assigned to Groups 61Modifying the Properties of a Group 61Method for Adding or Removing Settings 61Method for Modifying the Priority of Groups 62Method for Editing Matching Criteria 62Method for Modifying the Parameters of a Setting 64Creating New Polling Groups 64

66

A OSPF Terminology 67

B OSPF MIBs Polled and SNMP Traps Processed 73

SNMP MIBs Polled 73SNMP Traps Processed and Devices Rediscovered 78Cisco Traps Processed and Devices Rediscovered 81Limitation If Traps Are Not Used 81

C OSPF Syslog Messages Processed 83

Syslog Message Format 83Sample Syslog Messages 83Syslog Messages Processed and Actions Taken 84

D Polling for Analysis 87

SNMP Poller 87Just-In-Time Polling 88Request-Consolidation Polling 88

E Wildcards 91

Index 95

InCharge Network Protocol Manager for OSPF User’s Guide ix

Preface

This document provides detailed information about InCharge Network Protocol Manager for OSPF. Network Protocol Manager for OSPF, in conjunction with InCharge IP Availability Manager, diagnoses connectivity failures in Open Shortest Path First (OSPF) networks and sends the results of its analysis to InCharge Service Assurance Manager.

Intended AudienceThis document is intended to be read by operators receiving and acting upon Network Protocol Manager for OSPF notifications, by system administrators configuring and using Network Protocol Manager for OSPF, and by IT managers seeking to better understand the value of Network Protocol Manager for OSPF.

PrerequisitesBefore performing procedures in this document, InCharge Network Protocol Manager for OSPF, InCharge IP Availability Manager, and InCharge Service Assurance Manager must be installed. The Global Console is required to configure Network Protocol Manager for OSPF polling settings. For information about installing these products, see the InCharge Network Protocol Management Suite Installation Guide, the InCharge IP Management Suite Installation Guide, and the InCharge Service Assurance Management Suite Installation Guide.

Preface

x InCharge Network Protocol Manager for OSPF User’s Guide

Document OrganizationThis document consists of the following chapters.

1. INTRODUCTION Describes the concepts of managing OSPF network connectivity using Network Protocol Manager for OSPF.

2. OSPF ELEMENTS AND THEIR

FAILURES

Describes the OSPF elements managed by Network Protocol Manager for OSPF and identifies the root-cause problems and symptomatic events for each element type.

3. OSPF CROSS-DOMAIN IMPACT

CORRELATION ANALYSIS

Describes how Network Protocol Manager for OSPF correlates failures in the OSPF network domain with failures in the transport network domain to perform OSPF impact analysis.

4. VIEWING OSPF NOTIFICATIONS,

MAPS, AND CONTAINMENT

Describes using the Global Console to view OSPF notifications, topology maps, and containment information for Network Protocol Manager for OSPF.

5. CUSTOMIZING OSPF POLLING Provides information and procedures for customizing SNMP polling for Network Protocol Manager for OSPF.

A. OSPF TERMINOLOGY Describes basic terms and concepts for the OSPF routing protocol.

B. OSPF MIBS POLLED AND SNMP

TRAPS PROCESSED

Identifies the MIBs and SNMP traps used by Network Protocol Manager for OSPF to diagnose OSPF connectivity problems.

C. OSPF SYSLOG MESSAGES

PROCESSED

Identifies the syslog messages used by Network Protocol Manager for OSPF to diagnose OSPF connectivity problems.

D. POLLING FOR ANALYSIS Describes the SNMP polling engine used by Network Protocol Manager for OSPF for correlation analysis.

E. WILDCARDS Describes the wildcards used to create matching patterns.

InCharge Network Protocol Manager for OSPF User’s Guide xi

D o c um e n t a t i o n C o n v e n t i o n s

Documentation ConventionsSeveral conventions may be used in this document as shown in Table 1.

Directory path names are shown with forward slashes (/). Users of the Windows operating systems should substitute back slashes (\) for forward slashes.

Also, if there are figures illustrating consoles in this document, they represent the consoles as they appear in Windows. Under UNIX, the consoles appear with slight differences. For example, in views that display items in a tree hierarchy such as the Topology Browser, a plus sign displays for Windows and an open circle displays for UNIX.

Finally, unless otherwise specified, the term InCharge Manager is used to refer to InCharge programs such as Domain Managers, Global Managers, and adapters.

Table 1: Documentation Conventions

CONVENTION EXPLANATION

sample code Indicates code fragments and examples in Courier font

keyword Indicates commands, keywords, literals, and operators in bold

% Indicates C shell prompt

# Indicates C shell superuser prompt

<parameter> Indicates a user-supplied value or a list of non-terminal items in angle brackets

[option] Indicates optional terms in brackets

/InCharge Indicates directory path names in italics

yourDomain Indicates a user-specific or user-supplied value in bold, italics

File > Open Indicates a menu path in italics

▼▲ Indicates a command is wrapped over one or more lines. The command must be typed as one line.

Preface

xii InCharge Network Protocol Manager for OSPF User’s Guide

InCharge Network Protocol Suite Installation Directory

In this document, the term BASEDIR represents the location where InCharge software is installed.

• For UNIX, this location is: /opt/InCharge<n>/<productsuite>.

• For Windows, this location is: C:\InCharge<n>\<productsuite>.

The <n> represents the InCharge software platform version number. The <productsuite> represents the InCharge product suite to which the product belongs. For example, on UNIX operating systems, InCharge Network Protocol Manager is, by default, installed to: /opt/InCharge6/NPM/smarts. On Windows operating systems, this product is, by default, installed to: C:\InCharge6\NPM\smarts. This location is referred to as BASEDIR/smarts.

Optionally, you can specify the root of BASEDIR to be something other than /opt/InCharge6 (on UNIX) or C:\InCharge6 (on Windows), but you cannot change the <productsuite> location under the root directory.

For more information about the directory structure of InCharge software, refer to the InCharge System Administration Guide.

InCharge Network Protocol Suite ProductsThe InCharge Network Protocol Management Suite includes the following products:

• Network Protocol Manager for BGP

• Network Protocol Manager for OSPF

Additional ResourcesIn addition to this document, SMARTS provides the following resources.

InCharge CommandsDescriptions of InCharge commands are available as HTML pages. The index.html file, which provides an index to the various commands, is located in the BASEDIR/smarts/doc/html/usage directory.

InCharge Network Protocol Manager for OSPF User’s Guide xiii

Te c h n i c a l S u p p o r t

Documentat ionReaders of this document may find other SMARTS documentation (also available in the BASEDIR/smarts/doc/pdf directory) helpful.

I n C h a r g e Do c u me n t a t i o n

The following SMARTS documents are product independent and thus relevant to users of all InCharge products:

• InCharge Release Notes

• InCharge Documentation Roadmap

• InCharge System Administration Guide

• InCharge ICIM Reference

• InCharge ASL Reference Guide

• InCharge Perl Reference Guide

I n C h a r g e N e t w o r k P r o t o c o l M an a g e me n t D o c u m en t a t i o n

The following SMARTS documents are relevant to users of the InCharge Network Protocol Management product suite:

• InCharge Network Protocol Management Suite Installation Guide

• InCharge Network Protocol Manager for BGP User’s Guide

• InCharge Network Protocol Manager for OSPF User’s Guide

• InCharge Network Protocol Manager Configuration Guide

• InCharge IP Discovery Guide Supplement for Networking Protocols

Refer to the InCharge Documentation Roadmap for documentation resources provided with other SMARTS InCharge product suites.

Technical SupportSMARTS provides technical support by e-mail or phone during normal business hours (8:00 A.M.—6:00 P.M. U.S. Eastern and Greenwich Mean Time). In addition, SMARTS offers the InCharge Express self-service web tool. The web tool allows customers to access a personalized web page and view, modify, or create help/trouble/support tickets. To access the self-service web tool, point your browser to:

https://websupport.smarts.com/SelfService/smarts/en-us

Preface

xiv InCharge Network Protocol Manager for OSPF User’s Guide

U . S . A T e c hn i c a l S u p po r t

E-Mail: [email protected]: +1.914.798.8600

E M E A Te c h n i c a l S u p p o r t

E-Mail: [email protected]: +44 (0) 1753.878140

A s i a - P a c T ec h n i c a l S up p o r t

E-Mail: [email protected]

You may also contact SMARTS at:

For sales inquiries, contact SMARTS Sales at:[email protected]

SMARTS is on the World Wide Web at: http://www.smarts.com

U.S.A WORLD HEADQUARTERS UNITED KINGDOM

ADDRESS

SMARTS44 South BroadwayWhite Plains, New York 10601 U.S.A

SMARTSGainsborough House17-23 High StreetSloughBerkshire SL1 1DYUnited Kingdom

PHONE +1.914.948.6200 +44 (0)1753.878110

FAX +1.914.948.6270 +44 (0)1753.878111

InCharge Network Protocol Manager for OSPF User’s Guide 1

1

Introduction

The flow of data across IP networks depends upon both the physical connectivity between the network devices and the routing protocols that run on those devices. The routing protocols dictate the paths across which packets flow within and between the independent networks, or autonomous systems.

InCharge Network Protocol Manager for OSPF diagnoses connectivity failures for an interior gateway protocol known as Open Shortest Path First (OSPF). Network Protocol Manager for OSPF, working with InCharge IP Availability Manager (Availability Manager), discovers and monitors network devices running OSPF services, diagnoses OSPF-related failures, and reports the results of its analysis to InCharge Service Assurance Manager (Service Assurance Manager). Network Protocol Manager for OSPF also detects common configuration problems that occur when deploying and maintaining the routing infrastructure.

The challenge of managing routing protocol connectivity is that of determining which routing protocol alarms indicate real problems and which indicate symptomatic events that are caused by the failure of other physical or routing protocol elements.

Network Protocol Manager for OSPF meets this challenge by correlating and analyzing the alarms generated as a result of a physical or OSPF element failure, pinpointing the element failure, and identifying all monitored elements affected by the failure. This functionality allows Network Protocol Manager for OSPF users to address the problem of the failed element promptly and to dismiss all other alarms as symptomatic events.

Introduction

2 InCharge Network Protocol Manager for OSPF User’s Guide

Availability MonitoringAfter the initial discovery of the OSPF network elements in the managed network, Network Protocol Manager for OSPF continuously monitors the status of the OSPF network elements using:

• SNMP polling

• SNMP trap message processing (optional)

• Syslog message processing (optional)

Network Protocol Manager for OSPF uses the polling results and trap and syslog message processing, in addition to the events received from Availability Manager, to diagnose the failed elements that interrupt OSPF network connectivity.

SNMP Pol l ingNetwork Protocol Manager for OSPF monitors the OSPF network by periodically sending SNMP polls to the network to collect the status information needed to determine the availability of the OSPF elements. The polled results serve as input to Network Protocol Manager for OSPF correlation analysis.

For information about SNMP polling, see Customizing OSPF Polling on page 53.

SNMP Trap and Syslog Process ingWhen SNMP trap and syslog processing is enabled, Network Protocol Manager for OSPF obtains configuration, change, and adjacency status information for the OSPF routing devices from SNMP trap messages and syslog messages sent by the routing devices. Network Protocol Manager for OSPF extracts the information from the traps and syslog messages and updates the appropriate router attributes.

SNMP traps and syslog messages are recommended but not required because Network Protocol Manager for OSPF polls the OSPF network for status information. However, if neither SNMP traps nor syslog messages are received by Network Protocol Manager for OSPF, immediate asynchronous notification of status change is not available; rather, the response time is determined by the length of the SNMP polling interval (240 seconds by default).


Av a i l ab i l i t y N o t i f i c a t i o n s

By default, SNMP trap and syslog processing is disabled. For information about enabling trap and syslog processing, see the InCharge Network Protocol Manager Configuration Guide.

For information about the SNMP traps and the syslog messages processed by the Network Protocol Manager for OSPF, see OSPF MIBs Polled and SNMP Traps Processed on page 73 and OSPF Syslog Messages Processed on page 83.

Availability NotificationsNetwork Protocol Manager for OSPF performs root-cause analysis on alarms that occur at different layers of the OSPF network domain in order to pinpoint the root cause. When a physical network failure occurs, Network Protocol Manager for OSPF correlates the physical network element failure with the resulting OSPF element alarms, and diagnoses the physical network element failure as the root cause and the OSPF element alarms as impacts of the network element failure.

Network Protocol Manager for OSPF reports its analysis results to Service Assurance Manager in two types of notifications: root-cause problem notifications and symptomatic event notifications.

• Root-cause problem notifications indicate root-cause failures diagnosed by Network Protocol Manager for OSPF. Each root-cause problem pinpoints the exact cause of a failure and identifies the managed element where the failure occurred.

• Symptomatic event notifications indicate the abnormal conditions, or symptoms, that are used by Network Protocol Manager for OSPF to diagnose root-cause failures. They can also notify events that are not necessarily used for problem analysis but may be of interest to administrators or operators.

Notifications are displayed in the Notification Log Console view of the Global Console. Root-cause failures diagnosed by Network Protocol Manager for OSPF display a value of “Yes” for the value of the IsRoot attribute and identify the Network Protocol Manager for OSPF by its domain name in the Source attribute. Users can double-click a notification to view detailed information about the notification.

Introduction


For information about the root-cause problem and symptomatic event notifications reported by Network Protocol Manager for OSPF to Service Assurance Manager, see Summary of Root-Cause Problems and Symptomatic Events on page 6. For information about viewing the notifications, see Viewing OSPF Notifications, Maps, and Containment on page 39.


2

OSPF Elements and Their

Failures

This chapter describes the OSPF elements discovered and managed by InCharge Network Protocol Manager for OSPF and the connectivity-related failures diagnosed for each element. In addition, it includes descriptions of symptomatic events and OSPF element attributes.

Network Protocol Manager for OSPF correlates abnormal conditions, or symptoms, to identify OSPF root-cause problems, and reports the root-cause problems as well as key symptoms to InCharge Service Assurance Manager. It also correlates OSPF symptoms with transport root-cause failures received from InCharge IP Availability Manager to identify OSPF impacts, as explained in OSPF Cross-Domain Impact Correlation Analysis on page 29, and reports the OSPF impacts to Service Assurance Manager.

OSPF Elements, Relationships, and ConnectionsNetwork Protocol Manager for OSPF builds a data model of the discovered OSPF elements in its domain. The model represents the OSPF elements, their relationships, and their connections.

OSPF Elements and Their Failures


The elements in the discovered OSPF topology are represented as instances of the following InCharge Common Information Model™ (ICIM) classes:

• OSPFArea

• OSPFAreaConfiguration

• OSPFService

• OSPFNetwork

• OSPFInterface

• OSPFVirtualInterface

• OSPFNeighborEndpoint

• OSPFVirtualNeighborEndpoint

• OSPFNeighborRelationship

• OSPFVirtualLink

During the discovery post-processing phase, Network Protocol Manager for OSPF creates the relationships and connections between the OSPF elements. For every relationship or connection, there is an inverse relationship or connection. For example, the relationship PartOf is the inverse relationship of ComposedOf.

Note: ConnectedSystems has no inverse relationship.

For an illustration of the relationships and connections between the OSPF elements, see the InCharge IP Discovery Guide Supplement for Networking Protocols. For descriptions of ICIM classes, relationships, and connections, see the InCharge ICIM Reference.

Summary of Root-Cause Problems and Symptomatic Events

Network Protocol Manager for OSPF diagnoses root-cause problems and detects symptomatic events. It uses symptomatic events to diagnose root-cause problems.

Network Protocol Manager for OSPF creates root-cause problem notifications for the diagnosed root-cause problems, one notification per problem. It also creates symptomatic event notifications for key symptomatic


S u m m ar y o f R o o t - C au s e P r o b l e m s a n d S ym p t o m a t i c E v e n t s

events, to be used by Service Assurance Manager for global impact analysis. Notifications are imported by Service Assurance Manager and displayed in the Global Console.

Table 2 lists the OSPF root-cause problems diagnosed by Network Protocol Manager for OSPF, including the condition and symptoms for each problem. The table also identifies the managed elements for which the problems are diagnosed. For a discussion about the OSPF impacts diagnosed by Network Protocol Manager for OSPF, see OSPF Cross-Domain Impact Correlation Analysis on page 29.

Table 2: Root-Cause Problems Diagnosed by Network Protocol Manager for OSPF

MANAGED ELEMENT ROOT-CAUSE PROBLEM CONDITION SYMPTOMS OF ROOT CAUSE

OSPFNetwork AreaIDMismatch Misconfiguration symptoms exist on this OSPF network.

AreaIDMismatchSymptom

NeighborStateAlarm

AreaTypeMismatch Misconfiguration symptoms exist on this OSPF network.

AreaTypeMismatchSymptom

NeighborStateAlarm

AuthKeyMismatch Misconfiguration symptoms exist on this OSPF network.

AuthKeyMismatchSymptom

NeighborStateAlarm

AuthTypeMismatch Misconfiguration symptoms exist on this OSPF network.

AuthTypeMismatchSymptom

NeighborStateAlarm

DuplicateRouterID Misconfiguration symptoms exist on this OSPF network.

DuplicateRouterIDSymptom

NeighborStateAlarm

HelloOrDeadInterval-Mismatch

Misconfiguration symptoms exist on this OSPF network.

HelloOrDeadIntervalMismatch-Symptom

NeighborStateAlarm

MTUMismatch Misconfiguration symptoms exist on this OSPF network.

MTUMismatchSymptom

NeighborStateAlarm

NetmaskMismatch Misconfiguration symptoms exist on this OSPF network.

NetmaskMismatchSymptom

NeighborStateAlarm



Table 3 lists the symptomatic events detected by Network Protocol Manager for OSPF, including the condition for each symptomatic event, whether the symptomatic event is a symptom or an event, and whether the symptomatic event is reported to Service Assurance Manager. The table also identifies the managed elements for which the symptomatic events are detected.

OSPFInterface Disabled This interface or its associated physical interface is administratively down (manually disabled), and at least one OSPF adjacency on this interface is reporting an improper state.

DisabledAdminSymptom

NeighborStateAlarm

Down This interface is operationally down when two or more OSPF neighbor relationships exist on this interface and all of them are down.

NeighborStateAlarm

OSPFVirtualInterface Down This virtual interface is operationally down when two or more OSPF virtual links exist on this interface and all of them are down.

NeighborStateAlarm

OSPFNeighbor-Endpoint

UnknownNbmaNeighbor The NBMA neighbor for this OSPF neighbor endpoint is not present in the topology.

UnknownNbmaNeighbor-Symptom

NeighborStateAlarm

OSPFVirtualNeighbor-Endpoint

UnknownVirtualNeighbor The virtual neighbor for this OSPF virtual neighbor endpoint is not present in the topology.

UnknownVirtualNeighbor-Symptom

NeighborStateAlarm

OSPFNeighbor-Relationship

-or-OSPFVirtualLink

Down This OSPF link between neighboring endpoints is down.

NeighborStateAlarm

Table 2: Root-Cause Problems Diagnosed by Network Protocol Manager for OSPF (Continued)

MANAGED ELEMENT ROOT-CAUSE PROBLEM CONDITION SYMPTOMS OF ROOT CAUSE


S u m m ar y o f R o o t - C au s e P r o b l e m s a n d S ym p t o m a t i c E v e n t s

Table 3: Symptomatic Events Detected by Network Protocol Manager for OSPF

MANAGED ELEMENT SYMPTOM EVENT CONDITION

OSPFService N/A ABRNotInBackbone* The routing device on which this OSPF service is running is configured as an Area Border Router (ABR) but has no interfaces connected to the backbone area.

OSPFNetwork N/A DRElectionFailure* No Designated Router (DR) has been elected on this broadcast or NBMA network.

N/A RouterPrioritiesZero* No routing device on this broadcast or NBMA network has a priority greater than 0.

OSPFInterface DisabledAdminSymptom N/A This OSPF interface or its associated physical interface is administratively down (manually disabled), and OSPF adjacencies exist on this interface.

OSPFInterface-or-

OSPFVirtualInterface

AreaIDMismatchSymptom N/A An area ID misconfiguration exists on this interface, propagated from OSPF neighbor relationships.

AreaTypeMismatchSymptom N/A An area type misconfiguration exists on this interface, propagated from OSPF neighbor relationships.

AuthKeyMismatchSymptom N/A An authentication key misconfiguration exists on this interface, propagated from OSPF neighbor relationships.

AuthTypeMismatchSymptom N/A An authentication type misconfiguration exists on this interface, propagated from OSPF neighbor relationships.

DuplicateRouterIDSymptom N/A A duplicate router ID misconfiguration exists on this interface, propagated from OSPF neighbor relationships.

* Also reported as a symptomatic event notification to Service Assurance Manager.



OSPFAreaAn OSPF area is a set of IP subnets within an autonomous system (AS). If more than one OSPF area is configured for an AS, one of the areas is designated the backbone area (Area 0). All non-backbone areas within an AS have a physical connection to the backbone area.

OSPFInterface-or-

OSPFVirtualInterface(Continued)


N/A A Hello or Dead interval misconfiguration exists on this interface, propagated from OSPF neighbor relationships.

MTUMismatchSymptom N/A An MTU misconfiguration exists on this interface, propagated from OSPF neighbor relationships.

NetmaskMismatchSymptom N/A A netmask misconfiguration exists on this interface, propagated from OSPF neighbor relationships.

OSPFNeighbor-Endpoint

UnknownNbmaNeighbor-Symptom

N/A An NBMA neighbor misconfiguration exists on this OSPF neighbor endpoint.

OSPFVirtualNeighbor-Endpoint

UnknownVirtualNeighbor-Symptom

N/A A virtual neighbor misconfiguration exists on this OSPF virtual neighbor endpoint.

OSPFNeighbor-Relationship

-or-OSPFVirtualLink

NeighborStateAlarm* N/A The neighbor or virtual neighbor for this OSPF link is reporting an improper neighbor state.

Table 3: Symptomatic Events Detected by Network Protocol Manager for OSPF (Continued)

MANAGED ELEMENT SYMPTOM EVENT CONDITION

* Also reported as a symptomatic event notification to Service Assurance Manager.


O S P FA r e a C o n f i g u r a t i o n

Attr ibutes for OSPFAreaThe following table lists some key attributes for OSPFArea.

Root-Cause Problems for OSPFAreaNo root-cause problems are diagnosed for OSPFArea.

Symptomatic Events for OSPFAreaNo events or symptoms are detected for OSPFArea.

OSPFAreaConfigurationAn OSPF area configuration is an OSPF area as configured from the viewpoint of one of the routing devices running an OSPF service in the area. Each routing device has its own view of the area’s attributes.

Table 4: Attributes for OSPFArea

ATTRIBUTE DESCRIPTION ALLOWED VALUES

AreaID A 32-bit integer that uniquely identifies this OSPF area. Area ID 0.0.0.0 is used for the OSPF backbone.

String: IpAddress, an application-wide type representing a 32-bit internet address

AreaType This area’s support for importing AS external link-state advertisements.

String:• NORMAL• STUB• NSSA

IsBackbone True if this area is the OSPF backbone area (Area 0).

Boolean: true or false



Attr ibutes for OSPFAreaConfigurat ionThe following table lists some key attributes for OSPFAreaConfiguration.

Root-Cause Problems for OSPFAreaConf igurat ionNo root-cause problems are diagnosed for OSPFAreaConfiguration.

Symptomatic Events for OSPFAreaConf igurat ionNo events or symptoms are detected for OSPFAreaConfiguration.

OSPFServiceAn OSPF service is an OSPF protocol process running on a routing device. An OSPF service manages the protocol exchanges with other OSPF services.

Table 5: Attributes for OSPFAreaConfiguration


AreaID A 32-bit integer that uniquely identifies this OSPF area. Area ID 0.0.0.0 is used for the OSPF backbone.


AreaType This area’s support for importing AS external link-state advertisements.

String:• NORMAL• STUB• NSSA

IsBackbone True if this area is the OSPF backbone area (Area 0).



O S P F S e r v i c e

Attr ibutes for OSPFServiceThe following table lists some key attributes for OSPFService. Network Protocol Manager for OSPF uses these and other attributes to detect OSPF service events.

Root-Cause Problems for OSPFServiceNo root-cause problems are diagnosed for OSPFService.

Symptomatic Events for OSPFServiceThe following event is detected for OSPFService:

ABRNotInBackbone: The routing device on which this OSPF service is running is an ABR but has no interfaces in the backbone area.

Table 6: Attributes for OSPFService


AdminStatus Administrative status of the routing device on which this OSPF service is running.

String:• UNKNOWN• ENABLED• DISABLED

InBackbone True if at least one interface of the routing device on which this OSPF service is running is in the OSPF backbone area (Area 0).


IsABR True if the routing device on which this OSPF service is running is an ABR.


IsASBR True if the routing device on which this OSPF service is running is an AS Border Router (ASBR).


RouterID A 32-bit integer that uniquely identifies the routing device on which this OSPF service is running.




OSPFNetworkAn OSPF network is a collection of routing devices running OSPF services on an IP network.

Attr ibutes for OSPFNetworkThe following table lists some key attributes for OSPFNetwork. Network Protocol Manager for OSPF uses these and other attributes to diagnose OSPF network problems and to detect OSPF network events.

Table 7: Attributes for OSPFNetwork


DRElectionFailed True if the election of a DR on this OSPF network failed.


DRExists True if this OSPF network has a DR.


MaxRouterPriority Highest router priority of all routing devices connected to this OSPF network. In a multi-access network, the routing device having the highest router priority is elected the DR.

Integer

NetworkType Type of this OSPF network. String:• BROADCAST• NBMA• POINT_TO_POINT• POINT_TO_MULTIPOINT


O S P FN e t w o r k

Root-Cause Problems for OSPFNetworkThe following table lists the root-cause problems diagnosed for OSPFNetwork.

Table 8: Root-Cause Problems for OSPFNetwork

PROBLEM* DESCRIPTION

AreaIDMismatch Area ID on at least one of the interfaces in this OSPF network does not match the area ID on the neighboring interfaces.

AreaTypeMismatch Area type on at least one of the interfaces in this OSPF network does not match the area type on the neighboring interfaces.

AuthKeyMismatch Authentication key on at least one of the interfaces in this OSPF network does not match the authentication key on the neighboring interfaces.

AuthTypeMismatch Authentication type on at least one of the interfaces in this OSPF network does not match the authentication type on the neighboring interfaces.

DuplicateRouterID At least two neighboring interfaces in this OSPF network have the same OSPF router ID.

HelloOrDeadIntervalMismatch Either the Hello interval on at least one of the interfaces in this OSPF network does not match the Hello interval on the neighboring interface, or the Dead interval on at least one of the interfaces in this OSPF network does not match the Dead interval on the neighboring interfaces.

MTUMismatch Maximum transmission unit (MTU) on at least one of the interfaces in this OSPF network does not match the MTU on the neighboring interfaces.

NetmaskMismatch Netmask on at least one of the interfaces in this OSPF network does not match the netmask on the neighboring interfaces.

* Problems prevent neighbor relationships from forming on the affected interface(s).



Symptomatic Events for OSPFNetworkThe following table lists the events detected for OSPFNetwork.

OSPFInterfaceAn OSPF interface is a logical interface, associated with an underlying IP interface, that participates in the OSPF protocol exchange.

Attr ibutes for OSPFInterfaceThe following table lists some key attributes for OSPFInterface. Network Protocol Manager for OSPF uses these and other attributes to diagnose OSPF interface problems and to detect OSPF interface symptoms.

Table 9: Symptomatic Events for OSPFNetwork

EVENT DESCRIPTION

DRElectionFailure No DR was elected on this broadcast or NBMA network segment. This event prevents full neighbor relationships from forming between neighbors on this segment.

AllRouterPrioritiesZero All interfaces on this broadcast or NBMA network segment have their router priority set to 0. This event prevents a DR from being elected on this segment.

Table 10: Attributes for OSPFInterface


AdminStatus Administrative status of this OSPF interface.

String:• UNKNOWN• ENABLED• DISABLED

AuthKey Authentication key for simplePassword authentication for this OSPF interface.

Octet String

AuthType Type of authentication used by this OSPF interface.

String:• NONE• SIMPLE_PASSWORD• MD5• OTHER


O S P F I n t e r f a c e

DeadInterval For the routing device for this OSPF interface, number of seconds during which the router’s Hello packets have not been received before the router’s neighbors declare the routing device down.

IntegerShould be some multiple of the Hello interval and must be the same for all routing devices attached to a common network.

HelloInterval Length of time, in seconds, between the Hello packets that the routing device sends on this OSPF interface.

IntegerMust be the same for all routing devices attached to a common network.

IfEventCount Number of state changes or error events on this OSPF interface.

Integer

IfState Current state of this OSPF interface.

String:• UNKNOWN• DOWN• LOOPBACK• WAITING• POINT_TO_POINT• DESIGNATED_ROUTER• BACKUP_DESIGNATED_ROUTER• OTHER_DESIGNATED_ROUTER

IfType Type of this OSPF interface. String:• BROADCAST• NBMA• POINT_TO_POINT• POINT_TO_MULTIPOINT

IPAddress IP address of this OSPF interface.


IsBDR True if the routing device for this OSPF interface is a Backup Designated Router (BDR).


IsDR True if the routing device for this OSPF interface is a DR.


IsPassive True if this OSPF interface is passive—not in use.


Table 10: Attributes for OSPFInterface (Continued)




MulticastForwarding Way in which multicasts are forwarded on this OSPF interface. Data link multicasting is not meaningful on NBMA or point-to-point interfaces.

String:• DISABLED• BLOCKED• MULTICAST• UNICAST

PollInterval For this OSPF interface, the larger time interval, in seconds, between the Hello packets sent to an inactive NBMA neighbor.

Integer

RouterID A 32-bit integer that uniquely identifies the routing device on which this OSPF service is running.


RouterPriority Priority assigned to the routing device of this OSPF interface, used in multi-access networks for the DR election algorithm.

Integer0 signifies that the routing device is not eligible to become the DR on this particular network segment. If the routing devices on a network segment have the same priority, the devices use their router ID to determine the DR.

TransitDelay Estimated number of seconds to transmit a link-state update packet over this OSPF interface.

Integer

Table 10: Attributes for OSPFInterface (Continued)



O S P F I n t e r f a c e

Root-Cause Problems for OSPFInterfaceThe following table lists the root-cause problems diagnosed for OSPFInterface.

To prevent Network Protocol Manager for OSPF from notifying Disabled root-cause problems, you set a flag named AdminDownFlag. For directions on setting this flag, see the InCharge Network Protocol Manager Configuration Guide.

Symptomatic Events for OSPFInterfaceThe following table lists the symptoms detected for OSPFInterface.

Table 11: Root-Cause Problems for OSPFInterface

PROBLEM DESCRIPTION

Disabled This interface or its associated physical interface is administratively down (manually disabled), and at least one OSPF adjacency on this interface is reporting an improper state. This problem prevents neighbor relationships from forming on this interface.

Down This interface is operationally down when two or more OSPF neighbor relationships exist on this interface and all of them are down.

Table 12: Symptomatic Events for OSPFInterface

SYMPTOM DESCRIPTION

AreaIDMismatchSymptom Area ID on this interface does not match the area ID on the neighboring interfaces.

AreaTypeMismatchSymptom Area type on this interface does not match the area type on the neighboring interfaces.

AuthKeyMismatchSymptom Authentication key on this interface does not match the authentication key on the neighboring interfaces.

AuthTypeMismatchSymptom Authentication type on this interface does not match the authentication type on the neighboring interfaces.

DisabledAdminSymptom This interface or its associated physical interface is administratively down (manually disabled).

DuplicateRouterIDSymptom Two neighboring interfaces have the same OSPF router ID.



OSPFVirtualInterfaceAn OSPF virtual interface is a virtual interface, associated with an underlying IP interface, that participates in the OSPF protocol exchange. A virtual interface is associated with a virtual link, which is typically used to link an OSPF area that does not have a physical connection to the backbone area (Area 0). The virtual link is established between two ABRs having a common OSPF area, and the one ABR is connected to the backbone area.

Attr ibutes for OSPFVirtual InterfaceThe key attributes for OSPFVirtualInterface are the same as those for OSPFInterface, listed in Attributes for OSPFInterface on page 16. Network Protocol Manager for OSPF uses these and other attributes to diagnose OSPF virtual interface problems and to detect OSPF virtual interface symptoms.

Root-Cause Problems for OSPFVirtual InterfaceThe following root-cause problem is diagnosed for OSPFVirtualInterface:

Down: This virtual interface is operationally down when two or more OSPF virtual links exist on this interface and all of them are down.


Either the Hello interval on this interface does not match the Hello interval on the neighboring interfaces, or the Dead interval on this interface does not match the Dead interval on the neighboring interfaces.

MTUMismatchSymptom Maximum transmission unit (MTU) on this interface does not match the MTU on the neighboring interfaces.

NetmaskMismatchSymptom Netmask on this interface does not match the netmask on the neighboring interfaces.

Table 12: Symptomatic Events for OSPFInterface (Continued)

SYMPTOM DESCRIPTION


O S P F N e i g hb o r E n d p o i n t

Symptomatic Events for OSPFVirtual InterfaceThe following table lists the symptoms detected for OSPFVirtualInterface.

OSPFNeighborEndpointAn OSPF neighbor endpoint is a type of service access point defined for each OSPF interface on the host routing device. An OSPF neighbor endpoint is a logical element that holds the status of a single OSPF neighbor relationship from the point of view of one of the OSPF interfaces.

Table 13: Symptomatic Events for OSPFVirtualInterface

SYMPTOM DESCRIPTION

AreaIDMismatchSymptom Area ID on this virtual interface does not match the area ID on the neighboring virtual interfaces.

AreaTypeMismatchSymptom Area type on this virtual interface does not match the area type on the neighboring virtual interfaces.

AuthKeyMismatchSymptom Authentication key on this virtual interface does not match the authentication key on the neighboring virtual interfaces.

AuthTypeMismatchSymptom Authentication type on this virtual interface does not match the authentication type on the neighboring virtual interfaces.

DuplicateRouterIDSymptom Two neighboring virtual interfaces have the same OSPF router ID.


Either the Hello interval on this virtual interface does not match the Hello interval on the neighboring virtual interfaces, or the Dead interval on this virtual interface does not match the Dead interval on the neighboring virtual interfaces.

MTUMismatchSymptom Maximum transmission unit (MTU) on this virtual interface does not match the MTU on the neighboring virtual interfaces.

NetmaskMismatchSymptom Netmask on this virtual interface does not match the netmask on the neighboring virtual interfaces.



Attr ibutes for OSPFNeighborEndpointThe following table lists some key attributes for OSPFNeighborEndpoint. Network Protocol Manager for OSPF uses these and other attributes to diagnose OSPF neighbor endpoint problems and to detect OSPF neighbor endpoint symptoms.

Table 14: Attributes for OSPFNeighborEndpoint


AuthType Type of authentication used by this OSPF endpoint.

String:• NONE• SIMPLE_PASSWORD• MD5• OTHER

HelloSuppressed True if the Hello packets are being suppressed to the neighbor for this OSPF endpoint.


IfState Current state of this OSPF endpoint.

String:• UNKNOWN• DOWN• LOOPBACK• WAITING• POINT_TO_POINT• DESIGNATED_ROUTER• BACKUP_DESIGNATED_ROUTER• OTHER_DESIGNATED_ROUTER

IfType Type of this OSPF endpoint. String:• BROADCAST• NBMA• POINT_TO_POINT• POINT_TO_MULTIPOINT

NbmaNeighborPermanence Status indicating how the neighbor for this OSPF endpoint became known to the endpoint.

String:• DYNAMIC• PERMANENT

NeighborEventCount Number of state changes or error events for the neighbor relationship (session) for this OSPF endpoint.

Integer


O S P F N e i g hb o r E n d p o i n t

Root-Cause Problems for OSPFNeighborEndpointThe following root-cause problem is diagnosed for OSPFNeighborEndpoint:

UnknownNbmaNeighbor: The permanent NBMA neighbor for this OSPF neighbor endpoint is unknown in the topology, and the neighbor relationship is down.

Symptomat ic Events for OSPFNeighborEndpointThe following symptom is detected for OSPFNeighborEndpoint:

UnknownNbmaNeighborSymptom: An NBMA neighbor misconfiguration exists on this OSPF neighbor endpoint.

NeighborIpAddress IP address of the neighboring routing device for this OSPF endpoint.


NeighborState The current state of the neighbor relationship for this OSPF endpoint.

String:• UNKNOWN• DOWN• ATTEMPT• INIT• TWO_WAY• EXCHANGE_START• EXCHANGE• LOADING• FULL

NeighborStateImproper True if the current state of the neighbor relationship for this OSPF endpoint is not progressing to the two-way or full state as appropriate.


Table 14: Attributes for OSPFNeighborEndpoint (Continued)




OSPFVirtualNeighborEndpointAn OSPF virtual neighbor endpoint is a type of service access point defined for each OSPF virtual interface on the host routing device. An OSPF virtual neighbor endpoint is a logical element that holds the status of a single OSPF virtual link from the point of view of one of the OSPF virtual interfaces.

Attr ibutes for OSPFVirtualNeighborEndpointThe key attributes for OSPFVirtualNeighborEndpoint are the same as those for OSPFNeighborEndpoint, listed in Attributes for OSPFNeighborEndpoint on page 22. Network Protocol Manager for OSPF uses these and other attributes to diagnose OSPF virtual neighbor endpoint problems and to detect OSPF virtual neighbor endpoint symptoms.

Root-Cause Problems for OSPFVirtualNeighborEndpointThe following root-cause problem is diagnosed for OSPFVirtualNeighborEndpoint:

UnknownVirtualNeighbor: The virtual neighbor for this OSPF virtual neighbor endpoint is unknown in the topology, and the virtual link is down.

Symptomatic Events for OSPFVirtualNeighborEndpointThe following symptom is detected for OSPFVirtualNeighborEndpoint:

UnknownVirtualNeighborSymptom: A virtual neighbor misconfiguration exists on this OSPF virtual neighbor endpoint.

OSPFNeighborRelationshipAn OSPF neighbor relationship is a link between two OSPF neighbor endpoints. Each complete OSPF neighbor relationship connects two OSPF neighbor endpoints.


O S PF Vi r t u a l L i n k

Attr ibutes for OSPFNeighborRelat ionshipThe key attributes for OSPFNeighborRelationship are the same as those for OSPFNeighborEndpoint, except that the attribute names contain 1 or 2 to denote the attribute set for each of the two endpoints involved in the neighbor relationship. (Attributes named Endpoint1DisplayName and Endpoint2DisplayName identify the OSPF endpoints for the attribute sets.) For a list of the key attributes for OSPFNeighborEndpoint, see Attributes for OSPFNeighborEndpoint on page 22.

Network Protocol Manager for OSPF uses the two sets of OSPFNeighborEndpoint attributes as well as other attributes to diagnose OSPF neighbor relationship problems and to detect OSPF neighbor relationship symptoms.

Root-Cause Problems for OSPFNeighborRelat ionshipThe following root-cause problem is diagnosed for OSPFNeighborRelationship:

Down: This OSPF neighbor relationship is not progressing to the two-way or full state as appropriate, and no physical connectivity failures or OSPF configuration mismatches exist that can explain this condition.

Symptomat ic Events for OSPFNeighborRelat ionshipThe following symptom is detected for OSPFNeighborRelationship:

NeighborStateAlarm: The neighbor for this OSPF neighbor relationship is reporting an improper neighbor state.

OSPFVirtualLinkAn OSPF virtual link is a link between two OSPF virtual neighbor endpoints. Each complete OSPF virtual link connects two OSPF virtual neighbor endpoints.

As clarified in the following illustration, virtual links serve two purposes:

• Link an OSPF area that does not have a physical connection to the backbone area (Area 0).

• Patch the backbone in case discontinuity of Area 0 occurs.



Figure 1: Virtual Link Uses

Attr ibutes for OSPFVirtualLinkThe key attributes for OSPFVirtualLink are the same as those for OSPFNeighborEndpoint, except that the attribute names contain 1 or 2 to denote the attribute set for each of the two endpoints involved in the virtual link. (Attributes named Endpoint1DisplayName and Endpoint2DisplayName identify the OSPF endpoints for the attribute sets.) For a list of the key attributes for OSPFNeighborEndpoint, see Attributes for OSPFNeighborEndpoint on page 22.

Network Protocol Manager for OSPF uses the two sets of OSPFVirtualLink attributes as well as other attributes to diagnose OSPF virtual link problems and to detect OSPF virtual link symptoms.

Root-Cause Problems for OSPFVirtualLinkThe following root-cause problem is diagnosed for OSPFVirtualLink:

Down: This OSPF virtual link is not progressing to the two-way or full state as appropriate, and no physical connectivity failures or OSPF configuration mismatches exist that can explain this condition.

Symptomatic Events for OSPFVirtualLinkThe following symptom is detected for OSPFVirtualLink:

NeighborStateAlarm: The virtual neighbor for this OSPF virtual link is reporting an improper neighbor state.

ABR

Area YArea X Area 0

ABRVirtual Link

A. Linking

ABR

Area ZArea 0 Area 0

ABRVirtual Link

B. Patching


O S P F R ed u n d a n c y G r o u p s

OSPF Redundancy GroupsNetwork Protocol Manager for OSPF supports the creation and analysis of system redundancy groups. Each group is composed of two or more routing devices and their interfaces.

For example, an OSPF area accessed through two Area Border Router (ABR) routing devices can be modeled as a system redundancy group containing the two routing devices. If one ABR routing device experiences a failure, access to the OSPF area is not interrupted but is less resilient to additional failures. A failure in the other ABR routing device makes the OSPF area inaccessible.

By default, Network Protocol Manager for OSPF does not automatically create system redundancy groups. However, using an Adapter Scripting Language (ASL) discovery hook script, you can program Network Protocol Manager for OSPF to automatically create system redundancy groups after the initial discovery of the OSPF routing devices.

Creat ing a System Redundancy GroupTwo ASL discovery hook scripts named custom-end-system.asl and custom-end-post.asl, included in the Network Protocol Manager for OSPF software distribution, allow users to initiate ASL scripts that run after a device (system) or full discovery. By default, the ASL scripts do not perform any discovery processing, meaning that a user must provide the ASL code that performs the actual processing.

An example of adding code to the custom-end-post.asl script to create an ABR SystemRedundancyGroup element is included in the InCharge IP Discovery Guide Supplement for Networking Protocols. Essentially, the ASL code directs Network Protocol Manager for OSPF to create an instance of the SystemRedundancyGroup class and then insert the ABR routing devices participating in the redundancy group into the ComposedOf relationship of the redundancy group.

For information about using this script, see the InCharge IP Discovery Guide Supplement for Networking Protocols.

Symptomat ic Events for a System Redundancy GroupAnalysis and monitoring of a system redundancy group occur automatically when the redundancy group is created and its member elements are inserted into the group. The state of the redundancy group is based on the status of its member elements.



The following table lists the events detected for a system redundancy group and reported to Service Assurance Manager as symptomatic event notifications..

Through impact analysis, Network Protocol Manager for OSPF also links system redundancy group events to root-cause problems received from Availability Manager.

Underlying Transport Network FailuresTo understand how InCharge IP Availability Manager discovers and monitors the underlying transport network elements and diagnoses connectivity failures between those elements, see the InCharge IP Availability Manager User’s Guide.

To understand how Network Protocol Manager for OSPF correlates the underlying transport network failures received from Availability Manager with OSPF symptoms to identify OSPF impacts, see OSPF Cross-Domain Impact Correlation Analysis on page 29.

Table 15: Symptomatic Events for a System Redundancy Group

EVENT DESCRIPTION

All Components Down None of the member elements in the redundancy group are responsive or operational.

At Risk Only one of the member elements in the redundancy group is responsive or operational.

Reduced Redundancy Applies only to redundancy groups containing three or more member elements: At least one member element in the redundancy group is unresponsive or not operational, but the number of responsive or operational member elements is at least two.


3

OSPF Cross-Domain Impact

Correlation Analysis

OSPF failures, or apparent failures, detected by InCharge Network Protocol Manager for OSPF cannot be analyzed in isolation. Rather, the failures detected by Network Protocol Manager for OSPF must be correlated with the Layer 1 and 2 transport failures detected by InCharge IP Availability Manager in order to determine the root-cause problem underlying all observed symptoms. Network Protocol Manager for OSPF filters, synthesizes, and analyzes OSPF- and transport-detected failures to determine whether an OSPF failure is indeed a root-cause failure or simply a symptom of an underlying transport root-cause failure.

OSPF Impact Analysis OverviewWhen Network Protocol Manager for OSPF detects an OSPF failure, it checks for any problem received from Availability Manager that might be causing the failure. If it does not find such a problem, Network Protocol Manager for OSPF begins the OSPF root-cause analysis described in OSPF Elements and Their Failures on page 5.

If it does find such a problem, Network Protocol Manager for OSPF diagnoses the OSPF failure as a symptom and reports the underlying transport root-cause problem and the OSPF symptom in the form of a root-cause problem notification to InCharge Service Assurance Manager. Service Assurance Manager responds by adding the OSPF symptom as an impact of the underlying transport root-cause problem.

OSPF Cross-Domain Impact Correlation Analysis


Figure 2 shows the flow of information between the components in a Network Protocol Manager for OSPF deployment to achieve OSPF and global impact analysis.

Figure 2: OSPF and Global Impact Analysis

AvailabilityManager

AvailabilityManager

ServiceAssuranceManager

GlobalConsole

Managed Network

Root-CauseProblem Notification

(with Network Symptoms)

Root-Cause Problem Notification(with Network and OSPF Symptoms

Shown as Impacts)

Root-CauseProblem Notification

(with OSPF Symptoms)

Root-Cause Problemand Symptoms

NetworkProtocolManagerfor OSPF

AvailabilityManager

(one or more)

Pollingand Results

Pollingand Results


O S PF I m p ac t A n a l y s i s M o d e l

OSPF Impact Analysis ModelFigure 3 demonstrates how Network Protocol Manager for OSPF models (represents) its managed OSPF topology. The underlying transport network elements in the model, shown as white text on black background, are managed by Availability Manager. As such, Network Protocol Manager for OSPF receives the status of these elements from Availability Manager.

Figure 3: Network Manager Protocol View of its Managed OSPF Topology

OSPF Interface-or-

OSPF Virtual Interface

ConnectedTo

OSPF Interface-or-

OSPF Virtual Interface

ConnectedTo

ConnectedTo

L L

L L

L

L

ConnectedTo

AccessedVia

AccessedVia

OSPF Neighbor Endpoint-or-

OSPF Virtual Neighbor Endpoint

OSPF Neighbor Endpoint-or-

OSPF Virtual Neighbor Endpoint

Card

HostedBy

Router

OSPF Service

L

L

Interface

Card

HostedBy

Interface

Router

OSPF Service

L

L

2. OSPF Area/ OSPF Area Configuration elements not shown

Notes:= LayeredOverL1.

NetworkConnection

L

L

LOSPFNetwork

OSPF Neighbor Relationship-or-

OSPF Virtual Link



Not all of the transport network elements understood by Network Protocol Manager for OSPF are shown in the figure. For example, Network Protocol Manager for OSPF also understands Cable and Trunk Cable elements. In addition, the network cloud in the figure represents various types of connections between the two physical interfaces underlying the OSPF neighbor relationship, including connections between ports on intermediate switches.

OSPF Impact Analysis ExamplesThe examples that follow show how Network Protocol Manager for OSPF uses the relationships between the underlying transport network elements and the OSPF elements to perform OSPF impact analysis. In addition, the examples show how Service Assurance Manager picks up where Network Protocol Manager for OSPF leaves off to perform global impact analysis.

Example of Phys ica l Inter face DownIn this example, Network Protocol Manager for OSPF detects an alarming OSPF neighbor relationship. It also receives an Interface Down problem from Availability Manager for one of the physical interfaces underlying the alarming OSPF neighbor relationship.

When Availability Manager detects the Interface Down problem, it sends the problem along with the network symptoms to both Service Assurance Manager and Network Protocol Manager for OSPF. Network Protocol Manager for OSPF correlates the Interface Down problem with the alarming OSPF neighbor relationship and sends the problem along with the NeighborStateAlarm symptom to Service Assurance Manager.

Service Assurance Manager combines the Interface Down problem notifications received from Availability Manager and Network Protocol Manager for OSPF to form one notification, and combines the symptoms to form a list of impacts for the notification.

What follows is a summary of example notifications created for the Interface Down problem, followed by an example display (Figure 4) showing the impacts of the combined notification created by Service Assurance Manager.


O S PF I m p ac t A n a l y s i s E x a mp l e s

• Availability Manager Notification:Root Cause: Interface DownSymptom: NetworkConnection DownOrFlapping

• Network Protocol Manager for OSPF Notification:Root Cause: Interface DownSymptom: OSPFNeighborRelationship NeighborStateAlarm

• Service Assurance Manager Combined Notification:Root Cause: Interface DownSymptoms (Impacts): NetworkConnection DownOrFlapping and

OSPFNeighborRelationship NeighborStateAlarm

Figure 4: Notification Properties Dialog Box Showing an Interface Down Problem

For instructions on viewing detailed notification information, see Viewing OSPF Notifications, Maps, and Containment on page 39.

Example of Phys ica l Inter face DisabledIn this example, Network Protocol Manager for OSPF detects an alarming OSPF neighbor relationship. It also receives an Interface Disabled problem from Availability Manager for one of the physical interfaces underlying the alarming OSPF neighbor relationship.



What follows is a summary of example notifications created for the Interface Disabled problem, followed by an example display (Figure 5) showing the impacts of the combined notification created by Service Assurance Manager.

• Availability Manager Notification:Root Cause: Interface DisabledSymptom: NetworkConnection DownOrFlapping

• Network Protocol Manager for OSPF Notification:Root Cause: Interface DisabledSymptom: OSPFNeighborRelationship NeighborStateAlarm

• Service Assurance Manager Combined Notification:Root Cause: Interface DisabledSymptoms (Impacts): NetworkConnection DownOrFlapping and


Figure 5: Notification Properties Dialog Box Showing an Interface Disabled Problem



Example of Cable DownIn this example, Network Protocol Manager for OSPF detects several alarming OSPF neighbor relationships. It also receives a Cable Down problem from Availability Manager associated with the two physical interfaces underlying the alarming OSPF neighbor relationships.

What follows is a summary of example notifications created for the Cable Down problem, followed by an example display (Figure 6) showing the impacts of the combined notification created by Service Assurance Manager.

• Availability Manager Notification:Root Cause: Cable DownSymptom: Cable DownOrFlapping

• Network Protocol Manager for OSPF Notification:Root Cause: Cable DownOrFlappingSymptoms: OSPFNeighborRelationship NeighborStateAlarm, ...

• Service Assurance Manager Combined Notification:Root Cause: Cable DownSymptoms (Impacts): Cable DownOrFlapping,

OSPFNeighborRelationship NeighborStateAlarm, ...

Figure 6: Notification Properties Dialog Box Showing a Cable Down Problem



For the Cable Down problem, notice that Network Protocol Manager for OSPF lists the Cable DownOrFlapping symptom as the root cause in its notification. Upon receiving the Cable Down notification from Availability Manager and the Cable DownOrFlapping notification from Network Protocol Manager for OSPF, Service Assurance Manager stitches the two notifications together and lists Cable DownOrFlapping and OSPFNeighborRelationship NeighborStateAlarm as symptoms (impacts) in the Cable Down notification.

Example of TrunkCable DownIn this example, Network Protocol Manager for OSPF detects an alarming OSPF neighbor relationship. It also receives a TrunkCable Down problem from Availability Manager associated with the two physical interfaces underlying the alarming OSPF neighbor relationship.

What follows is a summary of example notifications created for the TrunkCable Down problem, followed by an example display (Figure 7) showing the impacts of the combined notification created by Service Assurance Manager.

• Availability Manager Notification:Root Cause: TrunkCable DownSymptom: TrunkCable DownOrFlapping

• Network Protocol Manager for OSPF Notification:Root Cause: TrunkCable DownOrFlappingSymptom: OSPFNeighborRelationship NeighborStateAlarm

• Service Assurance Manager Combined Notification:Root Cause: TrunkCable DownSymptoms (Impacts): TrunkCable DownOrFlapping and




Figure 7: Notification Properties Dialog Box Showing a TrunkCable Down Problem

For the TrunkCable Down problem, notice that Network Protocol Manager for OSPF lists the TrunkCable DownOrFlapping symptom as the root cause in its notification. Upon receiving the TrunkCable Down notification from Availability Manager and the TrunkCable DownOrFlapping notification from Network Protocol Manager for OSPF, Service Assurance Manager stitches the two notifications together and lists TrunkCable DownOrFlapping and OSPFNeighborRelationship NeighborStateAlarm as symptoms (impacts) in the TrunkCable Down notification.




4

Viewing OSPF Notifications,

Maps, and Containment

This chapter describes using the Global Console to view OSPF notifications, topology maps, and containment information for InCharge Network Protocol Manager for OSPF. You view this information by attaching the Global Console to InCharge Service Assurance Manager.

For instructions on viewing notifications, maps, and containment information, see the InCharge Operator’s Guide. For information about the topology elements monitored, the events detected, and the problems diagnosed by Network Protocol Manager for OSPF, see OSPF Elements and Their Failures on page 5.

Viewing OSPF NotificationsNetwork Protocol Manager for OSPF reports notifications to InCharge Service Assurance Manager, and Service Assurance Manager combines these notifications with the notifications received from InCharge IP Availability Manager. You can view the notifications through the Global Console in two basic ways:

• As table entries in a Notification Log Console view

• As color-coded severity icons in a Map Console view

Viewing OSPF Notifications, Maps, and Containment


Opening an OSPF Noti f icat ion Propert ies Dialog BoxTo obtain detailed information about an individual OSPF notification, you can use any of the following common methods to open the Notification Properties dialog box:

• Double-click an OSPF notification in the Notification Log Console.

• Select an OSPF notification in the Notification Log Console and click the Properties toolbar button.

• Right-click a selected OSPF notification and select Properties in the pop-up menu.

• Double-click an OSPF map icon affected by active events.

OSPF Noti f icat ion Propert iesFigure 8 and Figure 9 provide examples of detailed OSPF mismatch information displayed in the Notification Properties dialog box.

Figure 8: Notification Properties Dialog Box Showing a Mismatch


Vi ew i n g O S PF To p o l o g y i n M a p s

Figure 9: Notification Properties Dialog Box Showing the Mismatch Impact

The Impact tab shown in Figure 9 identifies the elements that are impacted by a root-cause failure: Seven OSPF neighbor relationships are impacted by the misconfiguration of the Hello or Dead interval on an OSPF network named OSPF-NET-172.18.150.0-255.255.255.128.

Viewing OSPF Topology in MapsNetwork Protocol Manager for OSPF sends a streamlined copy of its OSPF topology to InCharge Service Assurance Manager, and Service Assurance Manager combines this topology with the underlying transport network topology received from InCharge IP Availability Manager. Of the ten types of OSPF elements that may appear in OSPF topology, Network Protocol Manager for OSPF includes the following six types in the topology that it sends to Service Assurance Manager:

• OSPFArea

• OSPFAreaConfiguration

• OSPFService

• OSPFNetwork



• OSPFNeighborRelationship

• OSPFVirtualLink

You view the OSPF topology connectivity maps using the Map Console view of the Global Console.

Note: By default, the display of OSPF maps is disabled. For instructions on enabling the display of the OSPF maps, see the InCharge Network Protocol Manager Configuration Guide.

Opening an OSPF Topology MapYou can use any of the following common methods to access an OSPF map:

• Open the Map Console from the Global Console by selecting File > New > Map Console. In the Topology tab of the Map Console, click an OSPF topology element (other than an OSPFAreaConfiguration element) to display a map of the element. OSPFAreaConfiguration elements have no associated map display.

• Select the Show Map option from any opened console attached to Service Assurance Manager. For example, in the Notification Log Console, click an OSPF notification and then select Event > Show Map, or right-click the notification and then select Show Map in the pop-up menu. In the Topology Browser Console, right-click an OSPF element (other than an OSPFAreaConfiguration element) and select Show Map in the pop-up menu.

OSPF Topology Map Graphical Representat ionsAn OSPF topology map contains elements such as OSPF areas, OSPF services, OSPF networks, OSPF neighbor relationships, and OSPF virtual links; and relationships and connections. In a map display, a node is a graphical representation of an element, and an edge is a graphical representation of a relationship or connection between elements.

Table 16 identifies and describes the default icons and edges that may appear in an OSPF topology map. In the Map Console, you can also select Map > Map Legend to see a similar list.

Note that your system administrator may replace the standard map icons with other map icons that are preferred by your organization. In that case, use Map > Map Legend to see the definitions of your map icons.



Note: Additional icons may display, depending on the underlying InCharge products and certified devices.

Table 16: Default Nodes and Edges for OSPF Topology Maps

ICON / VISUAL INDICATOR DESCRIPTION

Icon represents an OSPF area.

Icon—standard router icon—represents an OSPF service running on a router, a router switch module (RSM), a multilayer switch feature card (MSFC), or a router switch feature card (RSFC).

Icon represents an OSPF network.

Jagged line can represent an OSPF neighbor relationship or an OSPF virtual link. A jagged green line indicates a normal connection.

Dotted black line with arrow represents composition.



OSPF Map LabelsOSPF topology maps use the labels shown in the following table to visually distinguish the different roles performed by the devices in the OSPF topology.

OSPF Map ViewsOSPF topology maps display the OSPF areas, the OSPF networks and their interconnections, and the routing devices that belong to the OSPF networks.

Table 17: Labels Showing the Roles of Devices in OSPF Maps

OSPF MAP LABEL DESCRIPTION

Area Border Router (ABR). An OSPF routing device that has interfaces in multiple OSPF areas.

Autonomous System Border Router (ASBR). An OSPF routing device that exchanges routing information with routing devices (running OSPF or other interior gateway protocols) belonging to other autonomous systems.

An OSPF routing device configured as an ABR and an ASBR.

ABR

lab-gw.smarts.com

ASBR

rld.smarts.com

ABR

jfk.smarts.com

ASBR



O S P F A r e a M ap

The OSPF Area map (Figure 10) shows the member devices and networks for the selected OSPF area. Each member device is running an OSPF service.

Figure 10: OSPF Area Map—Example



O S P F S e r v i c e M a p

The OSPF Service map (Figure 11) shows the selected device along with its neighbor devices, connected networks, and its OSPF area. Each device is running an OSPF service.

Figure 11: OSPF Service Map—Example



O S P F N e tw o r k M ap

The OSPF Network map (Figure 12) shows the selected OSPF network, along with the connected devices and the OSPF area.

Figure 12: OSPF Network Map—Example



OS P F N e i g hb o r R e l a t i o n sh i p M ap

The OSPF Neighbor Relationship map (Figure 13) shows the selected OSPF neighbor relationship between the two devices running neighboring OSPF services. The jagged line represents the OSPF neighbor relationship.

Figure 13: OSPF Neighbor Relationship Map—Example

O S P F V i r t u a l L i n k M ap

The OSPF Virtual Link map shows the selected OSPF virtual link between the two devices running neighboring OSPF services. An OSPF virtual link map is similar to an OSPF neighbor relationship map (Figure 13) except that the two devices connected by the virtual link are always ABRs.


Vi e w i n g OS P F C o n t a i n me n t

Viewing OSPF ContainmentAccompanying the OSPF topology that Network Protocol Manager for OSPF sends to InCharge Service Assurance Manager are instructions on what topology information to include in the Containment view for each type of OSPF element. An element’s Containment view displays in a dialog box that organizes the information for the element into tab pages and tables. The following figure shows a Containment dialog box for an OSPF network element.

Figure 14: OSPF Network Containment Dialog—Example

In a Containment view, different information is available for different types of elements.

Note: Containment is not available for user-defined groups and services.

Opening an OSPF Containment DialogTo obtain containment information about an individual OSPF element, you can use any of the following common methods to open a Containment dialog for the element:

• In an OSPF map tree, right-click the element and select Containment in the pop-up menu.

Class Name Element Name

Tabs



• In an OSPF map display, right-click the element and select Containment in the pop-up menu.

• In a Topology Browser Console, right-click the element and select Containment in the pop-up menu.

• In a Notification Log Console, double-click a notification for the element and click the Containment button in the Notification Properties dialog.

OSPF Containment Tab PagesThe OSPF tab pages that appear in a Containment view for an OSPF element contain the routing topology information listed in the following table.

Table 18: OSPF Classes and Their Containment Tab Pages and Associated Attributes

CLASS NAME OSPF TAB NAME ATTRIBUTES

OSPFArea Attached Systems DescriptionDisplayNameLocationModelVendor

OSPF Networks DisplayNameDRExistsMaxRouterPriority

OSPFNetwork OSPF Interface Configuration AreaTypeAuthKeyAuthTypeDeadIntervalDisplayNameHelloIntervalMaxTransferUnitNetmask

OSPFNetworkOSPFNeighborRelationshipOSPFVirtualLinkUnitaryComputerSystemOSPFService

OSPF Interfaces AdminStatusAreaIDBackupDesignatedRouterDesignatedRouterDisplayNameIfStateIfTypeIsPassive


Vi e w i n g OS P F C o n t a i n me n t

OSPF Containment Use as a Troubleshooting AidThe Containment view is an excellent aid for resolving OSPF problems. As an example, to begin resolving a misconfiguration problem for an OSPF network, you would open the Containment dialog for the failed OSPF network and click the OSPF Interface Configuration tab to determine which OSPF interface (or interfaces) has the configuration problem.

OSPFService OSPF Areas AreaIDAreaTypeOSPFAreaPropagatesSummaries

OSPFServiceOSPFNeighborRelationshipOSPFVirtualLinkUnitaryComputerSystem

OSPF Endpoints DisplayNameIfIndexIfStateIfTypeNeighborIpAddressNeighborDisplayNameNeighborState

Table 18: OSPF Classes and Their Containment Tab Pages and Associated Attributes

CLASS NAME OSPF TAB NAME ATTRIBUTES




5

Customizing OSPF Polling

InCharge Network Protocol Manager for OSPF monitors the OSPF network by sending SNMP polls to the OSPF elements in the network and comparing the polling results to threshold values that define acceptable and unacceptable levels of connectivity. Network Protocol Manager for OSPF uses the thresholds values, in conjunction with received trap messages, syslog messages, and events from Availability Manager, to diagnose the failed element or elements that interrupt OSPF connectivity.

Using the Polling and Thresholds Console, shown in Figure 15, you can customize the SNMP polling for Network Protocol Manager for OSPF by modifying default polling groups or by creating new polling groups. The polling groups periodically collect the data needed by Network Protocol Manager for OSPF to determine the availability of the OSPF elements in the managed OSPF network. The polled data serves as input to Network Protocol Manager for OSPF correlation analysis.

For a description of SNMP polling for correlation analysis, see Polling for Analysis on page 87.

Polling Groups and SettingsThe polling groups and settings for Network Protocol Manager for OSPF are accessible via the Polling tab of the Polling and Thresholds Console. A group contains one or more settings, and a setting contains a collection of parameters.



Pol l ing GroupsCurrently, Network Protocol Manager for OSPF provides one default polling group named OSPF, which has a single default setting named OSPF SNMP Setting. The OSPF polling group is used by Network Protocol Manager for OSPF to monitor OSPF interface connections.

The OSPF polling group accepts only elements of class OSPFInterface or OSPFVirtualInterface, so only OSPF interface elements become members of the OSPF polling group. You can specify additional matching criteria (OSPFInterface/OSPFVirtualInterface attribute values) for the OSPF polling group to further limit its membership, as explained in Method for Editing Matching Criteria on page 62.

Pol l ing Sett ingsCurrently, Network Protocol Manager for OSPF provides the following polling settings:

• OSPF SNMP Setting (default)

• OSPF External Setting

These settings are mutually exclusive, meaning that one or the other (but not both) can be specified for an OSPF polling group.

O S P F S N M P S e t t i n g

The OSPF SNMP Setting determines the polling intervals used by Network Protocol Manager for OSPF to monitor OSPF interface connections. Network Protocol Manager for OSPF monitors the connections by probing the SNMP tables maintained by the SNMP agents of the OSPF routing devices.


P o l l i n g G r o u ps a n d S e t t i n g s

Table 19 lists the OSPF SNMP Setting parameters.

OS P F E x t e r n a l S e t t i n g

The OSPF External Setting determines the initial states of the OSPF interface connections analyzed by Network Protocol Manager for OSPF. The analysis results are collected by an external process for test purposes.

Table 20 lists the OSPF External Setting parameters.

Table 19: OSPF SNMP Setting Parameters and Their Values

PARAMETER VALUES DESCRIPTION

AnalysisMode ENABLED,DISABLEDDefault: ENABLED

Enables or disables Network Protocol Manager for OSPF analysis; if analysis mode is disabled, no polling is performed.

PollingInterval 30 to 3600 secondsDefault: 240 seconds

Sets the time between successive polls.

Retries 0 to 10 retriesDefault: 3

Sets the number of retry polls to perform when the initial poll fails.

Timeout 10 to 10000 millisecondsDefault: 700 milliseconds

Sets the amount of time allowed for the first poll request before it times out. Successive retries use longer times.

Table 20: OSPF External Setting Parameters and Their Values


AnalysisMode ENABLED,DISABLEDDefault: ENABLED

Enables or disables Network Protocol Manager for OSPF analysis; if analysis mode is disabled, no information is collected by the external process.

InitialAdminStatus UNKNOWN,ENABLED,DISABLEDDefault: ENABLED

Sets the initial administrative state of all OSPF interfaces discovered in the managed OSPF network domain.



InitialIfState UNKNOWN,DOWN,LOOPBACK,WAITING,POINT_TO_POINT,DESIGNATED_ROUTER,BACKUP_DESIGNATED_ROUTER,OTHER_DESIGNATED_ROUTERDefault: POINT_TO_POINT

Sets the initial state of all OSPF interfaces discovered in the managed OSPF network domain.

InitialMulticastIfState UNKNOWN,DOWN,LOOPBACK,WAITING,POINT_TO_POINT,DESIGNATED_ROUTER,BACKUP_DESIGNATED_ROUTER,OTHER_DESIGNATED_ROUTERDefault: OTHER_DESIGNATED_ROUTER

Sets the initial state of all multicast OSPF interfaces discovered in the managed OSPF network domain.

InitialNeighborState UNKNOWN,DOWN,ATTEMPT,INIT,TWO_WAY,EXCHANGE_START,EXCHANGE,LOADING,FULLDefault: FULL

Sets the initial state of all neighboring OSPF interfaces discovered in the managed OSPF network domain.

InitialNonMulticastIfState UNKNOWN,DOWN,LOOPBACK,WAITING,POINT_TO_POINT,DESIGNATED_ROUTER,BACKUP_DESIGNATED_ROUTER,OTHER_DESIGNATED_ROUTERDefault: POINT_TO_POINT

Sets the initial state of all non-multicast OSPF interfaces discovered in the managed OSPF network domain.

Table 20: OSPF External Setting Parameters and Their Values (Continued)



T h r e s h o l d G r o u ps a n d S e t t i n g s

Threshold Groups and SettingsCurrently, there are no threshold groups and settings for Network Protocol Manager for OSPF. Network Protocol Manager for OSPF compares the polled data against fixed thresholds to determine fault conditions and to perform OSPF connectivity correlation analysis.

Opening the Polling and Thresholds ConsoleThe Polling and Thresholds Console is used to display groups and modify their properties. To access the Polling and Threshold Console, you must first open the Domain Manager Administration Console.

InitialVirtualState UNKNOWN,DOWN,LOOPBACK,WAITING,POINT_TO_POINT,DESIGNATED_ROUTER,BACKUP_DESIGNATED_ROUTER,OTHER_DESIGNATED_ROUTERDefault: POINT_TO_POINT

Sets the initial state of all virtual OSPF interfaces discovered in the managed OSPF network domain.

InitialVirtualNeighborState UNKNOWN,DOWN,ATTEMPT,INIT,TWO_WAY,EXCHANGE_START,EXCHANGE,LOADING,FULLDefault: FULL

Sets the initial state of all neighboring virtual OSPF interfaces discovered in the managed OSPF network domain.

NeedToValidateConfiguration ENABLED,DISABLEDDefault: DISABLED

Enables or disables the analysis of OSPF configuration errors found in the managed OSPF network domain.

Table 20: OSPF External Setting Parameters and Their Values (Continued)




Attaching to a Domain Manager, such as Network Protocol Manager for OSPF, with the Domain Manager Administration Console requires an InCharge user account with the following privileges and permissions:

• All privileges, specified in the serverConnect.conf file (or its equivalent) read by the Domain Manager.

• Permission to use the console operation Configure Domain Manager Admin Console. Through the Global Manager Administration Console, this permission is specified in the Console Operations section of the user profile.

For information about configuring access privileges, see the InCharge System Administration Guide. For information about configuring permissions to perform specific console operations, see the InCharge Service Assurance Manager Configuration Guide.

To open the Polling and Thresholds Console, follow these steps:

1 Attach to the Domain Manager with the Global Console. The Topology Browser Console opens.

2 In the Topology Browser Console, select Configure > Domain Manager Administration Console. The Domain Manager Administration Console Console opens.

3 In the Domain Manager Administration Console, select Edit > Polling and Thresholds. The Polling and Thresholds Console opens.

Layout of the Poll ing and Thresholds ConsoleThe Polling and Thresholds Console is divided into two panels.

• The left panel displays the icon for the analysis domain in the upper-left corner and provides two tabs, Polling and Thresholds, at the bottom. When the Polling tab is selected, the console displays polling groups. Likewise, when the Thresholds tab is selected, the console displays threshold groups. Threshold groups are not available to Network Protocol Manager for OSPF.

For each group, there are settings that provide adjustable parameters and a membership list of managed elements to which the settings are applied.

• The right panel remains blank until a group, setting, or member is selected in the left panel. When an item is selected in the left panel, the right panel displays additional information regarding that item.


Op e n i n g t h e Po l l i n g a n d T h r e s ho ld s C o n so l e

Figure 15 provides an example of a Polling and Thresholds Console attached to a Network Protocol Manager for OSPF Domain Manager named INCHARGE-OSPF.

Figure 15: Polling and Thresholds Console—Example

Pol l ing and Thresholds Console Toolbar ButtonsThe toolbar of the Polling and Thresholds Console provides quick access to the commands described in Table 21.



Working With Polling Groups and SettingsThe configuration of a Domain Manager, such as Network Protocol Manager for OSPF, applies polling parameters to defined sets of managed elements.

• A polling group is composed of settings and members.

• A setting is composed of one or more related parameters.

• A member is an element of the managed topology that belongs to a polling group.

Using the Polling and Thresholds Console, you can perform the following configuration tasks:

• Modify the properties of existing polling groups.

• Determine what settings are applied to a polling group.

• Modify the parameters of a setting.

• Create new polling groups.

Table 21: Polling and Thresholds Console Toolbar Buttons

BUTTON DESCRIPTION

Attach to a Domain Manager

Detach from a Domain Manager

Reconfigure polling and thresholds groups

Delete selected item


Wo r k i n g Wi t h P o l l i n g G r o u ps a n d S e t t i n g s

How Managed Elements Are Assigned to GroupsWhen a Domain Manager performs discovery, it automatically assigns each managed element to a group based on:

• Matching criteria defined for the group

• Priority of the group, which determines membership when a device meets the matching criteria for more than one group

A managed element can be a member of one and only one polling group.

Modifying the Propert ies of a GroupA polling group is composed of settings and members. A setting includes one or more polling parameters. The matching criteria specified for the group and the group’s priority determine which managed elements are members of the group.

When a group name is selected in the left panel of the Polling and Thresholds Console, four tabs are displayed:

• Settings

• Priorities

• Matching Criteria

• Description

Modifying the properties under each of these tabs changes the configuration of the group. When you finish editing the properties of a group, click the Apply button to save the changes and then select Reconfigure from the Group menu to make the configuration changes take effect.

Method for Adding or Removing Sett ingsA group’s settings determine what polling parameters are applied to the managed elements that are members of the group.

The Settings tab is divided into two sections: Current Settings and Available Settings. The Current Settings section lists the settings that are applied to the group. The Available Settings section lists additional available settings.



A d d in g o r Re mo v i n g a S e t t i n g

1 Select a setting from the Current Settings list or from the Available Settings list.

2 Click Add to move an available setting to the Current Settings list or click Remove to move a current setting to the Available Settings list.

3 Click Apply.

4 Select Reconfigure from the Group menu.

Method for Modifying the Pr ior i ty of GroupsPriority and matching criteria determine which managed elements are members of what group. When an element matches the criteria for two or more groups, the managed element becomes a member of the group with the highest priority. The Priorities tab lists groups in the order of their priority, from highest to lowest.

C h an g i n g t h e P r i o r i t y o f a G r o u p

1 Select the group for which you want to change the priority.

2 Click the up or down arrow to change its position relative to the other groups.

3 Click Apply.


Method for Edit ing Matching Cri ter iaMatching criteria, which appear at the top of the Matching Criteria tab, are defined using the attributes of the managed elements. Each matching criterion has three fields: Name, Description, and Value.

• Name identifies the attribute that is used as a matching criterion.

• Description is the description of the attribute taken from the ICIM model.

• Value is any combination of text, integers, and wildcards (see the Wildcards Appendix) that is matched against the value of the attribute in the managed element. The Value field for a matching criterion is not case-sensitive.

If the value of a managed element’s attribute matches a matching criterion, the managed element is eligible to become a member of the group. When more than one matching criterion is specified, a managed element must match all criteria to become a member of the group.



Thus, for an OSPF polling group, which may only contain OSPFInterface or OSPFVirtualInterface elements, you can specify additional matching criteria (OSPFInterface/OSPFVirtualInterface attribute values) to restrict which managed OSPF interface elements become members of the group.

For example, if you specify an AreaID matching criterion with a value of 172.16.*, only OSPF interface elements having the string 172.16 in their area ID will be members of the group. If, in addition, you specify an AreaIDMismatchAttribute matching criterion with a value of TRUE, only the OSPF interface elements having (1) string 172.16 in their area ID and (2) at least one neighboring interface having a mismatching area ID will be members of the group.

A d d in g o r R e mo v i n g M a t c h i n g C r i t e r i a

1 Select a matching criterion.

2 Click Enable to make the criterion active, moving it to the top of the Matching Criteria tab.

Use Disable to deactivate the criterion, moving it to the bottom of the Matching Criteria tab.

3 If you are adding a matching criterion, type a matching pattern in the Value field.

4 Click Apply.


C h an g i n g t h e V a l u e o f a M a t c h i n g C r i t e r i o n

1 Select the string in the Value field or double-click the Value field to highlight the current value.

2 Type the text, integers, or wildcard to match against the attribute.

3 Click Apply.


A Domain Manager processes matching criteria in the following manner. First, managed elements are compared against the matching criteria of the group with the highest priority. If an element matches all the criteria, it is added as a member of the group. If an element does not match all the criteria, it is compared against the matching criteria of the group with the second highest priority, and so on.



When no matching criteria are active (or appear in the top of the Matching Criteria dialog box), the group matches all managed elements—for Network Protocol Manager for OSPF, the group matches all managed OSPF interface elements. Priority determines whether the group contains members.

Method for Modify ing the Parameters o f a Sett ingThe parameters of a setting are changed in one of two ways: by (1) choosing a value from a drop-down menu or (2) entering a value in a Value field or adjusting a slider bar representing a range of values.

C h an g i n g t h e P a r a m e t e r s o f a S e t t i n g

1 Select the setting in the left panel of the Polling and Thresholds Console. The parameters of a setting are listed in the right panel of the console.

2 Change the value of a parameter using one of the following methods:

For a drop-down menu, click the menu and select a value.

For a slider bar presentation,

• Type a value into the Value field and press Enter or

• Select the slider bar and drag its handle with the mouse to change the value or select the slider bar and use the arrow keys to move its handle to change the value.

3 Click Apply to save the changes.


Re s t o r i n g t h e D e f au l t Va l ue s o f a S e t t i n g

The Restore Defaults button, which is visible when a setting is selected in the left panel of the Polling and Thresholds Console, restores the default values of all the parameters for the selected setting.

1 Select the setting.

2 Click Restore Defaults.


Creat ing New Poll ing GroupsCreating a new polling group enables you to customize the polling settings for a group of managed elements. You can use two methods to create a new group:



• Copy an existing group. The new group contains the same settings and thresholds as the original group. Matching criteria are not copied.

• Create an empty group. The new group does not contain any settings or members. You must add settings and matching criteria, and set the priority of the new group.

After you create a new group, use procedures previously described to adjust the settings of the new group. For information regarding settings, see Method for Modifying the Priority of Groups on page 62, and for information regarding groups, see Modifying the Properties of a Group on page 61.

C o p y i n g a n E x i s t i n g G r o u p

1 Right-click the Polling or Threshold group that you want to copy.

2 Select Copy from the pop-up menu to display the Copy Group dialog.

3 In the dialog, type a name and an optional description for the new group and click OK. The new group contains the same settings and thresholds as the group you copied.

4 Edit the settings, matching criteria, and priority of the new group. Change the value of any parameters as necessary.


C r e a t i n g a n E mp t y G r o u p

1 In the left panel of the Polling and Threshold Console, right-click the group type for which you want to create a new group. (When a Domain Manager provides more than one default group, you can create more than one type of group.)

2 Select New Group from the pop-up menu to display the New Group dialog.

3 In the dialog, type a name and an optional description for the new group and click OK.

4 Add settings and matching criteria, and set the priority of the new group. Change the values of any parameters as necessary.





A

OSPF Terminology

The terms and concepts presented in this appendix should prove helpful in understanding the Open Shorted Path First (OSPF) network domain discovered and monitored by InCharge Network Protocol Manager for OSPF.

Begin by examining the following diagram.

Figure 16: Interior Gateway Protocol and Exterior Gateway Protocol Links

OSPF Terminology


The links between the routing devices within an independent network, or autonomous system (AS), are referred to as Interior Gateway Protocol (IGP) links, and the links between routing devices in different autonomous systems are referred to as Exterior Gateway Protocol (EGP) links. OSPF is an IGP.

• ABR

Area Border Router. A router that has interfaces in multiple OSPF areas. It runs a copy of the basic OSPF algorithm for each area to which it belongs.

• ABR System Redundancy Group

Two or more ABRs that interface with and back up the same two OSPF areas.

• AS

Autonomous System. A collection of networks, or more precisely, the routing devices joining those networks, that are under the same administrative authority and that share a common routing strategy.

• ASBR

Autonomous System Border Router. An OSPF router that exchanges routing information with routing devices (running OSPF or other interior gateway protocols) belonging to other autonomous systems.

• BDR

Backup Designated Router. An OSPF router elected on a broadcast (multi-access) network segment to back-up the Designated Router.

• DR

Designated Router. An OSPF router elected on a broadcast (multi-access) network segment to flood routing updates. Instead of each router exchanging OSPF updates with every other router on the broadcast segment, each non-DR router on the segment builds a full adjacency with the DR to exchange information with the DR, and the DR relays the information to the other non-DR routers.

• EGP

Exterior Gateway Protocol. A routing protocol, such as Border Gateway Protocol (BGP), used to exchange routing information between two routing devices in a network of autonomous systems. An EGP protocol maintains routes between autonomous systems.


• IGP

Interior Gateway Protocol. A routing protocol used to calculate routes and exchange routing information among routers within an autonomous system.

• LSA

Link-State Advertisement. When a network link changes state (up to down, or vice versa) in an OSPF network, the change is flooded throughout the network as a link-state advertisement. All the routers note the change and recompute their routes accordingly.

• MTU

Maximum Transmission Unit. A setting that controls the maximum IP packet size that a PC will send.

• Multi-Access Segment

A network segment supporting three or more routing devices. A network segment is part of an Ethernet or other network on which all message traffic is common to all nodes, that is, a message is broadcast from one node on the segment and received by all others on the segment.

• NBMA

Non-Broadcast Multiple Access. A network without broadcast capabilities, but where all interfaces on the network are fully meshed (connected); for example, a fully meshed Frame Relay cloud.

• OSPF

Open Shortest Path First. A link-state based interior gateway protocol, defined in RFC 1253, used to distribute routing information within an autonomous system. Each OSPF router generates a full model of its OSPF area (portion of the autonomous system), including all IP subnets and all routers in the area, and executes a shortest path first (SPF) algorithm to determine the best route to each IP subnet in the model.

• OSPF Adjacency

OSPF adjacency, also known as OSPF neighbor relationship, is the next step after OSPF routers become neighbors. In order to minimize the amount of information exchanged on a particular broadcast (multi-access) network segment, OSPF elects one router to be a Designated Router (DR), and one router to be a Backup Designated Router (BDR), on each broadcast segment. Routers that become adjacent have the same link-state database.

OSPF Terminology


• OSPF Area

A set of IP subnets within an autonomous system. An OSPF area limits the flooding of link-state updates on an OSPF router to just those changes within its area. If more than one OSPF area is configured for an autonomous system, one of the areas is designated the backbone area (Area 0). All non-backbone areas within an autonomous system have a physical connection to the backbone area.

• OSPF Area Type

The OSPF area’s support for importing autonomous system (AS) external link-state advertisements (LSAs). An OSPF area can be configured in one of five ways, based on what routes external to the area are advertised into the area by the Area Border Routers (ABRs) and the Autonomous System Border Routers (ASBRs) within the area.

Normal Area: All OSPF routes, whether from outside the area or outside the AS, are advertised into this area. The backbone area is always a normal area.

Stub Area: No routes that are external to the AS are advertised into this area. Practically, this means that all packets to addresses outside the AS are sent to the nearest ABR for routing by the backbone area.

Totally Stub Area: No routes external to this area or the AS are advertised into this area except for the default router (0.0.0.0). All packets destined for addresses outside this area or the AS go to the nearest ABR for routing by the backbone.

Not-So-Stubby Area (NSSA): No routes external to the AS are advertised into this area except for the external routes advertised by an ASBR within this area. All packets destined for addresses outside the AS go to the nearest ABR, unless the addresses can be reached by an ASBR within this area.

Totally NSSA: No routes external to this area or the AS are advertised into this area except for the default router (0.0.0.0) and the external routes advertised by an ASBR within this area. All packets destined for addresses outside this area or the AS go to the nearest ABR, unless the addresses are AS external addresses that can be reached by an ASBR within this area.


• OSPF Interface

A link between an OSPF router and a network. The state of an OSPF interface is a description of the interface and its relationship to its neighboring routers. One or more router adjacencies may develop over an interface.

• OSPF Neighbors

OSPF routers that share a common network segment become neighbors on that segment. Neighbors are elected via the Hello protocol. Two-way communication exists between each pair of neighbors.

• OSPF Neighbor Relationship

See OSPF Adjacency in this list.

• OSPF Network

Interconnected routing devices running OSPF services. An OSPF network can exist for four network types: broadcast, NBMA (non-broadcast), point-to-point, and point-to-multipoint.

• OSPF Router

A routing device running an OSPF service.

• OSPF Service

An OSPF process: an instance of the OSPF routing protocol running in memory.

• OSPF Virtual Link

A tunnel that connects an OSPF area to the backbone area (Area 0) for an autonomous system. OSPF virtual links are common when merging OSPF networks from two companies.

• VLAN

Virtual Local Area Network. A network of computers that behave as if they are connected to the same wire even though they may actually be physically located on different network segments of a LAN. VLANs are configured through software rather than hardware, which makes them extremely flexible.

• VPN

Virtual Private Network. A private-access network over public connections.

OSPF Terminology



B

OSPF MIBs Polled and

SNMP Traps Processed

InCharge Network Protocol Manager for OSPF supports SNMP V1 and SNMP V2C for the OSPF MIB objects defined in RFC 1253 and the OSPF traps defined in RFC 1850. Network Protocol Manager for OSPF does not support SNMP V3.

SNMP MIBs PolledTable 22 lists the discovery MIB objects polled by Network Protocol Manager for OSPF.

OSPF MIBs Polled and SNMP Traps Processed


Table 22: Discovery MIB Objects Polled by Network Protocol Manager for OSPF

MIB OBJECT OID DESCRIPTION MODULE

ospfRouterId .1.3.6.1.2.1.14.1.1 A 32-bit integer uniquely identifying the router in the autonomous system (AS). Typically defaults to one of the router’s IP interface addresses.

OSPF MIB

ospfAdminStat .1.3.6.1.2.1.14.1.2 Administrative status of OSPF in the router.

OSPF MIB

ospfAreaBdrRtrStatus .1.3.6.1.2.1.14.1.4 Flag to note whether this router is an Area Border Router (ABR).

OSPF MIB

ospfASBdrRtrStatus .1.3.6.1.2.1.14.1.5 Flag to note whether this router is configured as an AS Border Router (ASBR).

OSPF MIB

ospfAreaId .1.3.6.1.2.1.14.2.1.1 A 32-bit integer uniquely identifying an OSPF area. Area ID 0.0.0.0 is used for the OSPF backbone.

OSPF MIB

ospfImportAsExtern .1.3.6.1.2.1.14.2.1.3 OSPF area’s support for importing AS external link-state advertisements (LSAs).

OSPF MIB

ospfAreaSummary .1.3.6.1.2.1.14.2.1.9 Controls the import of summary LSAs into Stub areas.

OSPF MIB

ospfIfAreaId .1.3.6.1.2.1.14.7.1.3 A 32-bit integer uniquely identifying the OSPF area to which the OSPF interface connects. Area ID 0.0.0.0 is used for the OSPF backbone.

OSPF MIB

ospfIfType .1.3.6.1.2.1.14.7.1.4 OSPF interface type. For example, broadcast LANs such as Ethernet take the value broadcast.

OSPF MIB

ospfIfAdminStat .1.3.6.1.2.1.14.7.1.5 OSPF interface’s administrative status. OSPF MIB

ospfIfTransitDelay .1.3.6.1.2.1.14.7.1.7 Estimated number of seconds to transmit a link-state update packet over this OSPF interface.

OSPF MIB

ospfIfRetransInterval .1.3.6.1.2.1.14.7.1.8 Number of seconds between LSA retransmissions, for adjacencies belonging to this OSPF interface.

OSPF MIB

ospfIfPollInterval .1.3.6.1.2.1.14.7.1.11 Interval, in seconds, between the Hello packets sent to an inactive non-broadcast multi-access neighbor.

OSPF MIB


S N M P M I B s Po l l e d

ospfIfMulticastForwarding .1.3.6.1.2.1.14.7.1.18 Specifies how multicasts are forwarded on this OSPF interface: not forwarded, forwarded as data-link multicasts, or forwarded as data-link unicasts.

OSPF MIB

ospfIfDemand .1.3.6.1.2.1.14.7.1.19 Indicates whether Demand OSPF procedures (for example, Hello suppression to full neighbors) should be performed on this interface.

OSPF MIB

ospfVirtIfTransitDelay .1.3.6.1.2.1.14.9.1.3 Estimated number of seconds to transmit a link-state update packet over this OSPF virtual interface.

OSPF MIB

ospfVirtIfRetransInterval .1.3.6.1.2.1.14.9.1.4 Number of seconds between LSA retransmissions, for adjacencies belonging to this OSPF virtual interface.

OSPF MIB

ospfVirtNbrArea .1.3.6.1.2.1.14.11.1.1 Transit area identifier. OSPF MIB

ospfVirtNbrRtrId .1.3.6.1.2.1.14.11.1.2 A 32-bit integer uniquely identifying the neighboring router in the AS.

OSPF MIB

ospfVirtNbrIpAddr .1.3.6.1.2.1.14.11.1.3 IP address that this virtual neighbor is using.

OSPF MIB

ospfNbrRtrId .1.3.6.1.2.1.14.10.1.3 A 32-bit integer uniquely identifying the neighboring router in the AS.

OSPF MIB

ospfNbmaNbrStatus .1.3.6.1.2.1.14.10.1.9 Displays the status of the entry. Setting it to invalid has the effect of making it inoperative.

OSPF MIB

ospfNbmaNbrPermanence .1.3.6.1.2.1.14.10.1.10 Displays the status of the entry; dynamic and permanent refer to how the neighbor became known.

OSPF MIB

ospfNbrHelloSuppressed .1.3.6.1.2.1.14.10.1.11 Indicates whether Hellos are being suppressed to the neighbor.

OSPF MIB

ospfVirtNbrHelloSuppressed .1.3.6.1.2.1.14.11.1.8 Indicates whether Hellos are being suppressed to the virtual neighbor.

OSPF MIB

Table 22: Discovery MIB Objects Polled by Network Protocol Manager for OSPF (Continued)




Figure 17 shows the mapping between the discovery MIB objects and the creation of the OSPF elements (objects).

Figure 17: OSPF Element Creation

Table 23 lists the instrumentation MIB objects polled by Network Protocol Manager for OSPF.

Table 23: Instrumentation MIB Objects Polled by Network Protocol Manager for OSPF


ospfIfRtrPriority .1.3.6.1.2.1.14.7.1.6 Priority of this OSPF interface. In multi-access networks, used in the Designated Router (DR) election algorithm.

OSPF MIB

ospfIfHelloInterval .1.3.6.1.2.1.14.7.1.9 Length of time, in seconds, between the Hello packets that the router sends on this OSPF interface.

OSPF MIB

ospfIfRtrDeadInterval .1.3.6.1.2.1.14.7.1.10 Number of seconds that a router’s Hello packets have not been received before its neighbors declare the router down.

OSPF MIB

ospfIfAuthKey .1.3.6.1.2.1.14.7.1.16 Authentication key used to authenticate OSPF interfaces.

OSPF MIB

ospfIfAuthType .1.3.6.1.2.1.14.7.1.20 Authentication type specified for an OSPF interface.

OSPF MIB

Discovered MIB Objects

ospfRouterId

Created OSPF Objects

OSPFArea

Created OSPF Objects

OSPFServiceOSPFAreaConfiguration

ospfIfAreaId

OSPFInterfaceospfIfAdminStatOSPFVirtualInterface

OSPFNeighborEndpointospfNbmaNbrStatus OSPFNeighborRelationshipospfVirtIfTransitDelay

OSPFVirtualNeighborEndpoint

OSPFNetwork

ospfVirtNbrIpAddr OSPFVirtualLink

ospfAreaId

(Created from AM-created IPNetwork object)


S N M P M I B s Po l l e d

ospfIfAdminStat .1.3.6.1.2.1.14.7.1.5 OSPF interface’s administrative status. The value formed on the interface is advertised as an internal route to some area.

OSPF MIB

ospfIfState .1.3.6.1.2.1.14.7.1.12 OSPF interface state. OSPF MIB

ospfIfDesignatedRouter .1.3.6.1.2.1.14.7.1.13 IP Address of the DR. OSPF MIB

ospfIfBackupDesignatedRouter .1.3.6.1.2.1.14.7.1.14 IP Address of the BDR. OSPF MIB

ospfIfEvents .1.3.6.1.2.1.14.7.1.15 Number of state changes or error events on this OSPF interface.

OSPF MIB

ospfVirtIfHelloInterval .1.3.6.1.2.1.14.9.1.5 Length of time, in seconds, between the Hello packets that the router sends on this OSPF virtual interface.

OSPF MIB

ospfVirtIfRtrDeadInterval .1.3.6.1.2.1.14.9.1.6 Number of seconds that a router’s Hello packets have not been received before its neighbors declare the router down.

OSPF MIB

ospfVirtIfState .1.3.6.1.2.1.14.9.1.7 OSPF virtual interface states. OSPF MIB

ospfVirtIfEvents .1.3.6.1.2.1.14.9.1.8 Number of state changes or error events on this virtual link.

OSPF MIB

ospfVirtIfAuthKey .1.3.6.1.2.1.14.9.1.9 If authentication type is simplePassword, the device left-adjusts and zero-fills to 8 octets.

OSPF MIB

ospfVirtIfAuthType .1.3.6.1.2.1.14.9.1.11 Authentication type specified for a virtual interface.

OSPF MIB

ospfNbrRtrId .1.3.6.1.2.1.14.10.1.3 A 32-bit integer uniquely identifying the neighboring router in the AS.

OSPF MIB

ospfNbrState .1.3.6.1.2.1.14.10.1.6 State of the relationship with this neighbor.

OSPF MIB

ospfNbrEvents .1.3.6.1.2.1.14.10.1.7 Number of times this neighbor relationship has changed state, or an error has occurred.

OSPF MIB

ospfNbrLsRetransQLen .1.3.6.1.2.1.14.10.1.8 Current length of the retransmission queue.

OSPF MIB

Table 23: Instrumentation MIB Objects Polled by Network Protocol Manager for OSPF (Continued)




SNMP Traps Processed and Devices RediscoveredNetwork Protocol Manager for OSPF supports OSPF standard SNMP V2C traps. It processes data found in the following fields of each trap message:

• Enterprise

• Generic Trap Identifier

• Specific Trap Identifier

• Variable-Bindings

• IP address of the SNMP agent

Network Protocol Manager for OSPF extracts the information from the trap messages and updates the appropriate router attributes. In addition, for any trap message received containing at least one OSPF endpoint that is not currently in the topology database, Network Protocol Manager for OSPF sends SNMP polls to the appropriate routing device to rediscover the device’s OSPF-related elements.

Table 24 lists the SNMP traps processed by Network Protocol Manager for OSPF.

ospfVirtNbrIpAddr .1.3.6.1.2.1.14.11.1.3 IP address this virtual neighbor is using.

OSPF MIB

ospfVirtNbrState .1.3.6.1.2.1.14.11.1.5 State of the virtual neighbor relationship.

OSPF MIB

ospfVirtNbrEvents .1.3.6.1.2.1.14.11.1.6 Number of times this virtual link has changed its state, or an error has occurred.

OSPF MIB

ospfVirtNbrLsRetransQLen .1.3.6.1.2.1.14.11.1.7 Current length of the retransmission queue.

OSPF MIB

Table 23: Instrumentation MIB Objects Polled by Network Protocol Manager for OSPF (Continued)



S N M P Tr a p s P r o c e s s e d a n d De v i c e s Re d i s c o v e r e d

Table 24: SNMP Traps Processed by Network Protocol Manager for OSPF

TRAP NAME OID DESCRIPTION MODULE

ospfVirtIfStateChange .1.3.6.1.2.1.14.16.2.1 Signifies a change in the state of an OSPF virtual interface. This trap should be generated when the interface state regresses (for example, goes from Point-to-Point to Down) or progresses to a terminal state (that is, Point-to-Point).

OSPF MIB

ospfNbrStateChange .1.3.6.1.2.1.14.16.2.2 Signifies a change in the state of a non-virtual OSPF neighbor. This trap should be generated when the neighbor state regresses or progresses to a terminal state.

OSPF MIB

ospfVirtNbrStateChange .1.3.6.1.2.1.14.16.2.3 Signifies a change in the state of an OSPF virtual neighbor. This trap should be generated when the neighbor state regresses or progresses to a terminal state.

OSPF MIB

ospfIfConfigError .1.3.6.1.2.1.14.16.2.4 Signifies that a packet has been received on a non-virtual interface from a router whose configuration parameters conflict with this router’s configuration parameters.

OSPF MIB

ospfVirtIfConfigError .1.3.6.1.2.1.14.16.2.5 Signifies that a packet has been received on a virtual interface from a router whose configuration parameters conflict with this router’s configuration parameters.

OSPF MIB

ospfIfAuthFailure .1.3.6.1.2.1.14.16.2.6 Signifies that a packet has been received on a non-virtual interface from a router whose authentication key or authentication type conflicts with this router’s authentication key or authentication type.

OSPF MIB

ospfVirtIfAuthFailure .1.3.6.1.2.1.14.16.2.7 Signifies that a packet has been received on a virtual interface from a router whose authentication key or authentication type conflicts with this router’s authentication key or authentication type.

OSPF MIB



ospfIfRxBadPacket .1.3.6.1.2.1.14.16.2.8 Signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.

OSPF MIB

ospfVirtIfRxBadPacket .1.3.6.1.2.1.14.16.2.9 Signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.

OSPF MIB

ospfTxRetransmit .1.3.6.1.2.1.14.16.2.10 Signifies that an OSPF packet has been retransmitted on a non-virtual interface.

OSPF MIB

ospfVirtIfTxRetransmit .1.3.6.1.2.1.14.16.2.11 Signifies that an OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmitted are associated with a link-state database entry.

OSPF MIB

ospfOriginateLsa .1.3.6.1.2.1.14.16.2.12 Signifies that a new link-state advertisement (LSA) has been originated by this router. This trap should not be invoked for simple refreshes of LSAs (which happens every 30 minutes), but instead is invoked only when an LSA is originated (or re-originated) due to a topology change.

OSPF MIB

ospfMaxAgeLsa .1.3.6.1.2.1.14.16.2.13 Signifies that one of the LSAs in the router’s link-state database has aged to MaxAge.

OSPF MIB

ospfLsdbOverflow .1.3.6.1.2.1.14.16.2.14 Signifies that the number of LSAs in the router’s link-state database has exceeded ospfExtLsdbLimit.

OSPF MIB

ospfLsdbApproachingOverflow .1.3.6.1.2.1.14.16.2.15 Signifies that the number of LSAs in the router’s link-state database has exceeded ninety percent of ospfExtLsdbLimit.

OSPF MIB

ospfIfStateChange .1.3.6.1.2.1.14.16.2.16 Signifies a change in the state of a non-virtual OSPF interface. This trap should be generated when the interface state regresses or progresses to a terminal state.

OSPF MIB

Table 24: SNMP Traps Processed by Network Protocol Manager for OSPF (Continued)

TRAP NAME OID DESCRIPTION MODULE


C i s c o Tr a p s P r o c e s s e d a n d De v i c e s R e d i s c o v e r e d

Cisco Traps Processed and Devices RediscoveredNetwork Protocol Manager for OSPF also processes the following Cisco configuration traps:

• ciscoConfigManEvent .1.3.6.1.4.1.9.9.43.2 specific Trap ID: 1

• ciscoConfigManEvent .1.3.6.1.4.1.9.9.43.2.0.1 (SNMP V2C)

For every Cisco configuration trap received, Network Protocol Manager for OSPF sends SNMP polls to the appropriate routing device to rediscover the device’s OSPF-related elements.

Limitation If Traps Are Not UsedSNMP traps and/or syslog messages are recommended but not required because Network Protocol Manager for OSPF polls for OSFP interface and OSPF neighbor relationship status information. However, if neither SNMP traps nor syslog messages are received by Network Protocol Manager for OSPF, immediate asynchronous notification of status change is not available; rather, the response time is determined by the length of the SNMP polling interval (240 seconds by default). For information about SNMP polling, see Customizing OSPF Polling on page 53.

Also, if neither OSPF traps nor OSPF Mismatch Authentication Key syslog messages are received by Network Protocol Manager for OSPF, Message Digest 5 (MD5) authentication failures cannot be detected by Network Protocol Manager for OSPF.




C

OSPF Syslog Messages

Processed

InCharge Network Protocol Manager for OSPF reads syslog messages to extract information relevant to its managed OSPF network domain.

Syslog Message FormatNetwork Protocol Manager for OSPF reads and parses syslog messages having the following format:

Time [Source] [Application]: %Facility[-Subfacility]-Severity-Mnemonic: Message Text

Network Protocol Manager for OSPF also reads and parses Mismatch Authentication Key syslog messages sent by Cisco devices to detect Message Digest 5 (MD5) authentication failures.

Sample Syslog MessagesSample syslog messages processed by Network Protocol Manager for OSPF are:

Jan 29 14:11:47.566: %OSPF-5-ADJCHG: Process 100, Nbr 10.0.0.110 on XTagATM51212 from LOADING to FULL, Loading Done

OSPF Syslog Messages Processed


Sep 11 18:27:23 ins-2.smarts.com 74: 3d00h: OSPF: Rcv pkt from 172.16.2.1, Ethernet0/0 : Mismatch Authentication Key - Message Digest Key 1

The message text portion of a syslog message is sometimes quite lengthy. For example, the message text portion of an OSPF-related syslog message might look like this:

Process 100, Nbr 10.0.0.100 on Switch1.1 from FULL to DOWN, Neighbor Down: Interface down or detached Process 100, Nbr 10.0.0.110 on XTagATM51212 from FULL to DOWN, Neighbor Down: Dead timer expired Process 100, Nbr 10.0.0.110 on XTagATM51212 from LOADING to FULL, Loading Done

Syslog Messages Processed and Actions TakenTable 25 identifies which syslog messages are processed by Network Protocol Manager for OSPF and what actions are taken by Network Protocol Manager for OSPF. As indicated in the table, candidate syslog messages have one of the following Facility-Mnemonic name combinations:

• OSPF & ADJCHG

• SYS & CONFIG_I

Table 25: Syslog Messages Processed and Actions Taken

FACILITY NAME MNEMONIC NAME ACTION

OSPF ADJCHG • Extracts the OSPF configuration, change, and adjacency status information from the message and updates the appropriate router attributes.

• If the message contains at least one OSPF endpoint that is not currently in the topology database, Network Protocol Manager for OSPF sends SNMP polls to the appropriate routing device to rediscover the device’s OSPF-related elements.

SYS CONFIG_I • Does not extract any status information from the message.

• Sends SNMP polls to the appropriate routing device to rediscover the device’s OSPF-related elements.


S y s l o g M es s a g e s P r o c e s s ed an d A c t i o n s Tak e n

In addition, Network Protocol Manager for OSPF responds to Mismatch Authentication Key syslog messages for Cisco devices in the same way that it responds to syslog messages containing the OSPF & ADJCHG Facility-Mnemonic name combination.

OSPF Syslog Messages Processed



D

Polling for Analysis

Network Protocol Manager uses Simple Network Management Protocol (SNMP) polling to obtain OSPF connectivity data for its correlation analysis. The parameters for controlling SNMP polling are accessed through the Polling and Thresholds Console.

Note: Network Protocol Manager does not use Internet Control Message Protocol (ICMP) polling.

SNMP PollerNetwork Protocol Manager uses a synchronous, multi-threaded SNMP poller. By default, the SNMP poller uses ten synchronous polling threads.

The SNMP poller fully supports the SNMP V1 and V2C protocols. With SNMP V1, the correlation model uses 32-bit counters in its correlation analysis. With SNMP V2C, the correlation model uses high-capacity 64-bit counters in its correlation analysis. Using 64-bit counters is critical for performance analysis of high-speed data links because using 32-bit counters might result in wrapping (overflow) of the counters between polls.

Note: The SNMP poller for Network Protocol Manager does not support SNMP V3.



Polling for devices with multiple IP addresses is supported because the SNMP poller supports multiple IP addresses for each SNMP agent. The SNMP poller automatically switches to an alternate IP address during failures, thereby ensuring the integrity of InCharge’s correlation analysis during an outage.

Just-In-Time PollingThe SNMP poller’s MIB variable poll list is driven by a Just-In-Time polling algorithm, which ensures that only those MIB variables needed for correlation are polled. For example, if a port monitored for performance data is disabled, or goes down, the SNMP poller automatically removes the relevant MIB variables from the poll list. If the port is re-enabled, or comes back up, the variables are automatically put back onto the MIB poll list.

Request-Consolidation PollingIssuing a single SNMP GET request that requests 10 variables is more efficient than issuing 10 GET requests each requesting a single variable. The SNMP poller consolidates as many variables as possible into a single SNMP GET request. The consolidation is not restricted to variables from the same SNMP table. Polling consolidation continually adapts to changes in the MIB variable poll list.

Upon encountering a non-fatal error during polling consolidation, the SNMP poller responds differently to an SNMP V1 agent than to an SNMP V2C for the following reason: Where an SNMP V1 agent stops processing a request upon encountering an error, an SNMP V2C agent continues processing a request upon encountering an error. An SNMP V2C agent handles errors on a per-OID basis.


R eq u e s t - C o n so l i d a t i o n Po l l i n g

If a non-fatal error is encountered by an SNMP V1 agent during a GET request seeking multiple variables, the SNMP poller suspends the polling of the affected variable because continuing to poll that variable would require the resending of the remainder of the request after receiving the error, which would probably impact the performance of the SNMP V1 agent; the SNMP poller continues to poll the unaffected variables. (An example of an affected variable is one that has become unavailable due to a configuration change.) This behavior enables the SNMP poller to operate efficiently with an SNMP V1 agent during unexpected changes to a device’s configuration.

In contrast, if a non-fatal error is encountered by an SNMP V2C agent during a GET request seeking multiple variables, the SNMP poller continues the polling of the affected variable as well as the unaffected variables.




E

Wildcards

A wildcard pattern is a series of characters that are matched against incoming character strings. You can use these patterns when you define pattern matching criteria.

Matching is done strictly from left to right, one character or basic wildcard pattern at a time. Basic wildcard patterns are defined in Table 26. Characters that are not part of match constructs match themselves. The pattern and the incoming string must match completely. For example, the pattern abcd does not match the input abcde or abc.

A compound wildcard pattern consists of one or more basic wildcard patterns separated by ampersand (&) or tilde (~) characters. A compound wildcard pattern is matched by attempting to match each of its component basic wildcard patterns against the entire input string. For compound wildcard patterns, see Table 27.

If the first character of a compound wildcard pattern is an ampersand (&) or tilde (~) character, the compound is interpreted as if an asterisk (*) appeared at the beginning of the pattern. For example, the pattern ~*[0-9]* matches any string not containing any digits. A trailing instance of an ampersand character (&) can only match the empty string. A trailing instance of a tilde character (~) can be read as “except for the empty string.”

Note: Spaces are interpreted as characters and are subject to matching even if they are adjacent to operators like "&".

Wildcards


Table 26: Basic Wildcard Patterns

CHARACTER DESCRIPTION

Note: Spaces specified before or after wildcard operators are interpreted as characters and are subject to matching.

? Matches any single character. For example, server?.smarts.com matches server3.smarts.com and serverB.smarts.com, but not server10.smarts.com.

* Matches an arbitrary string of characters. The string can be empty. For example, server*.smarts.com matches server-ny.smarts.com and server.smarts.com (an empty match).

[set] Matches any single character that appears within [set]; or, if the first character of [set] is (^), any single character that is not in the set. A hyphen (-) within [set] indicates a range, so that [a-d] is equivalent to [abcd]. The character before the hyphen (-) must precede the character after it or the range will be empty. The character (^) in any position except the first, or a hyphen (-) at the first or last position, has no special meaning. Example, server[789-].smarts.com matches server7.smarts.com through server9.smarts.com, but not server6.smarts.com. It also matches server-.smarts.com.Example: server[^12].smarts.com does not match server1.smarts.com or server2.smarts.com, but will match server8.smarts.com.

<n1-n2> Matches numbers in a given range. Both n1 and n2 must be strings of digits, which represent non-negative integer values. The matching characters are a non-empty string of digits whose value, as a non-negative integer, is greater than or equal to n1 and less than or equal to n2. If either end of the range is omitted, no limitation is placed on the accepted number.For example, 98.49.<1-100>.10 matches a range of IP addresses from 98.49.1.10 through 98.49.100.10. Example of an omitted high end of the range: <50-> matches any string of digits with a value greater than or equal to 50. Example of an omitted low end of the range: <-150> matches any value between zero and 150.A more subtle example: The pattern <1-10>* matches 1, 2, up through 10, with * matching no characters. Similarly, it matches strings like 9x, with * matching the trailing x. However, it does not match 11, because <1-10> always extracts the longest possible string of digits (11) and then matches only if the number it represents is in range.


Special characters for compound wildcard patterns are summarized below.

| Matches alternatives. For example,”ab|bc|cd” without spaces matches exactly the three following strings: “ab”, “bc”, and “cd”. A | as the first or last character of a pattern accepts an empty string as a match.Example with spaces “ab | bc” matches the strings “ab “ and “ bc”.

\ Removes the special status, if any, of the following character. Backslash (\) has no special meaning within a set ([set]) or range (<n1-n2>) construct.

Table 27: Compound Wildcard Patterns


& “And Also” for a compound wildcard pattern. If a component basic wildcard pattern is preceded by & (or is the first basic wildcard pattern in the compound wildcard pattern), it must successfully match. Example: *NY*&*Router* matches all strings which contain NY and also contain Router. Example: <1-100>&*[02468] matches even numbers between 1 and 100 inclusive. The <1-100> component only passes numbers in the correct range and the *[02468] component only passes numbers that end in an even digit. Example: *A*|*B*&*C* matches strings that contain either an A or a B, and also contain a C.

~ “Except” for a compound wildcard pattern (opposite function of &).If a component basic wildcard pattern is preceded by ~, it must not match. Example: 10.20.30.*~10.20.30.50 matches all devices on network 10.20.30 except 10.20.30.50.Example: *Router*~*Cisco*&*10.20.30.*~10.20.30.<10-20>* matches a Router, except a Cisco router, with an address on network 10.20.30, except not 10.20.30.10 through 10.20.30.20.

Table 26: Basic Wildcard Patterns (Continued)


Wildcards



Index

AABR system redundancy group

All components down 28At risk 28Reduced redundancy 28

Adding or removing a setting 62Adding or removing matching criteria 63All components down 28AnalysisMode

OSPF external setting 55OSPF SNMP setting 55

At risk 28

BBASEDIR xii

CChanging matching criteria 63Changing priority of a group 62Changing setting parameters 64Containment 49Containment dialog 49

Opening 49Copying a group 65Creating a group 65

DDisabled

OSPFInterface 19Domain Manager

Containment 49Domain Manager Administration Console 57Down

OSPFInterface 19OSPFNeighborRelationship 25OSPFVirtualInterface 20OSPFVirtualLink 26

EEdges

Table of 42

ElementAssigning to groups 61

GGlobal Console 3, 39

Containment dialog 49Domain Manager Administration Console 57Map Console view 39, 42Notification Log Console view 39Notification Properties dialog 40, 50Polling and Thresholds Console 58

GroupAssigning members 61Changing priority 62Copying 65Creating 65Definition of 53Properties 61

IInCharge IP Availability Manager 1InCharge Service Assurance Manager 1, 3Infrastructure

Containment 49InitialAdminStatus

OSPF external setting 55InitialIfState

OSPF external setting 56InitialMulticastIfState

OSPF external setting 56InitialNeighborState

OSPF external setting 56InitialNonMulticastIfState

OSPF external setting 56InitialVirtualNeighborState

OSPF external setting 57InitialVirtualState

OSPF external setting 57

MMap

Icons and indicators 42

Index


Map ConsoleIcons and indicators 42

MapsOpening 42OSPF Connectivity 42

MatchingPattern 91

Matching criteriaAdding or removing 63Changing 63

NNeedToValidateConfiguration

OSPF external setting 57Network Protocol Manager for OSPF

Polling 2Nodes

Table of 42Notification

Root causesee Root cause

Symptomaticsee Symptomatic event

Notification Log Console 3Notification Properties dialog 40, 50Notifications

Display of 3Problem 6Symptomatic 6Types 3

Notifications Properties dialogOpening 40

OOpening a Containment dialog 49Opening a Map 42Opening a Notification Properties dialog 40Operator

Wildcard 92OSPF area 10OSPF area configuration 11OSPF external setting 55

AnalysisMode 55InitialAdminStatus 55InitialIfState 56InitialMulticastIfState 56InitialNeighborState 56InitialNonMulticastIfState 56InitialVirtualNeighborState 57

InitialVirtualState 57NeedToValidateConfiguration 57

OSPF interface 16OSPF neighbor endpoint 21OSPF neighbor relationship 24OSPF network 14OSPF service 12OSPF SNMP setting 54

AnalysisMode 55PollingInterval 55Retries 55Timeout 55

OSPF virtual interface 20OSPF virtual link 25OSPF virtual neighbor 24OSPFInterface

AreaIDMismatchSymptom 9, 19AreaTypeMismatchSymptom 9, 19AuthKeyMismatchSymptom 9, 19AuthTypeMismatchSymptom 9, 19Disabled 8, 19DisabledAdminSymptom 9, 19Down 8, 19DuplicateRouterIDSymptom 9, 19HelloOrDeadIntervalMismatchSymptom 10, 20MTUMismatchSymptom 10, 20NetmaskMismatchSymptom 10, 20

OSPFNeighborEndpointUnknownNbmaNeighbor 8, 23UnknownNbmaNeighborSymptom 10, 23

OSPFNeighborRelationshipDown 8, 25NeighborStateAlarm 10, 25

OSPFNetworkAreaIDMismatch 7, 15AreaTypeMismatch 7, 15AuthKeyMismatch 7, 15AuthTypeMismatch 7, 15DRElectionFailure 9, 16DuplicateRouterID 7, 15HelloOrDeadIntervalMismatch 7, 15MTUMismatch 7, 15NetmaskMismatch 7, 15RouterPrioritiesZero 9, 16

OSPFServiceABRNotInBackbone 9, 13

OSPFVirtualInterfaceAreaIDMismatchSymptom 9, 21AreaTypeMismatchSymptom 9, 21AuthKeyMismatchSymptom 9, 21


AuthTypeMismatchSymptom 9, 21Down 8, 20DuplicateRouterIDSymptom 9, 21HelloOrDeadIntervalMismatchSymptom 10, 21MTUMismatchSymptom 10, 21NetmaskMismatchSymptom 10, 21

OSPFVirtualLinkDown 8, 26NeighborStateAlarm 10, 26

OSPFVirtualNeighborEndpointUnknownVirtualNeighbor 8, 24UnknownVirtualNeighborSymptom 10, 24

PPattern 91Pattern matching 91Polling

Groups 54Settings 54SNMP 2, 53, 88

Polling and Thresholds Console 57Layout 58Polling tab 58Thresholds tab 58Toolbar buttons 59

Polling tab 58PollingInterval

OSPF SNMP setting 55Priority

Changing 62Processing

SNMP traps 2Syslog messages 2

RRemoving or adding a setting 62Removing or adding matching criteria 63Restoring default values of a setting 64Retries

OSPF SNMP setting 55Root cause 3

OSPFInterfaceDisabled 8, 19Down 8, 19

OSPFNeighborEndpointUnknownNbmaNeighbor 8, 23

OSPFNeighborRelationshipDown 8, 25

OSPFNetwork

AreaIDMismatch 7, 15AreaTypeMismatch 7, 15AuthKeyMismatch 7, 15AuthTypeMismatch 7, 15DuplicateRouterID 7, 15HelloOrDeadIntervalMismatch 7, 15MTUMismatch 7, 15NetmaskMismatch 7, 15

OSPFVirtualInterfaceDown 8, 20

OSPFVirtualLinkDown 8, 26

OSPFVirtualNeighborEndpointUnknownVirtualNeighbor 8, 24

Summary table 7Root-cause problem 3

see Root cause

SserverConnect.conf 58Setting

Adding or removing 62Changing parameters 64Definition of 53Restoring default values 64

SNMPCisco configuration traps

List of 81Discovery OSPF MIB objects

List of 73Instrumentation OSPF MIB objects

List of 76OSPF traps

List of 78Polling 88Polls 2, 53Traps 2

SNMP trap message processing 2Symptomatic event 3

ABR system redundancy groupAll components down 28At risk 28Reduced redundancy 28

OSPFInterfaceAreaIDMismatchSymptom 9, 19AreaTypeMismatchSymptom 9, 19AuthKeyMismatchSymptom 9, 19AuthTypeMismatchSymptom 9, 19DisabledAdminSymptom 9, 19

Index


DuplicateRouterIDSymptom 9, 19HelloOrDeadIntervalMismatchSymptom 10, 20MTUMismatchSymptom 10, 20NetmaskMismatchSymptom 10, 20

OSPFNeighborEndpointUnknownNbmaNeighborSymptom 10, 23

OSPFNeighborRelationshipNeighborStateAlarm 10, 25

OSPFNetworkDRElectionFailure 9, 16RouterPrioritiesZero 9, 16

OSPFServiceABRNotInBackbone 9, 13

OSPFVirtualInterfaceAreaIDMismatchSymptom 9, 21AreaTypeMismatchSymptom 9, 21AuthKeyMismatchSymptom 9, 21AuthTypeMismatchSymptom 9, 21DuplicateRouterIDSymptom 9, 21HelloOrDeadIntervalMismatchSymptom 10, 21MTUMismatchSymptom 10, 21NetmaskMismatchSymptom 10, 21

OSPFVirtualLinkNeighborStateAlarm 10, 26

OSPFVirtualNeighborEndpointUnknownVirtualNeighborSymptom 10, 24

Summary table 8Syslog message processing 2System redundancy group

ABR 27

TTechnical Support xiiiThresholds tab 58Timeout

OSPF SNMP setting 55Topology

Containment 49

WWildcard 91

Chart of operators 92

Date post:	13-Apr-2018
Category:	Documents
Upload:	doanduong
View:	216 times
Download:	4 times

InCharge Network Protocol Manager for OSPF User's Guide Version 1 - Cisco · Crystal Decisions...

Documents