Naming convention for MPLS, VPN, and BGP objects

To name a discovered MPLS, VPN, or BGP object,
uses the appropriate naming format in Naming formats for discovered MPLS objects through Naming formats for discovered BGP objects to assign the object a unique name.
Naming formats for discovered MPLS objects
Class
Naming format
MPLSService 1
Name:MPLS-<host device name>
Example:MPLS-qa-vplsce2
DisplayName:<empty, which means that DisplayName defaults to Name>
LSP 1
Name of an LSP object depends on LSP type:
  • TE tunnel
  • Primary TE LSP
  • Backup TE LSP
  • P2MP LSP
  • subLSP
  • LDP LSP
In some cases, name of an LSP object also depends on discovery source: SNMP or CLI.
Naming format for TE tunnel
Name:TETunnel-<tunnel name>/<source device name>_<tunnel ID>
Example:TETunnel-dev-VPLS6_t9888/dev-Vpls6_9888
DisplayName:<same as Name>
No tunnel IDs appear in the TE tunnel names for Juniper M/T devices.
Naming format for primary TE LSP
Name:LSP-<source device name>/<outgoing label of first LSP segment>/<outgoing    interface name of first LSP segment>/<outgoing interface number of first LSP       segment>-><destination device name>/<LSP identifier>/<tunnel name>_Primary
Example:LSP-dev-Vpls6/-1/IF-dev-Vpls6/1->dev-MPLSp5/192.168.5.1/dev-VPLS6_t8695_   Primary
DisplayName:<tunnel name>_Primary
Example:dev-VPLS6_t8695_Primary
The LSP in this example is an SNMP-discovered LSP that is built on Cisco IOS devices. For LSPs that are built on Cisco IOX devices, CLI discovery is sometimes used to discover path-protection LSPs. For a TE LSP that is discovered in this manner, both Name and DisplayName are set to the CLI output.
LSP 1(continued)
Naming format for backup TE LSP
Name:LSP-<source device name>/<outgoing label of first LSP segment>/<outgoing    interface name of first LSP segment>/<outgoing interface number of first LSP       segment>-><destination device name>/<LSP identifier>/         <tunnel name>_Secondary
Example:LSP-dev-Vpls6/-1/IF-dev-Vpls6/1->dev-MPLSp5/192.168.5.1/dev-VPLS6_t9888_   Secondary
DisplayName:<tunnel name>_Secondary
Example:dev-VPLS6_t9888_Secondary
Naming format for P2MP LSP
Name:P2MP-<discovered P2MP LSP name>
Example:P2MP-192.168.10.1:6800:mvpn:NGMVPN_LSP2
DisplayName:<empty, which means that DisplayName defaults to Name>
Naming format for subLSP
Name: subLSP-<discovered subLSP name>
Example:subLSP-192.168.18.1:192.168.10.1:6800:mvpn:NGMVPN_LSP2
DisplayName:<empty, which means that DisplayName defaults to Name>
Naming format for LDP LSP
Name:LSP-<source device name>-><destination device name>/-<first hop (source device)    outgoing label>-<next hop outgoing label>- ... -<last hop outgoing label (3 = POP)>
Example:LSP-qa-vpls4->qa-vpls2/-33-172-28-37-3
DisplayName:<empty, which means that DisplayName defaults to Name>
LSPHop 1
Name of an LSPHop object depends on type of LSP to which LSP hop belongs:
  • Primary TE LSP
  • Backup TE LSP
  • subLSP
  • LDP LSP
In some cases, name of an LSPHop object also depends on discovery source: SNMP or CLI.
Naming format for LSPHop that belongs to primary TE LSP
Name:LSPHop-<source device name>/<outgoing interface name>/<outgoing interface    number>-><destination device name>/<LSP identifier>/<tunnel name>_Primary
Example:LSPHop-dev-Vpls6/IF-dev-Vpls6/1->dev-MPLSp9/192.168.5.1/dev-VPLS6_t8695_Primary
DisplayName:<same as Name>
Naming format for LSPHop that belongs to backup TE LSP
Name:LSPHop-<source device name>/<outgoing interface name>/<outgoing interface    number>-><destination device name>/<LSP identifier>/<tunnel name>_Secondary
Example:LSPHop-dev-Vpls6/IF-dev-Vpls6/1->dev-MPLSp9/192.168.5.1/dev-VPLS6_t9888    _Secondary
DisplayName:<same as Name>
Naming format for LSPHop that belongs to subLSP
Name:LSPHop-<source device name>/<IP of outgoing interface>-><destination device    name>/<IP of incoming interface>
Example:LSPHop-dev-Vpls0/172.18.10.18->dev-MPLSp8/172.18.10.17
DisplayName:<same as Name>
LSPHop 1(continued)
Naming format for LSPHop that belongs to LDP LSP
For an LDP-LSP-related LSP hop that has a label = 3, the outgoing label value is replaced with POP. POP stands for penultimate hop pop.
Outgoing label not equal to 3:
Name:LSPHop-<source device name>_<hop outgoing label>-><destination device name>
Example:LSPHop-qa-vpls4_33->qa-vpls1
DisplayName:<same as Name>
Outgoing label equal to 3:
Name:LSPHop-<source device name>_POP-><destination device name>
Example:LSPHop-qa-mplsp1_POP->qa-vpls2
DisplayName:<same as Name>
LdpProtocolEndpoint (non-targeted)
Name of an LdpProtocolEndpoint object depends on discovery source, SNMP or CLI. And for SNMP, name also depends on MIB source: Cisco or Juniper.
Naming format for LdpProtocolEndpoint based on Cisco MIB source
Name:LDP-<LDP endpoint IP address>.0.0.<MIB index>
Example:LDP-10.9.7.249.0.0.3232236545
DisplayName:<same as Name>
Naming format for LdpProtocolEndpoint based on Juniper MIB source (Juniper M/T)
Name:LDP-<LDP endpoint IP address>.0.0.1.<peer LDP endpoint IP address>.0.0
Example:LDP-192.168.0.1.0.0.1.192.168.10.1.0.0
DisplayName:<same as Name>
Naming format for LdpProtocolEndpoint based on CLI source (Juniper ERX)
Name:LDP-<LDP endpoint IP address>-><peer LDP endpoint IP address>
Example:LDP-193.212.68.161->193.212.68.74
DisplayName:<same as Name>
LdpAdjacency (non-targeted)
Name:LDP-ADJ-<Endpoint1 LdpProtocolEndpoint IP address>-<Endpoint2    LdpProtocolEndpoint IP address>
Example:LDP-ADJ-192.168.15.1-192.168.16.1
DisplayName:<same as Name>
Endpoint1 has the smaller IP address of the two endpoints.
RsvpProtocolEndpoint
Name:RSVP-Point-<source RSVP endpoint IP address>-><destination RSVP endpoint    IP address>/<tunnel identifier>/Source|Destination
Example:RSVP-Point-192.168.17.1->192.168.16.1/1209/Destination
DisplayName:<same as Name>
RsvpSession
Name:RSVP-Session-<source RsvpProtocolEndpoint IP address>-><destination    RsvpProtocolEndpoint IP address>/<tunnel identifier>
Example:RSVP-Session-192.168.17.1->192.168.16.1/1209
DisplayName:<same as Name>
1**This object type is imported by the
Global Manager
.
Naming formats for discovered L2VPN objects
Class
Naming format
VPN 1
Name of a Layer 2 VPN object depends on VPN type:
  • LDP-signaled VPWS
  • LDP-signaled VPLS
  • BGP-signaled VPWS
  • BGP-signaled VPLS
Naming format for LDP-signaled VPWS
Name:VPN-L2-<name of pseudowire that belongs to this VPWS>
Example:VPN-L2-PW-192.168.15.1-192.168.16.1-526
DisplayName:<same as Name>
Naming format for LDP-signaled VPLS
Name:VPLS-<VC ID of this VPLS>
Example:VPLS-388
DisplayName:<same as Name>
VC ID for an LDP-signaled VPLS is also known as the VPLS ID, and is the same value on all PEs that participate in the VPLS.
Naming format for BGP-signaled VPWS
Name:VPN-L2-<name of pseudowire that belongs to this VPWS>
Example:VPN-L2-PW-10.9.130.121-10.9.130.122-800008-800001
DisplayName:VPN-<route target index of this VPWS>
Example:VPN-4323:3333
Naming format for BGP-signaled VPLS
Name:VPLS-<route target index of this VPLS>
Example:VPLS-1:1
DisplayName:<same as Name>
Route target index for a BGP-signaled VPLS is also known as the VPLS ID, and is the same value on all PEs that participate in the VPLS.
VRF 1
VRF
Name:VRF-<VRF name>/<host device name>
Example:VRF-AQUA/dev-Vpls7
DisplayName:<same as Name>
RouteTarget
Name:RT-<route target index>
Example:RT-100:1000
DisplayName:<empty, which means that DisplayName defaults to Name>
Forwarder 1
Name:FORWARDER-<name of L2VPN to which this Forwarder belongs>/<host device name>
Four examples:FORWARDER-VPN-L2-PW-192.168.15.1-192.168.16.1-526/dev-Vpls5FORWARDER-VPLS-388/dev-MPLSp5FORWARDER-VPN-4323:3333/10.9.130.121FORWARDER-VPLS-1:1/Mimic-M7i
DisplayName:<empty, which means that DisplayName defaults to Name>
ForwarderEndpoint
Name of a ForwarderEndpoint object depends on type of L2VPN to which ForwarderEndpoint belongs:
  • LDP-signaled VPWS
  • LDP-signaled VPLS
  • BGP-signaled VPWS or VPLS
Naming format for ForwarderEndpoint that belongs to LDP-signaled VPWS
Name:FORWARDEREP-<VC ID of pseudowire terminated by this ForwarderEndpoint>-<peer    ForwarderEndpoint IP address>/<host device name>
Example:FORWARDEREP-106-192.168.6.1/qa-Vpls1
DisplayName:<same as Name>
VC ID for an LDP-signaled VPWS identifies the pseudowire.
Naming format for ForwarderEndpoint that belongs to LDP-signaled VPLS
Name:FORWARDEREP-<VC ID of VPLS to which this ForwarderEndpoint belongs>-<peer    ForwarderEndpoint IP address>/<host device name>
Example:FORWARDEREP-122-192.168.2.1/qa-Vpls2
DisplayName:<same as Name>
VC ID for an LDP-signaled VPLS, also known as the VPLS ID, identifies the VPLS.
Naming format for ForwarderEndpoint that belongs to BGP-signaled VPWS or VPLS
Name:FORWARDEREP-<incoming VC ID of pseudowire terminated by this    ForwarderEndpoint>-<outgoing VC ID of pseudowire terminated by this       ForwarderEndpoint>/<host device name>
Example:FORWARDEREP-262401-262406/Mimic-M7i
DisplayName:<same as Name>
PseudoWire 1
Name of a PseudoWire object depends on type of L2VPN to which PseudoWire belongs:
  • LDP-signaled VPWS or VPLS
  • BGP-signaled VPWS or VPLS
Naming format for PseudoWire that belongs to LDP-signaled VPWS or VPLS
Name:PW-<Termination1 ForwarderEndpoint IP address>-<Termination2    ForwarderEndpoint IP address>-<VC ID of this pseudowire>
Example:PW-192.168.5.1-192.168.19.1-824
DisplayName:<Termination1 device name>-<Termination2 device name>/<VC ID of this pseudowire>
Example:dev-MPLSp5 [PE]-dev-Vpls9 [PE]/824
Termination1 endpoint has the smaller IP address of the two endpoints. Termination1 device is hosting device for Termination1 endpoint.
Naming format for PseudoWire that belongs to BGP-signaled VPWS or VPLS
Name:PW-<Termination1 ForwarderEndpoint IP address>-<Termination2    ForwarderEndpoint IP address>-<incoming VC ID of this pseudowire relative to       Termination1 ForwarderEndpoint>-<outgoing VC ID of this pseudowire relative          to Termination1 ForwarderEndpoint>
Example:PW-192.168.1.113-192.168.1.114-262401-262406
DisplayName:<Termination1 device name>-<Termination2 device name>/<incoming VC ID of this    pseudowire relative to Termination1 ForwarderEndpoint>-<outgoing VC ID of this       pseudowire relative to Termination1 ForwarderEndpoint>
Example:Mimic-M7i [PE]-Mimic-t640 [PE]/262401-262406
Termination1 endpoint has the smaller IP address of the two endpoints. Termination1 device is hosting device for Termination1 endpoint.
LdpProtocolEndpoint (targeted)
The naming format for a
targeted
LdpProtocolEndpoint object is the same as the naming format for a
non-targeted
LdpProtocolEndpoint. See
“LdpProtocolEndpoint (non-targeted)” on page 138
.
LdpAdjacency (targeted)
The naming format for a
targeted
LdpAdjacency object is the same as the naming format for a
non-targeted
LdpAdjacency. See
“LdpAdjacency (non-targeted)” on page 139
.
VLAN 1
Name:VLAN-<VLAN number>/<name of L2VPN associated with this VLAN>
Example:VLAN-600/VPLS-388
DisplayName:<empty, which means that DisplayName defaults to Name>
1**This object type is imported by the
Global Manager
.
Naming formats for discovered L3VPN objects
Class
Naming format
VPN 1 (unicast VPN)
Full-mesh topology:
Name:VPN-<route target index of this unicast L3VPN>
Example:VPN-100:1000
DisplayName:<same as Name except that “[full mesh]” or “[full mesh (only one member)]” is    appended to    the name>
Example:VPN-100:1000 [full mesh]
Hub-and-spoke topology:
Name:VPN-<route target index for spoke of this unicast L3VPN>/<route target index for    hub of this unicast L3VPN>
Example:VPN-100:1000/200:2000
DisplayName:<same as Name except that “[hub-and-spoke]” or “[hub-and-spoke] (multiple    hubs)” is appended to the name>
Example:VPN-100:1000/200:2000 [hub-and-spoke]
MulticastVPN 1
Name:mVPN-<route target index of this multicast L3VPN>
Example:mVPN-300:6800
DisplayName:<same as Name except that “[FullMesh]” is appended to the name
Example:mVPN-300:6800[FullMesh]
MulticastGroup 1
Name:MCAST-GROUP-<group IP address>/RT-<route target index of the parent multicast    L3VPN>
Example:MCAST-GROUP-239.10.10.10/RT-300:6800
DisplayName:<empty, which means that DisplayName defaults to Name>
VRF 1
The naming format for a VRF object
in an L3VPN
is the same as the naming format for a VRF object
in an L2VPN
. See
“VRF” on page 141
.
RouteTarget
The naming format for a RouteTarget object
in an L3VPN
is the same as the naming format for a RouteTarget object
in an L2VPN
. See
“RouteTarget” on page 141
.
1**This object type is imported by the
Global Manager
.
Naming formats for discovered BGP objects
Class
Naming format
AutonomousSystem
Name:AS-<autonomous-system identifier>
For example:AS-1097
DisplayName:<same as Name>
BGPService 1
Name:BGP-SVC-<host device name>
For example:BGP-SVC-dev-Vpls5
DisplayName:BGP-SVC-<host device name> [<BGP identifier> - <AS identifier>]
For example:BGP-SVC-dev-Vpls5 [192.168.15.1 - 1097]
BGPProtocolEndpoint 1
Name:BGP-EP-<host device name>/<remote interface IP address>
For example:BGP-EP-dev-Vpls5/192.168.17.1
DisplayName:BGP-EP-<host device name>/<remote interface IP address>->   <remote device name>/<local interface IP address>       [<local AS identifier>-><remote AS identifier>] [local interface device identifier]
For example:BGP-EP-dev-Vpls5/192.168.17.1->lwqvp017.lss.vmware.com/192.168.15.1    [1097->1097] [Lo0]
Stub Name:BGP-EP-<host device name>/<remote interface IP address>
For example:BGP-EP-qa-mplspe3/10.9.254.4
Stub DisplayName:BGP-EP-<host device name>/<remote interface IP address>    [<local AS identifier>-><remote AS identifier>]
For example:BGP-EP-qa-mplspe3/10.9.254.4 [100->100]
BGPSession 1
Name:BGP-ADJ-<host device name>/<remote interface IP address><-->   <remote device name>/<local interface IP address>
For example:
BGP-ADJ-dev-Vpls5/192.168.17.1<-->lwqvp017.lss.vmware.com/192.168.15.1
DisplayName:BGP-ADJ-<host device name>/<remote interface IP address><-->   <remote device name>/<local interface IP address>       [<local AS identifier><--><remote AS identifier>]
For example:BGP-ADJ-dev-Vpls5/192.168.17.1<-->lwqvp017.lss.vmware.com/192.168.15.1 [1097<-->1097]
Stub Name:BGP-ADJ-<host device name>-><remote interface IP address>
For example:BGP-ADJ-qa-vpls1->172.23.21.2
Stub DisplayName:BGP-ADJ-<host device name>-><remote interface IP address>    [<local AS identifier>-><remote AS identifier>]
For example:BGP-ADJ-qa-vpls1->172.23.21.2 [1097->1097]
1**This object type is imported by the
Global Manager
.