scope.inferMPLSPEs table

Use the scope.inferMPLSPEs table when enabling inference of inaccessible provider-edge (PE) devices by using the BGP data on the customer-edge (CE) devices. This table enables you to optionally specify which zones to process to determine which of the inferred PE devices are valid devices.

To specify which zones to process to determine which of the inferred PE devices are valid devices populate the scope.inferMPLSPEs table, using standard format scope entries, as in the scope.zones table. Use this option when you have inaccessible devices that are connected by means of BGP but which are not actually PE devices.

If the following conditions are true, then the system creates a third-party network object to model this inaccessible provider network.
  • A router is within this scope
  • The router has BGP peers outside the discovered network
  • m_InferMPLSPEsUsingBGP is on. This can also be defined using the Advanced tab on the Discovery Configuration GUI.
Table 1. scope.inferMPLSPEs database table schema

Column name

Constraints

Data type

Description

 
m_Protocol
  • PRIMARY KEY
  • NOT NULL
  • Externally defined netProtocol data type

Integer
An integer representation of the IP protocol used by the presently-defined zone:
  • 1: IPv4
  • 2: IPv4 that has been through network address translation (NAT)
  • 3: IPv6
 
m_Action
  • NOT NULL
  • Externally defined filtAction data type

Integer
Action to perform for current zone:
  • 0: Undefined
  • 1: Include
  • 2: Exclude
 
m_Zones
 NOT NULL

List of type zone

A list of varbinds (name=value) that define the present discovery zone.

Only process interfaces in the 199.220.* network

The following example shows how to instruct the system to only process interfaces in the 199.220.* network.
insert into scope.inferMPLSPEs
(
     Protocol,
     m_Action,
     m_Zones
)
values
(
     1,
     1,  
     [ { m_Subnet = "199.220.*" } ]
);