To name a discovered BGP object, Network Protocol Manager for BGP uses the appropriate naming format in Naming formats for discovered BGP objects to assign the object a unique name. It then populates the object’s Name and DisplayName attributes with that name.
| Class |
Naming format |
|---|---|
| 1**This object type is not imported by the Global Manager. |
|
| AutonomousSystem |
Name:AS-<autonomous-system identifier> For example:AS-100 |
| DisplayName:<same as Name> |
|
| BGPService |
Name:BGP-SVC-<host device name> For example:BGP-SVC-qa-gw3 |
| DisplayName:BGP-SVC-<host device name> [<BGP identifier> - <AS identifier>] For example:BGP-SVC-qa-gw3 [192.168.101.1 - 100] |
|
| BGPProtocolEndpoint 1 |
Name:BGP-EP-<host device name>/<remote interface IP address> For example:BGP-EP-qa-vpls1/172.23.21.2 Stub Name:BGP-EP-<host device name>/<remote interface IP address> For example:BGP-EP-qa-mplspe3/10.9.254.4 |
| 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-qa-vpls1/172.22.21.2->qa-vpls2/172.22.21.1 [1097->1097] [Fa1/2] 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 |
Name:BGP-ADJ-<host device name>/<remote interface IP address><--> <remote device name>/<local interface IP address> For example: BGP-ADJ-qa-gw3/10.9.254.4<-->qa-gw4/10.9.254.3 Stub Name:BGP-ADJ-<host device name>-><remote interface IP address> For example:BGP-ADJ-qa-vpls1->172.23.21.2 |
| 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-qa-gw3/10.9.254.4<-->qa-gw4/10.9.254.3 [100<-->100] 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] |
|
In an overlapping IP environment, Network Protocol Manager for BGP observes the following rule to ensure that it creates the correct BGP sessions in its modeled topology:
For a BGP endpoint layered over a tagged IP that has a tag value of xxx, Network Protocol Manager for BGP will create a BGP session to a neighboring BGP endpoint if and only if that endpoint is also layered over a tagged IP that has a tag value of xxx.
The following BGP session confirms the observance of this rule. The tag value in the name of the BGP session is highlighted in bold.
BGP-ADJ-qa-vpls4/192.168.98.1/64577:11000<--> qa-vpls2/192.168.8.1/64577:11000 [1097<-->1097]
Here are the BGP endpoints for the BGP session:
BGP-EP-qa-vpls4/192.168.98.1/64577:11000-> qa-vpls2/192.168.8.1/64577:11000 [1097<-->1097] [Lo0] BGP-EP-qa-vpls2/192.168.8.1/64577:11000-> qa-vpls4/192.168.98.1/64577:11000 [1097<-->1097] [Lo98]
