05-10-2021 09:06 AM
Solved! Go to Solution.
07-30-2021 02:14 AM
Hello, I see you never got an answer.
[I am using NSO 5.5 here but _should_ work the same for earlier versions]
Couple of points:
>> when i modify rfs-service , is it not possible to re-store the service in rfs-node by help of re-deploying service in cfs-node ?
Yes it is possible
In your scenario above there is something quite not clear to me yet - once you have modified the service on the lower-node-1, your upper node should now see lower-node-1 as Out of sync like:
admin@upper-nso> request cfs-vlan v1 re-deploy dry-run { outformat cli } Error: Network Element Driver: device lower-nso-1: out of sync [error][2021-07-30 11:07:22] admin@upper-nso> *** ALARM out-of-sync: Device lower-nso-1 is out of sync
Are you doing anything specific in the configuration (I followed the example setup in example 22 btw)
A solution to go around this is to sync-from lower-node-1 from the upper node and then when I run the re-deploy dry-run command:
admin@upper-nso> request cfs-vlan v1 re-deploy dry-run { outformat cli } cli { local-node { data ncs:devices { device lower-nso-1 { config { services { vlan v1 { - unit 4; + unit 3; } } } } } } lsa-node { name lower-nso-1 data devices { device ex0 { config { sys { interfaces { interface eth3 { + unit 3 { + enabled; + description "Interface owned by CFS: v1"; + vlan-id 77; + } - unit 4 { - enabled; - description "Interface owned by CFS: v1"; - vlan-id 77; - } } } } } } } rfs-vlan:services { vlan v1 { - unit 4; + unit 3; } } } } [ok][2021-07-30 11:08:26]
[NOTE: deep-check-sync ignore OOS here]
07-30-2021 02:14 AM
Hello, I see you never got an answer.
[I am using NSO 5.5 here but _should_ work the same for earlier versions]
Couple of points:
>> when i modify rfs-service , is it not possible to re-store the service in rfs-node by help of re-deploying service in cfs-node ?
Yes it is possible
In your scenario above there is something quite not clear to me yet - once you have modified the service on the lower-node-1, your upper node should now see lower-node-1 as Out of sync like:
admin@upper-nso> request cfs-vlan v1 re-deploy dry-run { outformat cli } Error: Network Element Driver: device lower-nso-1: out of sync [error][2021-07-30 11:07:22] admin@upper-nso> *** ALARM out-of-sync: Device lower-nso-1 is out of sync
Are you doing anything specific in the configuration (I followed the example setup in example 22 btw)
A solution to go around this is to sync-from lower-node-1 from the upper node and then when I run the re-deploy dry-run command:
admin@upper-nso> request cfs-vlan v1 re-deploy dry-run { outformat cli } cli { local-node { data ncs:devices { device lower-nso-1 { config { services { vlan v1 { - unit 4; + unit 3; } } } } } } lsa-node { name lower-nso-1 data devices { device ex0 { config { sys { interfaces { interface eth3 { + unit 3 { + enabled; + description "Interface owned by CFS: v1"; + vlan-id 77; + } - unit 4 { - enabled; - description "Interface owned by CFS: v1"; - vlan-id 77; - } } } } } } } rfs-vlan:services { vlan v1 { - unit 4; + unit 3; } } } } [ok][2021-07-30 11:08:26]
[NOTE: deep-check-sync ignore OOS here]
07-30-2021 01:13 PM
Gmuloche hi,
Thank you very much for your reply.. this is something still remaining open for me.. i need to do some testing to reply, but currently i do have time for this, i will be able to reply mid to late next week.
kind regards
08-18-2021 05:04 AM
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