Troubleshooting tips:
•
Wait for the SLA profile to complete the process then try again.
• Configure a valid SLA type for the SLA profile before scheduling it.
Larger or negative time values in delay parameters
Symptom: “show sla profile [id]” will show large delay and jitter values.
Problem description: SLA calculates the delay and jitter values between two nodes by sending
packets to the destination. The timestamps added by the two nodes are used for the delay and
jitter calculations. One-way delay and jitter calculations depend on the time synchronization
between the nodes. If the time at both the nodes are not synchronized then these calculations
will not be accurate. Possible reasons for this problem are: 1. Time is not synchronized properly
between the source and destination. 2. There is more network congestion between the two
nodes. The interface, through which the SLA packets are sent, may be overloaded with more
traffic.
Prerequisite: SLA should be properly configured and scheduled.
Troubleshooting tips:
• Synchronize the clock between the two nodes and reschedule the SLA.
• If the network is too congested, schedule the SLA after some time to get the exact
values.
Response for the SLA packets sent is not received
Symptom: Receive count for the SLA profile will be less than transmit count.
Problem description: SLA sends out packets to the destination and wait for the response
packets. Once it receives the response packets, it will calculate the delay and jitter values. If
the packets have not reached within the timeout period then those packets are considered as
loss. If twenty packets are sent to the destination and only 15 packets are received before the
time out period, then 5 packets are considered as lost. “Remaining Time Out” value in the show
sla profile command gives the time-out value remaining. The reasons for packet getting lost
Chassis QoS troubleshooting
Troubleshooting August 2013 259
To Next Page
Loading...
