07-17-2019 03:14 AM - edited 07-17-2019 03:15 AM
Hi Expert,
I am facing issue; for L2VPN xConnect, IOS-NED is generating extra command which we are not configuring and not required; as per below
admin@ncs(config)# show full-configuration devices device 7606-S-PE config ios:interface Vlan 65
devices device 7606-S-PE
config
ios:interface Vlan65
description NSO_L2VPN_Testing
xconnect 12.13.14.15 1551 encapsulation mpls pw-class PVlan
backup peer 15.14.13.12 1232 pw-class PVlan
no mpls control-word (not required)
exit
no ip address
service-policy input 2M
service-policy output 2M
no shutdown
exit
!
!
How can I remove (no mpls control-word) command. Please anyone suggest. Thanks
Solved! Go to Solution.
07-17-2019 12:38 PM
I believe this is done because on some devices the xconnect is created with "mpls control-word" set. So (unless you have also set it in NSO) NSO has to clear it with the no command when it creates the xconnect.
It shouldn't cause a problem, but if it does then you should raise a TAC case.
07-17-2019 08:48 AM
In the NED this control-word leaf is modeled as an 'empty' type with 'tailf:cli-show-no' annotation:
/ interface * / xconnect encapsulation / mpls control-word
leaf control-word {
tailf:info "Include control-word in pseudowire packets";
tailf:cli-show-no;
type empty;
}
This means that it will show the 'no mpls control-word' if this leaf is not set and show 'mpls control-word' when it is set.
admin@ncs% set devices device ios0 config ios:interface Vlan 65 description NSO_L2VPN_Testing xconnect address 12.13.14.15 vcid 1551 mpls control-word
admin@ncs% commit dry-run outformat native
native {
device {
name ios0
data interface Vlan65
description "NSO_L2VPN_Testing"
xconnect 12.13.14.15 1551 encapsulation mpls
mpls control-word
exit
no shutdown
exit
}
}
[edit]
admin@ncs% delete devices device ios0 config ios:interface Vlan 65 description NSO_L2VPN_Testing xconnect address 12.13.14.15 vcid 1551 mpls control-word
admin@ncs% commit dry-run outformat native
native {
device {
name ios0
data interface Vlan65
xconnect encapsulation mpls
no mpls control-word
exit
no shutdown
exit
}
}
07-17-2019 11:23 AM - edited 07-17-2019 11:26 AM
Hi Imanor, Thanks for your reply.
Does this mean; We can not remove this command?, either "mpls control-word" or "no mpls control-word" command will be (must) available. So, there is no any-other way out to remove it?
Regards,
Bjron
07-17-2019 12:38 PM
I believe this is done because on some devices the xconnect is created with "mpls control-word" set. So (unless you have also set it in NSO) NSO has to clear it with the no command when it creates the xconnect.
It shouldn't cause a problem, but if it does then you should raise a TAC case.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide