Last Modified: Nov 07, 2022
Known Affected Versions:
14.0.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.0.1, 188.8.131.52, 14.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.1.2, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 15.0.0, 15.0.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
Opened: Aug 29, 2019 Severity: 2-Critical
The multicast routing protocols are implemented by pimd and mribd daemons. mribd daemon crashes in a specific configuration when debug logging is enabled for this daemon.
Dynamic routing daemon mribd crashes. Advanced routing not available while mribd restarts.
1) Dynamic Routing bundle is enabled and PIM protocol is enabled on a route domain. 2) High availability (HA) group/pair with floating self IP address is configured. 3) PIM neighbors are configured for each peer in high availability (HA) group/pair. 4) One of the peers in high availability (HA) is configured to use floating self IP address as an IP address for PIM protocol. This is done using the 'ip pim use-floating-address' command in the PIM configuration in imish: # ip pim use-floating-address 5) Multicast routing is configured in imish: # ip multicast-routing 6) Debug logging for mribd is enabled: # debug ip mrib all # debug ipv6 mrib all --- Note: Although steps 3 and 4 are optional, a practical configuration makes no sense without them.
Dynamic routing daemon mribd no longer crashes when mribd debug logging is enabled.