Use the show serviceengine service_engine_IP_address bgp command to verify the configuration.
The following is an example of the show output:
[admin:controller]: > show serviceengine 10.140.1.13 bgp +---------------------+--------------------------------------------------+ | Field | Value | +---------------------+--------------------------------------------------+ | se_uuid | 10-140-1-13:se-10.140.1.13-avitag-1 | | proc_id | C0_L4 | | name | global | | local_as | 65000 | | vrf | 1 | | active | 1 | | peer_bmp | 2147483648 | | peers[1] | | | remote_as | 1 | | peer_ip | 2006::54 | | peer_id | 1 | | active | 1 | | md5_secret | **** | | bfd | True | | advertise_snat_ip | True | | bgp_state | Established, | | | | | advertise_vip | True | +++ Output truncated +++
The bgp_state
value in Established
verifies successful BGP peering.
VIP |
BGP Peer |
Placement |
SE Infra |
SE Remarks |
---|---|---|---|---|
IPV4 Only |
IPV4 IPV6 |
Placed |
IPV6 Support enabled |
|
IPV4 Only |
IPV4 IPV6 |
Not Placed |
IPV6 Support not enabled |
|
IPV6 Only |
IPV4 IPV6 |
Placed |
IPV6 Support enabled |
|
IPV6 Only |
IPV4 IPV6 |
Not Placed |
IPV6 Support not enabled |
|
IPV4 Only |
IPV4 |
Placed |
IPV6 Support enabled |
|
IPV6 Only |
IPV6 |
Placed |
IPV6 Support enabled |
|
IPV4 IPV6 |
IPV4 IPV6 |
Placed |
IPV6 Support enabled |
|
IPV4 IPV6 |
Peer 1: IPV4 only Peer 2: IPV6 only |
Not Placed |
IPV6 Support enabled |
|
IPV4 IPV6 |
IPV4 Only |
Not Placed |
IPV6 Support enabled |
This is expected behaviour as no matching subnet for IPV6. |
IPV4 IPV6 |
IPV6 Only |
Not Placed |
IPV6 Support enabled |
This is expected behaviour as no matching subnet for IPV4. |