cc/td/doc/product/wanbu/access/aprod
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Events

Events

The Events functions are used to display a list of event messages, clear the event buffer, and to determine the number of event messages that have been stored. When the EVENTS function is selected from the Main Menu, the Events Menu is displayed:

EVENTS MENU Event Display Clear Buffer Event Count: <nn>

Position the cursor next to the Event Display caption and press the <Enter> key to display a list of events. Position the cursor next to the Clear Buffer caption and press the <Enter> key to clear the event buffer. Press the <Esc> key to return to the Main Menu.

Event Display

When the Event Display function is selected from the Events Menu, the system will display a list of events in the following format:

<#> <XX> <Time> <message> <#> <XX> <Time> <message>

The system will display the most recent event message first. Use the <Up Arrow> and <Down Arrow> keys to display previous and subsequent event messages. Press the <Esc> key to exit this screen and return to the Events Menu. The following paragraphs describe the fields in the events display:

<#>: This field identifies the event number. It is a sequential number in the range 0-99.

<XX>: This field identifies the event group code. The group code identifies the FastPAD component that generated the event. It can be one of the following:

  SY = System
  L = Composite Link
  D1 = Data Channel Number 1
  D2 = Data Channel Number 2
  D3 = Data Channel Number 3
  D4 = Data Channel Number 4
  D5 = Data Channel Number 5
  DHS = High Speed (HS) Data Channel
  DNMS = NMS Data Channel
  X1 = Expansion Channel Number 1
  X2 = Expansion Channel Number 2
  X3 = Expansion Channel Number 3
  X4 = Expansion Channel Number 4
  X5 = Expansion Channel Number 5
  X6 = Expansion Channel Number 6
  X7 = Expansion Channel Number 7
  X8 = Expansion Channel Number 8

<Date>: This field identifies the date the event occurred in the form: Mon dd.

<Time>: This field identifies the time the event occurred in the form: hh:mm:ss.

The following example event screen illustrates the format of the event display:

1 SY Jan 01 00:13:12 System Reset 2 L Jan 01 00:14:22 DCD On

Event messages are grouped by category according to the FastPAD component (System, Link, Data Channel, or Expansion Channel) that generated the event.

System (SY) Event Messages

The following paragraphs describe the event messages in the System (SY) category:

$$O.S. Failure: This event message indicates an operating system scheduling error occurred.

Bad EEPROM: This event messages indicates bad EEPROM has been detected.

Bad FLASH-E: This event message indicates the system was not able to correctly erase flash memory.

Bad FLASH ID: This event message indicates bad flash memory has been detected.

Bad FLASH-W: This event message indicates the system was not able to successfully write to flash memory

Bad FlashPAK: This event message indicates the FlashPAK is defective or not configured correctly.

Failed P/S: This event message indicates a failure of the primary power supply.

FLASH Update: This event message indicates flash memory has been updated.

Good P/S: This event message can occur after a Failed P/S 1 event has been posted. It indicates the primary power supply has recovered from the failure condition.

New date/time: This event message indicates a new system date and time has been set. This can occur via the front panel, from a remote FastPAD configuration of this unit, or from the NMS.

New EEPROM: This event message indicates the contents of EEPROM has been updated.

Old date/time: This event message indicates new date/time information has been downloaded to this FastPAD.

Link (L) Event Messages

The following paragraphs describe the event messages in the Link (L) category:

Bad EEPROM: This event message indicates bad EEPROM was detected by the composite link.

CI off: For a V.11 interface, this event message indicates the CI signal has been turned OFF.

CI on: For a V.11 interface, this event message indicates the CI signal has been turned ON.

DCD off: This event message indicates the composite link Data Carrier Detect (DCD) control signal has been turned OFF.

DCD on: This event message indicates the composite link Data Carrier Detect (DCD) control signal has been turned ON.

Link down: This event message indicates the composite link is down.

Link up: This event message indicates the composite link is up.

Data and Expansion Channel Event Messages

The following paragraphs describe the event messages in the Data Channel (D1 - D5, DHS, and DNMS) and Expansion Channel (E1-E8) category:

Bad EEPROM: This event message indicates the system has detected bad EEPROM.

Bad Module: This event message indicates the system has detected a bad expansion card. The group portion of the message (X1-X8) indicates the channel/card that is bad. This message is only applicable to expansion channels.

Clear Buffer

When the Clear Buffer function is selected from the Events Menu, the system will clear the contents of the event buffer. All event message are deleted.

Event Count

The Event Count field in the Events Menu indicates the number of event messages stored in the system's event buffer. The following example Events Menu shows a count of 98 messages:

EVENTS MENU Event Display Clear Buffer Event Count: 98

The system can maintain up to 99 event messages in the event buffer. After the 99th event, new events will write over the oldest events stored in the buffer. These events are listed in the following tables.


Table 15-1: Base System Event Summary
Major Code Minor Code Description

00h

Miscellaneous

00h

System Reset

01h

Old Time/Date (generated only if modified from SDM-FP

02h

New EEPROM (on Config Update)

03h

Bad EZEPROM (on Config Update)

04h

OS Failure

05h

Bad Flash Erase

06h

Bad Flash Write

07h

Bad Flash Update

08h

Link Up

09h

Watch Dog Timeout

0Ah

DCD on

0Bh

DCD off

0Ch

New Time/Date

0Dh

Link Down

0Eh

Reserved

0Fh

Failed PS1 (primary power supply)\

10h

Reserved

15h

Evt Que Overflow

02h

NMS (not available)

00h

Primary NMS Conn

01h

Primary NMS Disc

02h

Primary NMS To
(due to keep alive expiration)

03h

Secondary NMS Conn
(due to keep alive expiration)

04h

Secondary NMS Disc

05h

Secondary NMS to
(due to keep alive expiration)

03h

Propak Algorithm

00h

Bk1 S0 ATC-01

01h

Bk1 S0 ATC-03

02h

Bk1 S0 ACELP8K

03h

Bk1 S0 ACELP4.8K

04h

Bk1 S0 IMBE

05h

Bk1 S0 ATC-01

06h

Bk1 S0 ATC-03

07h

Bk1 S1 ACELP8K

08h

Bk1 ACELP4.8k

09h

Bk1 S1 IMBE

0Ah

Bk3 S0 ATC-01

0Bh

Bk3 S0 ATC-03

0Ch

Bk3 S0 ACELP8K

0Dh

Bk3 S0 ACELP4.8K

0Eh

Bk3 S0 IMBE

0Fh

Bk3 S1 ATC-01

10h

Bk3 S1 ATC-03

11h

Bk3 S1 ACELP8K

12h

Bk3 ACEL4.8K

13h

Bk3 S1 IMBE


Table 15-2: Data Channel Event Summary
Major Code Minor Code Description

00h

Miscellaneous

02h

New EEPROM (on configupdate)

03h

Bad EEPROM (on config update)

11h

V.11 - CI off

12h

V.11 - CI on

13h

Reserved


Table 15-3: Voice Channel
Major Code Minor Code Description

00h

Miscellaneous

02h

New EEPROM

03h

Bad EEPROM

01h

Algorithm

00h

Reserved

01h

Reserved

02h

Reserved

03h

No ATC-01 S/W

04h

No ATC -03 S/w

05h

No ACELP8K S/W

06h

No ACELP4.8K S/W

07h

No IMBE S/W

08h

V C Conflict

09h

Security Error

0Ah

S/W Load Failure

0Bh

Flow Cntl Ind RX (not available)

0Ch

Flow Cntl Ind Tx (not available)


Table 15-4: SVC Events Summary
Major Code Minor Code Description

00h

SVC - Q 9.22

00h

Inactive (on power up, it is determined that Q.922 is not to be activated)

01h

Reset (Q9.22 reset has occurred)

02h

Failed (Q9.22 failure has occurred)

03h

Active (Q.922 multiple frame acknowledged mode of operation has been established)


Table 15-5: IEC Data Card
Major Code Minor Code Description

00h

Frame Relay LMI

00h

LMI user down (number of error events is greater or equal to N392 on the user side)

01h

LMI user up (number of error event is less than N392 on user side

02h

LMI net down (number of error events is greater or equal to N392 on network side)

03h

LMI net up (number of error events is less than N392 on the network side

01h

PVC

00h

PVC New (new PVC is configured)

01h

PVC Act (PVC is activated)

02h

PVC !Act (PVC is deactivated)

03h

PVC Del (PVC is deleted)

04h

LMI New
(new PVC reported through the LMI full status)

05h

LMI New+
(new PVC confirmed through LMI full status)

06h

LMI Del
(Deleted PVC reported through LMI full status)

07h

LMI Act (activated PVC reported through LMI full status)

08h

LMI !ACT
(inactive PVC reported through LMI full status)

09h

LMI! Rdy (Ready PVC not reported through
LMI full status)

0Ah

LMI Rdy
(PVC is reported through LMI full status)

0Bh

LMI !Rep PVC is not reported any more through LMI full status)

0Ch

LMI Rep
(network side started reporting PVC status)


Table 15-6:
Major Code Minor Code Description

03h

Hardware

00h

Non volatile memory failure

04h

Remote Bridge

00h

Bridge restarted

01h

Becoming boot bridge

02h

Port number is root port

03h

Port up

04

Port down

05h

Topology change detected

IEC LAN Card (not available)

Table 15-7: IEC ISMOD Card
Major Code Minor Code Description

05h

Modulator hardware

00h

Synthesizer out of lock

01h

Transmission off

02h

General failure

06h

TBD

07h

RF

I

Table 15-8: IEC DEMOD Card
Major Code Minor Code Description

08h

Hardware

09h

TBD


Table 15-9: General Intelligent Expansion Card
Major Code Minor Code Description

00h

Miscellaneous

00h

Old IEC software (old version of intelligent expansion card software detected and consequently new features may not work.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Jan 25 14:16:07 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.