Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Configuring DHCP IPv6 proxy relay profile, and DAPS pool. DAPS state and connection handle state is seen in" INITIALIZED" state. Expected to see the state as " CONNECTED".
Configuring DHCP IPv6 proxy relay profile, and DAPS pool.
None
Hi Team, We are testing dhcp ipv6 for ASR9902 on release 7.8.2. When we configure the DAPS pool and the dhcp ipv6 proxy relay profile, the DAPS state and connection handle state is seen in" INITIALIZED" state. Expected to see the state as " CONNECTED". Configuration done on router is below: dhcp ipv6 profile v6relay relay helper-address vrf default 2001:4898:2001:8:fe::3 source-interface Loopback0 ! profile CORPNETv6 proxy helper-address vrf default 2001:4898:2001:8:fe::3 helper-address vrf default 2001:4898:2001:8:fe::120 source-interface Loopback0 ! profile v6relay-Ixia relay option remote-id test helper-address vrf default 2024:0:1:79::10 source-interface Loopback0 ! profile v6relay-msft1001 relay helper-address vrf msft_1001 2024:0:1:74::10 ! profile v6relay-msft1002 relay helper-address vrf msft_1002 2024:0:1:75::10 ! interface TenGigE0/0/0/20.2040 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2041 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2042 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2043 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2044 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2045 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2046 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2047 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2048 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2049 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2050 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2051 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2052 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2053 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2054 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2055 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2056 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2057 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2058 proxy profile CORPNETv6 interface TenGigE0/0/0/20.2059 proxy profile CORPNETv6 pool vrf default ipv6 PD_POOL prefix-length 92 pool vrf default ipv6 ADDR_POOL address-range 2201:abcd:1234:2400:f800::1 2201:abcd:1234:2400:f800::2 ! pool vrf default ipv6 PD_POOL prefix-range 3301:1ab7:2345:1200:f800:: 3301:1ab7:2345:1200:f800:fff0:: ! After configuring, and restarting the DAPS and DHCP IPv6 process the state is still seen as "INITIALIZED" We are expecting this to be in "CONNECTED" state as this was tested the same way on release 7.1.2 with same configuration except the DAPS pool configuration.