Smarts NPM/IP: BGP Interfaces that are unmanaged in Smarts IP still appear as IsManaged=True in NPM/BGP domain, while OSPF interfaces unmanaged in Smarts IP appear as IsManaged=False in OSPF domain
search cancel

Smarts NPM/IP: BGP Interfaces that are unmanaged in Smarts IP still appear as IsManaged=True in NPM/BGP domain, while OSPF interfaces unmanaged in Smarts IP appear as IsManaged=False in OSPF domain

book

Article ID: 303740

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:


This article explains the difference in behavior for unmanaged interfaces affecting Border Gateway Protocol (BGP) and Open Shortest Path First (OSPF) in a Smarts Network Protocol Manager (Smarts NPM) environment, and how to get the Smarts NPM/BGP domain to match the managed state setting in Smarts IP.

The following conditions, events or system behaviors may be observed with this issue:
  • Difference in behavior observed between Smarts NPM domains for BGP and OSPF and interfaces that are unmanaged in Smarts IP.
  • Smarts NPM/BGP unmanaged state does not match the setting in Smarts IP
  • When an interface is unmanaged in Smarts IP and a rediscovery is run in the Smarts NPM/BGP domain, the interface still shows as isManaged=True in the Smarts NPM/BGP domain.
  • When an interface is unmanaged in Smarts IP and a rediscovery is run in the Smarts NPM/OSPF domain, the interface shows as isManaged=False in the Smarts NPM/OSPF domain.


Environment

VMware Smart Assurance - SMARTS

Cause

For the BGP domain to match the Smarts IP setting, the BGP configuration files must be specifically configured as described in the following Resolution.

Resolution

To ensure that the BGP interface status matches the unmanaged interface setting in the Smarts IP Availability Manager, do the following:

  1. Using sm_edit, add the following line in both the dxa-am.conf (<smarts>/conf/bgp/dxa-am.conf) and theĀ  dxa-am-v4v6.conf (<smarts>/conf/bgp/dxa-am-v4v6.conf) configuration files, under the "Interface" class.
oper getManagedState setManagedState
  1. Comment/disable the "peek IsManaged TRUE" line by placing the hash character (#) in the beginning of the line as follows:
#peek IsManaged TRUE
  1. Save and close the configuration file.
Example
The following shows an example Interface class with both of the above changes made:

proxy Interface
in TopologyCollection ConsistsOf BGP-Interface
#in UnitaryComputerSystem ComposedOf
#peek IsManaged TRUE
attr DisplayName
attr Description
attr DeviceID
attr InterfaceNumber
attr InterfaceKey
attr MaxTransferUnit
attr SystemName DeviceName
attr Mode
rel Underlying
rel Peer
oper getManagedState setManagedState