Open Defects

The following defects are open in this release of the software.

Parent Defect ID: NPB-5182 Issue ID: NPB-5182
Severity: S2 - Major
Product: NPB Reported in Release: NPB 21.1.1.0
Symptom: Entity MIB item entPhysicalVendorType does not return any Vendor type OIDs, instead it returns {0 0} when SNMP walk is performed.
Condition: This issue is seen during SNMP walk of entPhysicalVendorType in the entity MIB.
Workaround: No workaround
Recovery: No recovery available
Parent Defect ID: NPB-5188 Issue ID: NPB-5188
Severity: S3 - Moderate
Product: NPB Reported in Release: NPB 21.1.1.0
Symptom: The Link Fault Status field in the Show interface ethernet command output may show incorrect fault status.
Condition: no shutdown on the ethernet interface.
Workaround: No workaround
Recovery: No functional impact
Parent Defect ID: NPB-5567 Issue ID: NPB-5567
Severity: S2 - Major
Product: NPB Reported in Release: NPB 21.1.2.0
Symptom: Transport tunnel is created while configuring invalid transport protocol for system logging host.
Condition: Configure invalid transport protocol for the system logging host.
Workaround: Avoid invalid configuration of transport protocol for system logging host.
Recovery: Configure UDP/TCP as transport and delete the transport-tunnel created using the invalid command.
Parent Defect ID: NPB-5724 Issue ID: NPB-5724
Severity: S3 - Moderate
Product: NPB Reported in Release: NPB 21.1.2.0
Symptom: LACP port-channel remains down after replaying the configuration with LACP rate as fast in the member interfaces.
Condition: The issue is seen when the LACP configurations are replayed with the node in default-configs.

Only when lacp rate fast is configured on member ports.

Workaround: Reboot the system with config or change lacp rate normal and after the port-channel comes up again change it to lacp rate fast on member ports.
Recovery: Disable and enable LACP in the global config mode.
# no protocol lacp
# protocol lacp
Parent Defect ID: NPB-5953 Issue ID: NPB-5953
Severity: S4 - Minor
Product: NPB Reported in Release: NPB 21.1.2.4
Symptom: ACL, route-map, or listener-policy configuration fails when the sequence number is greater than 4095, but the error message displays the supported range as 1-65535.
Condition: The NPB stratum supports only 24 bits. The valid ACL, route-map, or listenerPolicy sequence number range is 1-4095.
Workaround: Ignore the CLI message for the NPB.
Recovery: Configure the sequence number between 1-4095 for the NPB.