Smarts SAM/NPM: OSPF Area IDs display as 32-bit (IP address) integer format in the Smarts SAM OSPF connectivity Map Console and OSPF Topology Browser instead of the decimal integer configured on the router

Products

• VMware

Issue/Introduction

Symptoms:




OSPF Area IDs display as 32-bit (IP address) integer format in the Smarts SAM OSPF connectivity Map Console and OSPF Topology Browser instead of the decimal integer configured on the router

Environment

VMware Smart Assurance - SMARTS

Cause

An Area ID on a router can be defined by either an IP address (32-bit integer) or a decimal integer between 0 and 2,147,483,647. Smarts reports and displays Area IDs as 32-Bit integers, even if the Area ID is configured as the decimal integer.

For example, if an environment has an Area ID configured on a router as a decimal integer such as OSPF Area ID "601", Smarts would report this Area ID as 0.0.2.89 in Smarts SAM Map Console and OSPF Topology Browser, converting "601" to the 32-bit format as in the following:

601 = (2 x 256) + 89 = 0.0.2.89

The Area ID number is the same, but the display format is different.

Resolution

No fix is available or required for this issue. Smarts is functioning as designed.

Additional Information

The EMC Smarts NPM Manager for OSPF User Guide explains how Smarts defines Area ID as follows: 

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

Smarts retrieves the Area ID information from the OSPF Area Table in the MIB, which is defined as follows by the RFCs:

Cisco ospfAreaID
A 32-bit integer uniquely identifying an area. Area ID 0.0.0.0 is used for the OSPF backbone.
object identifier = 1.3.6.1.2.1.14.2.1.1