Utilizzare la CLI di per verificare dal router del servizio di livello 0 che venga attivata una connessione BGP a un router adiacente.
Procedura
- Accedere alla CLI di NSX Manager.
- In NSX Edge, eseguire il comando get logical-routers per trovare il numero VRF del router di servizio di livello 0.
nsx-edge-1> get logical-routers
Logical Router
UUID : 736a80e3-23f6-5a2d-81d6-bbefb2786666
vrf : 0
type : TUNNEL
Logical Router
UUID : 421a2d0d-f423-46f1-93a1-2f9e366176c8
vrf : 5
type : SERVICE_ROUTER_TIER0
Logical Router
UUID : f3ce9d7d-7123-47d6-aba6-45cf1388ca7b
vrf : 6
type : DISTRIBUTED_ROUTER
Logical Router
UUID : c8e64eff-02b2-4462-94ff-89f3788f1a61
vrf : 7
type : SERVICE_ROUTER_TIER1
Logical Router
UUID : fb6c3f1f-599f-4421-af8a-99692dff3dd4
vrf : 8
type : DISTRIBUTED_ROUTER
- Eseguire il comando vrf <number> per immettere il contesto del router di servizio di livello 0.
nsx-edge-1> vrf 5
nsx-edge1(tier0_sr)>
- Verificare che lo stato di BGP sia Stabilito, attivo.
get bgp neighbor
BGP neighbor: 192.168.100.254 Remote AS: 64511
BGP state: Established, up
Hold Time: 180s Keepalive Interval: 60s
Capabilities:
Route Refresh: advertised and received
Address Family: IPv4 Unicast:advertised and received
Graceful Restart: none
Restart Remaining Time: 0
Messages: 28 received, 31 sent
Minimum time between advertisements: 30s (default)
For Address Family IPv4 Unicast:advertised and received
Route Refresh: 0 received, 0 sent
Prefixes: 2 received, 2 sent, 2 advertised
1 Connections established, 2 dropped
Local host: 192.168.100.3, Local port: 179
Remote host: 192.168.100.254, Remote port: 33044