AFT Script run conditional next hop atomic flag on failed on 22.3X50.66-J3.4-EVO
The Atomic flag is set at the Next-hop-group container level and it will not be set at each condition level, We see this correct behavior in our lab on both Junos and EVO where the Atomic flag is set correctly at each next-hop-group level. Customer Script was failing due to parsing logic. The customer had to modify the messaging format for PTX and it started working.
update: {
timestamp: 1742800752728421460
prefix: {
elem: {
name: "network-instances"
}
name: "network-instance"
key: {
key: "name"
value: "DEFAULT"
name: "afts"
name: "next-hop-groups"
name: "next-hop-group"
key: "id"
value: "2662"
path: {
name: "state"
name: "id"
val: {
uint_val: 2662
name: "conditional"
name: "condition"
value: "67108865"
uint_val: 67108865
name: "dscp"
element: {
uint_val: 47
uint_val: 2663
value: "67305473"
uint_val: 67305473
leaflist_val: {
uint_val: 56
uint_val: 57
uint_val: 58
uint_val: 59
uint_val: 60
uint_val: 61
uint_val: 62
uint_val: 63
uint_val: 48
uint_val: 49
uint_val: 50
uint_val: 51
uint_val: 52
uint_val: 53
uint_val: 54
uint_val: 55
uint_val: 2666
atomic: true