Table 114 Bgp-Ad Cli Command Tree; Table 115 Bgp Parameters And Sdp Bindings In Use Example Display: Pe134 - Nokia 7302 Manual

FD 100/320Gbps NT and FX NT IHub Services Guide
*A:PE6>config>service>vpls# info
----------------------------------------------
bgp
exit
bgp-ad
exit
sap 1/1/20:600.* create
exit
no shutdown
----------------------------------------------
*A:PE6>config>service>vpls#
In many cases, VPLS connectivity is based on a pseudowire mesh. To reduce the
configuration requirement, the BGP values can be automatically generated using the
VPLS-ID and the MPLS router-ID. By default, the lower six bytes of the VPLS-ID are
used to generate the RD and the RT values. The VSI-ID value is generated from the
MPLS router-ID. All of these parameters are configurable and can be coded to suit
requirements and build different topologies. The BGP-AD CLI Command Tree is
described in Table 114.
Table 114
A helpful command displays the service information, the BGP parameters and the
SDP bindings in use as demonstrated in Tables
process is completed successfully each endpoint will have an entry for the service.
Table 115
(1 of 2)
Issue: 13
route-distinguisher 65535:100
route-target export target:65535:100 import target:65535:100
pw-template-bind 1
vpls-id 65535:100
vsi-id
prefix 1.1.1.6
no shutdown
BGP-AD CLI Command Tree
leg:isadmin>conf>service>vpls>bgp-ad#
[no] shutdown
vpls-id
vsi-id
BGP parameters and SDP bindings in use example display:
PE134
PE134># show service l2-route-table
Services: L2 Route Information — Summary Service
Svc Id
100
No. of L2 Route Entries: 1
3HH-11985-AAAA-TQZZA
- Administratively enable/disable BGP auto-discovery
- Configure VPLS-ID
+ Configure VSI-ID
L2-Routes (RD-Prefix)
Sdp Bind Id
65535:100-1.1.1.6
17406:4294967295
Virtual Private LAN Service
115 and 116. When the discovery
Next Hop
1.1.1.6
Origin
BGP-L2
235