The following defect was closed with code changes in this release of the software.
| Parent Defect ID: | NPB-6044 | Issue ID: | NPB-6044 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | LLDP Micro services restarts observed intermittently. | ||
| Condition: |
During processing of LLDP received frames at times micro services restarted. This is due to race condition and improper mutex handling. |
||
| Parent Defect ID: | NPB-6046 | Issue ID: | NPB-6046 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | The chassis status went to degraded temporary for few secs during which the configurations were not allowed to be changed. | ||
| Condition: | The chassis status went to degraded for few secs during which the configurations were not allowed to be changed. | ||
| Parent Defect ID: | NPB-6050 | Issue ID: | NPB-6050 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.6 |
| Symptom: | QSFP detection failed on certain SR optics | ||
| Condition: | Issue is seen intermittently when QSFP eeprom read fails | ||
| Parent Defect ID: | NPB-6051 | Issue ID: | NPB-6051 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | For some of the ports associated with ingress-groups, the port-sap was not updated in state db but was getting updated only in config db. | ||
| Condition: | Port-sap was not getting updated in state db when the ports are associated with ingress-groups. | ||
| Parent Defect ID: | NPB-6052 | Issue ID: | NPB-6052 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | Increase in the traffic volume was observed out of few of the egresses | ||
| Condition: | When multiple instances of same routemap were associated with egress group having the same egress. During add/delete operations, the sfc-id was wrongly updated correctly for egress-group, causing higher volume of traffic destined to those sfc-ids and egresses. | ||
| Parent Defect ID: | NPB-6057 | Issue ID: | NPB-6057 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | Route map/ACL/Listener policy instances are not allowed to configure more than 4095 sequence ID. | ||
| Condition: | Due to the SDE restrictions only 24 bits are allowed to configure for a Policy entry (combination of ACL and Route-map / listener policy sequence IDs). With this restriction and current design sequence ID is allowed to configure in the range 1 - 4095. | ||
| Parent Defect ID: | NPB-6069 | Issue ID: | NPB-6069 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | Traffic loss was observed when system was rebooted with replication configurations | ||
| Condition: | When replication configurations were done partially and system was rebooted, the sfc does not point to new path and traffic loss was observed. | ||
| Parent Defect ID: | NPB-6102 | Issue ID: | NPB-6102 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.6 |
| Symptom: | User was able to enter into config mode for nonexistent interface and still no error/warning thrown to the user. | ||
| Condition: | condition is when the user try to config a non existent interface | ||
| Parent Defect ID: | NPB-6119 | Issue ID: | NPB-6119 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.6 |
| Symptom: | The output of the CLI 'show inventory slot' was missing few of the critical information that includes the model, serial no, part no of the line card. | ||
| Condition: | On inserting a new line card after the chassis is up or if on removing and reinsert the line card, this issue was seen. As the EEPROM read was happening during the initialization period, it was missing this information. | ||
| Parent Defect ID: | NPB-6160 | Issue ID: | NPB-6160 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | Traffic matching Listener policy lp_e_vlantag100 was not getting forwarded to egress ports and being received at KPI tools. | ||
| Condition: | Listener policy failed to route incoming packets to high priority rules which has same ACLs but different VLAN IDs. | ||
| Parent Defect ID: | NPB-6177 | Issue ID: | NPB-6177 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.6 |
| Symptom: | Memory utilization of 9920 keeps increasing, eventually resulting into device reboot. | ||
| Condition: | This issue occurs when 9920 is managed by XCO. | ||
| Parent Defect ID: | NPB-6179 | Issue ID: | NPB-6179 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | TX laser is on even with admin down on LR optics | ||
| Condition: | Always reproducible on LR optics | ||
| Parent Defect ID: | NPB-6181 | Issue ID: | NPB-6181 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | Memory utilization of 9920 keeps increasing, eventually resulting into device reboot. | ||
| Condition: | This issue occurs when 9920 is managed by XCO. | ||
| Parent Defect ID: | NPB-6182 | Issue ID: | NPB-6182 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.6 |
| Symptom: | There was a gradual increase of memory consumption in the pbd-agent and target-proxy-agent services. | ||
| Condition: | There was a gradual increase of memory consumption in the pbd-agent and target-proxy-agent services. | ||
| Parent Defect ID: | NPB-6185 | Issue ID: | NPB-6185 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.6 |
| Symptom: | QSFP register access was failing because of which health monitor moved LC to faulty | ||
| Condition: | QSFP register failed with NACK. This can happen in case I2C bus is busy with other transactions | ||
| Parent Defect ID: | NPB-6186 | Issue ID: | NPB-6186 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | QSFP register access was failing because of which health monitor moved LC to faulty | ||
| Condition: | QSFP register failed with NACK. This can happen in case I2C bus is busy with other transactions | ||
| Parent Defect ID: | NPB-6190 | Issue ID: | NPB-6190 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | 9920 | Reported in Release: | NPB 21.1.2.5 |
| Symptom: | QSFP register access was failing because of which health monitor moved LC to faulty | ||
| Condition: | QSFP register failed with NACK. This can happen in case I2C bus is busy with other transactions | ||