Table of Contents
Advertisement
Virtual Private LAN Service
5.14 Configuring BGP Auto-Discovery with
BGP-AD configuration can be made non-persistently by configuring the MIB object
svsConfigPersistentControl to false using SNMP set along with the VPLS service
creation. This configuration does not get saved when admin save is issued. This is a
feature supported for DPoE. Info command will display this attribute as no-persist
keyword. The VPLS service created as no-persist cannot be modified to persist. This
attribute also cannot be configured via CLI and there is no equivalent command
available to set it. Similarly, pwConfigPersistentControl can be set to false via SNMP,
for the same purpose by DPoE.
For example, vpls 1002 created with svcConfigPersistentControl to false and
BGP-AD configuration looks as follows:
PERs6>configure>service# vpls 1002
PERs6>configure>service>vpls# info
----------------------------------------------
----------------------------------------------
For example, pw-template 6 created with pwConfigPersistentControl to false and
BGP-AD configuration looks like the following:
PERs6>configure>service# pw-template 6
PERs6>configure>service>pw-template# info
----------------------------------------------
----------------------------------------------
242
Non-Persistency
bgp
route-distinguisher 65500:800
route-target export target:65500:800 import target:65500:800
pw-template-bind 6
exit
bgp-aid
vpls-id 25.25.25.25:25
vsi-id
prefix 21.0.0.1
exit
no shutdown
exit
bgp-vpls
max-ve-id 50
ve-name 20
ve-id 15
exit
no shutdown
exit
stp
shutdown
exit
no shutdown
no-persist
no-persist
3HH-11985-AAAA-TQZZA
FD 100/320Gbps NT and FX NT IHub Services Guide
Issue: 13
- Quick Links:
- 2.3 Cli Command Syntax Symbols
Hide quick links:
Advertisement
Table of Contents
