The following example illustrates the conversion of a longer and more complex configuration that was pasted into the classic CLI using the above procedure.
A:node-2>config>service# info
----------------------------------------------
system
bgp-auto-rd-range 2.2.2.2 comm-val 1 to 5000
bgp-evpn
ingress-replication-bum-label-block evpnMcast
exit
exit
sdp 21 mpls create
far-end 10.20.1.1
ldp
path-mtu 1600
keep-alive
shutdown?
exit
no shutdown
exit
customer 1 name "1" create
description "Default customer"
exit
pw-template 100 name "100" create
split-horizon-group "shg1"
exit
exit
vpls 1 name "VPLS1" customer 1 vpn 1 create
description "Vpls 1 "
service-mtu 1400
split-horizon-group "vpls1" create
description "Default description for SHG vpls1"
exit
bgp
route-distinguisher auto-rd
route-target export target:100:1 import target:100:1
pw-template-binding 100
exit
exit
bgp-ad
vpls-id 1:1
no shutdown
exit
bgp-evpn
evi 1
mpls bgp 1
split-horizon-group "vpls1"
ingress-replication-bum-label
auto-bind-tunnel
resolution-filter
rsvp
exit
resolution filter
exit
no shutdown
exit
exit
stp
shutdown
exit
site "BGPMH1" create
site-id 1
split-horizon-group shg1
failed-threshold 2
no shutdown
exit
no shutdown
exit
----------------------------------------------
[gl:/configure]
A:admin@node-2# compare from url cf3:md-config.cfg
+ service {
+ pw-template "100" {
+ split-horizon-group {
+ name "shg1"
+ }
+ }
+ system {
+ bgp-auto-rd-range {
+ ip-address 2.2.2.2
+ community-value {
+ start 1
+ end 5000
+ }
+ }
+ bgp {
+ evpn {
+ ingress-replication-bum-label-block "evpnMcast"
+ }
+ }
+ sdp 21 {
+ admin-state enable
+ delivery-type mpls
+ path-mtu 1600
+ ldp true
+ far-end {
+ ip-address 10.20.1.1
+ }
+ }
+ vpls "VPLS1" {
+ admin-state enable
+ description "Vpls 1 "
+ service-id 1
+ customer "1"
+ vpn-id 1
+ service-mtu 1400
+ bgp 1 {
+ route-distinguisher auto-rd
+ route-target {
+ export "target:100:1"
+ import "target:100:1"
+ }
+ pw-template-binding "100" {
+ }
+ }
+ bgp-ad {
+ vpls-id "1:1"
+ }
+ bgp-evpn {
+ evi 1
+ mpls 1 {
+ split-horizon-group "vpls1"
+ ingress-replication-bum-label true
+ auto-bind-tunnel {
+ resolution filter
+ resolution-filter {
+ rsvp true
+ }
+ }
+ }
+ }
+ split-horizon-group "vpls1" {
+ description "Default description for SHG vpls1"
+ }
+ bgp-mh-site "BGPMH1" {
+ admin-state enable
+ id 1
+ failed-threshold 2
+ shg-name "shg1"
+ }
+ }
+ }
Revert to a saved classic CLI configuration or save changes to the classic CLI configuration in each CLI engine when converting a configuration snippet so that the MD-CLI comparison displays only the snippet that is converted.
Avoid configuration snippets that overlap with the existing configuration, including default configuration snippets, because they may not be displayed as a difference. A minimum configuration is recommended to ensure that all differences are displayed.
Consider using the same type of router for the conversion as the router the configuration is intended for (although this is not a strict requirement), because some CLI commands are specific to a product family or chassis.