SVC-IP6 doesn't follow IP6 AAP-IP when AAP has both IP4 & IP6 addresses

[Sunil Basker]

Test: check if IP4 & IP6 AAP can have different (VRRP) masters.

SVMs have both IP4 & IP6 vip addresses. VRRP is configured such that one SVM becomes master for IP4 vip & the other for IP6 vip. Both IP4 & IP6 addresses are configured as AAP-IP. IP6 SVC-IP doesn't follow IP6 AAP-IP, instead seems to follow IP4 AAP-IP
Ping6 traffic lands in SVM1 (IP4 master) instead of SVM2 (IP6 master)

Steps:
1) Configure
   VN1 (1.1.1.0/24, 1001::/64)
   VN2 (2.2.2.0/24, 1002::/64)
   SVM1 (left: 1.1.1.3, 1001::3
         right: 2.2.2.3, 1002::3)
   SVM2 (left: 1.1.1.4, 1001::4
         right 2.2.2.4, 1002::4)
   SI (in-network-firewall with 2 port-tuples
       AAP-IP: left: 1.1.1.100, 1001::100, right: 2.2.2.100, 1002::100)
2) Configure keepalived in SVM such that SVM1 is master for IP4 address &
   SVM2 is master for IP6 address
3) Ping IP4 & IP6 addresses.

Dump from Naveen
<iq>
 <instance-ip-address>1001::6</instance-ip-address>
 <instance-ip-family>v6</instance-ip-family>
 <instance-ip-mode>active-standby</instance-ip-mode>
 <secondary-ip-tracking-ip>
  <ip-prefix>1.1.1.100</ip-prefix>
  <ip-prefix-len>32</ip-prefix-len>
 </secondary-ip-tracking-ip>
 <instance-ip-secondary>true</instance-ip-secondary>
 <instance-ip-local-ip>false</instance-ip-local-ip>
 <service-instance-ip>true</service-instance-ip>
 <service-health-check-ip>false</service-health-check-ip>
 <id-perms>
  <permissions>