Fixed
Created: Apr 5, 2022
Updated: Apr 26, 2022
Resolved Date: Apr 7, 2022
Found In Version: 10.21.20.10
Fix Version: 10.21.20.12
Severity: Standard
Applicable for: Wind River Linux CD
Component/s: Kernel
Topology and cfg can be found in !topology.png|thumbnail! & ^fwd_cfg].
*Test scenario :*
---
After the configuration is applied and operational, the test steps continue as follows:
# Verify that VM 1 is reachable from VM 2 and vice versa using ping6 command (should only be possible through forwarding packets).
# On SSC node, in linux, in proper fib, remove default route to NW address which VM 2 resides in. This way, the packet won’t be forwarded by SSC due to no route pointing to destination address of VM 2.
# Collect the corresponding SNMP counters from SSC node using linux.
# Verify that there is no connectivity from VM 1 to VM 2 using ping6 command.
# Check the counters again.
---
They expect the behavior to be as per [RFC 4293 - Management Information Base for the Internet Protocol (IP) (ietf.org) (https://datatracker.ietf.org/doc/html/rfc4293)
# InForwDatagrams -----> + -----> OutForwDatagrams
# |
# V
# *InNoRoutes*
But instead the counters are incrementing as per [^Ip6Counters.docx].
The increment is in these 2 counters -> Type1/DestUnreachs from in /proc/net/dev_snmp6/
