06-29-2017 05:01 AM - edited 03-01-2019 03:54 AM
Dear All,
I am trying to run an example in Managing Network Services Chapter 5 - NSO_getting_Started.
The example running well until vpn l3vpn configuration with as-number 65101.
i am using Ubuntu - Unix .
here is my command line scenario....
********************************************************************************************************************************************
admin@ncs# devices sync-from
sync-result {
device ce0
result true
}
sync-result {
device ce1
result true
}
sync-result {
device ce2
result true
}
sync-result {
device ce3
result true
}
sync-result {
device ce4
result true
}
sync-result {
device ce5
result true
}
sync-result {
device ce6
result true
}
sync-result {
device ce7
result true
}
sync-result {
device ce8
result true
}
sync-result {
device p0
result true
}
sync-result {
device p1
result true
}
sync-result {
device p2
result true
}
sync-result {
device p3
result true
}
sync-result {
device pe0
result true
}
sync-result {
device pe1
result true
}
sync-result {
device pe2
result true
}
sync-result {
device pe3
result true
}
admin@ncs# config
Entering configuration mode terminal
admin@ncs(config)# vpn l3vpn volvo
admin@ncs(config-l3vpn-volvo)# as-number 65101
-------------------------------^
syntax error: unknown command
Always facing this problem with that as-number command & when I configure the l3vpn without as-number or set as-number inside config-endpoint-main-office I get error during commit dry-run outformat native.
Here is my scenario ...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
admin@ncs(config)# commit dry-run outformat native
Aborted: 'vpn l3vpn volvo route-distinguisher' is not configured
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here is the command documentation from cisco getting stated....
ncs# config
Entering configuration mode terminal
ncs(config)# vpn l3vpn volvo
ncs(config-l3vpn-volvo)# as-number 65101
ncs(config-l3vpn-volvo)# endpoint main-office
ncs(config-endpoint-main-office)# ce-device ce0
ncs(config-endpoint-main-office)# ce-interface GigabitEthernet0/11
ncs(config-endpoint-main-office)# ip-network 10.10.1.0/24
ncs(config-endpoint-main-office)# bandwidth 12000000
ncs(config-endpoint-main-office)# !
ncs(config-endpoint-main-office)# endpoint branch-office1
ncs(config-endpoint-branch-office1)# ce-device ce1
ncs(config-endpoint-branch-office1)# ce-interface GigabitEthernet0/11
ncs(config-endpoint-branch-office1)# ip-network 10.7.7.0/24
ncs(config-endpoint-branch-office1)# bandwidth 6000000
ncs(config-endpoint-branch-office1)# !
ncs(config-endpoint-branch-office1)# endpoint branch-office2
ncs(config-endpoint-branch-office2)# ce-device ce4
ncs(config-endpoint-branch-office2)# ce-interface GigabitEthernet0/18
ncs(config-endpoint-branch-office2)# ip-network 10.8.8.0/24
ncs(config-endpoint-branch-office2)# bandwidth 300000
ncs(config-endpoint-branch-office2)# !
ncs(config-endpoint-branch-office2)# top
ncs(config)# show configuration
.......
..................
..............................
It will be great help for me and also others if some-one have some solution how to fix this bug , how to set as-number in l3vpn.
any help will be appreciated.
Thanks
Samya Ghosh
Germany
Solved! Go to Solution.
06-29-2017 05:35 AM
Hi Samya,
I believe the documentation might not be inline with the code in the examples directory.
Looking at the YANG code on NSO 4.4.2, I see that the as-number parameter is associated with each endpoint, rather than being a global parameter on the service. This means that each of your endpoints should have this value provided.
so instead of providing this value at this stage, you will have to provided it for each endpoint.
For example,
ncs(config-l3vpn-volvo)# endpoint main-office
ncs(config-endpoint-main-office)# as-number 65101
The reason you are getting the error upon commit is because the VPN also includes a mandatory value called route-distinguisher which might be missing from the documentation:
leaf route-distinguisher {
description "Route distinguisher/target identifier unique for the
VPN";
mandatory true;
type uint32;
}
so, you'll have to also provide this value - unsigned 32 bits integer
For example, before you provide your endpoint details you can provide value for this field:
ncs(config)# vpn l3vpn volvo
ncs(config-l3vpn-volvo)# route-distinguisher 123456
generally speaking, the error you got there suggests that a mandatory value is missing, so you can try using tab completion or '?' in CLI to try to get some hints for the values that are available for you to provide.
Hope that helps,
Yftach
06-29-2017 05:35 AM
Hi Samya,
I believe the documentation might not be inline with the code in the examples directory.
Looking at the YANG code on NSO 4.4.2, I see that the as-number parameter is associated with each endpoint, rather than being a global parameter on the service. This means that each of your endpoints should have this value provided.
so instead of providing this value at this stage, you will have to provided it for each endpoint.
For example,
ncs(config-l3vpn-volvo)# endpoint main-office
ncs(config-endpoint-main-office)# as-number 65101
The reason you are getting the error upon commit is because the VPN also includes a mandatory value called route-distinguisher which might be missing from the documentation:
leaf route-distinguisher {
description "Route distinguisher/target identifier unique for the
VPN";
mandatory true;
type uint32;
}
so, you'll have to also provide this value - unsigned 32 bits integer
For example, before you provide your endpoint details you can provide value for this field:
ncs(config)# vpn l3vpn volvo
ncs(config-l3vpn-volvo)# route-distinguisher 123456
generally speaking, the error you got there suggests that a mandatory value is missing, so you can try using tab completion or '?' in CLI to try to get some hints for the values that are available for you to provide.
Hope that helps,
Yftach
06-30-2017 01:47 AM
Dear Yftach,
Thank you for your kind help & real good and right answer.
It's working fine now & I followed your suggestion.
Thanks & Regards
Samya
07-01-2017 11:13 PM
You're very welcome.
I'm glad it helped!
Yftach
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