Table Of Contents
Network Events
The tables in this chapter list probable causes and recommended courses of action for network events reported by the ASE and displayed in the PAC Event Processor window. The tables group network events by the following categories:
•
administrative events
•
•
•
•
For Cisco WAPMS to report an event, it must be configured either per ASE through the Performance Monitoring feature of the PAC Event Processor Toolset or across multiple ASEs using the PAM Templates Toolset of the PAM Manager application.
Table E-1 lists recommended actions for administrative events.
Table E-1 Recommended Actions for Administrative Events
ASE has rebooted.1
Power recycle (On/Off); software download.
Information only. If it occurs regularly, it could indicate an ASE problem. Call technical support.
Performance data collection poll failure; x out of y sections could not be updated.*
When x=y (that is, none of the sections could be updated), the circuit or router is down or there is some other communications failure (for example, LAN segment down) between the PAM and the ASE. When inband is being used, the management PVC could be the cause of failure.
When x<y (that is, only some of the sections could be updated), one of the following may be the cause:
•
•
•
When x=y, ping the ASE, then launch the Network Configuration Toolset and try to reach the ASE through ASE Setup.
When x<y, one of these actions is appropriate:
•
•
•
Incorrect SNMP community name used in attempt to contact ASE.
Community strings mismatch between ASE and console or other SNMP manager.
Verify community strings of ASEs and all consoles to make sure they are consistent with each other.
1 These events are always reported and cannot be configured on the ASE.
In Cisco WAPMS, physical layer state-change events notify you when an access line signal or data is lost or regained, the side of an ASE in which the change occurred, and the direction in which the change occurred. For T-carrier (T1 or FT1) and DDS signals, physical layer state-change events occur on the network side; for a V.35 signal, they occur on the user side. Because a DS3 signal can exist on both sides of an ASE, physical layer state-change events for DS3 signals can indicate network or user side. When the event does not indicate a direction, both to and from network directions are affected. Table E-2 lists recommended actions when the physical layer state-change events occur.
In Cisco WAPMS, circuit link layer state-change events notify you when a Frame Relay or ATM link is lost or regained and on which side of an ASE the change occurred. The network side is indicated as carrier. Table E-3 lists recommended actions when link layer state-change events occur.
In Cisco WAPMS, circuit state-change events notify you when a DLCI or VPI/VCI is lost, regained, or is not detected. Table E-4 lists recommended actions when certain circuit state-change events occur.
In Cisco WAPMS, specific statistical threshold events vary according to their performance monitoring values set using the Event Processor Toolset or the PAM Templates tool. Table E-5 lists recommended actions when specific statistical threshold events occur.