![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 73](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550073.webp)
1-17
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 1 Troubleshooting Overview
Managing Events and Alarms
The
type
and
value
tokens are both mandatory for the
change report-properties
command.
•
If type=event-logsize or alarm-logsize, then value must be an integer between 10 to 30000.
•
If type=event-level, then value designates the severity of the events or alarms to include in the log
files, which can be info, warning, minor, major, or critical.
All events or alarms whose severity is equal to or greater than the event level specified are included
in the designated event or alarm log file.
For example:
If info is designated, all events or alarms are included in the designated event or alarm log file. If
minor is designated, minor, major, and critical events or alarms are included in the designated event
or alarm log file.
Tip
Cisco recommends that you store events of
all
severity levels in the event and alarm log files by entering
info
as the value in this command. This permits the operator to access all event and alarm reports.
Changing Threshold and Throttle Values
The threshold and throttle values used in event and alarm reporting are user-provisionable. You can use
the following
show event-prov
command to display the current threshold and throttle values for any
event or alarm message:
CLI>
show event-prov type=callp; number=9;
Reply: Success: Entry 1 of 1 returned.
REPORTTYPE=2
REPORTNUMBER=9
REPORTDESCRIPTION=No Route Available for Carrier Dialed
THRESHLIM=100
THROTTLELIM=20
DW1NAME=Orig Type(Trunk or S
DW2NAME=Orig Sub or TG id
DW3NAME=Calling Party Number
DW4NAME=Called Party Number
DW5NAME=Carrier Code Dialed
DW6NAME=n/a
DW7NAME=n/a
DW8NAME=n/a
CAUSE1=No route is available for the interexchange carrier (IXC) dialed.
ACTION1=The data words in the event report indicate the parameters that need to be
corrected. Refer to office records for the carrier.
CAUSE2=Parameter(s) in the carrier and/or route-grp table are missing or incorrect for the
carrier.
ACTION2=Determine whether the routing parameters were entered correctly in the carrier
and/or route-grp tables.
ACTION3=If the carrier-id or route-grp-id are not specified, or are incorrect in the
dial-plan table, enter the correct values. Use the change carrier or change route-grp
command.
The command
show event-prov
with no parameters displays all events that are provisioned.
The command
show event-prov
with only
type
specified displays all events of that type.