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

Table of Contents

Outstanding Events Management Function

Outstanding Events Management Function

Definition

This internal service makes it possible to consult, at any time, outstanding events affecting the equipment. The outstanding events are classified per family and identified by their ACO Nos.

Access

The syntax of the access code is:

  DNIC ZO 99 D IS No PASSWORD ACO No (CR)

Chapter 1 provides a detailed breakdown of this code.


Table 3-1: Outstanding Events Access Code Breakdown
Code Distribution

01

02

15

16

Binary

ASCII

Clear language—distribution of line status (family 04)

Clear language—distribution of clears and resets
(10 outstanding events recorded).

· PASSWORD

exists if configured (EE by default)

· ACO No

The breakdown of the ACO suffix is:

  ACO = FA + Line No

FA:

outstanding event family number whose reports can be observed (see Table 3-2).


The family number is entered in decimal and displayed in hexadecimal.

· Line No

Number of line concerned.

The ACO No. may have the following formats:

    1. ACO No. absent:

  All outstanding events of the families and of all the lines are distributed.

    2. Only the FA No. is specified:

  All outstanding events of the family specified and all the lines are distributed.

    3. The FA No. and line No. are specified:

  All outstanding events of the family and of the line specified are used.

    4. FA No. = 99 and line No. is specified:

  All the outstanding events of all the families, but of the specified line are distributed.

Note The FA No. must correspond to a family in which the outstanding events are generated by a line. Otherwise (families 00, 01, etc.), the call is cleared with a diagnostic 184 (family No. incorrect).

The outstanding events of the families not depending on any line (family 00, 01, etc.) are not distributed.

In the following cases, the access is refused:

The line number is optional; it makes it possible to limit the generation of outstanding events to the specified line.


Table 3-2: FA Number Breakdown
FA (decimal) FA
(hexadecimal)
Family

00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

27

00

01

02

03

04

05

06

07

08

09

0A

0B

0C

0D

0E

0F

10

11

12

13

14

15

16

17

18

19

1B

Trouble reporting

Management

Signalling

X.25 procedure

Link

Line, physical level

Asynchronous line, protocol level

Asynchronous line, command level

Asynchronous line, semantic level

SDLC procedure

VIP procedure

Transport procedure - VIP, FRAD, BSC, FRT, FRIP

DLC/BSC procedure

Multi-link procedures (MLP)

X.25 - PSTN procedure

ESV securized virtual circuits

N4 securized virtual circuits

IR securized virtual circuits

ISDN, channel D

X.29 rerouting

Ethernet Bridge and IP router

Procedure DLC/MTR - FRAD - RAD, FRT, FRIP

Compression procedure

Dynamic routing procedure (DLM)

Configuration function

LM function

SNA on frame relay (FRSNA)


Note The OEV families of a B-channel (ISDN) are identical to those of an X.25 line.

Functions of outstanding event families

Trouble reporting (family = 00)

This family contains the trouble reports created following the system reset.

Management (family = 01)

These events concern trouble encountered in remote software implementation by a management center.

Signalling (family = 02)

These events concern trouble encountered in the processing of call requests from a private network.

X.25 procedure (family = 03)

These events concern all trouble in connection with the procedures, on the level 2 and 3 (X.25 or, inter-module links or inter-unit links).

Link (family = 04)

These events report when the links go in service and out of order (physical lines, inter-module links or inter-unit links).

Physical line (family = 05)

These events are produced by all transitions detected in the physical line.

Asynchronous line—Protocol level (family = 06)

These events are produced by any trouble detected in the asynchronous line.

Asynchronous line—Command level (family = 07)

These events are produced by any syntax errors detected in commands.

Asynchronous line - Semantic level (family = 08)

These events concern the control of asynchronous link activity (communication, X.29 message reception, triggering of supervision times for the telephone link).

SDLC procedure (family = 09)

These events concern any trouble relative to the SDLC procedure.

VIP procedure (family = 0A)

These events concern any trouble relative to the VIP procedure.

T.VIP, BSC, FRAD and DAR family (family = 0B)

These events relate to all problems concerning transport for the procedures VIP, FRAD, BSC, DAR, FRT and FRIP on X.25 network.

DLC/BSC (family = 0C)

These events concern any trouble relative to the DLC/BSC procedure.

MLP (family = 0D)

These events are produced when any trouble is detected in the Multi Link Protocol (MLP).

X.25-PSTN (family = 0E)

These events concern any trouble of an X.25 line with PSTN back-up.

ESV securized VCs (family = 0F)

These events are produced when any trouble is detected in the securized ESV procedure (ESV: virtual session entity).

N4 securized VCs (family = 10)

These events are produced when any trouble is detected in the securized N4 procedure (N4: level 4).

IR securized VCs (family = 11)

These events are produced when any trouble is detected in the securized IR procedure (IR: network interface).

ISDN, channel D, SW VN2/3 (family = 12)

These events are produced when any trouble is detected in the ISDN, channel D procedures (ISDN: Integrated Switched Data Network).

X.29 rerouting (family = 13)

These events are produced when any trouble is detected in X.29 rerouting.

Ethernet Bridge and IP router procedure (family = 14)

These events concern stabes and anomalies relative to the Ethernet Bridge and IP Router functions.

DLC/MFR-FRAD and DAR (family = 15)

These events relate to all problems concerning the procedures of the DAR, DLC and MRT of the FRAD, DLC and MTR of the IRT and FRIP.

DLC =

Data Link Control

MFR =

Multi-Frame

FRAD =

Frame Relay Assembler/Disassembler

DAR =

Dynamic Adaptative Routing

Compression (family = 16)

These events are produced when the compression function is switched on or switched off and when any failures are detected.

Dynamic routing procedure (DLM) (family = 17)

These events are relative to all trouble related to the dynamic routing procedure of the DLM function.

Configuration function (family = 18)

These events relate to the CONFIGURATOR management function.

LMI function (family = 19)

These events relate to the LMI function.

SNA on frame relay (FRSNA) (family = 1B)

These events relate to the SNA statuses and problems on FR.

Contents of the messages distributed

ASCII mode

A message transmitted by the outstanding events function is in Figure 3-1.


Figure 3-1: Outstanding Events Message

Clear-language mode

The following types of outstanding events are distributed in clear language:

Outstanding events of family 04

EQUIP No : ------

DATE : --/--/-- TIME --/--/--

HS LINK No : --

Clears or resets received or generated by an equipment item

CLEAR CAUSE --- DIAG --- FUNC No --- LC No ---

RESET CAUSE --- DIAG --- FUNC Nº --- LC Nº ---


Note FUNC No = Line No specified in class 1, recurrence 1.

Descriptions of outstanding events

Outstanding events are described in the appendices at the back of this section.


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