Incorrect Sequence Of Deletion Interface And QoS
(Doc ID 2694868.1)
Last updated on JULY 30, 2020
Applies to:
Oracle Communications IP Service Activator - Version 7.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
While monitoring the Audit Trails for a device the sequence that IPSA uses to delete a sub-interface (with QoS policies applied) on a Cisco device is incorrect. You can observe the interface being deleted then re-added back. This causes extra config on the router.
Audit log below –
2020-05-12 10:39:44|<IP ADDR>|interface TenGigabitEthernet9/2.1281
2020-05-12 10:39:44|<IP ADDR>|no ip address <IP ADDR> <MASK>
2020-05-12 10:39:44|<IP ADDR>|no encapsulation dot1Q
2020-05-12 10:39:44|<IP ADDR>|no bandwidth
2020-05-12 10:39:45|<IP ADDR>|no description
2020-05-12 10:39:45|<IP ADDR>|exit
2020-05-12 10:39:45|<IP ADDR>|no interface TenGigabitEthernet9/2.1281 ---->this removes the sub-interface
2020-05-12 10:39:45|<IP ADDR>|interface TenGigabitEthernet9/2.1281 ---->this command is putting it back on the router
2020-05-12 10:39:45|<IP ADDR>|no service-policy output "Policy Name"
2020-05-12 10:39:46|<IP ADDR>|exit
IPSA deletes the sub-interface first without removing the applied QOS policy
Then re-creates that sub-interface for removing the QOS policy.
This sequence leaves a sub-interface on the Cisco device.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |