RDKB-61542: IPV6 ping failure is high on 8.2 release#62
RDKB-61542: IPV6 ping failure is high on 8.2 release#62
Conversation
Reason for change: IPV6 ping failure is high on 8.2 release. Deprecated IPv6 ping and implemented rdisc mechanism to check connectivity Test Procedure: Load build on GW and wait for 1 - 2 hours of uptime. Check Selfheal.txt.0 logs. Should not see IPv6 ping failures. Risks: Low Priority: P0 Signed-off-by: Umesh_Ainapuram@comcast.com
|
|
| @@ -215,33 +239,21 @@ runPingTest() | |||
|
|
|||
| if [ "$IPv6_Gateway_addr" != "" ] | |||
There was a problem hiding this comment.
Whether in current sprint, whether this variable is properly set, I believe we have two addresses set on this variable. can you confirm
| if [ "$ping4_success" -ne 1 ] && [ "$connectivity_ipv6_success" -ne 1 ] | ||
| then | ||
| echo_t "RDKB_SELFHEAL : Ping to both IPv4 and IPv6 Gateway Address failed." | ||
| t2CountNotify "RF_ERROR_IPV4IPV6PingFailed" |
There was a problem hiding this comment.
Please modify this telemetry as well
| if [ "$CHECK_PACKET_RECEIVED" -ne 100 ] | ||
| then | ||
| ping6_success=1 | ||
| connectivity_ipv6_success=1 |
There was a problem hiding this comment.
Do we really need our connectivity test variable here. This is based on ipv4 server address and ipv6 address configured. It need not to be CMTS address. Can you please check the expected value here.
3 participants
Reason for change: IPV6 ping failure is high on 8.2 release. Deprecated IPv6 ping and implemented rdisc mechanism to check connectivity
Test Procedure: Load build on GW and wait for 1 - 2 hours of uptime. Check Selfheal.txt.0 logs. Should not see IPv6 ping failures.
Risks: Low
Priority: P0
Signed-off-by: Umesh_Ainapuram@comcast.com