Class CIM_BGPIPRoute
extends CIM_IPRoute

BGPIPRoute describes a BGP routing entry that connects two peer routers that are running BGP. The source and destination addresses may be either specific IP endpoints or IP subnets. Examining the BGPIPRoute class definition, note that its superclass IPRoute is deprecated. Unfortunately, IPRoute cannot be removed from the object hierarchy without a major Schema release. When/if this occurs, the IPRoute superclass will be removed, and BGPIPRoute will subclass from CIM_NextHopRouting directly.

Table of Contents
Hierarchy
Direct Known Subclasses
Class Qualifiers
Class Properties
Class Methods

Class Hierarchy

CIM_ManagedElement
   |
   +--CIM_ManagedSystemElement
   |
   +--CIM_LogicalElement
   |
   +--CIM_NextHopRouting
   |
   +--CIM_IPRoute
   |
   +--CIM_BGPIPRoute

Direct Known Subclasses

Class Qualifiers

NameData TypeValue
DescriptionstringBGPIPRoute describes a BGP routing entry that connects two peer routers that are running BGP. The source and destination addresses may be either specific IP endpoints or IP subnets. Examining the BGPIPRoute class definition, note that its superclass IPRoute is deprecated. Unfortunately, IPRoute cannot be removed from the object hierarchy without a major Schema release. When/if this occurs, the IPRoute superclass will be removed, and BGPIPRoute will subclass from CIM_NextHopRouting directly.
UMLPackagePathstringCIM::Network::BGP
Versionstring2.6.0

Class Properties

Local Class Properties

NameData TypeDefault ValueQualifiers
NameData TypeValue
IsBackDoorRouteboolean
DescriptionstringUsually, the administrative distance is used to determine which route gets installed in the routing table. Using this scheme, routes learned via EBGP will win over routes learned via an IGP. If this is not desired, then this assigns the administrative distance of this route to be equal to that of a local route, which means that the same route learned by an IGP will have a lower administrative distance and be installed instead.
UsesLoopbackPeeringboolean
DescriptionstringLoopback interfaces are often used by IBGP peers, because they eliminate a dependency that would otherwise occur if the actual IP address of a physical interface was used to configure BGP. The loopback interface instead instructs the router to use any available interface.

Inherited Properties

NameData TypeClass Origin
AddressTypeuint16CIM_IPRoute
CaptionstringCIM_ManagedElement
CommunicationStatusuint16CIM_ManagedSystemElement
CreationClassNamestringCIM_IPRoute
DescriptionstringCIM_ManagedElement
DestinationAddressstringCIM_IPRoute
DestinationMaskstringCIM_IPRoute
DetailedStatusuint16CIM_ManagedSystemElement
ElementNamestringCIM_ManagedElement
Generationuint64CIM_ManagedElement
HealthStateuint16CIM_ManagedSystemElement
InstallDatedatetimeCIM_ManagedSystemElement
InstanceIDstringCIM_ManagedElement
IPDestinationAddressstringCIM_IPRoute
IPDestinationMaskstringCIM_IPRoute
IsStaticbooleanCIM_NextHopRouting
NamestringCIM_ManagedSystemElement
NextHopstringCIM_NextHopRouting
OperatingStatusuint16CIM_ManagedSystemElement
PrimaryStatusuint16CIM_ManagedSystemElement
ServiceCreationClassNamestringCIM_IPRoute
ServiceNamestringCIM_IPRoute
StatusstringCIM_ManagedSystemElement
SystemCreationClassNamestringCIM_IPRoute
SystemNamestringCIM_IPRoute
OperationalStatusuint16[]CIM_ManagedSystemElement
StatusDescriptionsstring[]CIM_ManagedSystemElement

Class Methods