NSO LSA HA after switchover observation: Setup: NSO LSA L3 HA - CFS - 192.168.5.67 , 192.168.6.67 VIP 3.3.3.7 - nsoaz1/Cnc@1234NSO LSA L3 HA - RFS1 - 192.168.5.68 , 192.168.6.68 VIP 4.4.4.7 - nsoaz1/Cnc@1234NSO LSA L3 HA - RFS2 - 192.168.5.69 , 192.168.6.69 VIP 5.5.5.7 - nsoaz1/Cnc@1234Hi team,Kindly suggest on below points.Observation 1:After NSO LSA L3 HA (CFS+RFS) Switchover from AZ1 to AZ2, CRUD operations accepted only after executed below commands.request cluster remote-node rfs-1 ssh fetch-host-keysrequest cluster remote-node rfs-2 ssh fetch-host-keysrequest devices fetch-ssh-host-keysrequest devices sync-fromShow cluster device notification status goes from up to - state.Observation 2:NSO allows changing Circuit style Resource pool . But, receiving attached error while trying auto bidirectional association id during CS policy creationObservation 3:No change made to color pool association. But after NSO LSA L3 HA (CFS+RFS) Switchover, new CS policy creation with auto color edits existing CS policy that was created with auto color pool.Same observation for disjoint also.
 Hi Ajitha.Lets schedule a session to further investigate/validate observed behaviors.Thanks,AbeDid a session with Ajitha and confirmed the following cli commands are necessary after failover (observation 1):1. request cluster remote-node * ssh fetch-host-keys2. request devices fetch-ssh-host-keys3. request devices sync-fromFor observations 2 and 3, dry run error was avoided when triggering failover using ncs stop/start, instead of disabling HA (and not re-enabling HA) from the primary node.We did observe that after successful failover between primary and secondary nodes, applying CS SR policy shows inconsistent behavior where the dry-run values for color, disjoint and bi-directional fields where but was .I suspect some issue from the UI side and Ajitha will reach out to UI team and verify issue.Did a session with Ajitha and confirmed the following cli commands are necessary after failover (observation 1):1. request cluster remote-node * ssh fetch-host-keys2. request devices fetch-ssh-host-keys3. request devices sync-fromFor observations 2 and 3, dry run error was avoided when triggering failover using ncs stop/start, instead of disabling HA (and not re-enabling HA) from the primary node.We did observe that after successful failover between primary and secondary nodes, applying CS SR policyshows inconsistent behavior where the dry-run values for color, disjoint and bi-directional fields wherebut was.I suspect some issue from the UI side and Ajitha will reach out to UI team and verify issue.