Guest

Preview Tool

Cisco Bug: CSCvt97127 - Polaris 16.9 Timestamp of IPSLA API call response is wrong

Last Modified

May 12, 2020

Products (1)

  • Cisco Cloud Services Router 1000V Series

Known Affected Releases

16.6.6 16.9.1 17.3

Description (partial)

Symptom:
When sending a RESTCONF call to check ip sla statistics the response has the wrong timestamp:

{
  "Cisco-IOS-XE-ip-sla-oper:ip-sla-stats": {
    "sla-oper-entry": [
      {
        "oper-id": 10,
        "oper-type": "oper-type-udp-jitter",
        "latest-return-code": "ret-code-ok",
        "success-count": 10,
        "failure-count": 0,
        "latest-oper-start-time": "2019-08-27T10:38:03+00:00",

the CLI gives the correct timestamp:

#show ip sla statistics
Load for five secs: 1%/0%; one minute: 3%; five minutes: 3%
Time source is NTP, 01:40:49.527 EST-5 Mon Aug 26 2019

IPSLAs Latest Operation Statistics

IPSLA operation id: 10
Type of operation: udp-jitter

Conditions:
following clock configuration:

clock timezone EST -5 0
clock summer-time EST-5 recurring
Bug details contain sensitive information and therefore require a Cisco.com 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.