Preview Tool

Cisco Bug: CSCus14734 - IP SLA http operation with customizable status for return codes

Last Modified

Dec 23, 2018

Products (24)

  • Cisco IOS
  • Cisco ASR 901-6CZ-F-D Router
  • Cisco ASR 901-6CZ-FS-D Router
  • Cisco ASR 901-4C-FT-D Router
  • Cisco ASR 901S-4SG-F-D Router
  • Cisco ME 3600X-24TS-M Switch
  • Cisco ASR 901-6CZ-F-A Router
  • Cisco ASR 901S-2SG-F-D Router
  • Cisco ASR 901S-2SG-F-AH Router
  • Cisco ASR 901-6CZ-FT-A Router
View all products in Bug Search Tool Login Required

Known Affected Releases


Description (partial)

Due to the change of behaviour of the IP SLA http operation (see CSCus30538), there has been a significant impact in various scenarios where setups were using the well known behaviour and now configuration changes are needed to cope with the http operation behaviour change.

Here is an example user story:

Customer was using the previous behaviour of IP SLA http operation which had an OK status as long as there was any response from the remote server. This ensures that any routes dependent on the IP SLA status, are still installed in the routing table.

Customer proceeds to upgrade the IOS to a version containing the new behaviour of the operation, where the status of the operation will be OK only if the return status code of the same operation is HTTP 200 (OK). 
If, for example, the returned code is 3XX (Redirection), the SLA operation status will be down, however the redirection response code may represent a desirable state and considering the operation down, any routes dependent on the tracked object of the SLA operation will be removed.

The IP SLA http operation needs to provide a way to the user to specify which return codes are acceptable and which are not. This provides more granularity and offers an alternative to users who prefer the previous behavior of the IP SLA http operation where all responses were accepted as OK.

Not applicable
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.