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 just return {0 0} when SNMP walk is performed
Condition: This happens always 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: "Link Fault Status" field in "Show interface ethernet" might show incorrect fault status.
Condition: "no shutdown" on the ethernet interface.
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, as expected. And delete transport-tunnel which got created due to 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: If we reboot the system with config it will work properly or change the "lacp rate normal" and after the port-channel comes up again change it to "lacp rate fast" on member ports.
Recovery: Disable & enable lacp in the global config mode. ('no protocol lacp' & 'protocol lacp')
Parent Defect ID: NPB-5763 Issue ID: NPB-5763
Severity: S2 - Major
Product: NPB Reported in Release: NPB 21.1.2.1
Symptom: In some rare scenarios, nexthop-agent /interface-mgr goes for a restart because of watchdog timeout. If nexthop-agent restarts it will not be in a ready state post restart.
Condition: The issue is with connection with stratum service where the peer inside stratum is not responding back to agents while the agents continue to wait for a response.
Workaround: The issue is not seen persistently, there is no workaround for this issue at this point.
Recovery: Reboot the device.