Observed few incomplete objects in app-controller on customer router. Issue appeared after enabling IPv6 on the interface. This article explains one of the possible reason for seeing incomplete app-controller states for objects produced by ndp
labuser@labrouter-re0> show platform app-controller incomplete
evo-aftmand-bt (fpc0) App controller Object Info :
GUID : 1090921698579
Type : net::juniper::rtnh::Route
OLC : 31525197391597395
Producer : re0::ndp::50331993
Contents :
cos_rt_data : 0
cos_rt_data_type : (null)
dcu_index : 0
ifindex : 1019
iflist_index : 0
prefix : type: 0x2 bytes: 0xfe80000000000000a6e11afffe5f8733/128
rt_bitflags : Route is coupled with nexthop
rttype : destination learned by interface code
scu_index : 0
tid : 0
Default stage Info
Default OLC : 31525197391597395
NKDB name : Default
Natural name : [GUID: 1090921698579, OLC: 31525197391597395::Type:Route : destination learned by interface code(7)prefix: fe 80 0 0 0 0 0 0 a6 e1 1a ff fe 5f 87 33 0 0 0 80 prefix-len: 3fb]
State : NodeStateHoldIncomplete
Potential Reason : Colliding with existing live object [GUID: 923417970625, OLC: 21110623253314737::Type:Route : destination learned by interface code(7)prefix: fe 80 0 0 0 0 0 0 a6 e1 1a ff fe 5f 87 33 0 0 0 80 prefix-len: 3fb]
Potential Remedy : request system application restart app ifmand node re0
Delete status : Not Deleted
Parent : 1086626725964
Children
1090921698580
AMM details :
Ref Counts
Publish : 0
BQ : 1
App-Controller : 2
Evl Tables : 0
Total : 3
Is Facade live : true
In-use in Publish : false
...
Issue is related to IPv6 NDP where it’s trying to resolve local route and hence the anomaly. As you can see from the below logs that the apps are trying to resolve on local link local address.
This issue will not cause any user or business impacts
ifindex : 1019 << Points to AE1.0
prefix : type: 0x2 bytes: 0xfe80000000000000a6e11afffe5f8733/128 <<< Links Local address of AE1
GUID : 1090921698580
Type : net::juniper::interfaces::AddrResolveResp
OLC : 31525197391594485
reason : (null)
respFlags : Resolve Succeeded
Default OLC : 31525197391594485
Natural name : [GUID: 1090921698580, OLC: 31525197391594485::NhARResp]
State : NodeStateHoldIncDepChild
Potential Reason : Non-Parent [GUID: 1090921698579, OLC: 31525197391597395::Type:Route : destination learned by interface code(7)prefix: fe 80 0 0 0 0 0 0 a6 e1 1a ff fe 5f 87 33 0 0 0 80 prefix-len: 3fb] colliding with existing live object [GUID: 923417970625, OLC: 21110623253314737::Type:Route : destination learned by interface code(7)prefix: fe 80 0 0 0 0 0 0 a6 e1 1a ff fe 5f 87 33 0 0 0 80 prefix-len: 3fb]
Parent : 2250562944371
Non parent links:
1090921698579
App-Controller : 1
Total : 2
…
labuser@labrouter-re0> show ipv6 neighbors | match ae1
2001:0::80 dc:05:39:70:0e:0a reachable 9 yes no ae1.0
fe80::a6e1:1aff:fe5f:8733 00:00:00:00:00:00 unreachable 5 yes no ae1.0 <<< NDP is trying to resolve Local Link local address
fe80::de05:39ff:fe70:e0a dc:05:39:70:0e:0a stale 288 yes no ae1.0
labuser@labrouter-re0> show interfaces terse ae1.0 | no-more
Interface Admin Link Proto Local Remote
ae1.0 up up inet6 2001:1998:0:8::81/127
fe80::a6e1:1aff:fe5f:8733/64 <<<
Physical interface: ae1, Enabled, Physical link is Up
Interface index: 6354, SNMP ifIndex: 639, Generation: 923417970569
Current address: a4:e1:1a:5f:87:33, Hardware address: a4:e1:1a:5f:87:33
Logical interface ae1.0 (Index 1019) (SNMP ifIndex 640) (Generation 923417970574) <<<
Flags: Up SNMP-Traps Encapsulation: ENET2