SLA
Unable to modify the SLA profile
Symptom: An Error message will be thrown when SLA is configured.
Problem description: SLA can take six SLA types. They are UDP-Echo, UDP-v6-Echo, UDP-
Jitter, UDP-v6-Jitter, ICMP-Echo and ICMP-v6-Echo. A SLA profile can take only SLA type.
When an SLA profile is in Process state (actively sending or receiving packets), then the
configurations
for that SLA cannot be modified. The “Transmit Status” in “show sla profile [id]”
will give the status of the SLA profile. If the Transmit Status is “IN PROCESS” then the SLA
profile cannot be modified. There can be two reasons for failure of SLA profile modification: 1.
If a SLA profile is already configured with a SLA type, and a different SLA type configuration
is requested for that SLA, it will not be accepted. 2. If a SLA profile is IN PROCESS state then
the configuration cannot be modified.
Prerequisite: SLA profile has to be successfully configured with SLA type
Troubleshooting tips:
• Remove the previous configuration by executing “no” command and configure with the
required SLA type.
• Wait till the SLA profile completes its execution and goes to “IN IDLE” state.
Unable to schedule the SLA
Symptom: An Error message will be thrown when SLA is scheduled.
Problem description: SLA profile will be scheduled to find out the SLA parameters such as jitter
and delay. The reasons for this problem can be: 1. When an SLA profile is in Process state
(actively sending or receiving packets), then the configurations for that SLA cannot be modified.
Also it cannot be scheduled again. The “Transmit Status” in “show sla profile [id]” will
give the status of the SLA profile. If the Transmit Status is “IN PROCESS” then the SLA profile
cannot be modified. 2. If the SLA type is not configured for that SLA then it cannot be
scheduled.
Prerequisite: SLA profile has to be successfully created.
Troubleshooting Quality of Service
258 Troubleshooting August 2013
Comments? infodev@avaya.com
To Next Page
Loading...
