cs ext irs 7 2 working groups library/acp-… · 515 : srv degradation in case of cpu overload (no...

ARTASExternal Interface Requirements Specification(EIRS)

Version 7.2

11.11.2005

Prepared for: EUROCONTROL

Contract No: C/1.230/HQ/BE/01

Doc−ID: ARTAS − 46 127 300 − 506

Status: Accepted

COMSOFT

Approval

Version Quality Manager / Date Project Manager / Date

V7.2_____________________________

(Ludwig Merz)

______________________________

(Dr. Erwin Mayer)

Version Customer Representative / Date

V7.2 __________________________________________________________________

(Costas Christodoulou)

EUROCONTROL

European Organisation for the Safety of Air Navigation

Rue de la Fusée, 96

B−1130 Bruxelles

Phone +32 2 729 31 56

Fax +32 2 729 90 86

COMSOFT GmbH

Wachhausstraße 5a

D−76227 Karlsruhe

Phone +49 721 9497 − 0

Fax +49 721 9497 − 129

ARTAS External Interface Requirements Specification (EIRS)

i46 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

Revision History

REV. DATE No. DE DESCRIPTION RESPONSIBLE

D1.0

D1.1

1.2

1.3

1.4

1.5

3.0

3.1

09/02/94

28/04/94

06/05/94

21/07/94

27/01/95

03/04/95

12/10/98

10/12/98

First Issue : External Interfaces Architecture for phases

1.2. Remaining ASTERIX questions.

Version for SSR

Version for SSR including ECP [1].

Version taking into account comments of the Technical

Review and ECP [12]

Version taking into account comments DED.3/SUR/

ARTAS.FAX.158

Version taking into account comment in FAX.292.

In this version, the revision bars to make the

comparison with version 1.3 have been kept.

Update of the main part of the document for ARTAS

phase 3

Version taking into account comments DED.3/SUR/AR-TAS.COM323 and DED.3/SUR/ARTAS/e−mail/98102

A. BODENAN

A. BODENAN

A. BODENAN

A. BODENAN

A. BODENAN

A. BODENAN

S. MARCHADOUR

S. MARCHADOUR

ARTAS External Interface Requirements Specification(EIRS)

ii 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

Revision History


4.d

4.0

07/05/99

12/07/99

Update including :ECP 401 (Bias estimation monitoring) : no impactECP 402 (Addition of single track number)ECP 403 (Elaboration of track altitude and mode C) :no impactECP 406 (Extension of ARTAS Unit DOI maximumsize)ECP 408 (Backup radar in radar synchronized service): no impactECP 409 (Centralized supervision)ECP 411 (PDC over TCP/IP)ECP 412 (Reduction of Adjacent Units dependences incase of inter−units disconnection) : no impactECP 413 (Management of inter−units connections) : noimpactECP 415 (Double number of tracks to be processedand to be served per user) : no impactECP 416 (Audible alert in case of node status transi-tion) : no impactECP 417 (Confirmation in Artas System Control Menu): no impactECP 418 (Suppression of items in the static radar database) : no impact

Other updates including rewording, clarification anddiscrepancies handling.

The revision bars are marked w.r.t. the version 3.1−Add of note (5) for the attributes available in writting forthe class Artas System− Add of paragraph “Class Artasnode scm status” in the interface with the CentralizedSupervision

− Updates taking into account :EC comments (DIS/SUR/ARTAS/e−mail/99030)ATM quality comments

S. MARCHADOUR

S. MARCHADOUR


iii46 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

Revision History


5.0

5.1

06/09/99

25/10/99

Update including :

ECR 501 − 5 : Data prep. & consultation facility (Noimpact)ECR 502 − 2 : Extension of zoom scale in ASW (Noimpact)ECR 503 − 3 : New behavior in case of MMS CSCIrestart or startover (No impact)ECR 504 − 3 : Quick initialization with the Track modeAECR 505 − 4 : Service of Sensor InformationECR 506 − 3 : Increase of the runway width (Noimpact)ECR 507 − 3 : Quick initiation and termination onrunways (No impact)ECR 508 − 5 : Suppression of civil Emergency codeindicatorsECR 509 − 2 : Extend the number of blanking areas(No impact)ECR 510 − 6 : Management of several external LANsECR 511 − 4 : Broadcast mode number increaseECR 512 − 3 : Server and User identification rules inAsterix messages

− Comments from STNA(DIS/SUR/ARTAS/e−mail/99163)

− Other updates including rewording, clarification anddiscrepancies handling.

The revision bars of this version are defined w.r.t. version4.0.

This version includes :− EUROCONTROL comments(DIS/SUR/ARTAS/e−mail/99228) and AIRSYS ATManswers (ARTAS/e−mail/V5/SM/99022)

S. MARCHADOUR

S. MARCHADOUR


iv 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

Revision History


6.0

6.1

25/02/00

23/08/00

Version corresponding to the so−called V6A

Update to integrate :

−the following CAMOS ECPs :

419 : Asterix modification : maximum data flow (no im-pact)

421 : Measured track mode C w.r.t. not valid and/orgarbled plot mode C (no impact)

422 : Mode C credibility computation (no impact)

423 : Ages computation in case of late plot handling (noimpact)

425 : External timing source failure report

426 : Clock synchronization with NTP

428 : Display choice through the Artas System Controlmenu (no impact)

− the following V6 ECRs/ECPs :

420 : Inhibition of the use of the biases calculated bythe Server function (no impact)

424 : Number of pre−selected tracks forcorrespondence (no impact)

427 : Modification on management of radar status inradar synchronized services (no impact)

513 : Elementary Surveillance

514 : Suppression of 2 items in Static Radar Database(no impact)

515 : SRV degradation in case of CPU overload (noimpact)

516 : Amalgamation for track altitude and track flightlevel (no impact)

517 : Asterix modification for the service identification(no impact)

− Other updates including rewording, clarification anddiscrepancies handling.

The revision bars of this version are defined w.r.t. version5.1.

This version includes :

− agreed answers to EC comments(DIS/SUR/ARTAS/e−mail/00216)

− agreed answers to ATM Quality comments

M.C. DAVID

M.C. DAVID


v46 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

Revision History


6.2

6.3

6.4

20/09/00

24/11/00

03/07/01

Version corresponding to the so_called V6B

Update to integrate :

−the following CAMOS ECPs :

429 : Restoration of former activated areas & MREAfunctionalities at radar reconnection (no impact)

− the following V6 ECPs :

518 : Estimation of height from speed (no impact)

519 : Incorporation of an outlier model in the mode CIMM filter (no impact)

520 : Change the initialization of the vertical state in thetrack initiation (no impact)

600 : Management of IP Multicast protocol for radarinformation reception

[pages 4, 6, 7, 9, 29 to 33, 42, 54]

601 : Improvement of SSR false tracks classification(no impact)

− Other updates including rewording, clarification anddiscrepancies handling [pages 59, 60]

The revision bars are with respect to version 6.1

− modification according to comments and answers(e−mail MCD00069, e−mail DHt/00−006)

[pages 1, 6, 9, 29 to 33, 42, 59, 60, 68]

− Appendix updates [pages A−7, A−12 to A−15, A−17to A−21]

− Other updates including rewording, clarification anddiscrepancies handling [pages 9]

Version corresponding to the so_called V6B1. The revisionbars are with respect to version 6.3

Update to integrate:

− the following CAMOS ECPs

430 : time stamp inconsistency detection (no impact)

431 : Host−id for RMCDE header output (no impact)

603 : Use UDP/IP protocol for broadcast users [page 9,20, 21]

605 : Distinguish between LAN failure and LANcontroller failure [pages 61, A−15, A−16, A−22]

M.C. DAVID

D. HONDET

D. HONDET


vi 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

Revision History


6.5

6.6

10/08/01

03/06/02

606 : logging of external commands (no impact)

607 : Add a free field in MMS configuration file for dis-play [page 46]

− The following CAMOS ATR:

476 : Tracks lost during RBR swichover (no impact)

− Other updates [page 62, A−16]

− agreed answers to AIRSYS−ATM Quality comments

Integration of ATR 653 [page 60, 61]

Update of EXT IRS for:ATR 733 EXT IRS documentation update, Chapt.3.6.3.1.3 Events ; 3.6.3.6.2 Events;3.6.3.7.1 Attributes available for reading;3.6.3.7.3 Events;3.6.3.8.3 Events;Updated References concerning Asterix Documenta-tionNew Layout

P. BOCHET

I. Erbs


vii46 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

Revision History


6.7 16/04/04 Removal of revision bars;

Update of EXT IRS for:

ACP 184, No Information in ARTAS MIB on local clockdevices, Chapt. 3.6.3.2 CLASS ARTAS NODE, Chapt.3.6.3.2.1 Attributes available for reading;

ACP 199, Sending of a ”Hello” trap, Chapt. 3.6.3.1.1Attributes available for reading, Chapt. 3.6.3.1.2 Attributesavailable for writing, Chapt. 3.6.3.1.3 Events, AppendixA1, 10.1. ARTAS MIB DEFINITION, 10.2. ARTAS TRAPMIB DEFINITION

ACP 144, Extended information on status of processing ofSNMP SET commands, Chapt. 3.6.3.1.1 Attributesavailable for reading, Chapt. 3.6.3.1.2 − Attributesavailable for writing, Chapt. 3.6.3.1.3 − Events, Chapt.3.6.3.2.1 − Attributes available for reading, Chapt.3.6.3.2.2 − Attributes available for writing, Chapt. 3.6.3.2.3− Events, APPENDIX A1, 10.1. ARTAS MIB DEFINITION,10.2. ARTAS TRAP MIB DEFINITION;

ACP 137, Degradation of RBR CSCI because of too manyrequests to LMS agent, Chapt. 3.6.2 COMMUNICATIONPROTOCOL, Chapt. 3.6.3.6.1 Attributes available forreading;

ACP 185, Lack of information in centralised supervisionand in ARTAS MIB when a mode of operation is degraded,Chapt. 3.6.3.6.1 Attributes available for reading, Chapt.3.6.3.6.2 Events, Chapt. 3.6.3.7.1 Attributes available forreading, Appendix, 10.1. ARTAS MIB DEFINITION, 10.2.ARTAS TRAP MIB DEFINITION

I. Erbs

7.0 17/09/04 Update of EXT IRS for changes due to V7A0 developmenton top of V6B2 Baseline documentation.

Extension of Chapt. 2 APPLICABLE DOCUMENTS

Update of Chapt. 3.1 OVERVIEW OF THE EXTERNALINTERFACES

Update of Chapt. 3.2.1.2 COMMUNICATION PROTOCOL

Replacement of following Chapters: Chapt 3.2.1.2.3NETWORK LAYER; 3.2.1.2.4 TRANSPORT LAYER;3.2.1.3 APPLICATION PROTOCOL

Chapt. 3.2.1.3.1 − 3.2.1.3.3 have been added

Chapt. 3.2.1.4 DATA AND MESSAGES TRANSFERREDis changed

I. Jaki


viii 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

Revision History


7.0 17/09/04 Replacement of following Chapters (partially): Chapt.3.2.2.3 APPLICATION PROTOCOL; Chapt. 3.3.1FUNCTION; Chapt. 3.3.3 APPLICATION PROTOCOL;3.3.4 DATA AND MESSAGES TRANSFERRED

Chapt. 3.4.2 COMMUNICATION PROTOCOL, Re-moval of figure 10 PROTOCOL FOR ADJACENT UNITSINTERFACE

Replacement of following Chapters (partially): 3.4.2.3NETWORK LAYER; 3.4.2.4. TRANSPORT LAYER; 3.4.3APPLICATION PROTOCOL; 3.4.4 DATA ANDMESSAGES TRANSFERRED; 3.5.4.1.2 ASTERIXCategory 048; 3.5.4.2.2 ASTERIX Category 034

Chapt. 3.6 ADS−B GROUNDSTATION INTERFACESPECIFICATION (IF_RBR_ADS) has been added

Replacement of following Chapter: 3.7.3.7.1 Attributesavailable for reading; 3.7.3.7.2 Attributes for writing

Extension of Chapt. 3.7.3.8.1 Attributes available for read-ing

Change for ATR 832, a new Chapt. is added on AppendixA1, section 10.5 DEC ELAN MIB

Appendix changes in A1, sections 10.1; 10.2; 10.4; 10.5

I. Jaki

7.1 29/10/04 Update of EIRS due to review in following Chapters:

Chapt. 1.2 SYSTEM OVERVIEW

Chapt. 2 APPLICABLE DOCUMENTS

Chapt. 3.2.1.2 COMMUNICATION PROTOCOL

Chapt. 3.7.3.5 CLASS ARTAS NODE DUAL NODESTATUS and following Chapters

Chapt. 3.6 ADS−B GROUNDSTATION INTERFACESPECIFICATION (IF_RBR_ADS)

Chapt. 3.7.3.6.1 Attributes available for reading

Chapt. 3.7.3.6 .2 Events

Chapt. 3.7.3.9.2.1 Attributes available for reading;

The changes of Chapt. 3.7.3.9.4.1 Attributes available forreading are made due to ATR 752

Chapt. 3.7.3.9.4.1 Attributes available for reading

I. Jaki

7.2 11/11/05 Update of EXT IRS for changes due to V7A1 development

ACP 237 IP/Multicast channel definition for radars, 3.3.2.4Transport Layer, 3.5 RADAR INTERFACESPECIFICATION (IF_RBR_RAD), 3.5.2.4 TransportLayer, 3.5.3 APPLICATION PROTOCOL, 3.6 ADS−BGROUNDSTATION INTERFACE SPECIFICATION(IF_RBR_ADS), 3.6.2.4 Transport Layer, 3.6.3APPLICATION PROTOCOL

I. Jaki


ix46 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

Revision History


7.2 11/11/05 ATR 1006 Wrong reference in EXT IRS V7

2 Applicable Documents; 3.2.1.2.4 Transport layer; 3.4.2.4Transport layer; 3.6.4.1 ADS−B Message

ACP 230 Include sensor disconnection cause in MIB;3.7.3.9.1 Attributes available for reading, 3.7.3.9.3 Events

ACP 189 Make Netrain device and Syslan_mngcompatible; 3.2.1.2.2 Data link layer, 3.3.2.2 DATA LINKLAYER, 3.4.2.2 DATA LINK LAYER, 3.5.2.2 DATA LINKLAYER, 3.6 ADS−B GROUNDSTATION INTERFACESPECIFICATION (IF_RBR_ADS), 3.6.2.2 DATA LINKLAYER

ACP 227 Support for Additional BDSs; 3.5.4.1.2 ASTERIXCategory 48

ACP 267 Migrate ASTERIX CAT 65 from v0.12 to vl.1;3.2.1.3.3 CAT 065 SDPS Service Status Messages

ACP 205_223 Enhancement of system capacity limits;3.2.1.4 DATA AND MESSAGES TRANSFERRED,3.7.3.1.1 Attributes available for reading

Introduce Cat23 sensor monitoring for ADS−B sensors:3.6.4 DATA AND MESSAGES TRANSFERRED (insertparagraph for CAT023: 3.6.4.2 CSN/ATM ground stationservice message

I. Jaki


x 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

CONTENTS

Pages

1 − SCOPE 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 − IDENTIFICATION 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 − SYSTEM OVERVIEW 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 − DOCUMENT OVERVIEW 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.1 − DOCUMENT OBJECTIVES 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 − DOCUMENT CONTENT 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 − APPLICABLE DOCUMENTS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 − INTERFACES SPECIFICATION 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 − OVERVIEW OF THE EXTERNAL INTERFACES 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 − NORMAL USERS INTERFACE SPECIFICATION (IF_RBR_USR) 10 . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 − NORMAL USER EXCEPT FPPS USER 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.1 − Function 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.2 − Communication protocol 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.2.1 − Physical layer 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.2.2 − Data link layer 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.2.3 − Network layer 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.2.4 − Transport layer 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.3 − Application protocol 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.3.1 − CAT 062 System Track Data Messages 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.3.2 − CAT 063 Sensor Information 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.3.3 − CAT 065 SDPS Service Status Messages 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.4 − Data and messages transferred 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.5 − Data rate of flow 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 − FPPS USER 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2.1 − Functions 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2.2 − Communication protocol 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2.3 − Application protocol 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2.4 − Data and messages transferred 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2.5 − Data rate of flow 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 − BROADCAST MODE INTERFACE SPECIFICATION (IF_RBR_BRC) 24 . . . . . . . . . . . . . . . . . . . . . . 3.3.1 − FUNCTION 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2 − COMMUNICATION PROTOCOL 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2.1 − Physical layer 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2.2 − Data link layer 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2.3 − Network layer 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2.4 − Transport layer 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.3 − APPLICATION PROTOCOL 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4 − DATA AND MESSAGES TRANSFERRED 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5 − DATA RATE OF FLOW 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


xi46 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

3.4 − ADJACENT UNIT INTERFACE SPECIFICATION (IF_RBR_ADJ) 28 . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1 − FUNCTION 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2 − COMMUNICATION PROTOCOL 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.1 − Physical layer 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.2 − Data link layer 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.3 − Network layer 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2.4 − Transport layer 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.3 − APPLICATION PROTOCOL 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.4 − DATA AND MESSAGES TRANSFERRED 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.5 − DATA RATE OF FLOW 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 − RADAR INTERFACE SPECIFICATION (IF_RBR_RAD) 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1 − FUNCTION 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2 − COMMUNICATION PROTOCOL 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2.1 − Physical layer 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2.2 − Data link layer 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2.3 − Network layer 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2.4 − Transport layer 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.3 − APPLICATION PROTOCOL 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4 − DATA AND MESSAGES TRANSFERRED 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4.1 − Monoradar Target Reports 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4.1.1 − ASTERIX Category 001 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4.1.2 − ASTERIX Category 048 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4.2 − Monoradar Service Messages 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4.2.1 − ASTERIX Category 002 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4.2.2 − ASTERIX Category 034 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4.3 − RMCDE messages 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.5 − RADAR DATA RATE OF FLOW 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 − ADS−B GROUNDSTATION INTERFACE SPECIFICATION (IF_RBR_ADS) 49 . . . . . . . . . . . . . . . . . 3.6.1 − FUNCTION 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2 − COMMUNICATION PROTOCOL 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2.1 − Physical Layer 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2.2 − Data Link Layer 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2.3 − Network Layer 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2.4 − Transport Layer 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.3 − APPLICATION PROTOCOL 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.4 − DATA AND MESSAGES TRANSFERRED 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.4.1 − ADS−B Message 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.4.2 − CSN/ATM ground station service message 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.4.3 − ADS−B DATA RATE OF FLOW 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 − CENTRALIZED SUPERVISION INTERFACE SPECIFICATION (IF_ART_SNMP) 56 . . . . . . . . . . . . 3.7.1 − FUNCTION 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.2 − COMMUNICATION PROTOCOL 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3 − DATA AND MESSAGES TRANSFERRED 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.1 − CLASS ARTAS SYSTEM 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.1.1 − Attributes available for reading 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.1.2 − Attributes available for writing 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.1.3 − Events 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.2 − CLASS ARTAS NODE 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.2.1 − Attributes available for reading 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


xii 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

3.7.3.2.2 − Attributes available for writing 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.2.3 − Events 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.3 − CLASS ARTAS UBSS PROXY NODE 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.4 − CLASS ARTAS PROXY NODE 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.5 − CLASS ARTAS NODE DUAL NODE STATUS 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.5.1 − Attributes available for reading 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.6 − CLASS ARTAS TRAP FILTER STATUS 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.6.1 − Attributes available for reading 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.7 − CLASS ARTAS NODE SCM STATUS 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.7.1 − Attributes available for reading 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.7.2 − Events 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.8 − CLASS ARTAS FUNCTION 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.8.1 − Attributes available for reading 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.8.2 − Events 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.9 − CLASS ARTAS RADAR 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.9.1 − Attributes available for reading 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.9.2 − Attributes available for writing 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.9.3 − Events 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.10 − CLASS ARTAS USER 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.10.1 − Attributes available for reading 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.10.2 − Attributes available for writing 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.10.3 − Events 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11 − OTHER MANAGED OBJECT CLASSES 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.1 − Peripherals 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.2 − External timing source device 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.2.1 − Attributes available for reading 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.2.2 − Events 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.3 − Internal LAN devices 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.4 − External LANs status 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.4.1 − Attributes available for reading 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.4.2 − Events 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.3.11.5 − Centralised supervision private information 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8 − TIME INTERFACE SPECIFICATION (IF_RBR_CLK) 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.1 − PHYSICAL CONNECTION OVERVIEW 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.1.1 − Gorgy RT3000 time center 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.1.2 − NTP 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2 − DATA REQUIREMENTS 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2.1 − Gorgy RT3000 time center 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2.1.1 − Transmitters characteristics 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2.1.2 − Degraded mode 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2.1.3 − Transmission characteristics 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2.2 − NTP 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2.2.1 − Transmitter characteristics 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2.2.2 − Degraded mode 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 − QUALITY ASSURANCE 87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 − PREPARATION FOR DELIVERY 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 − GLOSSARY 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


xiii46 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

LIST OF FIGURES

Pages

FIGURE 1 − GENERAL INTERFACE DIAGRAM 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 2 − CONNECTION TO THE EXTERNAL LANS 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 4 − CAT 065 SDPS STATUS MESSAGE 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 5 − CAT 065 END OF BATCH MESSAGE 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 6 − CAT 065 BROADCAST SERVICE MESSAGE 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 7 − MESSAGES SENT BY NORMAL USERS FOR THE TRACK SERVICE 17 . . . . . . . . . . . . . . FIGURE 8 − MESSAGES SENT BY NORMAL USERS FOR THE SENSOR SERVICE 18 . . . . . . . . . . . . FIGURE 9 − PROTOCOL FOR BROADCAST USERS INTERFACE 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 10 − PROTOCOL FOR ADJACENT UNITS INTERFACE 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 11 − BASIC RULES FOR THE TRACKING CONTINUITY 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 12 − RADAR CONNECTION TO AN ARTAS UNIT 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 13 − PROTOCOL FOR RADAR INTERFACE 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 14 − ORADIS USER DATA MESSAGE 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 15 − ADS−B DATA SOURCE CONNECTION TO AN ARTAS UNIT 49 . . . . . . . . . . . . . . . . . . . . . FIGURE 16 − PROTOCOL FOR ADS−B DATA SOURCE INTERFACE 50 . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 17 − ORADIS USER DATA > MESSAGE 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIGURE 18 − PROTOCOL FOR THE CENTRALIZED SUPERVISION 56 . . . . . . . . . . . . . . . . . . . . . . . . . .


xiv 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

LIST OF TABLES

Pages

TABLE 1 − external interfaces 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 2 − ASTERIX CAT 062 Items for Track Information 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 3 − CAT 063 Broadcast Sensor Information 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 4 − asterix category 001 items for plot information 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 5 − asterix category 001 items for track information 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 6 − asterix category 048 items for plot & track information 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 7 − asterix category 002 items for north / south markeR 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 8 − asterix category 002 items for sector crossing messageS 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 9 − asterix category 034 items for north markeR 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 10 − asterix category 034 items for Sector crossing Messages 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 11 − ASTERIX CAT 021 Items for ADS−B Message Information 54 . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 12 − ASTERIX CAT 023 Items for GS Status Message 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 13 − ASTERIX CAT 023 Items for GS Service Status Message 55 . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 14 − CLASS ARTAS SYSTEM − ATTRIBUTES FOR READING 59 . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 15 − Class artas system − attributes for writing 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 16 − class artas system − events 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 17 − class artas node − attributes for reading 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 18 − class artas node − attributes for writing 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 19 − class artas node − events 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 20 − class artas ubss proxy node − attributes for reading 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 21 − class artas proxy node − attributes for reading 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 22 − CLASS ARTAS NODE DUAL NODE STATUS − attributes for reading 69 . . . . . . . . . . . . . . . . TABLE 23 − CLASS ARTAS TRAP filter STATUS − attributes for reading 69 . . . . . . . . . . . . . . . . . . . . . . . . TABLE 24 − class artas node scm status − attributes for reading 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 25 − class artas node scm status − EVENTS 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 26 − class artas function − attributes for reading 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 27 − class artas function − events 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 28 − class artas radar − attributes for reading 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 29 − class artas radar − attributes for writing 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 30 − class artas radar − events 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 31 − class artas user − attributes for reading 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 32 − class artas user − attributes for writing 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 33 − class artas user − events 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 34 − CLOCK − ATTRIBUTES FOR READING 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 35 − CLOCK − EVENTS 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 36 − EXTERNAL LANs status 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLE 37 − EXTERNAL LANs events 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


xv46 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

LIST OF APPENDICES

Pages

APPENDIX A1 − MIB DEFINITION A1 − 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10. MIB DEFINITION A1 − 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.1. ARTAS MIB DEFINITION A1 − 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2. ARTAS TRAP MIB DEFINITION A1 − 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3. DEC HUB 900 MIB DEFINITION A1 − 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4. GRAPHIC BOARD MIB DEFINITION A1 − 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


COMSOFT46 127 300 − 506 / V7.2 / 11.11.20051 of 93

1 − SCOPE

1.1 − IDENTIFICATION

The present document defines the external interface specifications of an ATM Surveillance Tracker AndServer (ARTAS) Unit.

SYSTEM IDENTIFICATION NUMBER : 46 127 300 − 506

TITLE : External Interface Requirements Specification

ABBREVIATION : Ext IRS

1.2 − SYSTEM OVERVIEW

Surveillance information play a critical role in the execution of the Air Traffic Control functions. Not only dothey provide, after appropriate processing, an up−to−date picture of the position and in certain cases alsospeed and other dynamic characteristics of all aircraft in the area of concern, but they provide also thecritical input for a number of functions making use of the radar derived aircraft data.

Such functions, in the ARTAS specifications referred to as Users, include Short Term Conflict Alert, FlightPlan Correlation, Military/Civil Coordination, Flow−Control etc.

At the present time a multitude of different Surveillance Data Processing Systems exist varying frommono−radar, mosaic to real multi−radars with a large variation in process sophistication and performance.Furthermore, all the existing systems are more or less autonomous, i.e. that they do not liaise in any waywith neighboring systems.

Due to this present incompatibility of systems, at the transfer of traffic from one ATC unit to another,considerably larger separation minima have to be applied than would be the case if these centres hadcompatible and coordinated systems.

Important advantages created by the introduction of ARTAS will be the very powerful provisions forcontingency, the potential for an enhanced Military/Civil coordination and above all, the capability to presentan accurate and continuous picture of the air situation to the users. It provides to the controllers and ATCsub−systems making use of aircraft derived data all required information with the required level of availabilityand accuracy. Also in favour of a harmonized system are the possibilities of central configurationmanagement, joint elaboration of improvements and commonly organized support.

ARTAS will also carry out information related to the sensors used by ARTAS in order to allow another ATCsystem using these information for local radar data processing (e.g. the fall−back RDPDS or direct displayof mono−radar data).

ARTAS will be designed as a distributed system composed of several individual and identical ARTAS UNITS,whereby the number of Units is a−priori unknown.

Each ARTAS UNIT will be in charge of the following four main functions :


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 2 of 93

1. The TRACKER will process the input surveillance information (from radars and ADS−B data sources) andmaintain the Track Data Base,

2. The SERVER will carry out the Track Information Service itself, i.e. the management of all requests fromUsers and the transmission of the relevant sets of track data to these Users. It will also execute the so−calledinter−ARTAS cooperation functions.

3. The SYSTEM MANAGER will carry out the functions related to the supervision and management of theARTAS Unit,

4. The RECORDING function will record selected data related to the operational use of ARTAS.

Several facilities will be also available :

1. MMS−DM will carry out the functions related to the data base management,

2. SIMARTAS will simulate the communications made with the SERVER by the ARTAS Users,

3. DAF will carry out the functions related to the analysis of data selected for recording.

Furthermore, the capability to have a global view of the functioning of an ARTAS Unit will be offered to aCentralized Supervision, such as a remote ATC Centre supervisor.

1.3 − DOCUMENT OVERVIEW

This document specifies the requirements applicable to the external interfaces identified for the ARTASsystem.

1.3.1 − DOCUMENT OBJECTIVES

The Ext. IRS document is a part of the development baseline for producing and validating each CSCIconcerned by the interfaces with the External Systems.

It allows to manage requirements regarding the interfaces at the System level, so as to ensure interfacechange control.

1.3.2 − DOCUMENT CONTENT

The Ext. IRS document is composed of six main chapters.

Chapter 1 forms the introduction to the Ext IRS document.

Chapter 2 contains the documents referred in this Ext IRS document.

Chapter 3 specifies the requirements related to the interfaces described in this Ext IRS document (externalinterfaces).

Chapter 4, about the Quality Assurance, is not applicable here.

Chapter 5, about the Preparation for Delivery, is not applicable here.

Chapter 6 presents a glossary.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.20053 of 93

2 − APPLICABLE DOCUMENTSThe following documents of the exact issue shown form a part of this specification to the extent specifiedherein. In the event of conflict between the documents referenced herein and the contents of thisspecification, the contents of this specification shall be considered a superseding requirement.

[1] Contract C/1.067/HQ/BE/99 − Amendment no 3/00

[2] Annex 2 of the Contract: ARTAS Specifications

* PART 1: General Requirements and information relevant to the ARTAS project, ref. 3E/T/600.2 ver-sion 2.2. dated 19 May1993,

* PART 2: Functional and Performance Specification, ref. 3E/T/600.1 version 2.2. dated 19 May 1993,

[3] ARTAS Contractor’s ProposalTHOMSON−CSF and NLR − May 1993

[4] EUROCONTROL Standard for Radar Data Exchange, Part 2a : Transmission of Monoradar Traget Re-ports (SUR.ET1.ST05.2000−STD−02a−01, Edition 1.0 − November 1997)

[5] EUROCONTROL Standard for Radar Data Exchange, Part 2b : Transmission of Monoradar ServiceMessages (SUR.ET1.ST05.2000−STD−02b−01, Edition 1.0 − November 1997).

[6] EUROCONTROL Standard Document for Surveillance Data Exchange, Part 4 : Transmission ofMonoradar Target Reports (SUR.ET1.ST05.2000−STD−04−01, Edition 1.14, November 2000)

[7] EUROCONTROL Standard Document for Surveillance Data Exchange, Part 2b : Transmission ofMonoradar Service Messages (SUR.ET1.ST05.2000−STD−02b−01, Edition 1.26, November 2000)

[8] RMCDE User Interface DescriptionEUROCONTROL − Document GD 0048−02 − December 1992.

[9] Specifications Techniques d’Utilisation du Reseau RENARDirection Generale de l’Aviation Civile − Service Technique de la Navigation Aerienne − STUR RENAR Version 2.0 − March 1993.

[10] Realisation et Fourniture d’un Equipement de Diffusion d’Information RadarDirection Generale de l’Aviation Civile − Service Technique de la Navigation Aerienne − 4TX/RENAR/LC/0991/18 − November 1992.

[11] ARTAS System/Segment Specification (SSS) 46 127 300 − 305

[12] ARTAS System/Segment Design Document (SSDD) 46 127 300 − 424

[13] ARTAS Interface Specification : Private Data Channel DED.3/SUR/ARTAS.SPE.028 − Rev 2.0

[14] SUM for System SNMP Agent 46 195 853 − 108 − Rev I

[15] V6B1 ECPs integrated in this revision : 430.4, 431.1, 603.1, 605.2, 606.3, 607.2

[16] SRS Router Bridge 46 127 306 − 306

[17] SRS MMI/Supervision 46 127 304 − 306

[18] ARTAS Version Description Document (VDD) 46 127 300 − 498

[19] Gorgy RT3000 time document (product datasheet edited by Gorgy Timing SA)

[20] RFC 1305 : Network Time Protocol (Version 3) Specification, Implementation (D.L. Mills, March 92)

[21] ARTAS Internal Interface Requirement Specification (INT IRS) 46 127 301 − 506

[22] RFC 1112 : Host extensions for IP Multicasting (S. Deering, August 1989)


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 4 of 93

[23] SOFTWARE USER’S MANUAL (SUM) of the UNIX BASED SYSTEM SOFTWARE (UBSS) 39 797384−108

[24] EUROCONTROL Standard Document for Surveillance Data Exchange − Part 12 : Category 21Transmission of ADS−B Messages (SUR.ET1.ST05.2000−STD−12−01, Edition: 0.20 (Working Draft),December 2002)

[25] EUROCONTROL Standard Document for Surveillance Data Exchange − Part 16 : Category 23CNS/ATM Ground Station Service Messages (SUR.ET1.ST05.2000−STD−16−01, Edition: 0.11(Working Draft), December 2002)

[26] EUROCONTROL Standard Document for Surveillance Data Exchange − Part 9 : Category 62 SDPSTrack Messages (SUR.ET1.ST05.2000−STD−09−01, Edition: 1.0 (Proposed Issue), March 2004)

[27] EUROCONTROL Standard Document for Surveillance Data Exchange − Part 10 : Category 63 SensorStatus Messages (SUR.ET1.ST05.2000−STD−10−01, Edition: 1.0 (Proposed Issue), March 2004)

[28] EUROCONTROL Standard Document for Surveillance Data Exchange − Part 15 : Category 65 SDPSService Status Messages (SUR.ET1.ST05.2000−STD−15−01, Edition: 0.12 (Working Draft), March2003)

[29] EUROCONTROL ARTAS : Application of ASTERIX to ARTAS ADD (DIS/SUR/ARTAS/ASTX.015,Edition: AA03 (Working Draft), August 2003)

[30] ARTAS Interface Requirement Specification − Interface Design Document (INT IRS), Doc−IDARTAS−46 127 301 − 506

[31] Functional and Technical Specification (FTS) for ARTAS for Aircraft Derived Data (ARTAS ADD).Document DIS/SUR/ARTAS/FTS/002. Edition 1 revision 0, 2nd Aug 2002.

[32] Minimum Aviation System Performance Standards for Automatic Dependent Surveillance Broadcast(MASPS for ADS−B, RTCA/DO242, February 19,1999)


COMSOFT46 127 300 − 506 / V7.2 / 11.11.20055 of 93

3 − INTERFACES SPECIFICATION

3.1 − OVERVIEW OF THE EXTERNAL INTERFACES

The following general interface diagram gives a sketch of the ARTAS System with the main ASTERIXcategories and other protocols used.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 6 of 93

ARTAS

USER RMCDE

HARDWAREEQUIPMENT

Ethernet /FDDI

WANRADAR or

ADS−BGroundstation

WAN

RADAR orADS−B

Groundstation

HARDWAREEQUIPMENT

Clock Signal

CAT 001,002,048,034,241,021, 023

CAT 001,002,048,034,021,023

CAT 001,002,021, 048,034

CAT030,031,252

HARDWAREEQUIPMENT

WAN

USER

CAT032,252,063,065,062

ARTAS

CentralizedSupervision

SNMP

NTPServer

NTP

CAT062,063,065

RADAR orADS−B

Groundstation

RADAR orADS−B

Groundstation

FIGURE 1 − GENERAL INTERFACE DIAGRAM


COMSOFT46 127 300 − 506 / V7.2 / 11.11.20057 of 93

An ARTAS Unit is connected to several LANs (Ethernet or FDDI) and has interfaces with Users, Radars,ADS−B ground stations, external timing source (either Gorgy clock or NTP Server) and CentralizedSupervision. The requirements for these interfaces are given in the following paragraphs.

Several users can be connected to an ARTAS unit through a LAN. The number of connected users is limited(see [12]). These users can receive track information or sensor information from the ARTAS Unit Tracks andcan also provide miniplans to the ARTAS unit if the user is a FPPS user or an Adjacent Unit. Two modes ofoperation are available :

− the point−to−point mode which permits a user to set−up a private ”data channel” with ARTAS and thento request his own service from ARTAS,

− the broadcast mode where a common service is broadcasted to a LAN. In this mode the service is de-fined from the relevant supervision position of the ARTAS unit. The users can then ”pick” the informationfrom the LAN. There are 2 different types of broadcast services:

� broadcast via ASTERIX CAT 030, 031, 252

� broadcast via ASTERIX CAT 062, 063, 065

The users connected in a point−to−point mode can be Adjacent Units, or so−called Normal Users (ShortTerm Conflict Alert, Flight Plan Correlation...). A specific LAN can be defined for these point−to−point users.

Up to 6 LANs (depending on the hardware configuration) are available for the users receiving ARTAS trackinformation or sensor information through a broadcast mode.

The users can be connected to ARTAS through a LAN or can be remote users. The latter are drawn indotted lines as far as they are not directly ”seen” by the ARTAS unit.

In order to provide tracks to its users, an ARTAS unit receives plots/local tracks from radars and/or ADS−Breports from the ADS−B data ground stations. These radars and ground stations are connected to theARTAS unit through hardware equipment, on their part connected to up to 2 LANs. This equipment can beRMCDE, SIR, MEGAPAC, �Lines with ORADIS...(see 3.5). Radars and ground stations are drawn in dottedlines in Figure 1, as they are not directly ”seen” by the ARTAS unit. These radars and ground stations canalso be part of a Wide Area Network. For instance this WAN is called RADNET in the frame of a 4−statesenvironment (Benelux/Germany area), and RENAR (refer to [10]) in the French environment.

The total number of connected radars and ADS−B sources is limited (see [12]).

Below is a general diagram of the connections of an ARTAS unit to the LANs with respect to the externalinterfaces.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 8 of 93

ARTAS

UserBroadcast service k

Normal User iFPPS

Normal User j

UserBroadcast Service j

User bBroadcast Service i

Centralized Supervision

1

5

1

2

a2

2

3

3

3

94

a9

4 9 b 9 a9 4

2 32 3

9 a

1

52

3

4Cat 001, 002, 241

Cat 252, 030

Cat 031

Cat 032

SNMP

Classical radar jMode S station i

LAN a

LAN b

LAN c

LAN d

LAN e

LAN f

User aBroadcast Service i

AdjacentARTAS Unit

5

NTPServer

6

6 NTP

1

7

7

7

7 Cat 048, 034, 241

6

ADS−B Groundstation

8 Cat 021, 023

8

8

9 Cat 062, 065

a Cat 063

9

a

2

b Cat 252

bb

9 a b

8

32 3

FIGURE 2 − CONNECTION TO THE EXTERNAL LANSFurthermore it is possible to use an ARTAS unit in the context of a simulation, with the use of a simulatorenabling to simulate radars, ADS−B ground stations and users. As far as there are no specific interfacerequirements for the use of these simulators, they have to be compliant with the interfaces defined for the


COMSOFT46 127 300 − 506 / V7.2 / 11.11.20059 of 93

real radars, ADS−B ground stations or the real users. For instance, it is possible to simulate radars throughthe use of SASS_C/DIVA, or to simulate normal users or users receiving services through a broadcast modewith the use of SIMARTAS.

The external interfaces of an ARTAS Unit are given in the following table with their main characteristics :

INTERFACE DATA TYPE PROTOCOL ATLEVEL 5 TO 7

PROTOCOL ATLEVEL 1 TO 4

NORMAL USERS TRACKS, SENSOR INFORMATION, SER-VICE STATUS MESSAGES, MINI-

PLANS,SESSION AND SERVICE CON-TROL

ASTERIX CAT 062, 063, 065, 032,252

PDC/TCP

BROADCASTMODE

CAT 30

TRACKS, SENSOR INFORMATION,SES-SION AND SERVICE CONTROL

ASTERIX CAT 030, 031, 252 LLC1, MACUDP/IP

BROADCASTMODE

CAT 62

TRACKS, SENSOR INFORMATION,SER-VICE STATUS MESSAGES

ASTERIX CAT 062, 063, 065 LLC1, MACUDP/IP

ADJACENT UNITS TRACKS, MINIPLANS,SESSION ANDSERVICE CONTROL

ASTERIX CAT 062, 032, 252 PDC/TCP

RADARS MONORADAR TARGET REPORTS &SERVICE MESSAGES, RMCDE PROTO-

COL

ASTERIX CAT 001, 002, 241,

ASTERIX CAT 048, 034 (FROMMODE S STATIONS)

LLC1, MACUDP/IP

ADS−B DATASOURCES

ADS−B−TARGET REPORTS

CNS/ATM GROUND STATION SERVICEMESSAGES

ASTERIX CAT 021

ASTERIX CAT 023

LLC1, MACUDP/IP

CENTRALIZED SU-PERVISION

MIB ARTAS SNMP UDP/IP

TIME INTERFACE UTC GORGY ASYNCHRONOUS

UTC NTP UDP

TABLE 1 − EXTERNAL INTERFACES


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 10 of 93

3.2 − NORMAL USERS INTERFACE SPECIFICATION (IF_RBR_USR)

This paragraph aims at defining the interface between ARTAS Units and Normal Users. The Normal Usersare defined as all Users which are connected to the ARTAS Unit in a point−to−point mode and which are notAdjacent Units. The FPPS Users are Normal Users, but they have specific characteristics. Therefore thisparagraph deals first with the Normal Users except the FPPS Users and afterwards takes into account thespecific characteristics of the FPPS Users.

3.2.1 − NORMAL USER EXCEPT FPPS USER

3.2.1.1 − FUNCTION

The main aim of this interface is to provide to Users ARTAS tracks in order to allow them to define an Airsituation picture, or information related to the Sensors used by ARTAS. With respect to this aim, thefollowing functions are defined in the SSS document (see [11]) and are fulfilled through this interface :

− The Normal User connection or disconnection request to an ARTAS Unit (User towards Unit),

− The Normal User service definition (Track or Sensor information) (User towards Unit),

− The Normal User service update (Track information) (User towards Unit),

− The Normal User service control (Track or Sensor information) (User towards Unit),

− The transmission of ARTAS tracks to the Normal Users (Unit towards User),

− The transmission of Sensor information to the Normal Users (Unit towards Users),

− The transmission of acknowledgements from the ARTAS Unit to the Normal Users.

Concerning the Normal Users, messages are then provided from ARTAS Units to Users but also from Usersto ARTAS Units.

3.2.1.2 − COMMUNICATION PROTOCOL

This paragraph deals with the definition of the protocol used for the layer 1 to 4 of the OSI model (ISO7498). The following set of protocols is available for this interface :


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200511 of 93

Physical Layer

LLC1 /MAC

IP

TCP

PDC

FIGURE 3 − PROTOCOL FOR NORMAL USERS INTERFACE

NOTE: The local ARTAS unit will support only the protocol stack in FIGURE 3. The connection of a NormalUser defined with a protocol not compliant with this protocol stack will not be possible.

3.2.1.2.1 − Physical layer

Users shall be connected to the ARTAS Unit through a specific LAN of type CSMA/CD (Ethernet) or FDDI(these Users are defined as the ”local Users”). This specific LAN shall be off−line (configuration file) chosenfor all Normal Users and all Adjacent Units amongst the LANs connected to the Artas Unit.

Remote Users shall use ARTAS Services through the use of hardware equipments themselves connected tothe ARTAS Unit through the LAN defined for the local Users.

3.2.1.2.2 − Data link layer

Concerning the connection of Users and ARTAS Units through a LAN, the data link layer is herein divided intwo layers (see IEEE 802.1) : MAC (Medium Access Control) and LLC (Logical Link Control).

The protocols used for the MAC sub−layer are defined with respect to the type of LAN :

− For an CSMA/CD LAN (Ethernet) the MAC protocol used shall be defined by ISO 8802.3,

− For an FDDI LAN the MAC protocol used shall be defined by ISO 9314.2.

The LLC1 sub−layer protocol, not dependent of the type of LAN, shall be defined by ISO 8802.2.

NOTE: On Tru64 5.1B system platforms it is also possible to bundle several physical LAN devices to form onevirtual LAN in order to achieve a higher availability and reliability. Such a virtual LAN device (”RedundantArray of Independent Network Adapters”, NetRAIN) can also be used as ARTAS User LAN device.

3.2.1.2.3 − Network layer

The protocol supported shall be IP.

3.2.1.2.4 − Transport layer

For the Normal Users, which are point−to−point Users, the protocol used for the Transport layer shall beTCP.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 12 of 93

Furthermore the Private Data Channel (PDC) protocol shall be also used (see [13]). This protocol is anon−standard protocol defined for the communication between redundant systems and enabling atransparent handling of the switch−over of the ARTAS system from the point of view of the communicationprotocol.

3.2.1.3 − APPLICATION PROTOCOL

The messages transmitted through this interface shall be defined with respect to the ASTERIX standardprotocol (see reference document [27]).

3.2.1.3.1 − CAT 062 System Track Data Messages

The track information served by ARTAS is composed of data items of ASTERIX CAT 062.

Data ItemReferenceNumber Description

Mandatory /Optional forASTERIX

Used / Pro-vided byARTAS Note

I062/010 Data Source Identifier M X

I062/015 Service Identification O X

I062/040 Track Number M X

I062/060 Track Mode 3/A Code O X

I062/070 Time Of Track Information M X

I062/080 Track Status M X

I062/100 Calculated Track Position (Cartesian) O X

I062/105 Calculated Track Position (WGS−84) O X

I062/110 Mode 5 Data reports & Extended Mode 1Code SF1− SF7

O X

I062/120 Track Mode 2 Code O X

I062/130 Calculated Track Geometric Altitude O X

I062/135 Calculated Track Barometric Altitude O X

I062/136 Measured Flight Level O X

I062/185 Calculated Track Velocity (Cartesian) O X

I062/200 Mode Of Movement O X

I062/210 Calculated Acceleration (Cartesian) O X

I062/220 Calculated Rate Of Climb/Descent O X

I062/245 Target Identification O −

I062/270 Target Size & Orientation O −

I062/290 System Track Update Ages SF1 − 10 O X

I062/295 Track Data Ages SF1 – 24 O X

I062/300 Vehicle Fleet Identification O −

I062/340 Measured Information SF1 – 6 O X


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200513 of 93

I062/380 Aircraft Derived Data SF1−28 O X

I062/390 Flight Plan Related Data SF1 1−16 O X

I062/500 Estimated Accuracies SF1 – 8 O X

I062/510 Composed Track Number O X

I062/SP SP: Number of target ids + target ids for all NN

plots/target reports

O X

TABLE 2 − ASTERIX CAT 062 ITEMS FOR TRACK INFORMATION

3.2.1.3.2 − CAT 063 Sensor Information

The sensor information message served by ARTAS is composed of data items of ASTERIX CAT 063.


Mandatory / Op-tional for AS-

TERIX



I063/015 Service Identification O X

I063/030 Time of Message M X

I063/050 Sensor Identifier M X

I063/060 Sensor Configuration and Status O X

I063/070 Time Stamping Bias O X 1

I063/080 SSR/Mode S Range Gain and Bias O X 1

I063/081 SSR/Mode S Azimuth Bias O X 1

I063/090 PSR Range Gain and Bias O X 1

I063/091 PSR Azimuth Bias O X 1

I063/092 PSR Elevation Bias O X 1

TABLE 3 − CAT 063 BROADCAST SENSOR INFORMATION

NOTE: The presence of the items in the output stream depends on the item selection and the sensor type:

− I063/070 for all SSR and PSR sensors

− I063/080 and I063/081 for SSR sensors only

− I063/090, I063/091 and I063/092 for PSR sensors only

3.2.1.3.3 − CAT 065 SDPS Service Status Messages

The service status message served by ARTAS is composed of data items of ASTERIX CAT 065.

SDPS Status





I065/000 Message Type M X


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 14 of 93

I065/015 Service Identification M X

I065/020 Batch Number − −


I065/040 SDPS Configuration and Status M X

I065/050 Service Status Report − −

FIGURE 4 − CAT 065 SDPS STATUS MESSAGE

End of Batch







I065/020 Batch Number M X


I065/040 SDPS Configuration and Status − −

I065/050 Service Status Report − −

FIGURE 5 − CAT 065 END OF BATCH MESSAGE

Service Status


Mandatory / Op-tional for AS-

TERIX





I065/020 Batch Number − −


I065/040 SDPS Configuration and Status − −

I065/050 Service Status Report M X

FIGURE 6 − CAT 065 BROADCAST SERVICE MESSAGE

3.2.1.4 − DATA AND MESSAGES TRANSFERRED

The data and messages transferred through this interface shall be compliant with the User ApplicationProfiles and the message types as defined in the reference documents [26], [27], [28] and [29] and withrespect to the function concerned.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200515 of 93

The User Application Profiles as defined in the documents [26], [27], [28] and [29] and related to thisinterface are:

− Connection related messages (ASTERIX CAT 252),

− Service related messages (ASTERIX CAT 065),

− SDPS track messages (ASTERIX CAT 062),

− Sensor information (ASTERIX CAT 063)

For the UAP ”Connection related messages”, the message types related to this interface are the followingones :

− Request for connection,

− Request for disconnection,

− Connection related report.

For the UAP ”Service related messages”, the messages types involved in this interface are given hereafter :

− Background service definition (Track information),

− Synchronized complementary service definition (Track information),

− Independent complementary service definition (Track information),

− Service update/stop track/item transmission (Track information),

− Service update/start track/item transmission (Track information),

− Service control/interruption (Track information),

− Service control/restart (Track information),

− Service control/end of service (Track information),

− Server status message,

− Track Service related report,

− Sensor information service related report,

− Sensor information service definition request,

− Sensor Service control request = interruption,

− Sensor Service control request = restart,

− Sensor Service control request = end of service.

Each of these message types enables to define data items of an ASTERIX Category, which are compulsoryor optional for transmission, and then the data items which are not transmitted. As far as the document [29]is specific to the use of ASTERIX with respect to ARTAS, the description of these data items is not recalledherein.

It must be noticed that the Unit serving the tracks or the sensor information is identified in the Asterixmessages through a Server identification tag defined as the SIC/SAC code of the Unit, and that the Userreceiving the tracks or the sensor information is identified in the messages through the User number.

The Asterix messages includes the Server identification tag related to the SIC/SAC code of the Unit servingTracks or Sensor Information to the Unit, and the User number


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 16 of 93

Two kinds of service can be defined for each Normal User :

− Track Information service,

− Sensor Information service.

As seen above a Normal User and an ARTAS Unit can exchange a lot of different types of messages relatedto one kind of service. The sending of the messages from the User to the ARTAS Unit has to follow apredefined sequence. The basic rules of this sequence are given in the following figures (see also figure 3 ofthe SSS document [11]).

The following figures aims to point out most of the dependencies between the message types for both kindof services. It must be noticed that both services are managed independently. Nevertheless a singleconnection request is necessary.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200517 of 93

Connection Request

Background Service definition

Service Restart

BackgroundServiceUpdate

BackgroundService

Interruption

End ofBackground

Service

ComplementaryService iDefinition

BackgroundServiceRestart

End ofBackground

Service

ComplementaryService iupdate

End ofComplementary

Service i

ComplementaryService i

Interruption

End ofComplementary

Service i

ComplementaryService iRestart

1

2

1

1

2

2

3

3

1

1

1

3

FIGURE 7 − MESSAGES SENT BY NORMAL USERS FOR THE TRACK SERVICE


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 18 of 93

Connection Request

Service definition

Service Restart

ServiceInterruption

End ofService

ServiceRestart

End ofService

2

1

1

2

2

FIGURE 8 − MESSAGES SENT BY NORMAL USERS FOR THE SENSOR SERVICE

Concerning this sequence, it must be noticed that :

− the ”Track Information Service Restart” performed after the connection request is applied to the Back-ground and the Complementary Services, if they have been off−line defined,

− a ”Track Information Background Service Interruption”, ”Restart” or ”End” implies the same effect onthe Complementary services defined with respect to this Background Service,

− a ”Complementary Service definition” can be performed only if it has not been already defined,

− a ”Disconnection request” is available as soon as the ”Connection request” has been accepted.

Furthermore, an automatic disconnection of the User is performed, if a predefined amount of time is elapsedsince :

− a ”Connection request”, without performing afterwards a ”Track Information Background Service defini-tion”, a “Sensor Information service definition”, a ”Track Information Service Restart”, or a “Sensor Ser-vice restart”,

− a “Track Information Background Service interruption” has been performed, while no “Sensor Informa-tion Service” is defined as “active”, without performing a “Track Information Service restart”,

− a “Sensor Information Service Interruption” has been performed, while no “Track Information Back-ground Service” is defined as “active” , without performing afterwards a “Sensor Information Servicerestart”,


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200519 of 93

− an “End of Track Information Background Service” has been performed, while no “Sensor InformationService” is defined as “active”, without performing a “Sensor Information Service definition”,

− an “End of Sensor Information Service” has been performed, while no “Track Information BackgroundService” is defined as “active” , without performing afterwards a “Sensor Information Service definition”,

Amongst the checks performed by ARTAS to accept a User connection request one aims to check that therelevant User maximum DOI is enclosed in a square of ARTAS_MAX_DOI_SIZE_C Nm centered on theUCP, and one aims to check that the User DOI is enclosed in the User maximum DOI.

As soon as the User is connected to the ARTAS Unit, and as a Track Information Service is defined, theARTAS Unit sends ARTAS Tracks to the User with respect to the Service definition. The track informationsent will be updated depending on the commands performed afterwards (Service update...).

For a Track Information service several transmission characteristics can be chosen for the tracks sending.For a periodical service the following characteristics are defined: scan period, batch period and updateperiod (please refer to [29]). The tracks are served to the User through batches (the number of the batchserved is defined through the item I252/330 used as Service Synchronized Report).

The number of batches is defined with the batch period and the scan period (scan period=number of batchesx batch period).

The User DOI is divided in strips. The total number of strips is defined as follows : number of strips =number of batches x mean number of strips/batch (parameter). The strip width is then the same for all stripsused for one User. The number of strips in a batch is defined afterwards dynamically to have, as far aspossible, the same number of tracks in each batch.

The transmission characteristics available for the Sensor Service Information are : periodical, a−periodicaland punctual.

NOTE: ARTAS V7 will support ASTERIX CAT 252 as specified in [29]. Due to the changes in that category,the following messages differ with respect to the previous version, in particular, the following protocolprimitives are different.

− Background service definition (Track information),

− Synchronized complementary service definition (Track information),

− Independent complementary service definition (Track information),

− Service update/stop track/item transmission (Track information),

− Service update/start track/item transmission (Track information)

− Sensor information service definition request

NOTE:

− In this document only the basic rules concerning the sequence of sent messages are described. Furtherchecks are performed by the ARTAS unit on these messages. These checks are described in the SSSdocument (see [12]).

− An equivalent representation of item I032/460 and I030/460 is not available in I062/390. Therefore theI032/460 information will not be available to users anymore.

− Miniplan information can also be sent to normal users. They are part of the data items of the User Ap-plication Profile ”Flight Plan Related Data” (ASTERIX CAT 062).

− Specific information on the management of the items of ASTERIX CAT 030 is provided in Appendix Eof the SSS Ref. [12].


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 20 of 93

− Specific information on the management of the items of ASTERIX CAT 062 is provided in this documentRef. [26].

3.2.1.5 − DATA RATE OF FLOW

Herein the data rate of flow deals with the sending of Tracks and Sensor information towards OrdinaryUsers. Nevertheless the computation is performed with respect to the data rate of flow for the sending ofTracks towards all Users (including Adjacent Units). Therefore this paragraph includes the data rate of flowfor both the Ordinary Users and the Adjacent Units.

This rate of flow is computed taking into account an Ethernet frame size of 1400 bytes.

� Ordinary Users

Number of Ordinary Users: 20

Average Track information update period : 5 s

Total number of Tracks / User / 5 s 200

Maximum Number of Tracks per message 36

Average Sensor information update period 10 s

Total number of sets of Sensor information / User / 10 s 30

Maximum Number of sets of Sensor information per message 54

The total number of tracks per second is then 800 Tracks. With the assumption that 50% of the Tracks areprovided to 25% of the Ordinary Users, 400 Tracks are transmitted to 20 x 0.25 = 5 Users and 400 Tracksare transmitted to 15 Users.

To send 400 Tracks to the first 5 Users, about 3 messages have then to be sent to each User. To send 400Tracks to the 15 remaining Users, 1 message have to be sent to each User.

The total number of sets of sensor information is 60. With the assumption that 50% of the sets of the sensorinformation are provided to 25% of the Ordinary Users, 30 sets are transmitted to 20 x 0.25 = 5 Users and30 sets are transmitted to 15 Users.

To send 30 sets of sensor information to the first 5 Users, about 1 message have then to be sent to eachUser. To send 30 sets of sensor information to the 15 remaining Users, 1 message have to be sent to eachUser.

The ARTAS Unit shall be able to send 30 Track information messages and 20 Sensor information messagesper second to 20 Ordinary Users.

� Adjacent Units

Total number of Adjacent Units : 3

Average update period : 10 s

Total number of Tracks / Unit / 10 s 250

Average number of Tracks per message 20

The average size of one Adjacent track taken into account is 80 bytes.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200521 of 93

The total number of tracks per second is then about 80 Tracks. With the assumption that 50% of the Tracksare provided to 25% of the Units, 40 Tracks are transmitted to 3 x 0.25 = about 1 Unit and 40 Tracks aretransmitted to 2 Units.

To send 40 Tracks to the first Unit, 2 messages have then to be sent to this Unit. To send 40 Tracks to the 2remaining Units, 1 message have to be sent to each Unit.

The ARTAS Unit shall be capable to send 4 messages (of up to 20 Tracks) per second to 3 Adjacent ARTASUnits.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 22 of 93

3.2.2 − FPPS USER

The FPPS Users are Normal Users which are able to send Miniplans to the ARTAS Unit. Afterwards theARTAS Unit is able to send Miniplans information to the Users interested in.

3.2.2.1 − FUNCTIONS

As far as a FPPS User is a Normal User, the same functions as defined above are available (see §3.1.1.1).To these functions is then added the function relating to the transmission of Miniplans to the ARTAS Unit.

3.2.2.2 − COMMUNICATION PROTOCOL

The same protocol as defined in §3.2.1.2 is used.

3.2.2.3 − APPLICATION PROTOCOL

The messages transmitted through this interface shall be defined with respect to the ASTERIX standard([26], [27], [28] and [29]). The encoding of the messages is described in §3.2.1.3.1, §3.2.1.3.2 and§3.2.1.3.3.

NOTE: The service provided to the user is realised by CAT 062, 063 and 065. CAT 030 will not be supportedto the FPPS user anymore.

3.2.2.4 − DATA AND MESSAGES TRANSFERRED

For the functions available for all Normal Users see §3.2.1.4.

Concerning the messages sent not related to the transmission of miniplans, the sequence followed is thesame as the one defined in §3.2.1.4.

Considering the transmission of miniplans, the data and messages transferred through this interface shall becompliant with the User Application Profile defined in the reference document [29] (ASTERIX category 032).The different types of messages sent are the following ones :

− Flight Plan to track initial correlation,

− Miniplan update,

− End of Correlation,

− Miniplan Cancellation.

In the above messages the FPPS User is identified through the User number. The Server identification tagincluded in the Asterix message is related to the Artas Unit sending the tracks to the FPPS User.

It must be noticed that a FPPS User can send Miniplans to an ARTAS Unit only after it has set a connectionwith the Unit and defined a Service.

A FPPS User can send a Miniplan, if and only if it is correlated to a Track (”Flight Plan to track initialcorrelation”). This Correlation is performed by the FPPS User and not by the ARTAS Unit. Therefore theFPPS User has to receive Tracks from the ARTAS Unit and the message sent by the FPPS User to theARTAS Unit has to include the related (local) track number (and not the ARTAS track number).


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200523 of 93

Afterward messages are sent in case of a Miniplan update or cancellation, or if the correlation between aMiniplan and a Track is ended.

3.2.2.5 − DATA RATE OF FLOW

Hereafter is computed the data rate of flow concerning the transmission of miniplans from the FPPS Usersto the ARTAS Unit with respect to the ARTAS performances requirements and the hypothesis listed below :

Total number of Miniplans (from all FFPS Users) 2850

Average number of bytes of a Miniplan 58

Average miniplan update 5 mn

The number of miniplans per second is about 10.

The number of messages received by the ARTAS Units depends afterwards on the number of Miniplansproviders.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 24 of 93

3.3 − BROADCAST MODE INTERFACE SPECIFICATION (IF_RBR_BRC)

This paragraph aims at defining the interface concerning the transmission of information in Broadcast mode.

3.3.1 − FUNCTION

Users can receive services from an ARTAS unit in two broadcast modes distinguished by the providedASTERIX categories:

− CAT 062, 063, 065

− CAT 030, 031, 252

The ARTAS unit broadcasts information to a LAN, which can then be received from the LAN by the users.For this interface the messages are transferred unidirectional: from the ARTAS unit to the LAN. Thefunctions fulfilled by this interface are :

− The transmission of ARTAS tracks,

− The transmission of sensor information,

− The transmission of service status information.

NOTE: For a single broadcast service (identified by a service identification), only one mode of broadcast is sup-ported.

3.3.2 − COMMUNICATION PROTOCOL

Two communication stacks are available for forwarding information in broadcast mode:

− MAC/LLC1

− UDP/IP with multicast facilities

The following figure shows the protocol layers involved in each case:

Physical Layer

LLC1 /MAC

Physical Layer

LLC1 /MAC

IP

UDP

MAC/LLC1 UDP/IP


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200525 of 93

FIGURE 9 − PROTOCOL FOR BROADCAST USERS INTERFACE

In MAC/LLC1:

− The Users shall be able to receive the information broadcasted by an ARTAS Unit as far as they aredirectly connected to the local LAN.

− only the layers 1 and 2 of the OSI architecture (ISO 7498) are then used.

In UDP /IP:

− The users will be able to receive the information broadcasted by an ARTAS unit even if they are notconnected on the local LAN. Depending on the value of an IP parameter, the datagrams will be allowedto be rerouted by IP routers.

− The lower layers of the stack are the same as for MAC/LLC1. The protocol suite UDP/IP is on top ofthem.

One of both stacks must be selected for a broadcast user at the registration of this one. The default value isMAC/LLC1.

3.3.2.1 − PHYSICAL LAYER

The ARTAS Unit shall be connected to up to 6 LANs (depending on the hardware configuration) of typeCSMA/CD (Ethernet) or FDDI. For each service using a broadcast mode it shall be possible to define oneLAN amongst the LANs available (through the geographical data base).

3.3.2.2 − DATA LINK LAYER

The data link layer is herein divided in two layers (see IEEE 802.1) : MAC (Medium Access Control) and LLC(Logical Link Control).






3.3.2.3 − NETWORK LAYER

The IP multicast facility [24] of IP is used to be able to broadcast information to a group of several hosts.Ony class D network addresses are supported by this facility. A class D address is an IP network address inthe range [224.0.1.1, 239.255.255.255]. Other network addresses are not supported.

The Time−to−live IP parameter indicates if a datagram is allowed to be rerouted on other networks and howmany times. The default value is 1, meaning that the datagram are multicasted on the LAN. This parameteris modifiable in parameter files.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 26 of 93

3.3.2.4 − TRANSPORT LAYER

The information is put by ARTAS into UDP datagrams. The destination port of each broadcast user must beunique for the list of broadcast users in an ARTAS database The UDP ports must be in the range [5001,65535].

3.3.3 − APPLICATION PROTOCOL

The messages transmitted through this interface shall be defined with respect to the ASTERIX standardprotocol (see reference documents [8] and [29]). The encoding of the messages is described in §3.2.1.3.1,§3.2.1.3.2 and §3.2.1.3.3.

3.3.4 − DATA AND MESSAGES TRANSFERRED

The data and messages transferred through this interface shall be compliant with the User ApplicationProfiles as defined in the reference documents [26], [27], [28] and [29] and with respect to the functionconcerned. This interface is concerned by the following User Application Profiles defined in the referencedocument [26], [27], [28] and [29]:

For broadcast service including CAT 252, 030, 031

− Service related messages (ASTERIX CAT 252),

− Track information (ASTERIX CAT 030),

− Sensor information (ASTERIX CAT 031).

And for broadcast service including CAT 062, 063, 065:

− Track information (ASTERIX CAT 062),

− Sensor information (ASTERIX CAT 063),

− Service related messages (ASTERIX CAT 065).

For the UAP ”Service related messages”, the messages types this interface is interested in are givenhereafter :


− Track Service related report,

− Sensor Information Service Related Report.

Each of these message types enables to define data items of the concerned ASTERIX Category, which arecompulsory, or optional for transmission, and then the data items which are not transmitted. As far as thereference document [29] is specific to the use of ASTERIX to ARTAS, the description of these items is notrecalled herein. Nevertheless it must be noticed that only a subset of the data items identified by the abovemessage types are used by ARTAS in the Broadcast modes.

The messages related to the Track information or the Sensor information served in a Broadcast mode willinclude a User number related to the Broadcast service which has leaded to their transmission.

NOTE: With respect to the interface between the Normal Users and the ARTAS Unit, the Service Definition,Update or Control commands are performed by an operator through the Supervision of the ARTAS Unit.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200527 of 93

Furthermore these commands are mainly performed in the same way if requested by the Operator, asif requested by a Normal User. Nevertheless in the case of a Broadcast Mode, there are specific charac-teristics.

The Track Information Service Update performed by an Operator is only applicable for :

− the geographical sub−areas,

− the Track Selector.A Restart of the Service (Track Information or Sensor Information) for a Broadcast Mode can also beperformed by the Operator. If the Service is interrupted, the Restart is performed in the same way asfor a Normal User : the service is restarted with the definition available before the interruption. If no Endof Service has been performed, before a disconnection of the Broadcast mode, at re−connection theService is restarted with the previous Service definition, and not with the Service defined by default inthe data base (if available) as for a Normal User.

NOTE: In case of a Track re−numbering (due to an ARTAS failure), the Users have to take into account thenew Track numbers, and to drop the previous ones. The Users receiving Tracks through a Broadcastmode will be aware of this Track re−numbering, through a change of the ”track numbering restart indica-tor” contained in the item 040 (Track number) of the ASTERIX category 030.

NOTE: Some information on the sending of tracks in batches for a periodical service are provided in 3.2.1.4.

3.3.5 − DATA RATE OF FLOW

See §3.2.1.5.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 28 of 93

3.4 − ADJACENT UNIT INTERFACE SPECIFICATION (IF_RBR_ADJ)

This paragraph aims at defining the interface between an ARTAS Unit and the Adjacent Units. The AdjacentUnits are connected in a point−to−point mode.

3.4.1 − FUNCTION

The following functions are defined in the SSS document (see [11]) and are fulfilled through this interface :

− The Tracking Continuity,

− The Service Continuity,

− The transmission of miniplan from the Adjacent Units to the local ARTAS Unit.

The Tracking Continuity will ensure that each aircraft is represented by only one Track served to the Usersdespite the fact that it may be maintained in two or more Adjacent Units.

Tracks outside the Domain of Cooperation are maintained by only one ARTAS Unit. The Service Continuityis involved in order to enable the ’local’ Unit to serve Tracks maintained by Adjacent ARTAS Units to itsUsers.


This paragraph deals with the definition of the protocol used for the layer 1 to 4 of the OSI model (ISO7498). The protocol stack available for this interface is schematically described below :

Physical Layer

LLC1 /MAC

IP

TCP

PDC

FIGURE 10 − PROTOCOL FOR ADJACENT UNITS INTERFACE

NOTE: The protocols off−line defined by the Operator for the local Unit and each Adjacent ARTAS Unit will haveto be compliant. In the case of protocols not compliant, the connection will not be possible.Furthermore in the case both protocols are available for the local Unit and one Adjacent Unit, the protocolused will be based on TP4.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200529 of 93


The communication between the Adjacent ARTAS Units and the local ARTAS Unit shall be performedthrough the use of a hardware equipment itself connected to a specific LAN of type CSMA/CD or FDDI ofthe local Unit. This specific LAN shall be off−line chosen (configuration file) for all Normal Users and allAdjacent Units amongst the LANs connected to the Artas Unit.


Concerning the connection of adjacent ARTAS Units and ARTAS Units through a LAN, the data link layer isherein divided in two layers (see IEEE 802.1) : MAC (Medium Access Control) and LLC (Logical LinkControl).







The protocol used shall be IP.


The protocol used for the Transport layer shall be TCP.

Furthermore the Private Data Channel (PDC) protocol shall be also used (see [13]).


The messages transmitted through this interface shall be defined with respect to the ASTERIX standardprotocol (see reference documents [26], [28] and [29]). The encoding of the messages is described in§3.2.1.3.1, §3.2.1.3.2 and §3.2.1.3.3.


The data and messages transferred through this interface shall be compliant with the User ApplicationProfiles and the message types as defined in the reference documents [26], [29] and with respect to thefunctions concerned.

Tracking Continuity


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 30 of 93

This function implies a cooperation between the adjacent ARTAS units in order to exchange their tracks. Themessages involved for this function are part of the following ASTERIX standards: CAT 062, CAT 032 andCAT 252 (see [26] and [29]).

− Connection related messages,

− Service related messages,

− Track Information.

For the UAP ”Connection related messages”, the message types, related to the Tracking Continuity are thefollowing ones :




For the UAP ”Service related messages”, this function involves the following message types :

− Service control/restart,


− Service related report.

The User Application Profile ”Track Information” deals with the message types :

− Track information,

− Slave track promotion.

In order to perform a Tracking Continuity in good conditions, each Adjacent Unit has to be connected to thelocal Unit and has then to send a ”Request for connection” (and reversely). The data flows defined aboveare then in both ways : from the local towards the Adjacent Units and reversely.

Following an accepted Connection request the Adjacent Unit does not perform a Background ServiceDefinition (as a Normal User), but a ”Service Restart”. The Service is started by the local Unit with a Servicepreviously defined by default. The characteristics of this default Service are the following ones :

− the Track selector keys define all Tracks needed for the Tracking Continuity,

− the Item selector may include all items except the items related to the Miniplans or Mode S,

− the transmission mode is an a−periodical one.

The Domain of connection of the Adjacent Unit is equal to the Domain of Interest of the local Unit.Nevertheless, only the tracks located in the Domain of Cooperation are sent to the Adjacent Unit. ThisBackground Service enables then to perform an exchange of the Tracks between the ARTAS Units in theframe of the Tracking Continuity.

If one Aircraft is seen by several ARTAS Units, a Unit Master has to be defined (see [11]). Hereafter areprovided the basic rules implied in case of cooperation between two Adjacent ARTAS Units (for furtherinformation, see [11]).

− if a Track is initiated by the Unit (B) with the lowest priority, this Track is sent to the other Unit (A).

If the Track sent is in correspondence with a Track of Unit A, an amalgamated Track is sent by the UnitA towards the Unit B (”Track information”). The message sent points out the responsibility of the UnitA for this Track through the ARTAS Track number (see [29]).

If the Track sent is not in correspondence with a Track of Unit A, this Unit informs the Unit B to takethe responsibility through a ”Slave Track promotion message”.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200531 of 93

− if a Track is initiated by the Unit (A) with the highest priority, this Unit takes the responsibility for thisTrack. If the same Aircraft induces an initiation of a Track in the Unit B, the Unit B will be aware of theresponsibility of Unit A through the mechanism described above.

AMASTER

BSLAVE

Track initiation

CorrespondenceA takes responsibility

”Track information”

”Track information” B accept responsibility of A

AMASTER

BSLAVE

Track initiation

No correspondence

”Track information”

”Slave Track promotion message” B takes responsibility

FIGURE 11 − BASIC RULES FOR THE TRACKING CONTINUITY

If a Track in correspondence between the Units is cancelled in one of the Units the following treatments willbe performed, depending on the concerned Unit :

− If the Track is cancelled in the Unit master of the Track (A) a Mastership transfer will be performed. Toinform the Unit B of this Mastership transfer the Unit A will send the Track (”Track information”) with anew ARTAS Track number pointing out the responsibility of the Unit B,


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 32 of 93

− If the Track is cancelled in the Unit with the lowest priority (B), this Unit will have to inform the Unit A(responsible for the amalgamation) of this cancellation. The message sent will point out the SystemTrack cancellation through the Asterix item ”ARTAS Track status”.

For a Track crossing a borderline between Adjacent ARTAS Units, the same mechanism will be applied (thistrack will be at a moment inside the Domain of Cooperation between the Units).

Service Continuity

The messages used for this function are part of the following User Application Profiles (see [26], [28] and[29]) :

− Connection related messages (CAT 252),

− Service related messages (CAT 65),

− Track information (CAT 062).

Some of these messages are already involved in case of ”Tracking Continuity”.

For the UAP ”Connection related messages”, the message types, related to this interface are the followingones :




For the UAP ”Service related messages”, this interface involves the following message types :

− Independent complementary service definition,

− Service update/stop track/item transmission,

− Service update/start track/item transmission,

− Service control/restart,


− Service related report.

The User Application Profile ”Track Information” deals with the message types :

− Track information.

If a Service Continuity (see [11]) is involved between the Units :

− a modification of the Track selector geographical sub−area may be performed in order to take into ac-count the connection Domain of Interest of a User,

− a modification of the Item selector may be performed with respect to the Item Selector defined by theUser and the Item Selector already defined between the Units.

The transmission mode for the Service Continuity remains the one of the Tracking Continuity, it means ana−periodical mode.

This Service modification induces an update of an complementary Service already defined, or the definitionof a new complementary Service.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200533 of 93

Transmission of miniplans

For the UAP ”Transmission of Miniplans”, this interface involves the following message types :

− Flight plan to track initial correlation,

− Miniplan update,

− End of correlation,

− Miniplan cancellation.

Herein the Adjacent Units are considered as Users of the local Unit. The above defined messages are thensent from the Adjacent Units towards the local Unit. The ARTAS Unit sending the miniplans will be identifiedin the Asterix message through the Server identification tag, and the ARTAS Unit receiving the miniplans willbe identified through the User number.

An Adjacent Unit will send a miniplan (”Flight plan to track initial correlation”) to the local Unit, if it isconnected to a FPPS User, and if a miniplan (sent by this FPPS User) is correlated to a Track received fromthe local Unit. The message sent to the local Unit has to include the ARTAS track number (and not the localtrack number) to point out the correlation. Concerning the other messages, the Adjacent ARTAS Unitbehavior is the same as a FPPS User (see §3.2.2.4).

3.4.5 − DATA RATE OF FLOW

See §3.2.1.5.

The data rate of flow is computed here with respect to the ARTAS performances, and with the hypothesislisted below. This data rate of flow deals with the Tracks sent by the local Unit to the Adjacent Units.

Total number of Adjacent Units : 3

Average update period : 10 s

Total number of Tracks / Unit / 10 s 250

Average number of Tracks per message 10

The total number of tracks per second is then about 80 Tracks. With the assumption that 50% of the Tracksare provided to 25% of the Units, 40 Tracks are transmitted to 3 x 0.25 = about 1 Unit and 40 Tracks aretransmitted to 2 Units.

To send 40 Tracks to the first Unit, 4 messages have then to be sent to each Unit. To send 40 Tracks to the2 remaining Units, 2 messages have to be sent to each Unit.

The ARTAS Unit shall be capable to send 20 messages (of up to 10 Tracks) per second to 8 AdjacentARTAS Units.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 34 of 93

3.5 − RADAR INTERFACE SPECIFICATION (IF_RBR_RAD)

Hereafter is provided a general diagram of the interface between a radar and an ARTAS Unit :

LAN a

LAN b

ARTAS

FIGURE 12 − RADAR CONNECTION TO AN ARTAS UNIT

ARTAS shall be capable to receive data from one radar through up to 2 LANs (except for radars using theRMCDE protocol). On each LAN ARTAS shall be capable to receive the same data from the same radarthrough up to 2 communication routes. Depending on the protocol used for the reception of the radar datamessages, the routes will be identified by:

− a different SIC/SAC code included in the ASTERIX message or

− a different combination of destination IP address (multicast address), destination UDP port and SAC/SIC code included in the ASTERIX message.

ARTAS shall be capable to receive information from different radar types. The detection capabilities of theseradars shall be based on so−called classical antennas (primary, enhanced primary −providing e.g. local plottracking and/or better clutter processing with MTD (Moving Target Detector), SSR, enhanced SSR such asmonopulse −providing e.g. local tracking capabilities−) or SSR Mode S enhanced technics.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200535 of 93

The radar stations may be :

− primary only, i.e. composed of a single primary antenna,

− secondary only, either classical SSR or SSR Mode S

− combined, i.e. composed of a primary and secondary antennas which are co−located (same position),co−mounted (their beam center is aligned) and co−rotating ; the corresponding target report messagesmay be primary and/or secondary and/or combined (all identified with the same Asterix radar identifica-tion, i.e. SIC/SAC),

− back to back, i.e. composed of two antennas, which are collocated, fitted back−to−back (their beamcenter azimuthal difference is of 180 degrees) and co−rotating ; their target report messages are identi-fied with the same SIC/SAC and the identification of the antenna shall be specified in item 020 of cate-gory 001. No back−to−back shall be considered in category 048.

The radar characteristics which are handled in the ARTAS system are part of the so−called “Radar StaticDatabase” described in the SRS MMS [17].

3.5.1 − FUNCTION

The main aim of this interface shall be to enable the reception of radar information. This information shall beprovided through the use of an hardware equipment such as a RMCDE (see [8]), a SIR (see [10] ), aMegapac or a �lines with ORADIS.

Furthermore, when the Radar Data Server through which are received the radar plot information will be aRMCDE, this interface shall allow also the transmission of messages to start a session, define thegeographical filtering of the radar data, or end the session. These messages are part of the so−calledRMCDE protocol.

The data flow is then carried out by this interface from the Radars to the ARTAS Unit, but also from theARTAS Unit to the Radars.

Please, note that with the aim of simplifying the designation of this interface, the word RADAR is used in thisdocument, to name the radar stations and their Data Server(s) at the same time.

The functions provided through this interface are then the following ones :

− The reception of monoradar target reports,

− The reception of monoradar service messages,

− The start of a session (RMCDE),

− The definition of a filter table (RMCDE),

− The end of a session (RMCDE),


The messages sent by the radars and received by the ARTAS Unit are in broadcast mode. Two protocolstacks can be used: the MAC/LLC1 protocol stack or the UDP/IP protocol stack. These stacks are describedin the following subsections. The following figure shows the protocol layers involved in each case:

FIGURE 13 − PROTOCOL FOR RADAR INTERFACE


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 36 of 93

Physical Layer

LLC1 /MAC

Physical Layer

LLC1 /MAC

IP

UDP

MAC/LLC1 UDP/IP

On a given configuration, all the radar information of any radar will have to be transmitted within a uniquecommunication protocol stack, either MAC/LLC1 or UDP/IP.


It shall be possible to connect a radar not using the RMCDE protocol to up to 2 LANs of type CSMA/CD(Ethernet) or FDDI. The LANs will be defined through the Static radar data base.

It shall be possible to connect a radar using the RMCDE protocol through one LAN of type CSMA/CD(Ethernet) or FDDI. The LAN will be defined through the Static radar data base.

It must be noticed that a radar can be connected to ARTAS through a RMCDE equipment without using theRMCDE protocol.

The connection of the ARTAS Unit to the 2 LANs will be performed through 2 different LAN Controllers orthrough a hardware equipment such as a transceiver. In the first case, for the radars connected to bothLANS, a redundancy between the LANs will be ensured by ARTAS (please refer to [11]).


The data link layer is herein subdivided in two layers (see IEEE 802.1) : MAC (Medium Access Control) andLLC (Logical Link Control). The MAC protocol is defined with respect to the type of LAN used, and the LLCprotocol not.

The MAC protocol used shall be defined by the following standards :

− ISO 8802.3 in case of a CSMA/CD LAN (Ethernet),

− ISO 9314.2 in case of a FDDI LAN.

The LLC protocol used shall be defined by the standard ISO 8802.2 (LLC type 1).

NOTE: In MAC/LLC1, a maximum of 30 multicast addresses using the same SAP number can be handled bythe ARTAS System. The radar addresses defined in the data base have to comply with this constraint.

When used with UDP/IP on top (UDP/IP stack), the MAC and LLC1 protocols are hidden and managedby the IP protocol directly.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200537 of 93

NOTE: On Tru64 5.1B system platforms it is also possible to bundle several physical LAN devices to form onevirtual LAN in order to achieve a higher availability and reliability. Such a virtual LAN device (”RedundantArray of Independent Network Adapters”, NetRAIN) can also be used as ARTAS Radar LAN device.


There is a network layer in the UDP/IP stack and the protocol is IP. In order to support the multicast facility,IP must be compliant with [RFC 1112]. In particular, the network address must be of class D and in therange [224.0.1.1, 239.255.255.255].


The transport layer of the UDP/IP stack is performed by UDP (User Datagram Protocol).

The UDP port number must be in the range [1024, 65535]. Several UDP ports can be defined for the sameIP network address, however there are constraints on the application layer on the combination of IP address,UDP port and radar identification (see also chapter 3.5.3 APPLICATION PROTOCOL).


The messages transmitted through this interface shall be defined with respect to the ASTERIX standardprotocol (see reference documents [8], [4], [5], [6] and [7]). The so−called classical radars shall transmit theirdata through categories 001 and 002, whereas Mode S stations shall deliver them through categories 048and 034. Please, refer to 3.5.4 for details on data items in each category.

It shall be possible to define up to two ”communication routes” for a radar not using the RMCDE protocol atthe application level. Both routes will provide the same radar information, but using different communicationroutes. The route(s) defined for one radar will be available and identical for all LANs (up to 2) defined for therelevant radar. This results in 1, 2 or 4 different communication channels for a radar:

− channel 1 : preferred LAN, preferred route

− channel 2 : preferred LAN, secondary route

− channel 3 : secondary LAN, preferred route

− channel 4 : secondary LAN, secondary route

Depending on the communication protocol stack used, channels (through which a particular ASTERIXmessage has been received) are identified in a different way:

− MAC/LLC1: a channel is identified by LAN identity together with route identity. The route identity is deter-mined by using the radar identification (SAC/SIC code) included in the received ASTERIX message.

− UDP/IP: a channel is identified by destination IP address and destination UDP port (of the received mes-sage) together with the radar identification (SAC/SIC code) or route alias (route_pref or route_sec) in-cluded in the received ASTERIX message (channel identity implicitly provides route identity). This com-bination of IP address, UDP port and radar identification or route alias must be unique amongst theconfigured radars and ADS−B data sources (i.e. unique per ARTAS database, see also chapter 3.6).Further, an IP address must not be used on more than 1 LAN (per ARTAS database).

For a radar connected through a RMCDE and using the RMCDE protocol, it shall be possible to define onlyone route and to use only the MAC/LLC1 stack.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 38 of 93

According to the equipment connected to the ARTAS unit, several formats of the user message can besupported:

− In case of a connection to a RMCDE, in MAC/LLC1 as well as in UDP/IP, the user message is composedof the radar message and eventually a 6 byte RMCDE header. The header is not used by ARTAS.

− In case of a connection to �lines/ORADIS in UDP/IP, a header is added to each radar message receivedby ORADIS and several sets {header + radar message} are concatenated into the user message. AR-TAS uses the byte count field contained in each header to deconcatenate the radar messages. The fol-lowing figure depicts how such a message is organised:

Byte count

Byte count

Byte count

Reserved

Reserved

Reserved

Radarmessage

# j

Radarmessage

#j+1

Radarmessage

# j+n

...

One user

message

header

header

header

FIGURE 14 − ORADIS USER DATA MESSAGE

− In the other cases, the radar message is inserted as such, with no header.


Two types of radar data will be received from radars.

− Monoradar Target Reports, containing plot or local track information (in ASTERIX Categories 001 and048),


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200539 of 93

− Monoradar Service Messages, used to signal radar status information (in ASTERIX Categories 002and 034).

Depending on the function considered, they shall be compliant with the appropriate User Application Profile,as defined in the documents [4], [5], [6] and [7].

Concerning the radars connected through a RMCDE, additional messages can be exchanged betweenARTAS and the RMCDE (in ASTERIX Category 241). They shall be compliant with the description given inthe reference document [8].

3.5.4.1 − MONORADAR TARGET REPORTS

Radar target reports shall be issued either in the form of plots or tracks generated by a local tracking systemat the radar site. For those transmitted via category 001, two User Application Profiles are defineddepending on whether plot or track information is provided by the radar, whereas a single User ApplicationProfile is used in category 048.

3.5.4.1.1 − ASTERIX Category 001

This User Application Profile is defined by data items of the ASTERIX category 01. Hereafter are giventhese items with respect to the reference document [4]. The following table gives a list of these items,defines if they are compulsory (C) or optional (O) with respect to the reference document [4], and defineswhether they are used by the ARTAS system.

Plot information

Data Item Information Compulsory /Optional

for ASTERIX

Used orTrans-

mitted by

ARTAS

Note

I001/010 Data Source Identifier C X

I001/020 Radar−Target Descriptor C X

I001/030 Warning/Error Conditions O

I001/040 Measured Target Position in polar coordinates C X

I001/050 Mode−2 Code in octal representation O X (2)

I001/060 Mode−2 Code Confidence Indicator O

I001/070 Mode−3/A Code in octal representation C X (1)(2)

I001/080 Mode−3/A Code Confidence Indicator O

I001/090 Mode−C Code in binary representation C X (1)

I001/100 Mode−C Code and Code Confidence Indicator O

I001/120 Measured Radial Doppler Speed O X

I001/130 Radar−plot characteristics O

I001/131 Received Power O

I001/141 Truncated Time of Day O X

I001/150 Presence of X pulse O


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 40 of 93

Data Item NoteUsed orTrans-

mitted by

ARTAS

Compulsory /Optional

for ASTERIX

Information

− Reserved for SP indicator O (3)

− Reserved for RFS indicator O (4)

TABLE 4 − ASTERIX CATEGORY 001 ITEMS FOR PLOT INFORMATION

NOTE: (1) : In Standard, compulsory for SSR or combined plots and transmitted when available

(2) : In ARTAS, a smoothed mode 3/A or 2 code will be considered as not present

(3) : In ARTAS, SP content is skipped when this indicator is present

(4) : this indicator has to be set to false to allow ARTAS proper functioning.

For details on cases of rejection and specific decoding rules, please refer to RBR SRS [16]. For details ondecoding and use of subfields, please refer to IRS [21] “PLOT_SECTOR” interface.

Track information

Data Item Information Compulsory /Optional

for ASTERIX

Used ortrans-mittedby AR-

TAS

Note


I001/020 Radar−Target Descriptor C X (8)


I001/040 Measured Target Position in polar coordinates C X (1) (2)

I001/042 Calculated Target Position in cartesian coordinates C (2)

I001/050 Mode−2 Code in octal representation O X (5)

I001/060 Mode−2 Code Confidence Indicator O

I001/070 Mode−3/A Code in octal representation C X (3)(5)

I001/080 Mode−3/A Code Confidence Indicator O

I001/090 Mode−C Code in binary representation C X (3)

I001/100 Mode−C Code and Code Confidence Indicator O

I001/120 Measured Radial Doppler Speed O X

I001/130 Radar−plot characteristics O

I001/131 Received Power O


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200541 of 93

Data Item NoteUsed ortrans-mittedby AR-

TAS

Compulsory /Optional

for ASTERIX

Information

I001/141 Truncated Time of Day O X (7)

I001/150 Presence of X pulse O

I001/161 Track/Plot number C X

I001/170 Track Status C

I001/200 Track Velocity in polar coordinates O X

I001/210 Track Quality O



TABLE 5 − ASTERIX CATEGORY 001 ITEMS FOR TRACK INFORMATION

NOTE: (1) : In ARTAS, this item is compulsory when there is a detection (as the tracking performancesmay only be met considering radar measured positions)

(2) : In Standard, one of the items 040 or 042 is at least compulsory (except in track cancellation)

(3) : In Standard, compulsory and transmitted when available


(5) : In ARTAS, a smoothed mode 3/A or 2 code will be considered as not present

(6) : This indicator has to be set to false to allow an ARTAS proper functioning.

(7) : Time has to be consistent with the reported plot position (i.e. set to the plot detection time) for AR-TAS proper functioning

(8) : In ARTAS, the report will not be used when no detection (SSR/PSR=000)

For details on cases of rejection, counting of invalid messages and specific decoding rules, please refer toRBR SRS [16]. For details on decoding and use of subfields, please refer to IRS [21] “PLOT_SECTOR”interface.


This User Application Profile is defined by data items of the ASTERIX CAT 048. The following table gives alist of these items, defines if they are mandatory (M) or optional (O) with respect to the reference document[6], and defines whether they are used by the ARTAS system.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 42 of 93

Data ItemReferenceNumber

DescriptionMandatory /Optional forASTERIX



I048/020 Radar−Target Descriptor M X (10)(13)

I048/030 Warning/Error Conditions O X− (14)

I048/040 Measured Target Position in Polar Coordi-nates

O X (1)

I048/042 Calculated Target Position in CartesianCoordinates

O −

I048/050 Mode−2 Code in Octal Representation O X (2)

I048/055 Mode−1 Code in Octal Representation O −

I048/060 Mode−2 Code Confidence Indicator O −

I048/065 Mode−1 Code Confidence Indicator O −

I048/070 Mode−3/A Code in Octal Representation O X (3)

I048/080 Mode−3/A Code Confidence Indicator O −

I048/090 Flight level in Binary Representation O X (4)

I048/100 Mode−C Code and Code Confidence Indica-tor

O −

I048/110 Height Measured by a 3D Radar O −

I048/120 Radial Doppler Speed O −

I048/130 Radar−plot Characteristics O −

I048/140 Time of Day M X (9)

I048/161 Track Number O X (5)

I048/170 Track Status O X (8)

I048/200 Track Velocity in Polar Coordinates O X (6)

I048/210 Track Quality O −

I048/220 Aircraft Address O X (7)

I048/230 Communications/ACAS Capability and FlightStatus

O X (7)(4)

I048/240 Aircraft Identification O X

I048/250 Mode S MB Data O X (11)

I048/260 ACAS Resolution Advisory Report O X (11)

I048/RE Reserved Expansion Field O X (12)

TABLE 6 − ASTERIX CATEGORY 048 ITEMS FOR PLOT & TRACK INFORMATION


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200543 of 93

NOTE: (1) : In ARTAS, this item is mandatory when there is a detection (as the tracking performance may onlybe met considering a measured position)

(2) : In ARTAS, a smoothed mode 2 code will be considered as not present

(3) : In ARTAS, a smoothed mode 3/A code will be considered as not present for a non Mode S detection(i.e. in case of type−number TYP#000,001,010,011,100,110), whereas a smoothed mode 3/A code willbe considered as not present only if not valid for a Mode S detection. The garbling indicator is forcedto ”not garbled” for a Mode S detection

(4) : For a Mode S equipped aircraft, altitude reporting capability may be of 25 ft resolution. In ARTAS,the ARC indicator in I048/230 will be used to know the effective resolution of I048/090

(5) : In the standard, this item is mandatory for local tracks. In ARTAS, the presence of this item willallow to differentiate a local track from a plot

(6) : In ARTAS, this item is mandatory when the radar station outputs tracks, accept for a track cancella-tion message.

(7) : In ARTAS, this item is mandatory for a Mode S detection

(8) : In ARTAS, this item is mandatory for a local track

(9) : Time has to be consistent with the reported plot position (i.e. set to the plot detection time) for properARTAS functioning

(10) : In ARTAS, the record will not be used when no detection (TYP=000). For details on cases of rejec-tion, counting of invalid messages and specific decoding rules, please refer to RBR SRS [16]. For de-tails on decoding and use of subfields, please refer to IRS [28] ”PLOT_SECTOR” interface.

(11) : The I048/250 and I048/260 data items are processed for Mode−S enhanced surveillance. TheBDS registers with COMM−B data selector 4.0, 5.0 and 6.0 are completely decoded. A set of up to 10additional BDS registers is decoded, if the respective COMM−B data selectors are configured (bymeans of off−line RBR CSCI parameters). For details, please refer to [16] RBR SRS.

(12) : The Mode 5 information given in I048/RE (Reserved Expansion Field) is decoded for Store & For-ward.

(13) : The FOE/FRI indicator in the first extent of I048/020 is decoded and used for Store & Forwardof Mode 4 information.

(14) : If the ”Reflected Plot Filter” is activated and I048/030 indicates the error condition ”Multipath Reply(Reflection)”, the plot is discarded.

3.5.4.2 − MONORADAR SERVICE MESSAGES

ARTAS will process North Marker Messages and/or Sector Crossing Messages from Radars.


Three types of Radar Service Messages are identified in this category :

− North and South Marker Messages,

− Sector Crossing Messages,


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 44 of 93

− Activation/Stop of Blind Zone Filtering Messages,

The last message type is not processed by ARTAS, hence will not be detailled in this document.

Hereafter are provided the ASTERIX data items which are specific of each message type (see [5]). Thefollowing tables define also if these items are compulsory or optional, from the point of view of ASTERIX,and whether they are used by ARTAS.

North / South Marker Messages

Data Item Information Compulsory/optional

for ASTERIX

Used ortrans-

mitted by

ARTAS

Note

I002/000 Message Type C X (1)


I002/030 Time of Day O X

I002/041 Measured Antenna Rotation Period O

I002/050 Station Configuration Status O

I002/060 Station Processing Mode O

I002/070 Plot Count Values O


I002/090 Collimation Error O



TABLE 7 − ASTERIX CATEGORY 002 ITEMS FOR NORTH / SOUTH MARKER

NOTE: (1) : The South Marker messages are not used by ARTAS.



For details on cases of rejection, counting of invalid messages and specific decoding rules, please refer toRBR SRS [16].

Sector Crossing Messages

Data Item Information Compulsory/optional

for ASTERIX

Used ortrans-

mitted by

ARTAS

Note

I002/000 Message Type C X



COMSOFT46 127 300 − 506 / V7.2 / 11.11.200545 of 93

Data Item NoteUsed ortrans-

mitted by

ARTAS

Compulsory/optional

for ASTERIX

Information

I002/020 Sector Number C X

I002/030 Time of Day O X

I002/041 Measured Antenna Rotation Period O

I002/050 Station Configuration Status O

I002/060 Station Processing Mode O






TABLE 8 − ASTERIX CATEGORY 002 ITEMS FOR SECTOR CROSSING MESSAGES

NOTE: (1) : In ARTAS, SP content is skipped when this indicator is present




Four types of Radar Service Messages are identified in this category :

− North Marker Messages,

− Sector Crossing Messages,

− Geographical Filtering Messages,

− Jamming Strobe Messages,

The two last message types are not processed by ARTAS and hence will not be detailled in this document.

The following tables (Table 8 and Table 9) define mandatory or optional items, from the point of view ofASTERIX, and whether they are used by ARTAS.

North Marker Messages



Ued / Pro-vided byARTAS Notes




COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 46 of 93

I034/030 Time of Day M X

I034/041 Antenna Rotation Period O

I034/050 System Configuration Status O X

I034/060 System Processing Mode O



I034/120 3D Position of Source O

TABLE 9 − ASTERIX CATEGORY 034 ITEMS FOR NORTH MARKER

NOTE: For ARTAS, items I034/020, 100 and 110 shall not be received in case of North Marker.


Sector Crossing Messages






I034/020 Sector Number M X

I034/030 Time of Day M X

I034/050 System Configuration Status O

I034/060 System Processing Mode O

I034/070 Count Values O


TABLE 10 − ASTERIX CATEGORY 034 ITEMS FOR SECTOR CROSSING MESSAGES

NOTE: For ARTAS, items I034/041, 100, 110 and 120 shall not be received in case of Sector Crossing Mes-sage.


3.5.4.3 − RMCDE MESSAGES

In case of radars connected through the hardware equipment RMCDE, some specific messages can beexchanged between the ARTAS Unit and the RMCDE. These messages are part of the so−called RMCDEprotocol and are the following ones :


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200547 of 93

− the start of a session,

− the definition of a filter table,

− the end of a session.

These messages are described in the reference document [8].

The start of a session enables to connect the ARTAS Unit to the RMCDE. Afterwards a filter table is sentfrom the Unit to the RMCDE in order to ask data from a specific radar data source and to define filteringcriteria. The Unit defines a filter table for each radar, from which it wants to receive data. The single criterionused by ARTAS deals with the geographical filtering.

The area covered by a radar is subdivided in polar bins (the origin of the polar coordinate system is locatedat the radar site). Several rings with a fixed range are then defined around a radar. Each ring is afterwardssubdivided with a fixed number of azimuth steps. For a radar, the Unit is interested in, the cells located to thefirst ring are always ”asked”. The cells of the other rings are ”asked” with respect to the Domain of Interest ofthe Unit.

As soon as a session and filter tables have been defined, the ARTAS Unit can receive radar data. TheRMCDE send these radar data with a format based on the ASTERIX format.

It must be noticed that 6 extra−bytes may be included in the data frames received by the ARTAS Unit fromthe RMCDE. These bytes are considered as ”extra−bytes” as far as they are not part of the standardASTERIX format. They are always present if the RMCDE protocol is used, but not if the radars areconnected through a RMCDE without using the related protocol.

”Alive messages” are periodically sent by the RMCDE in order to provide information on the RMCDE state. Ifthese messages are no more received by the ARTAS unit during a pre−defined period, the RMCDE isdeclared disconnected and the radars connected to the Unit through this RMCDE are disconnected.

The RMCDE protocol described above is not supported with the UDP/IP communication protocol stack. It issupported only on top of the MAC/LLC1 stack.

3.5.5 − RADAR DATA RATE OF FLOW

The radar data rate of flow is computed here from the ARTAS performance requirements and hypothesislisted below, independently of the phase of the project development.

Total number of plots/local tracks per second: 1000

Number of radars: 15

Average radar cycle (in seconds): 8

Number of sectors: 32

Average number of bytes per plots/local tracks: 40

From these hypothesis, the ARTAS unit should be able to receive and process a maximum of 1000 plots persecond from 15 radars. It is assumed that each radar sends at least one message per sector. The number ofsectors per radar is 32, and the radar period is 8 seconds. The minimum number of messages received fromthose 15 radars per second is therefore 60.

The average size for a plot/local track is about 40 bytes. Considering the size of the smaller frame over theLAN (Ethernet frame, in comparison to the FDDI frame), each message can contain up to 35 plots/localtracks.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 48 of 93

The usual assumption that 50% of plots are located within 25% of the radar coverage, leads approximatelyto the same result as if the plots were regularly distributed. Making the previous assumption, 500 plots arelocated within 60 X 0.25 = about 15 radar sectors and 500 other plots are located within 60 X 0.75 = about45 radar sectors. To send 500 plots, the first part needs 1 message almost full (33 plots/local tracks) perradar sector, whereas the second part needs 1 message containing 11 plots/local tracks in average per radarsector. The number of messages required to send 1000 tracks, with that assumption, is therefore: 15 + 45 =60.

In consequence, the ARTAS Unit should be able to receive up to 60 messages of up to 35 plots/localtracks per second.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200549 of 93

3.6 − ADS−B GROUNDSTATION INTERFACE SPECIFICATION (IF_RBR_ADS)

Hereafter is provided a general diagram of the interface between an ADS−B data source and an ARTAS unit:

LAN a

LAN b

ARTAS

ADS−BData Source

FIGURE 15 − ADS−B DATA SOURCE CONNECTION TO AN ARTAS UNIT

ARTAS shall be capable to receive data from one ADS−B data provider through up to 2 LANs (except forADS−B data sources using the RMCDE protocol). On each LAN, ARTAS shall be capable to receive thesame data from the same data source through up to 2 communication routes. Depending on the protocolused for the reception of the ADS−B data messages, the routes will be identified by:

− a different SAC/SIC code included in the ASTERIX message or

− a different combination of destination IP address (multicast address), destination UDP port andSAC/SIC code included in the ASTERIX message.

ARTAS shall be capable to receive information from ADS−B data sources having different types oftechnology: VDL4, Mode S Extended Squitter and UAT. The communication protocol will be identical for thethree of them, only the transmission and the message contents will differ.

Like for the radars, the ADS−B data source characteristics which are defined for the ARTAS system are partof the so−called ”Radar Static Database” described in the SRS MMS [18].

NOTE: removed

3.6.1 − FUNCTION

The main aim of this interface shall be to enable the reception of ADS−B information. This information shallbe provided by using a hardware equipment such as a RMCDE, a SIR, a Megapac or a �lines with


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 50 of 93

ORADIS. Nevertheless communication with ADS−B data sources through a RMCDE shall only be donewithout using the so−called RMCDE protocol, through a passive RMCDE.

Please note that with the aim of simplifying the designation of this interface, the word ADS−B data source isused in this document, to name the ADS−B ground stations and their data server(s) at the same time.

The function of this interface is the reception of ADS−B messages.


The messages sent by the ADS−B data providers and received by the ARTAS unit are in broadcast mode.Two protocol stacks can be used: the MAC/LLC1 protocol stack or the UDP/IP protocol stack. These stacksare described in the following subsections. The following figure shows the protocol layers involved in eachcase:

Physical Layer

LLC1 / MAC

Physical Layer

LLC1 / MAC

IP

UDP

FIGURE 16 − PROTOCOL FOR ADS−B DATA SOURCE INTERFACE

On a given configuration, all the ADS−B information of any ADS−B data source will have to be transmittedwithin a unique communication protocol stack, either MAC/LLC1 or UDP/IP.


It shall be possible to connect an ADS−B data source to up to 2 LANs of type CSMA/CD (Ethernet) or FDDI.The LANs will be defined through the static radar database.

The connection of the ARTAS unit to the 2 LANs will be performed through 2 different LAN controllers orthrough a hardware equipment such as a transceiver. For the ADS−B providers connected to both LANS, aredundancy between the LANs will be ensured by ARTAS.


The data link layer is herein subdivided in two layers (see IEEE 802.1) : MAC (Medium Access Control) andLLC (Logical Link Control). The MAC protocol is defined with respect to the type of LAN used, and the LLCprotocol is LAN independent.

The MAC protocol used shall be defined by the following standards :

− ISO 8802.3 in case of a CSMA/CD LAN (Ethernet),

− ISO 9314.2 in case of a FDDI LAN.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200551 of 93

The LLC protocol used shall be defined by the standard ISO 8802.2 (LLC type 1).

NOTE: In MAC/LLC1, a maximum of 30 multicast addresses using the same SAP number can be handled bythe ARTAS system.

When used with UDP/IP on top (UDP/IP stack), the MAC and LLC1 protocols are hidden and managedby the IP protocol directly.

NOTE: On Tru64 5.1B system platforms it is also possible to bundle several physical LAN devices to form onevirtual LAN in order to achieve a higher availability and reliability. Such a virtual LAN device (”RedundantArray of Independent Network Adapters”, NetRAIN) can also be used as ARTAS ADS−B ground stationLAN device.


There is a network layer in the UDP/IP stack and the protocol is IP. In order to support the multicast facility,IP must be compliant with [RFC 1112]. In particular, the network address must be of class D and in therange [224.0.1.1, 239.255.255.255].


The transport layer of the UDP/IP stack is performed by UDP (User Datagram Protocol).

The UDP port number must be in the range [1024, 65535]. Several UDP ports can be defined for the sameIP network address, however there are constraints on the application layer on the combination of IP address,UDP port and data source identification (see also chapter 3.6.3 APPLICATION PROTOCOL).


The type of data received from the ADS−B Data sources will be ADS−B messages and CNS/ATM groundstation messages. The messages transmitted through this interface shall be defined with respect to theASTERIX standard protocol ([24] and [25]).

It shall be possible to define up to two ”communication routes” for an ADS−B data source (not using theRMCDE protocol at the application level). Both routes will provide the same ADS−B information, but usingdifferent ways. The route(s) defined for one data source will be available and identical for all LANs (up to 2)defined for the relevant ADS−B data source. This results in 1, 2 or 4 different communication channels for adata source:

− channel 1 : preferred LAN, preferred route

− channel 2 : preferred LAN, secondary route

− channel 3 : secondary LAN, preferred route

− channel 4 : secondary LAN, secondary route

Depending on the communication protocol stack used, channels (through which a particular ASTERIXmessage has been received) are identified in a different way:

− MAC/LLC1: a channel is identified by LAN identity together with route identity. The route identity isdetermined by using the data source identification (SAC/SIC code) included in the received ASTERIXmessage.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 52 of 93

− UDP/IP: a channel is identified by destination IP address and destination UDP port (of the receivedmessage) together with the data source identification (SAC/SIC code) or route alias (route_pref orroute_sec) included in the received ASTERIX message (channel identity implicitly provides routeidentity). This combination of IP address, UDP port and data source identification or route alias mustbe unique amongst the configured radars and ADS−B data sources (i.e. unique per ARTAS database,see also chapter 3.5). Further, an IP address must not be used on more than 1 LAN (per ARTASdatabase).

For an ADS−B data source connected through a RMCDE and using the RMCDE protocol, it shall bepossible to define only one route and to use only the MAC/LLC1 stack.

According to the equipment connected to the ARTAS unit, several formats of the user message can besupported:

− In case of a connection to a RMCDE, in MAC/LLC1 as well as in UDP/IP, the user message is composedof the CAT 021 data block (ADS−B data block) and possibly a 6 byte RMCDE header. The header isnot used by ARTAS.

− In case of a connection to �lines/ORADIS in UDP/IP, a header is added to each CAT 021 record (ADS−Brecord) received by ORADIS and several sets {header + ADS−B record} are concatenated into the usermessage. ARTAS uses the byte count field contained in each header to de−concatenate the ADS−Bmessages. The following figure depicts how such a message is organized:

Byte count

Byte count

Byte count

Reserved

Reserved

Reserved

ADS−Brecord # j

ADS−Brecord# j+1

ADS−Brecord# j+n

...

One usermessage

header

header

header

FIGURE 17 − ORADIS USER DATA > MESSAGE

− In the other cases, the CAT 021 data block (ADS−B data block) is inserted as such, with no header.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200553 of 93


Two ADS−B related messages are transfered

− ADS−B message (CAT 021)

− CSN/ATM ground station service message (CAT 023)

The ADS−B messages and ground station messages received from the ADS−B data sources will becomposed of ADS−B target reports information.

They shall be compliant with the appropriate User Application Profile, as defined in the document [24] and[25].

3.6.4.1 − ADS−B MESSAGE

This User Application Profile is defined by data items of the ASTERIX CAT 021.



Used byARTAS Note

I021/010 Data Source Identification M X 2, 11

I021/020 Emitter Category O X 10,11

I021/030 Time of Day M X 3, 11I021/032 Time of Day Accuracy O X

I021/040 Target Report Descriptor M X 1I021/080 Target Address M X 4, 11

I021/090 Figure of Merit O X 5

I021/095 Velocity Accuracy O X 6I021/110 Trajectory Intent SF1 O X 1

I021/110 Trajectory Intent SF2 O X 7I021/130 Position in WGS−84 Co−ordinates O X 11

I021/140 Geometric Altitude O X

I021/145 Flight Level O XI021/146 Intermediate State Selected Altitude O X

I021/148 Final State Selected Altitude O XI021/150 Air Speed O X

I021/151 True Air Speed O X

I021/152 Magnetic Heading O XI021/155 Barometric Vertical Rate O X

I021/157 Geometric Vertical Rate O XI021/160 Ground Vector O X

I021/165 Rate of Turn O X

I021/170 Target Identification O X 8I021/200 Target Status O X

I021/210 Link Technology Indicator M X 11


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 54 of 93

I021/220 Met Report SF 1−3 O X 1, 9

I021/230 Roll Angle O X 1, 9

TABLE 11 − ASTERIX CAT 021 ITEMS FOR ADS−B MESSAGE INFORMATION

NOTE: Hereafter are listed the assumptions made in ARTAS for using or transmitting the different data items:

(1) Made available, within item I062/380. No use or other processing in ARTAS.

(2) Identifier of the ADS data provider, i.e. ground station, even if transmitted via an air server and/or anintermediate equipment

(3) Time of the elaboration of the position by the on−board equipment. The other items of the state vector(as altitude, heading, angle rate, vertical rate) are considered to be set consistently to this time.

(4) The Target Address corresponds to the Aircraft Address received from Mode S stations within CAT048. This item is mandatory for ARTAS; target reports that do not contain this item will be discarded.

(5) Indicates the accuracy on position at the time set in I021/030 (i.e. at time of measurement), not at thetime of transmission from the aircraft. It is a global error (bias + noise)

a. The coding follows the MASPS for ADS−B [32] table 2−1a:

b. A given NUCp value corresponds to a couple of position errors (horizontal, vertical). Coupled figures are given for levels 8 & 9 only

c. For levels 1 to 7, vertical error : an a−priori value corresponding to the barometric altitude error will be taken, even if the altitude is not barometric.

If both 140 or 145 items are present in the report, FOM will be set for the altitude.

(6) It corresponds to a couple of velocity errors (horizontal, vertical). It is a global error (bias + noise). Thecoding follows the MASPS for ADS−B [32] table 2−1B

(7) The repetition factor shall not exceed 4. If more than 4 series are received, only the first 4 will beprocessed and forwarded by ARTAS

(8) It corresponds to the Aircraft Identification received from Mode S stations within CAT 048

(9) Content is skipped when this indicator is present. For ARTAS V7 only the SP field may be set with athree−byte fixed length.

(10) ADS−B reports with emitter category different from flying objects (i.e. from 1 to 16) will be rejected.This check can be deactivated (parameter).

(11) ADS−B Messages are only processed if the following items are present:

a. I021/010 Data Source Identification

b. I021/030 Time of Day

c. I021/040 Target Report Descriptor

d. I021/080 Target Address

e. I021/210 Link Technology Indicator


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200555 of 93

For details on cases of rejection and specific decoding rules, please refer to RBR SRS [16].

3.6.4.2 − CSN/ATM GROUND STATION SERVICE MESSAGE

The following set of message types of CAT 023 are used by ARTAS

− 001 Ground Station Status message

− 002 Service Status message

− 003 Service Statistics message (will be discarded).

Ground Station Status Message:



Used / Pro-vided byARTAS

Note

I023/000 Message Type M X 1

I023/010 Data Source Identifier M X 1I023/070 Time of Day O X 1

I023/100 Ground Station Configuration & Status M X 1

TABLE 12 − ASTERIX CAT 023 ITEMS FOR GS STATUS MESSAGE


1. Ground station service messages are only processed if the following items are present:

a. I023/000 Message Type

b. I023/010 Data Source Identifier

c. I023/070 Time of Day

d. I023/100

Service Status Message:



Used / Pro-vided byARTAS

Note

I023/000 Message Type M X 1

I023/010 Data Source Identifier M X 1

I023/015 Service Type M X 1,2I023/070 Time of Day O X 1

I023/110 Service Status M X 1

TABLE 13 − ASTERIX CAT 023 ITEMS FOR GS SERVICE STATUS MESSAGE


1. Service status messages are only processed if the following items are present:


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 56 of 93

a. I023/000 Message Type

b. I023/010 Data Source Identifier

c. I023/015 Service Type

d. I023/070 Time of Day

e. I023/110 Service Status

2. Service status messages are discarded when its Service Type is not of Type ADS (1−3)

3.6.4.3 − ADS−B DATA RATE OF FLOW

The maximum number of ADS−B data sources and load figures to be handled and the dimensioning of theinput flow coming from each source are not known for the time being. This will be consolidated following anevaluation phase of ARTAS V7. Therefore, it will be considered that they are similar to the one accepted forthe radars. Also neither frequency nor synchronization for the reception of the data from the ADS−Bproviders can be assumed.

The messages are being processed in the order they are received.

3.7 − CENTRALIZED SUPERVISION INTERFACE SPECIFICATION (IF_ART_SNMP)

3.7.1 − FUNCTION

The aim of this function is to enable the exchange of messages between the ARTAS Unit and theCentralized Supervision. These messages are split between different categories (classes) :

− messages related to the whole ARTAS Unit,

− messages related to the ARTAS Nodes,

− messages related to the functions of an ARTAS Unit (Tracker, Server...),

− messages related to the ARTAS Radars of the local ARTAS Unit,

− messages related to the ARTAS Users (Normal Users, Broadcast Modes, Adjacent Units),

− messages related to the peripherals, external devices, and internal LAN device.


The information exchange between the ARTAS Unit and the Centralized Supervision shall use the followingprotocols :

FIGURE 18 − PROTOCOL FOR THE CENTRALIZED SUPERVISION


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200557 of 93

Physical Layer

LLC1 /MAC

IP

UDP

SNMP





It shall be possible to define off−line (configuration file) a specific LAN amongst the LANs available for theinterface with a Centralized Supervision.

As there is a limitation to the Centralised Supervision requests served and as the SNMP protocol is basedupon UDP/IP exchange, there is a chance that requests or their answers are lost due to

− the inherently unreliable service provided by the UDP protocol

− the fact that the RBR may unilaterally decide to ignore requests from a management station based ona too high load of messages.

This makes it a requirement for any Centralised Supervision station to cope with unanswered requests byresending requests.


The messages transferred deal with :

− attributes which can be read by the Centralized Supervision to get information,

− attributes which can be set by the Centralized Supervision and which lead to actions on the ARTAS Sys-tem,

− messages (traps) sent directly towards the Centralized Supervision.

A description of the MIB used is also provided in Annex.

3.7.3.1 − CLASS ARTAS SYSTEM

3.7.3.1.1 − Attributes available for reading

Attributes Definition Possible values Note

Unit_mode_of_use Live

Simulation


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 58 of 93

Unit_configuration Single

Dual

Dual Split

Operational_status ARTAS Plan status Plan_activated (2)

Plan_activating (2)

Plan_deactivating (2)

Plan_synchronizing (2)

Plan_deactivated (2)

Incoming_plot_number number of plots received by

the local ARTAS Unit per sec-

ond

0 ..

ARTAS_MAX_INCOMING_PL

OTS_C plots/sec

(1)

Incoming_track_number number of tracks coming from

the Adjacent ARTAS Units per

minute

0 .. 6 *

ARTAS_MAX_SYSTEM_TRA

CKS_C tracks/minute

(1)

Unit_version ARTAS software version (3)

artasHelloTrapStatus The emission of ”hello/alive” notActive

traps at regular intervals active

artasHelloTrapFrequency The frequency of hello trap

generation

non−negative number of

seconds

System_cold_start_comman Command status idle (4)

d_status busy (5)

System_cold_start_comman Command result clear

d_result accepted

successful

error_command_rejected

error_mms_unreachable

error_database_locked

error_incorrect_chain_number

System_hot_start_command Command status idle (4)

_status busy (5)


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200559 of 93

System_hot_start_command Command result clear

_result accepted

successful


error_mms_unreachable


error_incorrect_chain_number

System_stop_command_stat Command status idle (4)

us busy (5)

System_stop_command_res Command result clear

ult accepted

successful


error_node_unreachable

System_activate_plan_com Command status idle (4)

mand_status busy (5)

TABLE 14 − CLASS ARTAS SYSTEM − ATTRIBUTES FOR READING

NOTE: (1) : These attributes are only available if the ”Operational_status” is defined as ”Plan_activated”

(2) : The attribute ’Operational_status’ is up−to−date only if the function MMI/Supervision is available

(3) : This attribute may contain more information than just the ARTAS version number. This additionalinformation will be appended to the original version number and will be in ASCII format. Typically, thisinformation will be the date of the ARTAS version. The additional information is set in MMS configurationfile.

(4) : ’Idle’ shall indicate that the system is ready to receive the related command.

(5) : ’Busy’ shall indicate that the system has not finished processing the last command of this nature.

3.7.3.1.2 − Attributes available for writing


System_cold_start (1) (5)

System_hot_start (2) (5)

System_stop (3) (5)

System_activate_plan (4) (5)

artasHelloTrapStatus The emission of ”hello/alive” traps at notActive (6)

regular intervals active (6)


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 60 of 93

artasHelloTrapFrequency The frequency of hello trap generation non−negative number

of seconds

System_cold_start_comman

d_result

Command result clear (7)

System_hot_start_command

_result


System_stop_command_res

ult


TABLE 15 − CLASS ARTAS SYSTEM − ATTRIBUTES FOR WRITING

NOTE: (1) : This command will lead to a system cold start−up (please refer to SSDD [12] for details),

(2) : This command will lead to system hot start−up with a hot ARTAS Plan Activation (please refer toSSDD [12] for details),

(3) : Please refer to SSDD [12]for details on the system stop,

(4) : This command will lead to a plan cold activation using the default ARTAS Plan name defined inthe ARTAS_CONFIGURATION_FILE (please refer to VDD [18]),

(5) : These commands are available even if UBSS is not running.

(6) : The artasHelloTrapStatus attribute can be set to ”active” to cause ARTAS to emit ”artasHello” trapsat regular intervals. This behaviour can be switched off by setting the attribute to ”notActive”.

(7) : The manager should only write the value 1 (clear), although other values are writable.

3.7.3.1.3 − Events

Trap Foreseen event(s) Note

Unit_configuration_change The Unit_configuration of the system has changed (after a

split/merge operation)

Operational_status_change The operational status of the system has changed.

ArtasHello Periodic trap sent to confirm that ARTAS trap emission is

still working.

System_cold_start_command_statu

s_change (incl. actual state)

System cold start command status has changed from idle to

busy or vice versa

(1)


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200561 of 93

System_hot_start_command_status

_change (incl. actual state)

System hot start command status has changed from idle to

busy or vice versa

(1)

System_stop_command_status_cha

nge (incl. actual state)

System stop command status has changed from idle to

busy or vice versa

(1)

System_activate_plan_command_st

atus_change (incl. actual state)

System activate plan command status has changed from

idle to busy or vice versa

(1)

System_cold_start_command_error

_command_rejected

System cold start command rejected because a lock was

found − the command was already running

(2)


_mms_unreachable

System cold start command failed because MMS node is

not reachable

(2)


_database_locked

System cold start command failed because the Ingres

database is locked

(2)


_incorrect_chain_number

System cold start command failed because of wrong

platform file configuration

(2)

System_cold_start_command_warni

ng_node_unreachable (incl. node

name)

System cold start command encountered an unreachable

node

(2)


ng_node_already_running (incl.

node name)

System cold start command encountered an already

running node

(2)


ng_master_chain_time_exceeded

System cold start exceeded a defined time for the start of

the master chain (configured to 120s)

(2)

System_hot_start_command_error_

command_rejected

System hot start command rejected because a lock was

found − the command was already running

(3)


mms_unreachable

System hot start command failed because MMS node is not

reachable

(3)


database_locked

System hot start command failed because the Ingres

database is locked

(3)

System_hot_start_command_error_i

ncorrect_chain_number

System hot start command failed because of wrong

platform file configuration

(3)

System_hot_start_command_warnin

g_node_unreachable (incl. node

name)

System hot start command encountered an unreachable

node

(3)


g_node_already_running (incl. node

name)

System hot start command encountered an already running

node

(3)


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 62 of 93


g_master_chain_time_exceeded

System hot start exceeded a defined time for the start of the

master chain (configured to 120s)

(3)


g_dynamic_files_inconsistent_cold_

start_forced

System hot start encountered an inconsistency between the

dynamic files and the database and forced a cold start

(3)

System_stop_command_error_node

_unreachable

System stop command could not reach a node (4)

System_stop_command_error_com

mand_rejected

System stop command rejected because a lock was found

− the command was already in progress

(4)

TABLE 16 − CLASS ARTAS SYSTEM − EVENTS

NOTE: (1) : These traps reflect a status change of the respective command.

(2) : These traps are the system cold start error and warning traps.

(3) : These traps are the system hot start error and warning traps.

(4) : These traps are the system stop error traps.

3.7.3.2 − CLASS ARTAS NODE

In order to gain read or write access to the SNMP attributes of single ARTAS nodes the community”private_<name−of−the−node>” has to be used (<name−of−the−node> is the node name as specified in theARTAS platform file and the /etc/hosts file).



Node name name of up to 10 characters

Node_function_SMS True (1)

False (1)

Node_function_SS True (1)

False (1)

Node_function_TS True (1)

False (1)


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200563 of 93

Node_function_RB True (1)

False (1)

Node_function_DAS True (1)

False (1)

Node_Operational_status Operational (2)

Starting (2)

Stopping (2)

Stopped (2)

Node_Redundancy_status Principal

Single

Hot_standby

Cold_standby

Not_available

artasLocalClockStatus The device status of the

UBSS

“LOCAL_CLOCK”

device

Please refer to the UBSS device

specification for local clock devices

[23]

(3)

artasNodeInfoNTPStratum NTP stratum value of

the node.

1−255:

=1: primary reference

>2: secondary reference

Local clocks will typically have a

relatively low value of 10.

artasNodeInfoNTPStatus NTP status of the node Refer to NTP documentation.

ntp_sync (node is synchronized)

ntp_unspec (node NTP is in startup)

ntp_alarm (node in not synchronized)

in addition ARTAS defines special

values for error situations:

no_net (no network connection from

the RBR to the node)

no_ntp (NTP is not running on the

node)


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 64 of 93

artasNodeInfoNTPPeerCoun

t

Amount of peers

configured in the NTP

configuration.

2 for non−RBR nodes

amount of external NTP sources for

RBR nodes

artasNodeInfoNTPMainPeer Which peer is the one

being used

0 (not synced to any peer)

1−3 (pointer to peer info number)

artasNodeInfoNTPPeer1Stra

tum

NTP stratum value of

the NTP time source

1−255:

=1: primary reference

>2: secondary reference

(4)

artasNodeInfoNTPPeer1Add

ress

IP address of NTP peer. IP4 address in dot separation (4)

artasNodeInfoNTPPeer1Host

name

Hostname of NTP peer

as found in /etc/hosts

(Remark: Note that this value

may not necessarily be cor-

rectly maintained in ARTAS.

We recommend to use a re-

verse lookup of the IP on a

maintained DNS)

String value (4)

artasNodeInfoNTPPeer1Offs

et

Offset between this

node and that NTP time

source.

String value identifying float (4)

artasNodeInfoNTPPeer1Rea

chable

Reachability of that NTP

peer

yes/no (4)

artasNodeInfoNTPPeer1Stat

us

Status of the that NTP

peer

Refer to NTP documentation.

Can be:

sys.peer (node syncs to this peer)

candidat (node could sync to this

peer once the main peer degrades)

reject (peer is unacceptable as time

source)

(4)

Node_start_command_statu Command status idle (5)

s busy (6)


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200565 of 93

Node_start_command_result Command result clear

accepted

successful

error_node_unreachable (7)


error_database_access

error_with_configuration_file

error_ubss_still_present

error_basic_system_already_called

Node_stop_command_status Command status idle (5)

busy (6)

Node_stop_command_result Command result clear

accepted

successful

error_node_unreachable (7)

error_no_basic_system

error_not_owner_of_basic_system

Node_shutdown_command_ Command status idle (5), (8)

status busy (6)

Node_restart_command_stat Command status idle (5), (8)

us busy (6)

TABLE 17 − CLASS ARTAS NODE − ATTRIBUTES FOR READING

NOTE: (1) : this attribute may be not compliant with the ”real” node function, if the MMS CSCI is not available,

(2) : this attribute does not take into account the ARTAS Plan status

(3) : see also the status of the global clock [see also chapter 3.7.3.11.2.1]

(4) : this information is available per peer (at the moment there are up to 3 peers 1..3).

(5) : ’Idle’ shall indicate that the system is ready to receive the related command.

(6) : ’Busy’ shall indicate that the system has not finished processing the last command of this nature.

(7) : An unreachable node cannot be detected during a node start or stop command due to limitationsimposed by the current ARTAS SNMP framework. However the values for ”error_node_unreachable”are introduced for the node start and stop commands and are reserved for possible future use.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 66 of 93

(8) : No ”result attributes” shall be added for the node shutdown and restart commands.

NOTE: To provide the Centralized Supervision with information related to the number of the nodes involvedand to the list of these nodes names two other classes are used in the MIB ARTAS : Ar-tas_ubss_px_node (nodes managed by UBSS) and Artas_px_node (all nodes involved in the system).Please refer to 3.7.3.3 and 3.7.3.4 for a description of these classes.

To access to the list of the nodes names, the Centralized Supervision will have to get the relevant attributefrom the class artas_ubss_px_node (please refer to annex A). Through this class the number of nodesinvolved is also available.



Node_start (1)

Node_stop (1)

Node_restart (1)

Node_shutdown (1)

Node_start_command_result Command result clear (2)

Node_stop_command_result Command result clear (2)

TABLE 18 − CLASS ARTAS NODE − ATTRIBUTES FOR WRITING

NOTE: (1) : These commands are accepted whatever is the node operational status, but their effect will dependon this status.

(2) : The manager should only write the value 1 (clear), although other values are writable.

3.7.3.2.3 − Events


Node_Operational_status−

stopped

The node operational status is passed to ’stopped’

Node_Operational_status−opera-

tional

The node operational status is passed to ’operational’

Node_Operational_status−starting The node operational status is passed to ’starting’

Node_Operational_status−stop-

ping

The node operational status is passed to ’stopping’

Node_Redundancy_status−

not_Available

The node redundancy status is passed to ’Not available’

and the node operational status is set to ”Operational”


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200567 of 93

Node_Redundancy_status−princi-

pal

The node redundancy status is passed to ’Principal’ and

the node operational status is set to ”Operational”

Node_Redundancy_status−single The node redundancy status is passed to ’Single’ and the

node operational status is set to ”Operational”


hot_standby

The node redundancy status is passed to ’Hot standby’



cold_standby

The node redundancy status is passed to ’Cold standby’


Node_start_command_status_ch

ange (incl. node name and actual

state)

Node start command status has changed from idle to

busy or vice versa

(1)

Node_stop_command_status_cha

nge (incl. node name and actual

state)

Node stop command status has changed from idle to busy

or vice versa

(1)

Node_shutdown_command_statu

s_change (incl. node name and

actual state)

Node shutdown command status has changed from idle to

busy or vice versa

(1)

Node_restart_command_status_c

hange (incl. node name and

actual state)

Node restart command status has changed from idle to

busy or vice versa

(1)

Node_start_command_error_nod

e_unreachable

Node start command failed because node was

unreachable. This trap is reserved for future use (see note

below)

(2), (4)

Node_start_command_error_data

base_locked (incl. node name)

Node start command failed because database was locked (2)

Node_start_command_error_data

base_access (incl. node name)

Node start command failed because database is not

accessible

(2)

Node_start_command_error_with

_configuration_file (incl. node

name)

Node start command failed because of missing or empty

ncf, nsf or scmsys_conf.scf configuration file

(2)

Node_start_command_error_ubss

_still_present (incl. node name)

Node start command failed because UBSS still present on

node

(2)

Node_start_command_error_basi

c_system_already_called (incl.

node name)

Node start command failed because Basic System has

already been called

(2)


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 68 of 93

Node_stop_command_error_nod

e_unreachable

Node stop command failed because node was

unreachable. This trap is reserved for future use (see note

below)

(3), (4)

Node_stop_command_error_no_

basic_system (incl. node name)

Node stop command failed because Basic System not

running on that node

(3)

Node_stop_command_error_not_

owner_of_basic_system (incl.

node name)

Node stop command failed because another Basic

System is running under a different owner

(3)

TABLE 19 − CLASS ARTAS NODE − EVENTS

NOTE: (1) : These traps reflect a status change of the respective command.

(2) : These traps are the node start error traps.

(3) : These traps are the node stop error traps.

(4) : Since an unreachable node cannot be detected during a node start or stop command due tolimitations imposed by current ARTAS SNMP framework, the corresponding traps above are also notissued, but are reserved for future use.

The traps sent will identify the related node through the node name included in the message sent.

3.7.3.3 − CLASS ARTAS UBSS PROXY NODE

This class deals with the nodes managed by UBSS. The attributes belonging to this class are only availablefor ’reading’.


UBSS_px_node_number Number of nodes managed by UBSS

UBSS_px_node_index 1..UBSS_Px_node_

number

UBSS_px_node_name

TABLE 20 − CLASS ARTAS UBSS PROXY NODE − ATTRIBUTES FOR READING

3.7.3.4 − CLASS ARTAS PROXY NODE

This class deals with all nodes involved in the ARTAS system (UBSS nodes + other nodes). The attributesbelonging to this class are only available for ’reading’.


Px_node_number Number of all nodes involved in the AR-

TAS system


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200569 of 93

Px_node_index 1..Px_node_number

Px_node_name

TABLE 21 − CLASS ARTAS PROXY NODE − ATTRIBUTES FOR READING

3.7.3.5 − CLASS ARTAS NODE DUAL NODE STATUS



Artas_dual_node_status Indicates the node dual node status from unused

UBSS DNC master

slave

single

offline

rundown

TABLE 22 − CLASS ARTAS NODE DUAL NODE STATUS − ATTRIBUTES FOR READING

3.7.3.6 − CLASS ARTAS TRAP FILTER STATUS



Artas_trap_filter Indicates if traps are forwarded or not. forward

noforward

TABLE 23 − CLASS ARTAS TRAP FILTER STATUS − ATTRIBUTES FOR READING

3.7.3.7 − CLASS ARTAS NODE SCM STATUS



COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 70 of 93


Artas_node_scm_status SCM status on the node central

local

TABLE 24 − CLASS ARTAS NODE SCM STATUS − ATTRIBUTES FOR READING

3.7.3.7.2 − Events

Trap Foreseen event(s)

Artas_node_scm_status−central The node SCM status is passed to ’central’

Artas_node_scm_status−local The node SCM status is passed to ’local’

TABLE 25 − CLASS ARTAS NODE SCM STATUS − EVENTS

These traps enable to identify the node on which the Agent is defined as Master.

3.7.3.8 − CLASS ARTAS FUNCTION


Attributes Definition Possible

values

Note

Function_Number Number of functions

involved

Function_index 1..Func-

tion_num-

ber

Function_Technical_status Normal

Degraded

Function_name SMS

RB

TS

SS

DAS

Function_Software_version_node_A ARTAS Application

version running on

node A

(1)


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200571 of 93

Function_Software_version_node_B ARTAS Application

version running on

node B

(1)

Function_Node_A_name Node A name of the

function

(2)

Function_Node_B_name Node B name of the

function

(2)

Function_Node_Overload_SUP_A_Any

Function_Node_Overload_SUP_B_Any

Overload status of the

node

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overload_SUP_A_Request_Limit_All_IP

Function_Node_Overload_SUP_B_Request_Limit_All_IP

Function_Node_Overload_SUP_A_Request_Limit_Per_IP

Function_Node_Overload_SUP_B_Request_Limit_Per_IP

Overload status based

on SNMP request limit

for all IP addresses or

per IP address

respectively (one IP

address is considered

to identify one SNMP

management station)

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overload_TRK_A_Any

Function_Node_Overload_TRK_B_Any

Function_Node_Overload_RBR_A_Any

Function_Node_Overload_RBR_B_Any

Function_Node_Overload_SRV_A_Any

Function_Node_Overload_SRV_B_Any

Function_Node_Overload_MMS_A_Any

Function_Node_Overload_MMS_B_Any

Function_Node_Overload_REC_A_Any

Function_Node_Overload_REC_B_Any

Overload status of the

node

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overloads_RBR_A_Mono_Radar_Plot

Function_Node_Overloads_RBR_B_Mono_Radar_Plot

Does at least one

radar have mono

radar plot overload

situation

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 72 of 93

Function_Node_Overloads_RBR_A_Total_Plot

Function_Node_Overloads_RBR_B_Total_Plot

Has RBR a total plot

overload situation

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overloads_RBR_A_Radar_Sector_Memory

Function_Node_Overloads_RBR_B_Radar_Sector_Memory

Which radars have

radar plots overload in

sectors on RBR

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overloads_RBR_A_SRV_Transmission

Function_Node_Overloads_RBR_B_SRV_Transmission

Does the RBR have a

output transmission

overload situation

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overloads_TRK_A_Comms

Function_Node_Overloads_TRK_B_Comms

Communication

overload in TRK

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overloads_TRK_A_Memory

Function_Node_Overloads_TRK_B_Memory

Memory overload in

TRK

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overloads_SRV_A_CPU

Function_Node_Overloads_SRV_B_CPU

Function_Node_Overloads_TRK_A_CPU

Function_Node_Overloads_TRK_B_CPU

Function_Node_Overloads_RBR_A_CPU

Function_Node_Overloads_RBR_B_CPU

Function_Node_Overloads_MMS_A_CPU

Function_Node_Overloads_MMS_B_CPU

Function_Node_Overloads_REC_A_CPU

Function_Node_Overloads_REC_B_CPU

CPU overload for the

node

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200573 of 93

Function_Node_Overloads_SRV_A_Transmission

Function_Node_Overloads_SRV_B_Transmission

SRV is affected by

RBR output

transmission overload

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

Function_Node_Overloads_RBR_A_TRK_Filtering_Level_No

n_Zero

Function_Node_Overloads_RBR_B_TRK_Filtering_Level_No

n_Zero

RBR is applying a

non−zero filtering to

the plot output

according to TRK

Overloads

Unknown,

Unavail,

OK,

Warning,

Alarm

(3)

(4)

TABLE 26 − CLASS ARTAS FUNCTION − ATTRIBUTES FOR READING

NOTE: (1) : This attributes are only available if the related nodes operational status are set to ”operational”

(2) : These attributes are only available when MMS has started

(3) : For each individual value there is an individual ”value−changed” TRAP that carries a time ofdetection for the event as well as the current value of the changed item.

(4) : These attributes are only available when the system is not stopped.

3.7.3.8.2 − Events


Function_Technical_status−normal The node technical status is passed to ’nor-

mal’

Function_Technical_status−degraded The node technical status is passed to ’de-

graded’

Function_Software_version_change_node_A The software version of the ARTAS applica-

tion running on node A has changed

Function_Software_version_change_node_B The software version of the ARTAS applica-

tion running on node B has changed

Function_Node_A_name_change The name of the node A has changed

Function_Node_B_name_change The name of the node B has changed

Function_Node_Overloads_X_Y_Z_Change The value of the overload Z for function X on

chain Y has changed.

(1)

TABLE 27 − CLASS ARTAS FUNCTION − EVENTS


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 74 of 93

(1) : See table 26 in section 3.7.3.8.1 for the possible values of X, Y, and Z.

3.7.3.9 − CLASS ARTAS RADAR


NOTE: For downward compatibility to the existing MIB terminology, the term radar in the following is used for”Radar and ADS−B ground station”

Attributes Definition Possible Values Note

Radar_biases_computa-tion_status

Active

Not_active

(1) (5)

Radar_number Number of radars in theactivated plan

Radar_index 1..Radar_number

Radar_SIC Asterix SIC of the radar

Radar_SAC Asterix SAC of the radar

Radar_name Name of the radar

Radar_type Primary

Secondary

Combined

Mode_S

Combined Mode_SADS−B

Radar_period Period of the radar (2) (5)

Radar_time_stamping_bias Time stamping bias of theradar

(2) (3) (5)

Radar_vertical_direction Vertical direction of theradar

(2) (3) (5)

Radar_vertical_bias Vertical bias of the radar (2) (3) (5)

Radar_PR_azimuth_bias PR azimuth bias of theradar

(2) (3) (5)

Radar_PR_range_bias PR range bias of the radar (2) (3) (5)

Radar_PR_range_gain PR range gain of the radar (2) (3) (5)

Radar_PR_squint_bias PR squint bias of the radar (2) (3) (5)

Radar_PR_elevation_bias PR elevation bias of theradar

(2) (3) (5)

Radar_SSR_azimuth_bias SSR azimuth bias of theradar

(2) (3) (5)

Radar_SSR_range_bias SSR range bias of the radar (2) (3) (5)

Radar_SSR_range_gain SSR range gain of the radar (2) (3) (5)

Radar_SSR_squint_bias SSR squint bias of theradar

(2) (3) (5)


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200575 of 93

Radar_Operational_status Not_connected

Init

InitRMCDE

Operational

Degraded

Radar_Connection_status Disconnect

Connect

Radar_Degradation_Time_out Radar degradation cause TrueFalse

(3) (5)

Radar_Degradation_Incoher-ent_Time_stamping

Radar degradation cause TrueFalse

(3) (5)

Radar_Degradation_High_In-valid_Mode_A


(3) (5)

Radar_Degradation_Inco−her-ent_Radar_period


(3) (5)

Radar_Degradation_High_In-valid_Mode_C


(3) (5)

Radar_Degrada-tion_High_Old_information


(3)

Channel_1_status Active

available

not_available

not_defined

defined

(4)

Channel_2_status Active

available

not_available

not_defined

defined

(4)

Channel_3_status active

available

not_available

not_defined

defined

(4)


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 76 of 93

Channel_4_status active

available

not_available

not_defined

defined

(4)

Radar_Mono_Over-load_Status_On_RBR_ARadar_Mono_Over-load_Status_On_RBR_B

Does the radar have amono radar plot overloadsituation on the RBR node.

Unknown,Unavail,OK,Warning,Alarm

(5)

Radar_Sector_Memory_Over-load_Status_On_RBR_ARadar_Sector_Memory_Over-load_Status_On_RBR_B

Does the radar have amemory overload situationon the RBR node.

Unknown,Unavail,OK,Warning,Alarm

(5)

Radar_disconnection_cause Indicates the cause of aradar disconnection.

None,Manual,BiasAlarm

Radar_bias_status Indicates whether at leastone bias value calculatedfor this radar exceeds itscorresponding warning oralarm threshold

Normal,Warning,Alarm

(5)

TABLE 28 − CLASS ARTAS RADAR − ATTRIBUTES FOR READING

NOTE:

(1) : This attribute is the only one defined for all radars (the others are dedicated to one radar)

(2) : For each of these attributes an associated attribute gives the unit used (for instance : radar_period_unit)(please refer to appendix A)

(3) Please refer to the RBR SRS [17] for a definition of these attributes

(4) The channels statuses are provided in the following order : channel_1_status = channel of priority 1 channel_2_status = channel of priority 2 channel_3_status = channel of priority 3 channel_4_status = channel of priority 4.

The channel priorities are defined in the ARTAS SSS [12].


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200577 of 93

(5) Attributes are not relevant for ADS−B ground stations.



Radar_Connection_status Attribute enabling to request aconnection/disconnection of aradar

Connect

Disconnect

Radar_biases_computation_status Attribute leading to a computationor a non−computation of thebiases for all radars

Active (1)

Not_active (1)

Radar_time_stamping_bias Time stamping bias of the radar (1)

Radar_vertical_direction Vertical direction of the radar (1)

Radar_vertical_bias Time stamping bias of the radar (1)

Radar_PR_azimuth_bias PR azimuth bias of the radar (1)

Radar_PR_range_bias PR range bias of the radar (1)

Radar_PR_range_gain_bias PR range gain bias of the radar (1)

Radar_PR_squint_bias PR squint bias of the radar (1)

Radar_PR_elevation_bias PR elevation bias of the radar (1)

Radar_SSR_azimuth_bias SSR azimuth bias of the radar (1)

Radar_SSR_range_bias SSR range bias of the radar (1)

Radar_SSR_range_gain_bias SSR range gain bias of the radar (1)

Radar_SSR_squint_bias SSR squint bias of the radar (1)

TABLE 29 − CLASS ARTAS RADAR − ATTRIBUTES FOR WRITING

NOTE:

(1) Attributes are not relevant for ADS−B ground stations.

3.7.3.9.3 − Events


Radar_bias_computation_status−active The Radar_bias_computation_status is passed to ’active’

Radar_bias_computation_status−not_active The Radar_bias_computation_status is passed to ’not ac-

tive’


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 78 of 93

Radar_Operational_status−not_Connected The radar operational status is passed to ’not connected’

Radar_Operational_status−init The radar operational status is passed to ’initialization’

Radar_Operational_status−degraded The radar operational status is passed to ’degraded’

Radar_Operational_status−operational The radar operational status is passed to ’operational’

Radar_Operational_status−init_RMCDE The radar operational status is passed to ’initialization

RMCDE’

Radar_Connection_status−disconnected The radar connection status is passed to ’disconnected’

Radar_Connection_status−connected The radar connection status is passed to ’connected’

Channel_1_status_change The status of Channel 1 of the radars has changed




Radar_disconnection_cause_change There has been a change of state of the attribute

Radar_Disconnection_Cause (i.e. either a radar has been

disconnected or re−connected)

Radar_bias_status_change There has been a change of state of the attribute

Radar_bias_state.

TABLE 30 − CLASS ARTAS RADAR − EVENTS

3.7.3.10 − CLASS ARTAS USER



Number_of_Users Number of Users in the activated Plan

User_index 1..Number_of_users

User_number User identification

User_name Name of the user

User_class first_class

second_class

User_type Adjacent

Normal

Broadcast


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200579 of 93

User_Background_ser- Status of the Track information back- Active (1)

vice_status ground service Passive (1)

Suspended (1)

Empty (1)

Sensor_service_status Status of the Sensor information service Active (1)

Passive (1)

Suspended (1)

Empty (1)

User_Connection_status Connected

Disconnected

User_Transmission_type Transmission type of Track information Periodical

service A_periodical

Radar_synchronized

Sensor_Transmission_type Transmission type of the Sensor informa- Periodical

tion service A_periodical

Punctual

User_Transmission_load Average load used for transmission used

by the User (Track and Sensor informa-

tion)

Broadcast_Protocol_type Protocol used for transmission of

broadcast messages

AST30

AST62

TABLE 31 − CLASS ARTAS USER − ATTRIBUTES FOR READING

NOTE: (1) : Please refer to SSS ([11]) for the definition of related Background service status



User_Background_ser- Command related to the Track Informa- Interrupt (1)

vice_command tion service Restart (2)

Sensor_service_command Command related to the Sensor informa- Interrupt (1)

tion service Restart (2)


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 80 of 93

User_Connection_authoriza- Allow (3)

tion Disallow (4)

TABLE 32 − CLASS ARTAS USER − ATTRIBUTES FOR WRITING

NOTE: (1) : the relevant service is interrupted for the related User

(2) : the relevant service is restarted for the related User

(3) : the related User is allowed to connect. In case of a Broadcast mode, this commands leads alsoto a connection of the Broadcast mode and to the start of the service

(4) : the related User is disconnected


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200581 of 93

3.7.3.10.3 − Events


Background_service_status_change The status of the background Track information service pro-vided has changed

Sensor_service_status_change The status of the Sensor information service provided haschanged

Connection_status_change The connection status of the user has changed (spontane-ously or following an ARTAS request)

TABLE 33 − CLASS ARTAS USER − EVENTS

3.7.3.11 − OTHER MANAGED OBJECT CLASSES

3.7.3.11.1 − Peripherals

The definition of the MIB of the agent shall take into account the MIBs managed by the DEC agents relatedto the graphic boards of DAS and SMS HWCI (please refer to 10.4. in appendix A).

3.7.3.11.2 − External timing source device

The MIB shall include information related to the status of the Gorgy or NTP clock device located on theMASTER or SINGLE RBR (please refer to 10.1. in appendix A).


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 82 of 93

3.7.3.11.2.1 − Attributes available for reading


Clock_status The computation is in progress unknown (1) (2)

The application is busy with initialization of the clock sta-

tus. The initialization is in progress.

starting (1) (2)

(1) The clock is working correctly, the synchronisation is

done

(2) The global clock is synchronised and the external ref-

erence is failed

ok (1) (2)

(1) The clock is failed, the synchronisation is not done

(2) The global clock is unsynchronised and the external

reference clock is failed

failed (1) (2)

The clock cannot be used detached (1) (2)

inUse (3)

mainthalt (3)

maintoff (3)

The global clock is unsynchronised and the external ref-

erence clock is OK

standby (2)

The global clock is synchronised and the external refer-

ence clock is OK

operational (2)

transmit (3)

The local clock is synchronised and the external refer-

ence clock connected to the node is failed

ready (2)

The local clock is unsynchronised and the external refer-

ence clock connected to the node is failed

notOK (2)

TABLE 34 − CLOCK − ATTRIBUTES FOR READING

NOTE: (1) : Status which can be taken by the Gorgy clock device

(2) : Status which can be taken by the NTP clock device

(3) : Not used

Deleted text

Meaning of global clock synchronised for NTP clock device: All operational nodes (or a percentage of operational nodes according to −p argument value of the NTPIprocess, by default 100%) are synchronised.

Meaning of External Reference OK for NTP clock device:


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200583 of 93

The global status of the external reference is OK.A local external reference clock is OK if it works properly and it is considered as a primary server (itsstratum shall be inferior or equal to the value of the −m argument of the NTPI process, default value is 1).The global status of the external reference clock is OK if at least one local external reference clock status isOK (−P argument of the NTPI process, default value 1).In case of several external references used, a single local status is calculated by merging all the externalreferences states into one. In this case, all external references shall be OK to have the external referencelocal status set to OK.

3.7.3.11.2.2 − Events


Clock_status_changed The status of the clock has changed (refer to possible sta-tus according to clock type, table 34)

TABLE 35 − CLOCK − EVENTS

3.7.3.11.3 − Internal LAN devices

The MIB shall include the MIB related to the LAN Concentrator device (if available). The management of thisdevice shall be processed by the SNMP agent included in the LAN Concentrator (if existing) (please refer to10.3. in appendix A).

3.7.3.11.4 − External LANs status

The MIB shall include information about the status of the external LAN on each RB node (master and slave)(please refer to 10.1 in appendix A).

3.7.3.11.4.1 − Attributes available for reading


Ext_LAN_name the name of the LAN A, B, C, D, E, F

Ext_LAN_Chain_A_Sta-

tus

The status of the ext LAN on the RB of the

chain A

OK, NOK, Unavailable,

OKEndWarning,

NOKEndWarning

Ext_LAN_Chain_B_Sta-

tus

The status of the ext LAN on the RB of the

chain B

OK, NOK, Unavailable,

OKEndWarning,

NOKEndWarning

TABLE 36 − EXTERNAL LANS STATUS


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 84 of 93

3.7.3.11.4.2 − Events


ArtasExtLanChainAStatusChanged The status of the ext LAN on RBR A has changed

ArtasExtLanChainBStatusChanged The status of the ext LAN on RBR B has changed

TABLE 37 − EXTERNAL LANS EVENTS

3.7.3.11.5 − Centralised supervision private information

The MIB includes information for the private use of the centralised supervision (please refer to 10.1 inAppendix A1).


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200585 of 93

3.8 − TIME INTERFACE SPECIFICATION (IF_RBR_CLK)

This interface allows to receive the Clock signals from an external master timing source to synchronize thewhole ARTAS Unit with a Universal Time Coordinated (UTC) reference. These Clock signals are eitherreceived by a Gorgy RT3000 time center included in the RB HWCI (serial input), or through an external LANwith the use of the Network Time Protocol (NTP).

3.8.1 − PHYSICAL CONNECTION OVERVIEW

3.8.1.1 − GORGY RT3000 TIME CENTER

The internal GORGY RT3000 time center can be radio−synchronized with hourly time signals (Tele Diffusionde France (France Inter) transmitter in France (162 kHz Long Wave) or DCF in Germany (77.5kHz)) or canbe synchronized through the GPS system.

For a description of the synchronization of the GORGY RT3000 time center, please refer to [19].

3.8.1.2 − NTP

The protocol NTP allows a host to synchronize its date and time to one or several NTP servers on thenetwork. In case of several NTP servers, the best one is selected by the use of a specific algorithm.

When the NTP protocol is used for the ARTAS System, at least one NTP server has to be connectedthrough an external LAN and to send on this LAN NTP Packets.

3.8.2 − DATA REQUIREMENTS

3.8.2.1 − GORGY RT3000 TIME CENTER

3.8.2.1.1 − Transmitters characteristics

For a description of the transmitter characteristics, please refer to [19].

Deleted text.

3.8.2.1.2 − Degraded mode

In absence of transmitter (failure, maintenance, bad reception...) the system is no longer externallysynchronized. However the GORGY RT3000 time center continues to supply the Router Bridges with aninternally generated Universal Time Coordinated reference. In this case the accuracy is 0.1s/24h undernormal conditions of use (20°C). The GORGY RT3000 time center will be automatically synchronized againwhen the transmitter becomes available again.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 86 of 93

3.8.2.1.3 − Transmission characteristics

The transmission parameters are set as follows :

− rate = 9600 bauds,

− parity = off,

− format = 8 bits,

− stop bit = 1.

The Gorgy time is sent at the Master RBR every second.

3.8.2.2 − NTP

For a detailed description of the Network Time Protocol, please refer to [20].

3.8.2.2.1 − Transmitter characteristics

The NTP servers send time packets according to Network Time Protocol packet format (version 3).

3.8.2.2.2 − Degraded mode

In case none NTP server is available the system is no longer external synchronized. The system timing isthen supplied by the Router Bridge internal clock. When a NTP Server is available again, the system will beautomatically re−synchronized on this external timing source provided that the delta time between thesystem clock and the external clock is within a given range (parameter).


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200587 of 93

4 − QUALITY ASSURANCENone.


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 88 of 93

5 − PREPARATION FOR DELIVERYNone.


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200589 of 93

6 − GLOSSARY

�

ARTAS ATM Surveillance Tracker And Server

ASTERIX All−purpose STructured Eurocontrol Radar Information eXchange.

ATC Air Traffic Control

�

BNS Basis system Name Server. (UBSS facility)

�

CLNP Connection Less Network Protocol

COTP Connection Oriented Transport Protocol

CPU Computer Processing Unit

CSCI Computer Software Configuration Item

�

DAS Data Analysis Station

DEC Digital Equipment Corporation

DSAP Destination Service Access Point


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 90 of 93

�

ECR Engineering Change Request

�

FCS Field Control Sequence

FDDI Fibre Distributed Data Interface

FIFO First In First Out

FPPS Flight Plan data Processing System

FRN Field Reference Number

FSPEC Field SPECification

�

HDLC High Level Data Link Communication

HWCI HardWare Configuration Item

�

IP Internet Protocol

IPC Inter Process Communication. (UBSS facility)

IPM Internet protocol Multicast

IRMA Indicateur Radar des Mouvements d’Aerodrome

IRS Interface Requirement Specification

ISO International Standards Organization

LAN Local Area Network


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200591 of 93

LLC Logical Link Control

MAC Medium Access Control

MCPA Méthodologie de Conduite de Projet et d’Affaire

MIB Management Information Base

MOF Mode Of Flight

�

NCF Node Configuration File

NPDU Network Protocol Data Unit

�

OSI Open Systems Interconnection

PDC Private Data Channel

PDU Protocol Data Unit

PR Primary surveillance Radar

�

RADNET RADar NETwork implemented in the so−called four states area (Benelux & Germany)

RB Router Bridge HWCI

RBR Router Bridge CSCI

RDPDS Radar Data Processing and Distribution System

RFS Random Field Sequencing


COMSOFT 46 127 300 − 506 / V7.2 / 11.11.2005 92 of 93

RENAR REseau de la Navigation AeRienne

RMCDE Radar Message Conversion and Distribution Equipment

RS Random Sequence indicator

RSTNA Reseau Specifique de Test de la Navigation Aerienne

RSAP RADNET Service Access Point

�

SAC Source Area Code

SAP Service Access Point

SIC Source Identity Code

SIR Serveur d’Informations Radar

SMS System Manager Station

SNMP Simple Network Management protocol

SRS Software Requirement Specification

SSA System SNMP Agent

SSAP Source Service Access Point

SSDD System/Segment Design Document

SSR Secondary Surveillance Radar

SSS System/Segment Specification

STNA Service Technique de la Navigation Aerienne

SUM Software User Manual

�

TDF Tele Diffusion Francaise

TPDU Transport Protocol Data Unit

�

UAP User Application Profile

UBSS Unix Based System Software


COMSOFT46 127 300 − 506 / V7.2 / 11.11.200593 of 93

UDP User Datagram Protocol

UT Universal Time

UTC Universal Time Clock

�

WAN Wide Area Network


A1−146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

APPENDIX A1

MIB DEFINITION

10. MIB DEFINITION

Hereafter are provided files used to define the MIB available for ARTAS. This definition includes also ”standard” MIBs not provided herein :

− SMI ASN.1 description (RFC 1155),

− view ASN.1 description,

− MIB−II ASN.1 description (RFC 1213).Please refer to the SSA SUM [14] for a definition of these ”standard” MIBs.

10.1. ARTAS MIB DEFINITION−− Artas MIB−−−− Creation date : 08/06/98−−−− Prepared by Comsoft GmbH for EUROCONTROL−−−− Author : M. PENICAUD SDD/TCE/TFP−−−− Modified by M. PENICAUD 15/07/98−− M. PENICAUD 19/08/98−− M. PENICAUD 09/11/98−− MJ PEDRON 17/08/99 PCR_ARTAS V5_0134 − ECR505−− MJ PEDRON 17/09/99 ECR_ART_V5_0512−− MJ PEDRON 17/09/99 PCR_ARTAS V5_0164 − ECR511 ECR512−− MJ PEDRON 17/09/99 ECR_ART_V5_0510−− MJ PEDRON 03/11/99 PCR_ARTAS_V4_0433−− MJ PEDRON 09/12/99 ECR_ART_V5_0513−− E. FAROUX 21/06/00 PCR_ARTAS_V4_0533−− MJ PEDRON 07/11/00 PCR ARTAS_V6B_0045 − Pb after ECR_ART_V5_0512 modif−− E. FAROUX 19/01/01 PCR_ARTAS_V6B_0069−− M. RAVAILHE 24/04/01 ECP_ART_0605−− M. BUTOW 06/06/02 ATR 654 and 702−− K. HAYEN 22/07/03 ATR 843−− M. BUTOW 24/07/03 ATR_850−− M. BUTOW 01/08/03 ACP_199−− K. HAYEN 01/08/03 ACP 184−− K. HAYEN 02/08/03 ACP 185−− M. BUTOW 09/10/03 V6C0: change enterprise to Eurocontrol−− K. HAYEN 18/12/03 ACP 137−− K. HAYEN 21.01.04 Modified some comments of overload values to not mention ”degradation”−− K. HAYEN 20.02.04 Added MIB values for overload details−− M. BUTOW 16.03.04 Added V7A0 attributes for radar and broadcast types−− M. BUTOW 15.06.04 Incorporate ECAMOS modifications from CAMOS email 03890


A1−2 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− (IMPORT statements changes, but acoldStart change not yet)−−−− Version 7.A.0.0−− $Header: /v/CvsTree/artas/src/snmp/mibs/artas.my,v 1.1.30.12.2.8 2004/06/15 11:52:34 mbutow Exp $

ARTAS−MIB DEFINITIONS ::= BEGIN

IMPORTS enterprises, OBJECT−TYPE FROM RFC1155−SMIDisplayString FROM RFC1213−MIB;

eurocontrol OBJECT IDENTIFIER ::= { enterprises 2363 }masAgents OBJECT IDENTIFIER ::= { eurocontrol 3 }artas OBJECT IDENTIFIER ::= { masAgents 7 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artas−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−artasApplication OBJECT IDENTIFIER ::= { artas 1 }

artasTechnical OBJECT IDENTIFIER ::= { artas 2 }

artasTrap OBJECT IDENTIFIER ::= { artas 3 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasApplication−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−artasSystem OBJECT IDENTIFIER ::= { artasApplication 1 }

artasNode OBJECT IDENTIFIER ::= { artasApplication 2 }

artasFunction OBJECT IDENTIFIER ::= { artasApplication 3 }

artasRadar OBJECT IDENTIFIER ::= { artasApplication 4 }

artasUser OBJECT IDENTIFIER ::= { artasApplication 5 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasSystem−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

artasSystemInfo OBJECT IDENTIFIER ::= { artasSystem 1 }

artasSystemCommand OBJECT IDENTIFIER ::= { artasSystem 2 }

artasUnitModeOfUse OBJECT−TYPE SYNTAX INTEGER { live(1), simulation(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”The unit mode of use : static value.” ::= { artasSystemInfo 1 }

artasUnitConfiguration OBJECT−TYPE SYNTAX INTEGER { single(1), dual(2), dualSplit(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”The unit configuration.” ::= { artasSystemInfo 2 }

artasOperationalStatus OBJECT−TYPE SYNTAX INTEGER { planDeactivated(1), planActivated(2), planActivating(3), planDeactivating(4), planSynchronising(5) } ACCESS read−only STATUS mandatory DESCRIPTION ” The flight plan operational status.” ::= { artasSystemInfo 3 }

artasIncomingPlotNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Current incoming plot number per second : updated


A1−346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

every 10 seconds.” ::= { artasSystemInfo 4 }

artasIncomingTrackNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Current incoming adjacent unit tracks per minute.” ::= { artasSystemInfo 5 }

artasUnitVersion OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”ARTAS software version.” ::= { artasSystemInfo 6 }

−− ACP_199 beginartasHelloTrapStatus OBJECT−TYPE SYNTAX INTEGER { notActive(1), active(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Controls sending of hello traps by ARTAS.” ::= { artasSystemInfo 7 }

artasHelloTrapPeriod OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The period in seconds at which hello traps are sent by ARTAS.” ::= { artasSystemInfo 8 }

artasHelloTrapTrigger OBJECT−TYPE SYNTAX INTEGER { foo(1), bar(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”A trap trigger which is toggled by ARTAS to dispatch a Hello Trap.” ::= { artasSystemInfo 9 }−− ACP_199 end

−− ACP_144 beginartasSystemColdStartCommandStatus OBJECT−TYPE SYNTAX INTEGER { idle(1), busy(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Status of system cold start command execution.” ::= { artasSystemInfo 10 }

artasSystemColdStartCommandResult OBJECT−TYPE SYNTAX INTEGER { clear(1), accepted(2), successful(3), error−command−rejected(4), error−mms−unreachable(5), error−database−locked(6), error−incorrect−chain−number(7) } ACCESS read−write STATUS mandatory DESCRIPTION ”Result of last system cold start command.” ::= { artasSystemInfo 11 }

artasSystemHotStartCommandResult OBJECT−TYPE SYNTAX INTEGER { clear(1), accepted(2), successful(3), error−command−rejected(4), error−mms−unreachable(5), error−database−locked(6), error−incorrect−chain−number(7)


A1−4 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

} ACCESS read−write STATUS mandatory DESCRIPTION ”Result of last system hot start command.” ::= { artasSystemInfo 12 }

artasSystemStopCommandResult OBJECT−TYPE SYNTAX INTEGER { clear(1), accepted(2), successful(3), error−command−rejected(4), error−node−unreachable(5) } ACCESS read−write STATUS mandatory DESCRIPTION ”Result of last system stop command.” ::= { artasSystemInfo 13 }

artasSystemHotStartCommandStatus OBJECT−TYPE SYNTAX INTEGER { idle(1), busy(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Status of system hot start command execution.” ::= { artasSystemInfo 14 }

artasSystemStopCommandStatus OBJECT−TYPE SYNTAX INTEGER { idle(1), busy(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Status of system stop command execution.” ::= { artasSystemInfo 15 }

artasSystemActivatePlanCommandStatus OBJECT−TYPE SYNTAX INTEGER { idle(1), busy(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”Status of system plan activation command execution.” ::= { artasSystemInfo 16 }−− ACP_144 end

artasSystemHotStart OBJECT−TYPE SYNTAX INTEGER { hot(1) } ACCESS write−only STATUS mandatory DESCRIPTION ”Hot start of the ARTAS UBSS System with scripts. ” ::= { artasSystemCommand 1 }

artasSystemColdStart OBJECT−TYPE SYNTAX INTEGER { cold(1) } ACCESS write−only STATUS mandatory DESCRIPTION ”Cold start of the ARTAS UBSS System with scripts. ” ::= { artasSystemCommand 2 }

artasSystemStop OBJECT−TYPE SYNTAX INTEGER { stop(1) } ACCESS write−only STATUS mandatory DESCRIPTION ”Stop the ARTAS UBSS System.” ::= { artasSystemCommand 3 }

artasSystemActivatePlan OBJECT−TYPE SYNTAX INTEGER { planColdActivation(1)


A1−546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

} ACCESS write−only STATUS mandatory DESCRIPTION ”Activate the flight plan.” ::= { artasSystemCommand 4 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasNode−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

artasNodeInfo OBJECT IDENTIFIER ::= { artasNode 1 }

artasNodeCommand OBJECT IDENTIFIER ::= { artasNode 2 }

artasNodeName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The name of the node.” ::= { artasNodeInfo 1 }

artasNodeFunctionSMS OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”The node is configured to run the MMS CSCI.” ::= { artasNodeInfo 2 }

artasNodeFunctionSS OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”The node is configured to run the SRV CSCI.” ::= { artasNodeInfo 3 }

artasNodeFunctionRB OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”The node is configured to run the RBR CSCI.” ::= { artasNodeInfo 4 }

artasNodeFunctionTS OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”The node is configured to run the TRK CSCI.” ::= { artasNodeInfo 5 }

artasNodeFunctionDAS OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”The node is configured to run the REC CSCI.” ::= { artasNodeInfo 6 }

artasNodeOperationalStatus OBJECT−TYPE SYNTAX INTEGER { stopped(1), operational(2), starting(3), stopping(4), residentOnly(5) } ACCESS read−only


A1−6 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

STATUS mandatory DESCRIPTION ”The ARTAS application status.” ::= { artasNodeInfo 7 }

artasNodeRedundancyStatus OBJECT−TYPE SYNTAX INTEGER { notAvailable(1), principal(2), single(3), hotStandby(4), coldStandby(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”The ARTAS redundancy status.” ::= { artasNodeInfo 8 }

−− ACP_144 beginartasNodeStartCommandStatus OBJECT−TYPE SYNTAX INTEGER { idle(1), busy(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Status of node start command execution.” ::= { artasNodeInfo 9 }

artasNodeStopCommandStatus OBJECT−TYPE SYNTAX INTEGER { idle(1), busy(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Status of node stop command execution.” ::= { artasNodeInfo 10 }

artasNodeShutdownCommandStatus OBJECT−TYPE SYNTAX INTEGER { idle(1), busy(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Status of node shutdown command execution.” ::= { artasNodeInfo 11 }

artasNodeRestartCommandStatus OBJECT−TYPE SYNTAX INTEGER { idle(1), busy(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Status of node restart command execution.” ::= { artasNodeInfo 12 }

artasNodeStartCommandResult OBJECT−TYPE SYNTAX INTEGER { clear(1), accepted(2), successful(3), error−node−unreachable(4), error−database−locked(5), error−database−access(6), error−with−configuration−file(7), error−ubss−still−present(8), error−basic−system−already−called(9) } ACCESS read−write STATUS mandatory DESCRIPTION ”Result of last node start command.” ::= { artasNodeInfo 13 }

artasNodeStopCommandResult OBJECT−TYPE SYNTAX INTEGER { clear(1), accepted(2), successful(3), error−node−unreachable(4), error−no−basic−system(5),


A1−746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

error−not−owner−of−basic−system(6) } ACCESS read−write STATUS mandatory DESCRIPTION ”Result of last node start command.” ::= { artasNodeInfo 14 }−− ACP_144 end

−− ACP 184 beginartasLocalClockStatus OBJECT−TYPE SYNTAX INTEGER { unknown(1), starting(2), ok(3), failed(4), detached(5), inUse(6), mainthalt(7), maintoff(8), standby(9), operational(10), transmit(11), ready(12), notOK(13) } ACCESS read−only STATUS mandatory DESCRIPTION ”Local UBSS clock status.” ::= { artasNodeInfo 15 }

artasNodeInfoNTP OBJECT IDENTIFIER ::= { artasNodeInfo 16 }

artasNodeInfoNTPStatus OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Technical NTP Status string of the node.” ::= { artasNodeInfoNTP 1 }artasNodeInfoNTPStratum OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Technical NTP Stratum of the node.” ::= { artasNodeInfoNTP 2 }artasNodeInfoNTPPeerCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Technical NTP Peer count of the node.” ::= { artasNodeInfoNTP 3 }artasNodeInfoNTPMainPeer OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Technical NTP Peer id with which the node syncs.” ::= { artasNodeInfoNTP 4 }

artasNodeInfoNTPPeers OBJECT IDENTIFIER ::= { artasNodeInfoNTP 5 }

artasNodeInfoNTPPeer1 OBJECT IDENTIFIER ::= { artasNodeInfoNTPPeers 1 }

artasNodeInfoNTPPeer1Hostname OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Hostname of the peer.” ::= { artasNodeInfoNTPPeer1 1 }

artasNodeInfoNTPPeer1Address OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Hostname of the peer.” ::= { artasNodeInfoNTPPeer1 2 }

artasNodeInfoNTPPeer1Status OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Status of the peer.”


A1−8 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

::= { artasNodeInfoNTPPeer1 3 }

artasNodeInfoNTPPeer1Reachable OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Reachability of the peer.” ::= { artasNodeInfoNTPPeer1 4 }

artasNodeInfoNTPPeer1Offset OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Offset of the peer.” ::= { artasNodeInfoNTPPeer1 5 }

artasNodeInfoNTPPeer1Stratum OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Technical NTP Stratum of the peer node.” ::= { artasNodeInfoNTPPeer1 6 }



artasNodeInfoNTPPeer2Address OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Hostname of the peer.” ::= { artasNodeInfoNTPPeer2 2 }

artasNodeInfoNTPPeer2Status OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Status of the peer.” ::= { artasNodeInfoNTPPeer2 3 }



artasNodeInfoNTPPeer2Stratum OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Technical NTP Stratum of the peer node.” ::= { artasNodeInfoNTPPeer2 6 }



artasNodeInfoNTPPeer3Address OBJECT−TYPE SYNTAX DisplayString ACCESS read−only


A1−946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

STATUS mandatory DESCRIPTION ”Hostname of the peer.” ::= { artasNodeInfoNTPPeer3 2 }

artasNodeInfoNTPPeer3Status OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Status of the peer.” ::= { artasNodeInfoNTPPeer3 3 }



artasNodeInfoNTPPeer3Stratum OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Technical NTP Stratum of the peer node.” ::= { artasNodeInfoNTPPeer3 6 }−− ACP 184 end

artasNodeStart OBJECT−TYPE SYNTAX INTEGER { start(1) } ACCESS write−only STATUS mandatory DESCRIPTION ”UBSS start node command : implemented with subsystems in UBSS configuration.” ::= { artasNodeCommand 1 }

artasNodeStop OBJECT−TYPE SYNTAX INTEGER { stop(1) } ACCESS write−only STATUS mandatory DESCRIPTION ”UBSS stop node command : standard UBSS command.” ::= { artasNodeCommand 2 }

artasNodeShutdown OBJECT−TYPE SYNTAX INTEGER { shutdown(1) } ACCESS write−only STATUS mandatory DESCRIPTION ”UBSS shutdown node command : standard UBSS command.” ::= { artasNodeCommand 3 }

artasNodeRestart OBJECT−TYPE SYNTAX INTEGER { restart(1) } ACCESS write−only STATUS mandatory DESCRIPTION ”UBSS restart node command : standard UBSS command.” ::= { artasNodeCommand 4 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasFunction−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

artasFunctionTable OBJECT−TYPE SYNTAX SEQUENCE OF ArtasFunctionEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of function Entries”


A1−10 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

::= { artasFunction 1 }

artasFunctionNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The Number of functions in the system” ::= { artasFunctionTable 1 }

artasFunctionEntry OBJECT−TYPE SYNTAX ArtasFunctionEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Function Entries” INDEX { artasFunctionIndex } ::= { artasFunctionTable 2 }

ArtasFunctionEntry ::= SEQUENCE { artasFunctionIndex INTEGER, artasFunctionName DisplayString, artasFunctionTechnicalStatus INTEGER, artasFunctionSoftwareVersionNodeA DisplayString, artasFunctionSoftwareVersionNodeB DisplayString, artasFunctionNodeAName DisplayString, artasFunctionNodeBName DisplayString }

−− ACP 185 beginartasFunctionNodeOverloads OBJECT IDENTIFIER ::= { artasFunction 2 }

artasFunctionNodeOverloadsRBR OBJECT IDENTIFIER ::= { artasFunctionNodeOverloads 1 }artasFunctionNodeOverloadsRBRA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsRBR 1 }artasFunctionNodeOverloadsRBRB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsRBR 2 }artasFunctionNodeOverloadsSRV OBJECT IDENTIFIER ::= { artasFunctionNodeOverloads 2 }artasFunctionNodeOverloadsSRVA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsSRV 1 }artasFunctionNodeOverloadsSRVB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsSRV 2 }artasFunctionNodeOverloadsTRK OBJECT IDENTIFIER ::= { artasFunctionNodeOverloads 3 }artasFunctionNodeOverloadsTRKA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsTRK 1 }artasFunctionNodeOverloadsTRKB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsTRK 2 }artasFunctionNodeOverloadsMMS OBJECT IDENTIFIER ::= { artasFunctionNodeOverloads 4 }artasFunctionNodeOverloadsMMSA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsMMS 1 }artasFunctionNodeOverloadsMMSB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsMMS 2 }artasFunctionNodeOverloadsREC OBJECT IDENTIFIER ::= { artasFunctionNodeOverloads 5 }artasFunctionNodeOverloadsRECA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsREC 1 }artasFunctionNodeOverloadsRECB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsREC 2 }

−− ACP 137 beginartasFunctionNodeOverloadsSUP OBJECT IDENTIFIER ::= { artasFunctionNodeOverloads 6 }artasFunctionNodeOverloadsSUPA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsSUP 1 }artasFunctionNodeOverloadsSUPB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsSUP 2 }−− ACP 137 end

artasFunctionNodeOverloadsRBRAAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on this RBR A node.” ::= { artasFunctionNodeOverloadsRBRA 1 }

artasFunctionNodeOverloadsRBRBAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on this RBR B node.” ::= { artasFunctionNodeOverloadsRBRB 1 }


A1−1146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

artasFunctionNodeOverloadsRBRACPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the RBR A node.” ::= { artasFunctionNodeOverloadsRBRA 2 }

artasFunctionNodeOverloadsRBRBCPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the RBR B node.” ::= { artasFunctionNodeOverloadsRBRB 2 }

artasFunctionNodeOverloadsRBRASRVTransmission OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”SRV Transmission overload detected on the RBR A node.” ::= { artasFunctionNodeOverloadsRBRA 3 }

artasFunctionNodeOverloadsRBRBSRVTransmission OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”SRV Transmission overload detected on the RBR B node.” ::= { artasFunctionNodeOverloadsRBRB 3 }

artasFunctionNodeOverloadsRBRATotalPlot OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Total plot overload on RBR.” ::= { artasFunctionNodeOverloadsRBRA 4 }

artasFunctionNodeOverloadsRBRBTotalPlot OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Total plot overload on RBR.” ::= { artasFunctionNodeOverloadsRBRB 4 }

artasFunctionNodeOverloadsRBRAMonoRadarPlot OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1),


A1−12 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Radar plot overload on RBR.” ::= { artasFunctionNodeOverloadsRBRA 5 }

artasFunctionNodeOverloadsRBRBMonoRadarPlot OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Radar plot overload on RBR.” ::= { artasFunctionNodeOverloadsRBRB 5 }

artasFunctionNodeOverloadsRBRARadarSectorMemory OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Radar plot overload in sectors on RBR.” ::= { artasFunctionNodeOverloadsRBRA 6 }

artasFunctionNodeOverloadsRBRBRadarSectorMemory OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Radar plot overload in sectors on RBR.” ::= { artasFunctionNodeOverloadsRBRB 6 }

artasFunctionNodeOverloadsRBRATRKFilteringLevelNonZero OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Filtering due to TRK overload on RBR is active.” ::= { artasFunctionNodeOverloadsRBRA 7 }

artasFunctionNodeOverloadsRBRBTRKFilteringLevelNonZero OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Filtering due to TRK overload on RBR is active.” ::= { artasFunctionNodeOverloadsRBRB 7 }

artasFunctionNodeOverloadsSRVAAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory


A1−1346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

DESCRIPTION ”Any overload on this SRV A node.” ::= { artasFunctionNodeOverloadsSRVA 1 }

artasFunctionNodeOverloadsSRVBAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on this SRV B node.” ::= { artasFunctionNodeOverloadsSRVB 1 }

artasFunctionNodeOverloadsSRVACPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the SRV A node.” ::= { artasFunctionNodeOverloadsSRVA 2 }

artasFunctionNodeOverloadsSRVBCPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the SRV B node.” ::= { artasFunctionNodeOverloadsSRVB 2 }

artasFunctionNodeOverloadsSRVATransmission OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”SRV transmission overload on the SRV A node.” ::= { artasFunctionNodeOverloadsSRVA 3 }

artasFunctionNodeOverloadsSRVBTransmission OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”SRV transmission overload on the SRV B node.” ::= { artasFunctionNodeOverloadsSRVB 3 }

artasFunctionNodeOverloadsTRKAAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on this TRK A node.” ::= { artasFunctionNodeOverloadsTRKA 1 }

artasFunctionNodeOverloadsTRKBAny OBJECT−TYPE


A1−14 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on this TRK B node.” ::= { artasFunctionNodeOverloadsTRKB 1 } artasFunctionNodeOverloadsTRKACPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the TRK A node.” ::= { artasFunctionNodeOverloadsTRKA 2 }

artasFunctionNodeOverloadsTRKBCPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the TRK B node.” ::= { artasFunctionNodeOverloadsTRKB 2 } artasFunctionNodeOverloadsTRKACommunication OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the TRK A node.” ::= { artasFunctionNodeOverloadsTRKA 3 }

artasFunctionNodeOverloadsTRKBCommunication OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the TRK B node.” ::= { artasFunctionNodeOverloadsTRKB 3 } artasFunctionNodeOverloadsTRKAMemory OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the TRK A node.” ::= { artasFunctionNodeOverloadsTRKA 4 }

artasFunctionNodeOverloadsTRKBMemory OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2),


A1−1546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the TRK B node.” ::= { artasFunctionNodeOverloadsTRKB 4 }

artasFunctionNodeOverloadsMMSAAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on this MMS A node.” ::= { artasFunctionNodeOverloadsMMSA 1 }

artasFunctionNodeOverloadsMMSBAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on this MMS B node.” ::= { artasFunctionNodeOverloadsMMSB 1 }

artasFunctionNodeOverloadsMMSACPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the MMS A node.” ::= { artasFunctionNodeOverloadsMMSA 2 }

artasFunctionNodeOverloadsMMSBCPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the MMS B node.” ::= { artasFunctionNodeOverloadsMMSB 2 }

artasFunctionNodeOverloadsRECAAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on this REC A node.” ::= { artasFunctionNodeOverloadsRECA 1 }

artasFunctionNodeOverloadsRECBAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION


A1−16 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

”Any overload on this REC B node.” ::= { artasFunctionNodeOverloadsRECB 1 }

artasFunctionNodeOverloadsRECACPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the REC A node.” ::= { artasFunctionNodeOverloadsRECA 2 }

artasFunctionNodeOverloadsRECBCPU OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”CPU overload on the REC B node.” ::= { artasFunctionNodeOverloadsRECB 2 }

−− ACP 137 beginartasFunctionNodeOverloadsSUPAAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on SUP A node.” ::= { artasFunctionNodeOverloadsSUPA 1 } artasFunctionNodeOverloadsSUPBAny OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Any overload on SUP B node.” ::= { artasFunctionNodeOverloadsSUPB 1 } artasFunctionNodeOverloadsSUPARequestLimitAllIP OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”SNMP overload of the all IP request limit on the SUP A node.” ::= { artasFunctionNodeOverloadsSUPA 2 }

artasFunctionNodeOverloadsSUPBRequestLimitAllIP OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”SNMP overload of the all IP request limit on the SUP B node.” ::= { artasFunctionNodeOverloadsSUPB 2 }

artasFunctionNodeOverloadsSUPARequestLimitPerIP OBJECT−TYPE


A1−1746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”SNMP overload of the per IP request limit on the SUP A node.” ::= { artasFunctionNodeOverloadsSUPA 3 }

artasFunctionNodeOverloadsSUPBRequestLimitPerIP OBJECT−TYPE SYNTAX INTEGER { unknown(255), unavail(254), ok(1), warning(2), alarm(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”SNMP overload of the per IP request limit on the SUP B node.” ::= { artasFunctionNodeOverloadsSUPB 3 }−− ACP 137 end

artasFunctionNodeOverloadsDetailsRBRATRKFilteringLevel OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Numeric filtering level applied by the RBR node” ::= { artasFunctionNodeOverloadsDetailsRBRA 4 }

artasFunctionNodeOverloadsDetailsRBRBTRKFilteringLevel OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Numeric filtering level applied by the RBR node” ::= { artasFunctionNodeOverloadsDetailsRBRB 4 }−− ACP 185 end

artasFunctionIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each node. Its value ranges between 1 and the value of functionNumber” ::= { artasFunctionEntry 1 }

artasFunctionName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The function name.” ::= { artasFunctionEntry 2 }

artasFunctionTechnicalStatus OBJECT−TYPE SYNTAX INTEGER { normal(1), degraded(2), notAvailable(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”The function technical status.” ::= { artasFunctionEntry 3 }

artasFunctionSoftwareVersionNodeA OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The software version of the function on node A.” ::= { artasFunctionEntry 4 }

artasFunctionSoftwareVersionNodeB OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The software version of the function on node B.” ::= { artasFunctionEntry 5 }


A1−18 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

artasFunctionNodeAName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The name of the node on which the function is running on chain A.” ::= { artasFunctionEntry 6 }

artasFunctionNodeBName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The name of the node on which the function is running on chain B.” ::= { artasFunctionEntry 7 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasRadar −− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

artasRadarBiasComputationStatus OBJECT−TYPE SYNTAX INTEGER { notActive(1), active(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Biases computation status for all radars.” ::= { artasRadar 1 }

artasRadarTable OBJECT−TYPE SYNTAX SEQUENCE OF ArtasRadarEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of Radar Entries” ::= { artasRadar 2 }

artasRadarNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The Number of Radars” ::= { artasRadarTable 1 }

artasRadarEntry OBJECT−TYPE SYNTAX ArtasRadarEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Radar Entries” INDEX { artasRadarIndex } ::= { artasRadarTable 2 }

ArtasRadarEntry ::= SEQUENCE { artasRadarIndex INTEGER, artasRadarSIC INTEGER, artasRadarSAC INTEGER, artasRadarName DisplayString, artasRadarType INTEGER, artasRadarPeriod INTEGER, artasRadarPeriodUnit DisplayString, artasRadarTimeStampingBias INTEGER, artasRadarTimeStampingBiasUnit DisplayString, artasRadarVerticalDirection INTEGER, artasRadarVerticalDirectionUnit DisplayString, artasRadarVerticalBias INTEGER, artasRadarVerticalBiasUnit DisplayString, artasRadarPRAzimuthBias INTEGER, artasRadarPRAzimuthBiasUnit DisplayString,


A1−1946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

artasRadarPRRangeBias INTEGER, artasRadarPRRangeBiasUnit DisplayString, artasRadarPRRangeGain INTEGER, artasRadarPRRangeGainUnit DisplayString, artasRadarPRSquintBias INTEGER, artasRadarPRSquintBiasUnit DisplayString, artasRadarPRElevationBias INTEGER, artasRadarPRElevationBiasUnit DisplayString, artasRadarSSRAzimuthBias INTEGER, artasRadarSSRAzimuthBiasUnit DisplayString, artasRadarSSRRangeBias INTEGER, artasRadarSSRRangeBiasUnit DisplayString, artasRadarSSRRangeGain INTEGER, artasRadarSSRRangeGainUnit DisplayString, artasRadarSSRSquintBias INTEGER, artasRadarSSRSquintBiasUnit DisplayString, artasRadarOperationalStatus INTEGER, artasRadarConnectionStatus INTEGER, artasRadarDegrTimeOut INTEGER, artasRadarDegrIncoherentTimeStamp INTEGER, artasRadarDegrIncoherentRadarPeriod INTEGER, artasRadarDegrHighInvalidModeA INTEGER,−− $PCR_ARTAS_V4_0433 Begin−− artasRadarDegrHighInvalidModeB artasRadarDegrHighInvalidModeC−− $PCR_ARTAS_V4_0433 End INTEGER, artasRadarDegrHighOldInfo −− $ECR_ART_0510 Begin −− INTEGER INTEGER, artasRadarChannel1Status INTEGER, artasRadarChannel2Status INTEGER, artasRadarChannel3Status INTEGER, artasRadarChannel4Status INTEGER, −− ACP 185 begin artasRadarMonoOverloadStatusOnRBRA INTEGER, artasRadarMonoOverloadStatusOnRBRB INTEGER, artasRadarSectorMemoryOverloadStatusOnRBRA INTEGER, artasRadarSectorMemoryOverloadStatusOnRBRB INTEGER−− ACP 185 end }

artasRadarIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each radar. Its value ranges between 1 and the value of radarNumber” ::= { artasRadarEntry 1 }

artasRadarSIC OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Radar SIC.” ::= { artasRadarEntry 2 }


A1−20 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

artasRadarSAC OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Radar SAC.” ::= { artasRadarEntry 3 }

artasRadarName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Name of the radar.” ::= { artasRadarEntry 4 }

artasRadarType OBJECT−TYPE SYNTAX INTEGER { primary(1), secondary(2), combined(3),−− $ECR_ART_V5_513 Begin − add CombinedModeS modeS(4), combinedmodeS(5),−− V7A0 begin − add ADS−B radar type ads−b(6)−− V7A0 end − add ADS−B radar type−− $ECR_ART_V5_513 End } ACCESS read−only STATUS mandatory DESCRIPTION ”Type of the radar.” ::= { artasRadarEntry 5 }

artasRadarPeriod OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Period of the radar.” ::= { artasRadarEntry 6 }

artasRadarPeriodUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarPeriod object.” ::= { artasRadarEntry 7 }

artasRadarTimeStampingBias OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 8 }

artasRadarTimeStampingBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarTimeStampingBias object.” ::= { artasRadarEntry 9 }

artasRadarVerticalDirection OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 10 }

artasRadarVerticalDirectionUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarVerticalDirection object.” ::= { artasRadarEntry 11 }

artasRadarVerticalBias OBJECT−TYPE SYNTAX INTEGER


A1−2146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 12 }

artasRadarVerticalBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarVerticalBias object.” ::= { artasRadarEntry 13 }

artasRadarPRAzimuthBias OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 14 }

artasRadarPRAzimuthBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarPRAzimuthBias object.” ::= { artasRadarEntry 15 }

artasRadarPRRangeBias OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 16 }

artasRadarPRRangeBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarPRRangeBias object.” ::= { artasRadarEntry 17 }

artasRadarPRRangeGain OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 18 }

artasRadarPRRangeGainUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarPRRangeGain object.” ::= { artasRadarEntry 19 }

artasRadarPRSquintBias OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 20 }

artasRadarPRSquintBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarPRSquintBias object.” ::= { artasRadarEntry 21 }

artasRadarPRElevationBias OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ”


A1−22 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

::= { artasRadarEntry 22 }

artasRadarPRElevationBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarPRElevationBias object.” ::= { artasRadarEntry 23 }

artasRadarSSRAzimuthBias OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 24 }

artasRadarSSRAzimuthBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarSSRAzimuthBias object.” ::= { artasRadarEntry 25 }

artasRadarSSRRangeBias OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 26 }

artasRadarSSRRangeBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarSSRRangeBias object.” ::= { artasRadarEntry 27 }

artasRadarSSRRangeGain OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 28 }

artasRadarSSRRangeGainUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarSSRRangeGain object.” ::= { artasRadarEntry 29 }

−− ad DESCRIPTIONartasRadarSSRSquintBias OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 30 }

artasRadarSSRSquintBiasUnit OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” unit of the artasRadarSSRSquintBias object.” ::= { artasRadarEntry 31 }

artasRadarOperationalStatus OBJECT−TYPE SYNTAX INTEGER { notConnected(1), init(2), degraded(3), operational(4), initRMCDE(5) } ACCESS read−only


A1−2346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

STATUS mandatory DESCRIPTION ”Operational status of the radar.” ::= { artasRadarEntry 32 }

artasRadarConnectionStatus OBJECT−TYPE SYNTAX INTEGER { disconnect(1), connect(2) } ACCESS read−write STATUS mandatory DESCRIPTION ” ” ::= { artasRadarEntry 33 }

artasRadarDegrTimeOut OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”Degradation caused by time out.” ::= { artasRadarEntry 34 }

artasRadarDegrIncoherentTimeStamp OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”Degradation caused by incoherent radar station time stamping.” ::= { artasRadarEntry 35 }

artasRadarDegrIncoherentRadarPeriod OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”Degradation caused by incoherent calculated radar period.” ::= { artasRadarEntry 36 }

artasRadarDegrHighInvalidModeA OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”Degradation caused by too high rate of invalid mode A.” ::= { artasRadarEntry 37 }

−− $PCR_ARTAS_V4_0433 Begin−− artasRadarDegrHighInvalidModeB OBJECT−TYPEartasRadarDegrHighInvalidModeC OBJECT−TYPE−− $PCR_ARTAS_V4_0433 End

SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”Degradation caused by too high rate of invalid mode C.” ::= { artasRadarEntry 38 }

artasRadarDegrHighOldInfo OBJECT−TYPE SYNTAX INTEGER { false(0), true(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”Degradation caused by too high rate of old information.” ::= { artasRadarEntry 39 }


A1−24 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−−$ECR_ART_0510 BeginartasRadarChannel1Status OBJECT−TYPE SYNTAX INTEGER { active(1), available(2), notavailable(3), notdefined(4), defined(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”Radar Channel 1 status” ::= { artasRadarEntry 40 }artasRadarChannel2Status OBJECT−TYPE SYNTAX INTEGER { active(1), available(2), notavailable(3), notdefined(4), defined(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”Radar Channel 2 status” ::= { artasRadarEntry 41 }artasRadarChannel3Status OBJECT−TYPE SYNTAX INTEGER { active(1), available(2), notavailable(3), notdefined(4), defined(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”Radar Channel 3 status” ::= { artasRadarEntry 42 }artasRadarChannel4Status OBJECT−TYPE SYNTAX INTEGER { active(1), available(2), notavailable(3), notdefined(4), defined(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”Radar Channel 4 status” ::= { artasRadarEntry 43 }−−$ECR_ART_0510 End

−− ACP 185 begin−− These are per RBR overload statuses for the radar.artasRadarMonoOverloadStatusOnRBRA OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Radar mono radar overload on RBR A.” ::= { artasRadarEntry 44 }

artasRadarMonoOverloadStatusOnRBRB OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Radar mono radar overload on RBR B.” ::= { artasRadarEntry 45 }

artasRadarSectorMemoryOverloadStatusOnRBRA OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Radar sector memory overload on RBR A.” ::= { artasRadarEntry 46 }

artasRadarSectorMemoryOverloadStatusOnRBRB OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Radar sector memory overload on RBR B.” ::= { artasRadarEntry 47 }


A1−2546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

−− ACP 185 end−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasUser−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

artasUserTable OBJECT−TYPE SYNTAX SEQUENCE OF ArtasUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of user Entries” ::= { artasUser 1 }

−−$PCR_ARTAS_V5_0164 Begin−−Change name of attribut−−artasUserNumber OBJECT−TYPE−− SYNTAX INTEGER−− ACCESS read−only−− STATUS mandatory−− DESCRIPTION−− ”The Number of users”−− ::= { artasUserTable 1}artasNumberOfUsers OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The Number of users” ::= { artasUserTable 1}−−$PCR_ARTAS_V5_0164 End

artasUserEntry OBJECT−TYPE SYNTAX ArtasUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”user Entries” INDEX { artasUserIndex } ::= { artasUserTable 2 }

−− $PCR_ARTAS V5_0134 Begin − add artasUserSensorServiceStatus and artasUserSensorServiceCommand−− and artasUserSensorTransmissionTypeArtasUserEntry ::= SEQUENCE { artasUserIndex INTEGER,−− $ECR_ART_0512 Begin − replace Sic/Sac by User number −− artasUserSIC−− INTEGER,−− artasUserSAC−− INTEGER, artasUserNumber INTEGER,−− $PCR ARTAS_V6B_0045 Begin − restore the one previous field −− to keep the same number for the following fields artasUserSACUNUSED INTEGER,−− $PCR ARTAS_V6B_0045 End−− $ECR_ART_0512 End artasUserName DisplayString, artasUserClass INTEGER, artasUserType INTEGER, artasUserBackgroundServiceStatus INTEGER, artasUserTransmissionType INTEGER, artasUserConnectionStatus INTEGER, artasUserConnectionAuthorisation INTEGER, artasUserTransmissionLoad INTEGER, artasUserBackgroundServiceCommand INTEGER, artasUserSensorServiceStatus INTEGER, artasUserSensorServiceCommand INTEGER, artasUserSensorTransmissionType INTEGER, artasUserBroadcastProtocolType INTEGER }−− $PCR_ARTAS V5_0134 End

−− $ECR_ART_0512 Begin − replace Sic/Sac by User number artasUserIndex OBJECT−TYPE


A1−26 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each user. Its value ranges between 1 and the value of NumberOfUsers” ::= { artasUserEntry 1 }

−− and incrementation of artasUserEntry −− artasUserSIC OBJECT−TYPE−− SYNTAX INTEGER−− ACCESS read−only−− STATUS mandatory−− DESCRIPTION−− ”The SIC of the user.”−− ::= { artasUserEntry 2 }−− −− artasUserSAC OBJECT−TYPE−− SYNTAX INTEGER−− ACCESS read−only−− STATUS mandatory−− DESCRIPTION−− ”The SAC of the user.”−− ::= { artasUserEntry 3 }

artasUserNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The user number.” ::= { artasUserEntry 2 }

−− $PCR ARTAS_V6B_0045 Begin−− in order to restore the previous numbering the artasUserSACUNUSED is added−− then the other entry are re−numberedartasUserSACUNUSED OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The SAC of the user.” ::= { artasUserEntry 3 } artasUserName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Name of the user.” ::= { artasUserEntry 4 }

artasUserClass OBJECT−TYPE SYNTAX INTEGER { firstClass(1), secondClass(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”Class of the user.” ::= { artasUserEntry 5 }

−−$PCR_ARTAS_V5_0164 Begin−−artasUserType OBJECT−TYPE−− SYNTAX INTEGER {−− normal(1),−− adjacent(2),−− localBroadcast(3),−− remoteBroadcast(4)−− }−− ACCESS read−only−− STATUS mandatory−− DESCRIPTION−− ”Type of the user.”−− ::= { artasUserEntry 6 }artasUserType OBJECT−TYPE SYNTAX INTEGER { normal(1), adjacent(2), broadcast(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Type of the user.” ::= { artasUserEntry 6 }−−$PCR_ARTAS_V5_0164 End


A1−2746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

artasUserBackgroundServiceStatus OBJECT−TYPE SYNTAX INTEGER { active(1), passive(2), suspended(3), empty(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”Background service status for the user.” ::= { artasUserEntry 7 }

artasUserTransmissionType OBJECT−TYPE SYNTAX INTEGER { periodical(1), radarSynchronised(2), aperiodical(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Transmission type for the user.” ::= { artasUserEntry 8 }

artasUserConnectionStatus OBJECT−TYPE SYNTAX INTEGER { disconnect(1), connect(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”Connection status for the user.” ::= { artasUserEntry 9 }

artasUserConnectionAuthorisation OBJECT−TYPE SYNTAX INTEGER { allow(1), disallow(2) } ACCESS write−only STATUS mandatory DESCRIPTION ”Connection authorisation for the user.” ::= { artasUserEntry 10 }

artasUserTransmissionLoad OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Average load of transmission used by the user.” ::= { artasUserEntry 11 }

artasUserBackgroundServiceCommand OBJECT−TYPE SYNTAX INTEGER { interrupt(1), restart(2) } ACCESS write−only STATUS mandatory DESCRIPTION ”Background service command for the user.” ::= { artasUserEntry 12 }−− $PCR_ARTAS V5_0134 BeginartasUserSensorServiceStatus OBJECT−TYPE SYNTAX INTEGER { active(1), passive(2), suspended(3), empty(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”Sensor service status for the user.” ::= { artasUserEntry 13 }

artasUserSensorServiceCommand OBJECT−TYPE SYNTAX INTEGER { interrupt(1), restart(2) } ACCESS write−only STATUS mandatory DESCRIPTION ”Sensor service command for the user.” ::= { artasUserEntry 14 }


A1−28 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

artasUserSensorTransmissionType OBJECT−TYPE SYNTAX INTEGER { punctual(1), periodical(2), aperiodical(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Transmission type for the user.” ::= { artasUserEntry 15 }−− $PCR_ARTAS V5_0134 End−− $ECR_ART_0512 End−− $PCR ARTAS_V6B_0045 End

−− V7A0 begin − add broadcast protocol typeartasUserBroadcastProtocolType OBJECT−TYPE SYNTAX INTEGER { ast30(1), ast62(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”In case of broadcast user, this gives the protocol type.” ::= { artasUserEntry 16 }−− V7A0 end − add broadcast protocol type

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasTechnical−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−artasClockStatus OBJECT−TYPE SYNTAX INTEGER { unknown(1), starting(2), ok(3), failed(4), detached(5), inUse(6), mainthalt(7), maintoff(8), standby(9), operational(10), transmit(11), ready(12), notOK(13) } ACCESS read−only STATUS mandatory DESCRIPTION ” ” ::= { artasTechnical 1 }

artasNodeScmStatus OBJECT−TYPE SYNTAX INTEGER { central(1), local(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”Indicate if the SCM on the node is central or local.” ::= { artasTechnical 2 }

−−$ECP_ART_0605 beginartasExtLanTable OBJECT−TYPE SYNTAX SEQUENCE OF ArtasExtLanEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ” A list of external Lan entry” ::= { artasTechnical 4 }artasNbOfExtLans OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ” The number of external Lans ” ::= { artasExtLanTable 1 }artasExtLanEntry OBJECT−TYPE SYNTAX ArtasExtLanEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ” External Lan entries” INDEX {artasExtLanIndex} ::= { artasExtLanTable 2 }


A1−2946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ArtasExtLanEntry ::= SEQUENCE { artasExtLanIndex INTEGER, artasExtLanName DisplayString, artasExtLanChainAStatus INTEGER, artasExtLanChainBStatus INTEGER }artasExtLanIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ” A unique value for each external Lan. Its value ranges between 1 end the value of artasNbOfExtLans ” ::= { artasExtLanEntry 1 }artasExtLanName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ” Name of the external Lan ” ::= { artasExtLanEntry 2 }artasExtLanChainAStatus OBJECT−TYPE SYNTAX INTEGER { unavailable(0), ok(1), nok(2), okendwarning(3), nokendwarning(4) } ACCESS read−only STATUS mandatory DESCRIPTION ” The status of the Lan on the RB node of the chain A ” ::= { artasExtLanEntry 3 }artasExtLanChainBStatus OBJECT−TYPE SYNTAX INTEGER { unavailable(0), ok(1), nok(2), okendwarning(3), nokendwarning(4) } ACCESS read−only STATUS mandatory DESCRIPTION ” The status of the Lan on the RB node of the chain B ” ::= { artasExtLanEntry 4 }−−$ECP_ART_0605 end

−− PCR ARTAS_V6B_0069 Begin−− ATR_850 begin

artasDualNodeStatus OBJECT−TYPE SYNTAX INTEGER { unused(0), master(1), slave(2), single(3), offline(4), rundown(5) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasTechnical 5 }

artasTrapFilter OBJECT−TYPE SYNTAX INTEGER { forward(1), noforward(2) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates if traps are forwarded or not. ” ::= { artasTechnical 6 }−− ATR_850 end−− PCR ARTAS_V6B_0069 End

artasProxy OBJECT IDENTIFIER ::= { artasTechnical 3 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasProxy−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−


A1−30 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− The artasUBSSPxNodeTable table contains the list of the node−− names (hostnames) managed by the SSA and running in the UBSS−− system. By default the localhost is managed and to address−− the other node names an extended community name must be used.−−−− The artasPxNodeTable table contains the list of the all the−− nodes managed by the SSA (not only UBSS node). The proxy is−− the same as the one for the artasUBSSPxNodeTable.

artasUBSSPxNodeTable OBJECT−TYPE SYNTAX SEQUENCE OF ArtasUBSSPxNodeEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ” A list of UBSS proxy node entry” ::= { artasProxy 1 }

artasUBSSPxNodeNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of UBSS proxy nodes ” ::= { artasUBSSPxNodeTable 1 }

artasUBSSPxNodeEntry OBJECT−TYPE SYNTAX ArtasUBSSPxNodeEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ” artas UBSS proxy node Entry ” INDEX { artasUBSSPxNodeIndex } ::= { artasUBSSPxNodeTable 2 }

ArtasUBSSPxNodeEntry ::= SEQUENCE { artasUBSSPxNodeIndex INTEGER, artasUBSSPxNodeName DisplayString }

artasUBSSPxNodeIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”ARTAS UBSS proxy node index ” ::= { artasUBSSPxNodeEntry 1 }

artasUBSSPxNodeName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Name of the UBSS artas proxy node ” ::= { artasUBSSPxNodeEntry 2 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasPxNodeTable−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−artasPxNodeTable OBJECT−TYPE SYNTAX SEQUENCE OF ArtasPxNodeEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ” A list of proxy node entry” ::= { artasProxy 2 }

artasPxNodeNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of proxy nodes ” ::= { artasPxNodeTable 1 }

artasPxNodeEntry OBJECT−TYPE SYNTAX ArtasPxNodeEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ” artas proxy node Entry ” INDEX { artasPxNodeIndex } ::= { artasPxNodeTable 2 }

ArtasPxNodeEntry ::= SEQUENCE { artasPxNodeIndex INTEGER, artasPxNodeName DisplayString }

artasPxNodeIndex OBJECT−TYPE


A1−3146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”ARTAS proxy node index ” ::= { artasPxNodeEntry 1 }

artasPxNodeName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Name of the arats proxy node ” ::= { artasPxNodeEntry 2 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− artasTrap−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−artasEventDetectionTime OBJECT−TYPE SYNTAX DisplayString ACCESS not−accessible STATUS mandatory DESCRIPTION ”Detection time for a trap ” ::= { artasTrap 1 }

artasTextMessage OBJECT−TYPE SYNTAX DisplayString ACCESS not−accessible STATUS mandatory DESCRIPTION ”This object is used by an agent to fill in a trap a free comment or SCM application message” ::= { artasTrap 2 }

−− ACP 185 beginartasFunctionNodeOverloadsDetails OBJECT IDENTIFIER ::= { artasFunction 3 }

artasFunctionNodeOverloadsDetailsRBR OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetails 1 }

artasFunctionNodeOverloadsDetailsRBRA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsRBR 1 }artasFunctionNodeOverloadsDetailsRBRADegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRBRA 1 }artasFunctionNodeOverloadsDetailsRBRADegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRBRA 2 }artasFunctionNodeOverloadsDetailsRBRADegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRBRA 3 }artasFunctionNodeOverloadsDetailsRBRB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsRBR 2 }artasFunctionNodeOverloadsDetailsRBRBDegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRBRB 1 }artasFunctionNodeOverloadsDetailsRBRBDegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory


A1−32 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRBRB 2 }artasFunctionNodeOverloadsDetailsRBRBDegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRBRB 3 }

artasFunctionNodeOverloadsDetailsSRV OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetails 2 }

artasFunctionNodeOverloadsDetailsSRVA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsSRV 1 }artasFunctionNodeOverloadsDetailsSRVADegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), transmission(2) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSRVA 1 }artasFunctionNodeOverloadsDetailsSRVADegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), transmission(2) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSRVA 2 }artasFunctionNodeOverloadsDetailsSRVADegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), transmission(2) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSRVA 3 }artasFunctionNodeOverloadsDetailsSRVB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsSRV 2 }artasFunctionNodeOverloadsDetailsSRVBDegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), transmission(2) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSRVB 1 }artasFunctionNodeOverloadsDetailsSRVBDegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), transmission(2) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSRVB 2 }artasFunctionNodeOverloadsDetailsSRVBDegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), transmission(2) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSRVB 3 }

artasFunctionNodeOverloadsDetailsTRK OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetails 3 }

artasFunctionNodeOverloadsDetailsTRKA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsTRK 1 }artasFunctionNodeOverloadsDetailsTRKADegradationCause1 OBJECT−TYPE


A1−3346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

SYNTAX INTEGER { none(0), cpu(1), trkcomms(8), trkmemory(9) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsTRKA 1 }artasFunctionNodeOverloadsDetailsTRKADegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), trkcomms(8), trkmemory(9) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsTRKA 2 }artasFunctionNodeOverloadsDetailsTRKADegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), trkcomms(8), trkmemory(9) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsTRKA 3 }artasFunctionNodeOverloadsDetailsTRKB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsTRK 2 }artasFunctionNodeOverloadsDetailsTRKBDegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), trkcomms(8), trkmemory(9) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsTRKB 1 }artasFunctionNodeOverloadsDetailsTRKBDegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), trkcomms(8), trkmemory(9) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsTRKB 2 }artasFunctionNodeOverloadsDetailsTRKBDegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1), trkcomms(8), trkmemory(9) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsTRKB 3 }

artasFunctionNodeOverloadsDetailsMMS OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetails 4 }

artasFunctionNodeOverloadsDetailsMMSA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsMMS 1 }artasFunctionNodeOverloadsDetailsMMSADegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsMMSA 1 }artasFunctionNodeOverloadsDetailsMMSADegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0),


A1−34 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsMMSA 2 }artasFunctionNodeOverloadsDetailsMMSADegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsMMSA 3 }artasFunctionNodeOverloadsDetailsMMSB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsMMS 2 }artasFunctionNodeOverloadsDetailsMMSBDegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsMMSB 1 }artasFunctionNodeOverloadsDetailsMMSBDegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsMMSB 2 }artasFunctionNodeOverloadsDetailsMMSBDegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsMMSB 3 }

artasFunctionNodeOverloadsDetailsREC OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetails 5 }

artasFunctionNodeOverloadsDetailsRECA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsREC 1 }artasFunctionNodeOverloadsDetailsRECADegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRECA 1 }artasFunctionNodeOverloadsDetailsRECADegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRECA 2 }artasFunctionNodeOverloadsDetailsRECADegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRECA 3 }artasFunctionNodeOverloadsDetailsRECB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsREC 2 }artasFunctionNodeOverloadsDetailsRECBDegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only


A1−3546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRECB 1 }artasFunctionNodeOverloadsDetailsRECBDegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRECB 2 }artasFunctionNodeOverloadsDetailsRECBDegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), cpu(1) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsRECB 3 }

artasFunctionNodeOverloadsDetailsSUP OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetails 6 }

artasFunctionNodeOverloadsDetailsSUPA OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsSUP 1 }artasFunctionNodeOverloadsDetailsSUPADegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), −− SNMP overloads are degradation causes, despite it has no status in ARTAS yet alliprequestlimit(10), periprequestlimit(11) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSUPA 1 }artasFunctionNodeOverloadsDetailsSUPADegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), −− SNMP overloads are degradation causes, despite it has no status in ARTAS yet alliprequestlimit(10), periprequestlimit(11) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSUPA 2 }artasFunctionNodeOverloadsDetailsSUPADegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), −− SNMP overloads are degradation causes, despite it has no status in ARTAS yet alliprequestlimit(10), periprequestlimit(11) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSUPA 3 }artasFunctionNodeOverloadsDetailsSUPB OBJECT IDENTIFIER ::= { artasFunctionNodeOverloadsDetailsSUP 2 }artasFunctionNodeOverloadsDetailsSUPBDegradationCause1 OBJECT−TYPE SYNTAX INTEGER { none(0), −− SNMP overloads are degradation causes, despite it has no status in ARTAS yet alliprequestlimit(10), periprequestlimit(11) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSUPB 1 }artasFunctionNodeOverloadsDetailsSUPBDegradationCause2 OBJECT−TYPE SYNTAX INTEGER { none(0), −− SNMP overloads are degradation causes, despite it has no status in ARTAS yet alliprequestlimit(10), periprequestlimit(11) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSUPB 2 }


A1−36 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

artasFunctionNodeOverloadsDetailsSUPBDegradationCause3 OBJECT−TYPE SYNTAX INTEGER { none(0), −− SNMP overloads are degradation causes, despite it has no status in ARTAS yet alliprequestlimit(10), periprequestlimit(11) } ACCESS read−only STATUS mandatory DESCRIPTION ” Indicates the node dual node status from UBSS DNC. ” ::= { artasFunctionNodeOverloadsDetailsSUPB 3 }−− ACP 185 end−− END OF MIBEND


A1−3746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

10.2. ARTAS TRAP MIB DEFINITION−− Artas MIB − trap−−−− Prepared by Comsoft GmbH for EUROCONTROL−−−− This file should be validated using a MIB validator such as−− http://wwwsnmp.cs.utwente.nl/ietf/mibs/validate/−−−− Modified by M. BUTOW 09/10/03 V6C0: change enterprise to Eurocontrol−− Modified by K. HAYEN 09/12/03 V6C0: added ACP 185 traps and made this−− file the template for non−automatic−− generated TRAPs. The build process−− produces a complete MIB under the−− (same name) artasTrap.my−− Modified by M.BUTOW 14/12/03 V6C0: shorten trap name > 64 chars−− (SMI error frequently tolerated)−− Modified by MAS/CS 27/12/04 V6C0: Added import statement for enterprises.−− Modified by M. BUTOW 15.06.04 Incorporate ECAMOS modifications from CAMOS email 03890−− (IMPORT statements changes, but acoldStart change not yet) ARTAS−TRAP−MIB DEFINITIONS ::= BEGIN

IMPORTS enterprises FROM RFC1155−SMI TRAP−TYPE FROM RFC−1215

artasApplication, artasTechnical , artasEventDetectionTime ,artasTextMessage, artasNodeName, artasOperationalStatus, artasUnitConfiguration, artasFunctionName, artasFunctionSoftwareVersionNodeA, artasFunctionSoftwareVersionNodeB, artasFunctionNodeAName, artasFunctionNodeBName, artasRadarName , artasRadarChannel1Status, artasRadarChannel2Status, artasRadarChannel3Status, artasRadarChannel4Status, artasUserName, artasUserBackgroundServiceStatus, artasUserConnectionStatus,artasUserSensorServiceStatus, artasNodeScmStatus, artasClockStatus, artasExtLanName, artasExtLanChainAStatus, artasExtLanChainBStatus,artasSystemColdStartCommandStatus, artasSystemHotStartCommandStatus,artasSystemStopCommandStatus, artasSystemActivatePlanCommandStatus, artasNodeStartCommandStatus, artasNodeStopCommandStatus, artasNodeShutdownCommandStatus, artasNodeRestartCommandStatus, artasFunctionNodeOverloadsRBRAAny, artasFunctionNodeOverloadsRBRBAny, artasFunctionNodeOverloadsMMSAAny, artasFunctionNodeOverloadsMMSBAny, artasFunctionNodeOverloadsTRKAAny, artasFunctionNodeOverloadsTRKBAny, artasFunctionNodeOverloadsRECAAny, artasFunctionNodeOverloadsRECBAny,artasFunctionNodeOverloadsSRVAAny, artasFunctionNodeOverloadsSRVBAny, artasFunctionNodeOverloadsRBRACPU, artasFunctionNodeOverloadsRBRBCPU,artasFunctionNodeOverloadsMMSACPU, artasFunctionNodeOverloadsMMSBCPU,artasFunctionNodeOverloadsTRKACPU, artasFunctionNodeOverloadsTRKBCPU, artasFunctionNodeOverloadsRECACPU, artasFunctionNodeOverloadsRECBCPU, artasFunctionNodeOverloadsSRVACPU, artasFunctionNodeOverloadsSRVBCPU, artasFunctionNodeOverloadsRBRASRVTransmission, artasFunctionNodeOverloadsRBRBSRVTransmission,artasFunctionNodeOverloadsRBRATRKFilteringLevelNonZero, artasFunctionNodeOverloadsRBRBTRKFilteringLevelNonZero, artasFunctionNodeOverloadsRBRATotalPlot, artasFunctionNodeOverloadsRBRBTotalPlot, artasFunctionNodeOverloadsRBRAMonoRadarPlot, artasFunctionNodeOverloadsRBRBMonoRadarPlot,artasFunctionNodeOverloadsRBRARadarSectorMemory, artasFunctionNodeOverloadsRBRBRadarSectorMemory, artasFunctionNodeOverloadsSRVATransmission, artasFunctionNodeOverloadsSRVBTransmission, artasFunctionNodeOverloadsTRKACommunication, artasFunctionNodeOverloadsTRKBCommunication,artasFunctionNodeOverloadsTRKAMemory, artasFunctionNodeOverloadsTRKBMemory,artasFunctionNodeOverloadsSUPAAny, artasFunctionNodeOverloadsSUPBAny, artasFunctionNodeOverloadsSUPARequestLimitAllIP, artasFunctionNodeOverloadsSUPBRequestLimitAllIP,artasFunctionNodeOverloadsSUPARequestLimitPerIP, artasFunctionNodeOverloadsSUPBRequestLimitPerIP,artasNodeInfoNTPStatus, artasNodeInfoNTPStratum, artasNodeInfoNTPPeerCount, artasNodeInfoNTPMainPeer, artasNodeInfoNTPPeer1Hostname, artasNodeInfoNTPPeer1Address, artasNodeInfoNTPPeer1Status, artasNodeInfoNTPPeer1Reachable, artasNodeInfoNTPPeer1Offset, artasNodeInfoNTPPeer1Stratum,artasNodeInfoNTPPeer2Hostname, artasNodeInfoNTPPeer2Address, artasNodeInfoNTPPeer2Status, artasNodeInfoNTPPeer2Reachable, artasNodeInfoNTPPeer2Offset, artasNodeInfoNTPPeer2Stratum,artasNodeInfoNTPPeer3Hostname, artasNodeInfoNTPPeer3Address, artasNodeInfoNTPPeer3Status, artasNodeInfoNTPPeer3Reachable, artasNodeInfoNTPPeer3Offset, artasNodeInfoNTPPeer3Stratum FROM ARTAS−MIB;

eurocontrol OBJECT IDENTIFIER ::= { enterprises 2363 }masAgents OBJECT IDENTIFIER ::= { eurocontrol 3 }artas OBJECT IDENTIFIER ::= { masAgents 7 }

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− TRAPs definition−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

coldStart TRAP−TYPE ENTERPRISE artas DESCRIPTION ”This event is sent after the agent starting restarting when it is ready to communicate with a manager” ::= 0

−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−


A1−38 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− artas traps−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

artasApplMessage TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasTextMessage, artasNodeName } DESCRIPTION ”Trap sent when SCM receives from an application a message via the scm_appl_msg() function.” ::= 7

unitConfigurationChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasUnitConfiguration } DESCRIPTION ”Trap sent when the artasUnitConfiguration object is modified to a valid value.” ::= 101

operationalStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasOperationalStatus } DESCRIPTION ”Trap sent when the artasOperationalStatus object is modified to a valid value.” ::= 102

nodeOperationalStatus−stopped TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeOperationalStatus object moves to stopped.” ::= 201

nodeOperationalStatus−operational TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeOperationalStatus object moves to operational.” ::= 202

nodeOperationalStatus−starting TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeOperationalStatus object moves to starting.” ::= 203

nodeOperationalStatus−stopping TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeOperationalStatus object moves to stopping.” ::= 204

nodeOperationalStatus−residentOnly TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName }


A1−3946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

DESCRIPTION ”Trap sent when the artasNodeOperationalStatus object moves to residentOnly.” ::= 205

nodeRedundancyStatus−notAvailable TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeRedundancyStatus object moves to notAvailable.” ::= 211

nodeRedundancyStatus−principal TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeRedundancyStatus object moves to principal.” ::= 212

nodeRedundancyStatus−single TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeRedundancyStatus object moves to single.” ::= 213

nodeRedundancyStatus−hotStandby TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeRedundancyStatus object moves to hotStandby.” ::= 214

nodeRedundancyStatus−coldStandby TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName } DESCRIPTION ”Trap sent when the artasNodeRedundancyStatus object moves to coldStandby.” ::= 215

functionTechnicalStatus−normal TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionName } DESCRIPTION ”Trap sent when the artasFunctionTechnicalStatus object moves to normal.” ::= 301

functionTechnicalStatus−degraded TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionName } DESCRIPTION ”Trap sent when the artasFunctionTechnicalStatus object moves to degraded.” ::= 302

functionSoftwareVersionChangeNodeA TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionName, artasFunctionSoftwareVersionNodeA }


A1−40 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

DESCRIPTION ”Trap sent when the artasFunctionSoftwareVersionNodeA object is modified to a valid value.” ::= 310

functionSoftwareVersionChangeNodeB TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionName, artasFunctionSoftwareVersionNodeB } DESCRIPTION ”Trap sent when the artasFunctionSoftwareVersionNodeB object is modified to a valid value.” ::= 311

artasFunctionNodeANameChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionName, artasFunctionNodeAName } DESCRIPTION ”Trap sent when the artasFunctionNodeAName object is modified to a valid value.” ::= 320

artasFunctionNodeBNameChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionName, artasFunctionNodeBName } DESCRIPTION ”Trap sent when the artasFunctionNodeBName object is modified to a valid value.” ::= 321

artasRadarBiasComputationStatus−notActive TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when the artasRadarBiasComputationStatus object moves to notActive.” ::= 401

artasRadarBiasComputationStatus−active TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when the artasRadarBiasComputationStatus object moves to active.” ::= 402

artasRadarOperationalStatus−notConnected TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasRadarName } DESCRIPTION ”Trap sent when the artasRadarOperationalStatus object moves to notConnected.” ::= 411

artasRadarOperationalStatus−init TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasRadarName } DESCRIPTION ”Trap sent when the artasRadarOperationalStatus object moves to init.” ::= 412

artasRadarOperationalStatus−degraded TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasRadarName }


A1−4146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

DESCRIPTION ”Trap sent when the artasRadarOperationalStatus object moves to degraded.” ::= 413

artasRadarOperationalStatus−operational TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasRadarName } DESCRIPTION ”Trap sent when the artasRadarOperationalStatus object moves to operational.” ::= 414

artasRadarOperationalStatus−initRMCDE TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasRadarName } DESCRIPTION ”Trap sent when the artasRadarOperationalStatus object moves to initRMCDE.” ::= 415

artasRadarConnectionStatus−disconnected TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasRadarName } DESCRIPTION ”Trap sent when the artasRadarConnectionStatus object moves to disconnect.” ::= 421

artasRadarConnectionStatus−connected TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasRadarName } DESCRIPTION ”Trap sent when the artasRadarConnectionStatus object moves to connect.” ::= 422

artasRadarChannel1StatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasRadarName, artasRadarChannel1Status } DESCRIPTION ”Trap sent when the artasRadarChannel1Status object is modified to a valid value.” ::= 431



artasRadarChannel4StatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime,


A1−42 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

artasRadarName, artasRadarChannel4Status } DESCRIPTION ”Trap sent when the artasRadarChannel4Status object is modified to a valid value.” ::= 434

artasUserBackgroundServiceStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasUserName, artasUserBackgroundServiceStatus } DESCRIPTION ”Trap sent when the artasUserBackgroundServiceStatus object is modified to a valid value.” ::= 501

artasUserConnectionStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasUserName, artasUserConnectionStatus } DESCRIPTION ”Trap sent when the artasUserConnectionStatus object is modified to a valid value.” ::= 502

artasUserSensorServiceStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasUserName, artasUserSensorServiceStatus } DESCRIPTION ”Trap sent when the artasUserSensorServiceStatus object is modified to a valid value.” ::= 503

nodeScmStatus−central TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeScmStatus } DESCRIPTION ”Trap sent when the artasNodeScmStatus becomes central. The artasNodeScmStatus contains the previous status.” ::= 601

nodeScmStatus−local TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeScmStatus } DESCRIPTION ”Trap sent when the artasNodeScmStatus becomes local. The artasNodeScmStatus contains the previous status.” ::= 602

artasClockStatus−changed TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasClockStatus, artasTextMessage } DESCRIPTION ”Trap sent when the artasClockStatus object is modified to a valid value.” ::= 651

−−$ECP_ART_0605 beginartasExtLanChainAStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasExtLanName, artasExtLanChainAStatus } DESCRIPTION ”Trap sent when the status of the Lan changes on the RB node of the chain A ”


A1−4346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

::= 652

artasExtLanChainBStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasExtLanName, artasExtLanChainBStatus } DESCRIPTION ”Trap sent when the status of the Lan changes on the RB node of the chain B ” ::= 653−−$ECP_ART_0605 end

−− ACP_199 beginartasHello TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent with specified period to indicate functioning of the ARTAS trap sending mechanism.” ::= 654−− ACP_199 end

−− ACP_144 beginartasSystemColdStartCommandStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasSystemColdStartCommandStatus } DESCRIPTION ”Trap sent when system cold start command status changes.” ::= 655

artasSystemHotStartCommandStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasSystemHotStartCommandStatus } DESCRIPTION ”Trap sent when system hot start command status changes.” ::= 656

artasSystemStopCommandStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasSystemStopCommandStatus } DESCRIPTION ”Trap sent when system stop command status changes.” ::= 657

artasSystemActivatePlanCommandStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasSystemActivatePlanCommandStatus } DESCRIPTION ”Trap sent when system plan activation command status changes.” ::= 658

artasSystemColdStartCommandErrorCommandRejected TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system cold start command is rejected.” ::= 659

artasSystemColdStartCommandErrorMMSUnreachable TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system cold start command fails because MMS is unreachable.” ::= 660

artasSystemColdStartCommandErrorDatabaseLocked TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system cold start command fails because database is locked.” ::= 661

artasSystemColdStartCommandErrorIncorrectChainNumber TRAP−TYPE ENTERPRISE artas VARIABLES {


A1−44 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

artasEventDetectionTime } DESCRIPTION ”Trap sent when system cold start command fails because the chain number is incorrect.” ::= 662

artasSystemColdStartCommandWarningNodeUnreachable TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system cold start encounters an unreachable node.” ::= 663

artasSystemColdStartCommandWarningNodeAlreadyRunning TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system cold start encounters an already running node.” ::= 664

artasSystemColdStartCommandWarningMasterChainTimeExceeded TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system cold start exceeds a defined time duration.” ::= 665

artasSystemHotStartCommandErrorCommandRejected TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system hot start command is rejected.” ::= 666

artasSystemHotStartCommandErrorMMSUnreachable TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system hot start command fails because MMS is unreachable.” ::= 667

artasSystemHotStartCommandErrorDatabaseLocked TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system hot start command fails because database is locked.” ::= 668

artasSystemHotStartCommandErrorIncorrectChainNumber TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system hot start command fails because the chain number is incorrect.” ::= 669

artasSystemHotStartCommandWarningNodeUnreachable TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system hot start encounters an unreachable node.” ::= 670

artasSystemHotStartCommandWarningNodeAlreadyRunning TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system hot start encounters an already running node.” ::= 671

artasSystemHotStartCommandWarningMasterChainTimeExceeded TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system hot start exceeds a defined time duration.” ::= 672

artasSystemHotStartCommandWarningDFInconsColdStartForced TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime


A1−4546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

} DESCRIPTION ”Trap sent when system hot start dynamic files are inconsistent with the database and a cold start is forced.” ::= 673

artasSystemStopCommandErrorNodeUnreachable TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system stop encounters an unreachable node.” ::= 674

artasSystemStopCommandErrorCommandRejected TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when system stop command is rejected.” ::= 675

artasNodeStartCommandStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeStartCommandStatus } DESCRIPTION ”Trap sent when node start command status changes.” ::= 676

artasNodeStopCommandStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeStopCommandStatus } DESCRIPTION ”Trap sent when node stop command status changes.” ::= 677

artasNodeShutdownCommandStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeShutdownCommandStatus } DESCRIPTION ”Trap sent when node shutdown command status changes.” ::= 678

artasNodeRestartCommandStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeRestartCommandStatus } DESCRIPTION ”Trap sent when node restart command status changes.” ::= 679

artasNodeStartCommandErrorNodeUnreachable TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node start command fails because node is unreachable.” ::= 680

artasNodeStartCommandErrorDatabaseLocked TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node start command fails because database is locked.” ::= 681

artasNodeStartCommandErrorDatabaseAccess TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node start command fails because of database access.” ::= 682

artasNodeStartCommandErrorWithConfigurationFile TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node start command fails because of a configuration file error.” ::= 683


A1−46 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

artasNodeStartCommandErrorUBSSstillPresent TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node start command fails because UBSS is still present.” ::= 684

artasNodeStartCommandErrorBasicSystemAlreadyCalled TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node start command fails because basic system already called.” ::= 685

artasNodeStopCommandErrorNodeUnreachable TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node stop command fails because node is unreachable.” ::= 686

artasNodeStopCommandErrorNoBasicSystem TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node stop command fails because no basic system.” ::= 687

artasNodeStopCommandErrorNotOwnerOfBasicSystem TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime } DESCRIPTION ”Trap sent when node stop command fails because not owner of basic system.” ::= 688−− ACP_144 end−− ACP 185 begin−− Automatically created artasFunctionNodeOverloadsRBRAAny generation for ACP 185.artasFunctionNodeOverloadsRBRAAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRAAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRAAny changed.” ::= 800−− Automatically created artasFunctionNodeOverloadsRBRBAny generation for ACP 185.artasFunctionNodeOverloadsRBRBAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRBAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRBAny changed.” ::= 801−− Automatically created artasFunctionNodeOverloadsMMSAAny generation for ACP 185.artasFunctionNodeOverloadsMMSAAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsMMSAAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsMMSAAny changed.” ::= 802−− Automatically created artasFunctionNodeOverloadsMMSBAny generation for ACP 185.artasFunctionNodeOverloadsMMSBAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsMMSBAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsMMSBAny changed.” ::= 803−− Automatically created artasFunctionNodeOverloadsTRKAAny generation for ACP 185.artasFunctionNodeOverloadsTRKAAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsTRKAAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsTRKAAny changed.” ::= 804−− Automatically created artasFunctionNodeOverloadsTRKBAny generation for ACP 185.artasFunctionNodeOverloadsTRKBAnyChange TRAP−TYPE ENTERPRISE artas


A1−4746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsTRKBAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsTRKBAny changed.” ::= 805−− Automatically created artasFunctionNodeOverloadsRECAAny generation for ACP 185.artasFunctionNodeOverloadsRECAAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRECAAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRECAAny changed.” ::= 806−− Automatically created artasFunctionNodeOverloadsRECBAny generation for ACP 185.artasFunctionNodeOverloadsRECBAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRECBAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRECBAny changed.” ::= 807−− Automatically created artasFunctionNodeOverloadsSRVAAny generation for ACP 185.artasFunctionNodeOverloadsSRVAAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSRVAAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSRVAAny changed.” ::= 808−− Automatically created artasFunctionNodeOverloadsSRVBAny generation for ACP 185.artasFunctionNodeOverloadsSRVBAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSRVBAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSRVBAny changed.” ::= 809−− Automatically created artasFunctionNodeOverloadsRBRACPU generation for ACP 185.artasFunctionNodeOverloadsRBRACPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRACPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRACPU changed.” ::= 810−− Automatically created artasFunctionNodeOverloadsRBRBCPU generation for ACP 185.artasFunctionNodeOverloadsRBRBCPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRBCPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRBCPU changed.” ::= 811−− Automatically created artasFunctionNodeOverloadsMMSACPU generation for ACP 185.artasFunctionNodeOverloadsMMSACPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsMMSACPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsMMSACPU changed.” ::= 812−− Automatically created artasFunctionNodeOverloadsMMSBCPU generation for ACP 185.artasFunctionNodeOverloadsMMSBCPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsMMSBCPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsMMSBCPU changed.” ::= 813−− Automatically created artasFunctionNodeOverloadsTRKACPU generation for ACP 185.artasFunctionNodeOverloadsTRKACPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsTRKACPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsTRKACPU changed.” ::= 814−− Automatically created artasFunctionNodeOverloadsTRKBCPU generation for ACP 185.artasFunctionNodeOverloadsTRKBCPUChange TRAP−TYPE


A1−48 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsTRKBCPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsTRKBCPU changed.” ::= 815−− Automatically created artasFunctionNodeOverloadsRECACPU generation for ACP 185.artasFunctionNodeOverloadsRECACPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRECACPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRECACPU changed.” ::= 816−− Automatically created artasFunctionNodeOverloadsRECBCPU generation for ACP 185.artasFunctionNodeOverloadsRECBCPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRECBCPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRECBCPU changed.” ::= 817−− Automatically created artasFunctionNodeOverloadsSRVACPU generation for ACP 185.artasFunctionNodeOverloadsSRVACPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSRVACPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSRVACPU changed.” ::= 818−− Automatically created artasFunctionNodeOverloadsSRVBCPU generation for ACP 185.artasFunctionNodeOverloadsSRVBCPUChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSRVBCPU } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSRVBCPU changed.” ::= 819−− Automatically created artasFunctionNodeOverloadsRBRASRVTransmission generation for ACP 185.artasFunctionNodeOverloadsRBRASRVTransmissionChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRASRVTransmission } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRASRVTransmission changed.” ::= 820−− Automatically created artasFunctionNodeOverloadsRBRATRKFilteringLevelNonZero generation for ACP 185.artasFunctionNodeOverloadsRBRATRKFilteringLevelNonZeroChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRATRKFilteringLevelNonZero } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRATRKFilteringLevelNonZero changed.” ::= 821−− Automatically created artasFunctionNodeOverloadsRBRBTRKFilteringLevelNonZero generation for ACP 185.artasFunctionNodeOverloadsRBRBTRKFilteringLevelNonZeroChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRBTRKFilteringLevelNonZero } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRBTRKFilteringLevelNonZero changed.” ::= 822−− Automatically created artasFunctionNodeOverloadsRBRBSRVTransmission generation for ACP 185.artasFunctionNodeOverloadsRBRBSRVTransmissionChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRBSRVTransmission } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRBSRVTransmission changed.” ::= 823−− Automatically created artasFunctionNodeOverloadsRBRATotalPlot generation for ACP 185.artasFunctionNodeOverloadsRBRATotalPlotChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRATotalPlot } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRATotalPlot changed.” ::= 824−− Automatically created artasFunctionNodeOverloadsRBRBTotalPlot generation for ACP 185.


A1−4946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

artasFunctionNodeOverloadsRBRBTotalPlotChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRBTotalPlot } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRBTotalPlot changed.” ::= 825−− Automatically created artasFunctionNodeOverloadsRBRAMonoRadarPlot generation for ACP 185.artasFunctionNodeOverloadsRBRAMonoRadarPlotChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRAMonoRadarPlot } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRAMonoRadarPlot changed.” ::= 826−− Automatically created artasFunctionNodeOverloadsRBRBMonoRadarPlot generation for ACP 185.artasFunctionNodeOverloadsRBRBMonoRadarPlotChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRBMonoRadarPlot } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRBMonoRadarPlot changed.” ::= 827−− Automatically created artasFunctionNodeOverloadsRBRARadarSectorMemory generation for ACP 185.artasFunctionNodeOverloadsRBRARadarSectorMemoryChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRARadarSectorMemory } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRARadarSectorMemory changed.” ::= 828−− Automatically created artasFunctionNodeOverloadsRBRBRadarSectorMemory generation for ACP 185.artasFunctionNodeOverloadsRBRBRadarSectorMemoryChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsRBRBRadarSectorMemory } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsRBRBRadarSectorMemory changed.” ::= 829−− Automatically created artasFunctionNodeOverloadsSRVATransmission generation for ACP 185.artasFunctionNodeOverloadsSRVATransmissionChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSRVATransmission } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSRVATransmission changed.” ::= 830−− Automatically created artasFunctionNodeOverloadsSRVBTransmission generation for ACP 185.artasFunctionNodeOverloadsSRVBTransmissionChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSRVBTransmission } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSRVBTransmission changed.” ::= 831−− Automatically created artasFunctionNodeOverloadsTRKACommunication generation for ACP 185.artasFunctionNodeOverloadsTRKACommunicationChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsTRKACommunication } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsTRKACommunication changed.” ::= 832−− Automatically created artasFunctionNodeOverloadsTRKBCommunication generation for ACP 185.artasFunctionNodeOverloadsTRKBCommunicationChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsTRKBCommunication } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsTRKBCommunication changed.” ::= 833−− Automatically created artasFunctionNodeOverloadsTRKAMemory generation for ACP 185.artasFunctionNodeOverloadsTRKAMemoryChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsTRKAMemory } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsTRKAMemory changed.” ::= 834


A1−50 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− Automatically created artasFunctionNodeOverloadsTRKBMemory generation for ACP 185.artasFunctionNodeOverloadsTRKBMemoryChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsTRKBMemory } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsTRKBMemory changed.” ::= 835−− Automatically created artasFunctionNodeOverloadsSUPAAny generation for ACP 185.artasFunctionNodeOverloadsSUPAAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSUPAAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSUPAAny changed.” ::= 836−− Automatically created artasFunctionNodeOverloadsSUPBAny generation for ACP 185.artasFunctionNodeOverloadsSUPBAnyChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSUPBAny } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSUPBAny changed.” ::= 837−− Automatically created artasFunctionNodeOverloadsSUPARequestLimitAllIP generation for ACP 185.artasFunctionNodeOverloadsSUPARequestLimitAllIPChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSUPARequestLimitAllIP } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSUPARequestLimitAllIP changed.” ::= 838−− Automatically created artasFunctionNodeOverloadsSUPBRequestLimitAllIP generation for ACP 185.artasFunctionNodeOverloadsSUPBRequestLimitAllIPChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSUPBRequestLimitAllIP } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSUPBRequestLimitAllIP changed.” ::= 839−− Automatically created artasFunctionNodeOverloadsSUPARequestLimitPerIP generation for ACP 185.artasFunctionNodeOverloadsSUPARequestLimitPerIPChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSUPARequestLimitPerIP } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSUPARequestLimitPerIP changed.” ::= 840−− Automatically created artasFunctionNodeOverloadsSUPBRequestLimitPerIP generation for ACP 185.artasFunctionNodeOverloadsSUPBRequestLimitPerIPChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasFunctionNodeOverloadsSUPBRequestLimitPerIP } DESCRIPTION ”Trap sent when value of artasFunctionNodeOverloadsSUPBRequestLimitPerIP changed.” ::= 841−− ACP 185 end−− ACP 184 begin−− Automatically created artasNodeInfoNTPStatus generation for ACP 184.artasNodeInfoNTPStatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPStatus } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPStatus changed.” ::= 850−− Automatically created artasNodeInfoNTPStratum generation for ACP 184.artasNodeInfoNTPStratumChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPStratum } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPStratum changed.” ::= 851−− Automatically created artasNodeInfoNTPPeerCount generation for ACP 184.artasNodeInfoNTPPeerCountChange TRAP−TYPE ENTERPRISE artas VARIABLES {


A1−5146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeerCount } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeerCount changed.” ::= 852−− Automatically created artasNodeInfoNTPMainPeer generation for ACP 184.artasNodeInfoNTPMainPeerChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPMainPeer } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPMainPeer changed.” ::= 853−− Automatically created artasNodeInfoNTPPeer1Hostname generation for ACP 184.artasNodeInfoNTPPeer1HostnameChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer1Hostname } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer1Hostname changed.” ::= 854−− Automatically created artasNodeInfoNTPPeer1Address generation for ACP 184.artasNodeInfoNTPPeer1AddressChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer1Address } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer1Address changed.” ::= 855−− Automatically created artasNodeInfoNTPPeer1Status generation for ACP 184.artasNodeInfoNTPPeer1StatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer1Status } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer1Status changed.” ::= 856−− Automatically created artasNodeInfoNTPPeer1Reachable generation for ACP 184.artasNodeInfoNTPPeer1ReachableChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer1Reachable } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer1Reachable changed.” ::= 857−− Automatically created artasNodeInfoNTPPeer1Offset generation for ACP 184.artasNodeInfoNTPPeer1OffsetChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer1Offset } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer1Offset changed.” ::= 858−− Automatically created artasNodeInfoNTPPeer1Stratum generation for ACP 184.artasNodeInfoNTPPeer1StratumChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer1Stratum } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer1Stratum changed.” ::= 859−− Automatically created artasNodeInfoNTPPeer2Hostname generation for ACP 184.artasNodeInfoNTPPeer2HostnameChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer2Hostname } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer2Hostname changed.” ::= 860−− Automatically created artasNodeInfoNTPPeer2Address generation for ACP 184.artasNodeInfoNTPPeer2AddressChange TRAP−TYPE ENTERPRISE artas


A1−52 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer2Address } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer2Address changed.” ::= 861−− Automatically created artasNodeInfoNTPPeer2Status generation for ACP 184.artasNodeInfoNTPPeer2StatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer2Status } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer2Status changed.” ::= 862−− Automatically created artasNodeInfoNTPPeer2Reachable generation for ACP 184.artasNodeInfoNTPPeer2ReachableChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer2Reachable } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer2Reachable changed.” ::= 863−− Automatically created artasNodeInfoNTPPeer2Offset generation for ACP 184.artasNodeInfoNTPPeer2OffsetChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer2Offset } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer2Offset changed.” ::= 864−− Automatically created artasNodeInfoNTPPeer2Stratum generation for ACP 184.artasNodeInfoNTPPeer2StratumChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer2Stratum } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer2Stratum changed.” ::= 865−− Automatically created artasNodeInfoNTPPeer3Hostname generation for ACP 184.artasNodeInfoNTPPeer3HostnameChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer3Hostname } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer3Hostname changed.” ::= 866−− Automatically created artasNodeInfoNTPPeer3Address generation for ACP 184.artasNodeInfoNTPPeer3AddressChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer3Address } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer3Address changed.” ::= 867−− Automatically created artasNodeInfoNTPPeer3Status generation for ACP 184.artasNodeInfoNTPPeer3StatusChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer3Status } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer3Status changed.” ::= 868−− Automatically created artasNodeInfoNTPPeer3Reachable generation for ACP 184.artasNodeInfoNTPPeer3ReachableChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer3Reachable } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer3Reachable changed.” ::= 869−− Automatically created artasNodeInfoNTPPeer3Offset generation for ACP 184.artasNodeInfoNTPPeer3OffsetChange TRAP−TYPE


A1−5346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer3Offset } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer3Offset changed.” ::= 870−− Automatically created artasNodeInfoNTPPeer3Stratum generation for ACP 184.artasNodeInfoNTPPeer3StratumChange TRAP−TYPE ENTERPRISE artas VARIABLES { artasEventDetectionTime, artasNodeName, artasNodeInfoNTPPeer3Stratum } DESCRIPTION ”Trap sent when value of artasNodeInfoNTPPeer3Stratum changed.” ::= 871−− ACP 184 end−− END OF MIBEND


A1−54 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

10.3. DEC HUB 900 MIB DEFINITION

DECHUB900−COMMON DEFINITIONS ::= BEGIN−−−− Definitions of Managed Objects for Digital Equipment Corporation’s−− Common DEChub900 Objects−− ========================−−−−−− Name: dec−hub900−common−mib−v2−0.txt−− Version: 2.0−− Date: June, 1995−− Company: Digital Equipment Corporation−− Mail: hub900−[email protected]−− −−−− −−−− −− This Digital Equipment Corporation SNMP Management Information Base−− Specification embodies Digital Equipment Corporation’s confidential and−− proprietary intellectual property. Digital Equipment Corporation−− retains all title and ownership in the Specification, including any−− revisions.−− −− It is Digital Equipment Corporation’s intent to encourage the widespread−− use of this Specification in connection with the management of Digital−− Equipment Corporation products.−− −− Digital Equipment Corporation grants vendors, end−users, and other−− interested parties a non−exclusive license to use this Specification in−− connection with the management of Digital Equipment Corporation−− products.−− −− Digital Equipment Corporation reserves the right to make changes in this−− specification and other information contained in this document without−− prior notice.−− −− Digital Equipment Corporation makes no warranty, either expressed or−− implied, as to the use, operation, condition, or performance of the−− Specification. In no event shall Digital Equipment Corporation be−− liable for any incidental, indirect, special, or consequential damages−− whatsoever (including but not limited to loss of profits) arising out of−− or related to this document or the information contained in it.−−−−−−−− −−−− −−−− −− 1 Status of This Memo−−−− This MIB module provides definitions for object which are common to−− several of Digital Equipment Corporation’s DEChub 900 MultiSwitch −− products.−−−− Digital offers Internet anonymous ftp access to DEChub900 MIBs from −− gatekeeper.dec.com.−−−− 1) Use the Internet application ”ftp” to connect to −− ftp.dec.com (Internet address 16.1.0.2).−− 2) Log in as user ”anonymous”.−− 3) Use you electronic mail address as the password.−− 4) Change directories to the /pub/DEC/hub900/mibs area using−− ”cd /pub/DEC/hub900/mibs”.−− 5) Use the ”ascii” command to specify that you are −− retrieving ASCII test files.−− 6) Get the README file using ”get README”.−− 7) The README file explains how to retrieve this MIB.−− It lists the latest version on the MIB. It may−− instruct you to ”cd” to another directory where


A1−5546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

−− you can ”get” this MIB.−− 8) When you are finished, use the ”quit” command to log out.−−−− Inquiries about the contents and use of this MIB may be sent to −− hub900−[email protected].−−−−−−−− 2 Relationship to Other MIBs−−−−−− The objects defined in this MIB are located under the−− private.enterprises subtree as shown below:−−−− iso(1).org(3).dod(6).internet(1)−− |−− private(4)−− |−− enterprises(1)−− |−− dec(36)−− |−− ema(2)−− |−− decMIBextension(18)−− |−− decHub900(11)−− |−− .___________.___________.___________// ...etc...−− | |−− | .____________.−− mgmtAgent(1) | common(2) |−− | |____________|−− | |−− ..etc.. ..etc..−−−−−−−−−− 3 Abstract−−−−−− This MIB contains definitions of objects which are common to DEChub900−− modules.−−−−−−−− 4 References−−−−−− [1] RFC 1213. McCloghrie, K., and M. Rose, ”Management Information Base −− for Network Management of TCP/IP−based Internets”. March, 1991.−−−− [2] RFC 1155. Rose, M., and K. McCloghrie, ”Structure and Identification −− of Management Information for TCP/IP−based Internets”. May, 1990.−−−− [3] DEChub 900 MultiSwitch Owner’s Manual. Digital Equipment −− Corp. Order number: EK−DH2MS−OM.<version>.−−−−−−−−−− 5 Object Synopsis−− −−−− All objects within this MIB are prefixed with the OBJECT IDENTIFIER ”p”,−− where ”p” is:−−−− iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).−− dec(36).ema(2).decMIBextension(18).decHub900(11)−−−− or, 1.3.6.1.4.1.36.2.18.11.−−−−−− Object Name Object Id Non−vol−− ================================== ================ =======−−−− pubCommon p.2


A1−56 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− pcomSlot p.2.1−− pcomOperStatus p.2.1.1.0−− pcomAdminStatus p.2.1.2.0 Yes−− pcomDiagFailure p.2.1.3.0−− pcomSerialNumber p.2.1.4.0 Yes−− pcomSlotNumber p.2.1.5.0−− pcomEsn p.2.1.6.0−− pcomHub p.2.2−− pcomHubId p.2.2.1.0 Yes−− pcomHubIpAddress p.2.2.2.0−− pcomHubCommunity p.2.2.3.0−− pcomLed p.2.3−− pcomLedTable p.2.3.1−− pcomLedEntry p.2.3.1.1−− pcomLedIndex p.2.3.1.1.1.n−− pcomLedDescr p.2.3.1.1.2.n−− pcomLedProgram p.2.3.1.1.3.n−− pcomLedInterestingChanges p.2.3.2.0−− pcomLoad p.2.4−− pcomLoadAdminStatus p.2.4.1.0−− pcomLoadOperStatus p.2.4.2.0−− pcomLoadFilename p.2.4.3.0−− pcomLoadIpHostAddr p.2.4.4.0−− pcomLoadDevSpecific p.2.4.5.0−− pcomSnmpAuth p.2.5 −− pcomSnmpAuthTrap p.2.5.1−− pcomSnmpAuthTrapCommunity p.2.5.1.1.0 Yes−− pcomSnmpAuthTrapUserTable p.2.5.1.2.1.1.n −− pcomSnmpAuthTrapUserEntry p.2.5.1.2.1.2.n −− pcomSnmpAuthTrapUserAddr p.2.5.1.2.1.3.n Yes−− pcomSnmpAuthTrapUserStatus p.2.5.1.2.1.4.n Yes−− pcomSnmpAuthReadOnly p.2.5.2−− pcomSnmpAuthReadOnlyCommunity p.2.5.2.1.0 Yes−− pcomSnmpAuthReadOnlyUserTable p.2.5.2.2.1−− pcomSnmpAuthReadOnlyUserEntry p.2.5.2.2.1.1.n −− pcomSnmpAuthReadOnlyUserAddr p.2.5.2.2.1.2.n Yes−− pcomSnmpAuthReadOnlyUserMask p.2.5.2.2.1.3.n Yes−− pcomSnmpAuthReadOnlyUserStatus p.2.5.2.2.1.4.n Yes−− pcomSnmpAuthReadWrite p.2.5.3−− pcomSnmpAuthReadWriteCommunity p.2.5.3.1.0 Yes−− pcomSnmpAuthReadWriteUserTable p.2.5.3.2.1.1.n −− pcomSnmpAuthReadWriteUserEntry p.2.5.3.2.1.2.n−− pcomSnmpAuthReadWriteUserAddr p.2.5.3.2.1.3.n Yes−− pcomSnmpAuthReadWriteUserMask p.2.5.3.2.1.4.n Yes−− pcomSnmpAuthReadWriteUserStatus p.2.5.3.2.1.5.n Yes−− pcomSnmpAuthUnauth p.2.5.4−− pcomSnmpAuthUnauthTable p.2.5.4.1−− pcomSnmpAuthUnauthEntry p.2.5.4.1.1−− pcomSnmpAuthUnauthIndex p.2.5.4.1.1.1.n−− pcomSnmpAuthUnauthTimeStamp p.2.5.4.1.1.2.n−− pcomSnmpAuthUnauthIpAddress p.2.5.4.1.1.3.n−− pcomSnmpAuthUnauthUdpPort p.2.5.4.1.1.4.n−− pcomSnmpAuthUnauthCommunity p.2.5.4.1.1.5.n−− pcomSnmpAuthUnauthOperation p.2.5.4.1.1.6.n−− pcomSnmpAuthUnauthReason p.2.5.4.1.1.7.n−− pcomErrLog p.2.6−− pcomErrLogNumEntries p.2.6.1.0−− pcomErrLogTable p.2.6.2−− pcomErrLogEntry p.2.6.2.1−− pcomErrLogIndex p.2.6.2.1.1.n Yes−− pcomErrLogTimeStamp p.2.6.2.1.2.n Yes−− pcomErrLogResetNumber p.2.6.2.1.3.n Yes−− pcomErrLogInfo p.2.6.2.1.4.n Yes−− pcomEsys p.2.7−− pcomEsysPowerups p.2.7.1.0 Yes−− pcomEsysMgmtResets p.2.7.2.0 Yes−− pcomEsysUnsolicitedResets p.2.7.3.0 Yes−− pcomEsysNVRAMfailedFlag p.2.7.4.0−− pcomEsysNVRAMsize p.2.7.5.0−− pcomEsysNVRAMavailableOctets p.2.7.6.0−− pcomEsysHUBversion p.2.7.7.0−− pcomEif p.2.8−− pcomEifTable p.2.8.1−− pcomEifEntry p.2.8.1.1−− pcomEifIndex p.2.8.1.1.1.n−− pcomEifInBroadcastPkts p.2.8.1.1.2.n−− pcomLigo p.2.9−− pcomLigoNumEntries p.2.9.1.0


A1−5746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

−− pcomLigoTable p.2.9.2−− pcomLigoEntry p.2.9.2.1−− pcomLigoIndex p.2.9.2.1.1.n−− pcomLigoType p.2.9.2.1.2.n−− pcomLigoSubtypeSelect p.2.9.2.1.3.n−− pcomLigoSubtypeNumEntries p.2.9.3.0−− pcomLigoSubtypeTable p.2.9.4−− pcomLigoSubtypeEntry p.2.9.4.1−− pcomLigoSubtypeIndex p.2.9.4.1.1.n−− pcomLigoSubtypeLigoIndex p.2.9.4.1.2.n−− pcomLigoSubtypeLabelIndexMask p.2.9.4.1.3.n−− pcomLigoSubtypeFlavor p.2.9.4.1.4.n−− pcomLigoLabelNumEntries p.2.9.5.0−− pcomLigoLabelTable p.2.9.6−− pcomLigoLabelEntry p.2.9.6.1−− pcomLigoLabelIndex p.2.9.6.1.1.n−− pcomLigoLabelString p.2.9.6.1.2.n−− pcomCon p.2.10−− pcomConTotalConfigChanges p.2.10.1.0−− pcomConNumEntries p.2.10.2.0−− pcomConTable p.2.10.3−− pcomConEntry p.2.10.3.1−− pcomConIndex p.2.10.3.1.1.n−− pcomConTech p.2.10.3.1.2.n−− pcomConClass p.2.10.3.1.3.n−− pcomConGroupId p.2.10.3.1.4.n−− pcomConGroupSet p.2.10.3.1.5.n−− pcomConLabel p.2.10.3.1.6.n−− pcomConSubtypeSelect p.2.10.3.1.7.n−− pcomConSubtypeNumEntries p.2.10.4.0−− pcomConSubtypeTable p.2.10.5−− pcomConSubtypeEntry p.2.10.5.1−− pcomConSubtypeIndex p.2.10.5.1.1.n−− pcomConSubtypeConSet p.2.10.5.1.2.n−− pcomConSubtypeFlavor p.2.10.5.1.3.n−− pcomConIntLanNumEntries p.2.10.6−− pcomConIntLanTable p.2.10.7−− pcomConIntLanEntry p.2.10.7.1−− pcomConIntLanIndex p.2.10.7.1.1.n−− pcomConIntLanGroupIdMask p.2.10.7.1.2.n−− pcomConIntLanName p.2.10.7.1.3.n−− pcomConAssignNumEntries p.2.10.8.0−− pcomConAssignTable p.2.10.9−− pcomConAssignEntry p.2.10.9.1−− pcomConAssignIndex p.2.10.9.1.1.n−− pcomConAssignConGroup p.2.10.9.1.2.n−− pcomConAssignIntLan p.2.10.9.1.3.n−− pcomConAssignEntryStatus p.2.10.9.1.4.n−− pcom90mgt p.2.11−− pcom90mgtBackplaneMode p.2.11.1.0−− pcom90mgtBackplaneState p.2.11.2.0−− pcom90mgtBackplaneConfig p.2.11.3.0−−IMPORTS Counter, TimeTicks, IpAddress, enterprises FROM RFC1155−SMI OBJECT−TYPE FROM RFC−1212 DisplayString FROM RFC1213−MIB;−− Path to the decHub900 common MIB.dec OBJECT IDENTIFIER ::= { enterprises 36 }ema OBJECT IDENTIFIER ::= { dec 2 }decMIBextension OBJECT IDENTIFIER ::= { ema 18 }decHub900 OBJECT IDENTIFIER ::= { decMIBextension 11 }−− Dec Hub Module Common definitions, authorized to be defined by this−− MIB only.pubCommon OBJECT IDENTIFIER ::= { decHub900 2 }−− Groups within this MIB.pcomSlot OBJECT IDENTIFIER ::= { pubCommon 1 }pcomHub OBJECT IDENTIFIER ::= { pubCommon 2 }pcomLed OBJECT IDENTIFIER ::= { pubCommon 3 }pcomLoad OBJECT IDENTIFIER ::= { pubCommon 4 }pcomSnmpAuth OBJECT IDENTIFIER ::= { pubCommon 5 }pcomErrLog OBJECT IDENTIFIER ::= { pubCommon 6 }pcomEsys OBJECT IDENTIFIER ::= { pubCommon 7 }pcomEif OBJECT IDENTIFIER ::= { pubCommon 8 }pcomLigo OBJECT IDENTIFIER ::= { pubCommon 9 }


A1−58 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

pcomCon OBJECT IDENTIFIER ::= { pubCommon 10 }pcom90mgt OBJECT IDENTIFIER ::= { pubCommon 11 }−− +−−−− Slot Group−−−− Objects within the slot group describe the component’s relationship−− to the hub.−−−− −pcomOperStatus OBJECT−TYPE SYNTAX INTEGER { enabled(1), initializing(2), failure(3), nonFatalFailure(4), loading(5), disabled(6), needProgramLoad(7), testing(8) } ACCESS read−only STATUS mandatory DESCRIPTION ”Describes the current operational state of the device. Operational status may be expressed as one of the following: enabled(1) − indicates that the device in online and fully functional. initializing(2) − indicates that the device is initializing. Devices enter the initializing state when powered on, or when reset. failure(3) − indicates that the device’s self−test has detected a fault. The device is functionally offline, and may or may not be powered. nonFatalFailure(4) − indicates that the device’s self−test has detected a non−fatal fault. The operates are less than a fully functional level in the presence of non−fatal errors. loading(5) − indicates that the device is attempting to load. disabled(6) − indicates that the device has been disabled. The device must still be able to respond to management messages. needProgramLoad(7) − indicates that the device is waiting to be loaded. other(8) − is a catch all. Modules may only be managed via an NMS when they are in the online and/or disabled states. Not all components implement all state of this object. For example, if a component can not report ’failure’, then it doesn’t. The enabled and disabled states are supported by all components.” ::= { pcomSlot 1 }pcomAdminStatus OBJECT−TYPE SYNTAX INTEGER { enable(1), disable(2), reset(3), restoreToDefaults(4) } ACCESS read−write STATUS mandatory DESCRIPTION ”enabled(1) − setting this object to enabled causes the device to begin it’s power up sequence and attempt to enter its operational state. If the value of this object was disabled, then the non−volatile value of this object is changed to enabled. As part of the power up sequence, the device’s management parameters may or may not be reset. (In other words, the device may go through the equivalent of a reset or before returning to the online state. If the device is capable of going directly from the disabled state to the enabled state without resetting any of its management parameters, then it may do so. Such action is product specific.) disabled(2) − setting this object to offline causes the device to cease network activity and enter a quiescent state. A disabled device must still be able to respond to management messages.


A1−5946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

The value enable(1) or disable(2) shall be stored in non−volatile memory for the initial reset value of this variable. The factory default NV value is enable(1). reset(3) − setting this object to this state resets the module, including its volatile managed objects. Resetting may involve running the devices self−test diagnostic. If diagnostics fail, this object will remain in the reset state and failure status will be reflected elsewhere in the mib. If diagnostics pass, then the device will automatically return to the enabled state. After reset, this object shall assume the non−volatile value of enable(1) or disable(2). (So, if you reset a disabled module, the device will reset and come back up still in the disabled state.) restoreToDefaults(4) − setting this object to this state restores all of its non−volatile parameters to their factory default state and resets the module (see reset(3)). Note: The default value of this object is, or course, enabled. Note: Some devices may not send a getResponse to a PDU which commands the device to reset. Setting this object to reset, restoreToDefaults, or enable may cause the device to reset.” ::= { pcomSlot 2 }pcomDiagFailure OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”This object contains the results of power−on self test. When zero, the unit passed self test okay. When non−zero and pcomOperStatus indicates a failure the value is a module−specific error code. When non−zero and pcomOperStatus indicates a nonFatalFailure the value is a module−specific non−fatal error code.” ::= { pcomSlot 3 }pcomSerialNumber OBJECT−TYPE SYNTAX DisplayString (SIZE(0..31)) ACCESS read−write −− ** Non Volatile STATUS mandatory DESCRIPTION ”Serial number for the module. This variable is set to a zero length string initially. Users may store a serial number for the module. The value of this object in not affected by a ’restoreToDefaults’ operation.” ::= { pcomSlot 4 }pcomSlotNumber OBJECT−TYPE SYNTAX INTEGER (0..15) ACCESS read−only STATUS mandatory DESCRIPTION ”Number of the slot in which module is inserted, as indicated by pins on the backplane connector. If module is not inserted in a hub the value of this object is 0.” ::= { pcomSlot 5 }pcomEsn OBJECT−TYPE SYNTAX INTEGER (0..4294967295) ACCESS read−only STATUS mandatory DESCRIPTION ”Extended Slot Number assigned to module. An ESN is a 32−bit integer which has a decimal representation that indicates the physical connectivity of both local and remote modules to the hub. The decimal representation is of the form: ss [aa [bb [cc [dd]]]] where [] indicates optional. A module inserted directly in the hub has an ESN ’ss’ that is the same as its slot number (e.g 3). A remote module connected to the local module’s ’aa’ port has ESN ssaa. For example, if a concentrator in slot 3 has a repeater connected to port 2, the repeater has ESN 302. Dec Hubs can manage devices up to four remote hops away from the hub.” ::= { pcomSlot 6 }−− +−−−− Hub Group (aka ”Reverse MIB”)−−−− Using the Reverse MIB, network management stations can easily determine−− the the component is in a hub, and find out how to communicate with the


A1−60 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− hub’s management agent.−−−− These objects may only be set by the hub manager.−− −− Modules which do not implement a MAC layer are still required−− to implement these variables, in order to permit a consistent view−− to external network operation centers.−−−− −pcomHubId OBJECT−TYPE SYNTAX OCTET STRING (SIZE(6)) ACCESS read−only STATUS deprecated DESCRIPTION ”A 6−byte unique identifier. The HubId is assigned to the component by hub manager when the new component is recognized. The initial HubId is zero. The component stores the HubId in non−volatile memory. There is an internal read−write version of this public common read−only variable. *************************************************************** This object has been deprecated. Not all devices support it. *************************************************************** ” ::= { pcomHub 1 }pcomHubIpAddress OBJECT−TYPE SYNTAX IpAddress ACCESS read−only STATUS mandatory DESCRIPTION ”The IP address used to reach to Hub Manager via the MAC implemented by the component. This is initialized to all zeros (0.0.0.0) at reset. There is an internal read−write version of this public common read−only variable.” ::= { pcomHub 2 }pcomHubCommunity OBJECT−TYPE SYNTAX OCTET STRING (SIZE(0..32)) ACCESS read−only STATUS mandatory DESCRIPTION ”The public read−only SNMP community string used by the Hub Manager. This value is initialized to the null (zero−length) string at reset. There is an internal read−write version of this public common read−only variable.” ::= { pcomHub 3 }−− +−− −− Led Group−− −− −pcomLedTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomLedEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of led entries, one for led on the device.” ::= { pcomLed 1 }pcomLedEntry OBJECT−TYPE SYNTAX PcomLedEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Values for a led.” INDEX { pcomLedIndex } ::= { pcomLedTable 1 }PcomLedEntry ::= SEQUENCE { pcomLedIndex INTEGER, pcomLedDescr DisplayString, pcomLedProgram OCTET STRING }pcomLedIndex OBJECT−TYPE SYNTAX INTEGER (1..127) ACCESS read−only STATUS mandatory DESCRIPTION


A1−6146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

”Index into the table.” ::= { pcomLedEntry 1 }pcomLedDescr OBJECT−TYPE SYNTAX DisplayString (SIZE(0..80)) ACCESS read−only STATUS mandatory DESCRIPTION ”A textual description of the information which the LED is meant to convey. i.e.: +5 Volt Power, DC Okay Ethernet segment activity. Diagnostic status.” ::= { pcomLedEntry 2 }pcomLedProgram OBJECT−TYPE SYNTAX OCTET STRING (SIZE(0..48)) ACCESS read−only STATUS mandatory DESCRIPTION ”The pcomLedProgram string is a sequence of instructions for the LED state. The LED constantly repeats the program. Each LED state is represented by a two octet sequence where the value of the first octet of the pair indicates the color of the LED, and the value of the seconds octet of the pair indicates the duration in which that color will be present. +−−−−−−−−−−+−−−−−−−−−−+ −−/ /−− +−−−−−−−−−−+−−−−−−−−−−+ | Color | Duration | | Color | Duration | +−−−−−−−−−−+−−−−−−−−−−+ −−/ /−− +−−−−−−−−−−+−−−−−−−−−−+ The ’color’ octet may have one of the following values: 0 − off 1 − other 2 − red 3 − yellow 4 − green 5 − blue 6 − red−blinking 7 − yellow−blinking 8 − blue−blinking 9 − green−blinking The value ’off’ indicates that the led is off. The value ’other’ indicates a color not covered by any others in the list. The value of the second octet in each pair indicates the duration in which that color will be present. A value of zero indicates that the LED is off. A value of 0xff indicates that the LED is always on. Values in between 0 and 0xff indicate the duration in 10 ms ticks. A zero length string may be returned if the LED is ’not present’. This indicates that the LED is currently not visible. (This is provided for modules which may attach to different chassis, i.e. an 8−slot chassis or a single−slot chassis, in which a different LEDs may be visible. For example, say an extra three LEDs are visible when the device is inserted in a single−slot chassis. When the device is removed from the single slot chassis and inserted into the 8−slot chassis, these three LEDs may not be visible. Therefore, a zero length string may be returned to indicate that these three LEDs are not present.) Activity LEDs are a special case. Activity LEDs are defined as LEDs which blink whenever data is received on the line. They are typically on solid under heavy activity. Since these LEDs can change rapidly, the following rules apply: o The initial state of activity LEDs is off. o If the line shows activity any time in a 10 second period, then the LED is shown as on. o If the line shown inactivity any time in a 10 second period, then the LED is shown as off. Example: Consider a 4−bank, 12−port repeater: Bank: Ports: −−−− −−−−− Bank A: A1, A2, A3 Bank B: B1, B2, B3 Bank C: C1, C2, C3 Bank D: D1, D2, D3 Which has the following LEDs: LED: pcomLedDescr: pcomLedIndex: −−− −−−−−−−−−−−− −−−−−−−−−−−− PWR Hub Power On 1 DIAG Diagnostics 2


A1−62 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

A Bank Indicator A 3 B Bank Indicator B 4 C Bank Indicator C 5 D Bank Indicator D 6 P1: Port Status 1A/B/C/D 7 P2: Port Status 2A/B/C/D 8 P3: Port Status 3A/B/C/D 9 Assume the ports of this repeater are in the following states: Port: State: −−−− −−−−− 1A Operational, auto−partitioned, media available 2A Not operational 3A Operational, not auto−partitioned, media available 1B Operational, not auto−partitioned, media available 2B Not operational 3B Not operational 1C Operational, not auto−partitioned, media available 2C Operational, auto−partitioned, media available 3C Not operational 1D Operational, auto−partitioned, media available 2D Not operational 3D Operational, auto−partitioned, media available Here are the contents of the pcomLedTable for this example: ledIndex: ledDescr: ledProgram: −−−−−−−− −−−−−−−− −−−−−−−−−− 1 Hub Power On 0x04, 0xFF 2 Diagnostics 0x04, 0x32, 0x00, 0x32 3 Bank Indicator A 0x04, 0xC8, 0x00, 0xC8, 0x00, 0xC8, 0x00, 0xC8 4 Bank Indicator B 0x00, 0xC8, 0x04, 0xC8, 0x00, 0xC8, 0x00, 0xC8 5 Bank Indicator C 0x00, 0xC8, 0x00, 0xC8, 0x04, 0xC8, 0x00, 0xC8 6 Bank Indicator D 0x00, 0xC8, 0x00, 0xC8, 0x00, 0xC8, 0x04, 0xC8 7 Port 1A/B/C/D 0x00, 0xC8, 0x04, 0xC8, 0x04, 0xC8, 0x00, 0xC8 8 Port 2A/B/C/D 0x08, 0xC8, 0x08, 0xC8, 0x00, 0xC8, 0x08, 0xC8 9 Port 3A/B/C/D 0x04, 0xC8, 0x08, 0xC8, 0x08, 0xC8, 0x00, 0xC8 This example shows: o LED 1 is green, and always on o LED 2 is blinking at a frequency of 1 Hz (1/2 sec green, 1/2 sec. off) LED’s 3−6 indicate for which bank (a−D) of ports status is currently being displayed on LED’s 7−9. o LED 3 is on for 2 seconds, then off for 6 seconds o LED 4 is off for 2 seconds, on for 2 seconds, off for 4 seconds o LED 5 is off for 4 seconds, on for 2 seconds, off for 2 seconds o LED 6 is off for 6 seconds, then on for 2 seconds o LED 7 is the status LED for Ports 1A, 1B, 1C and 1D. In this example, it is: off for 2 seconds (indicating port 1A is operational but auto−partitioned), solid green for 4 seconds (indicating ports 1B and 1C are operational, not auto−partitioned with media available), and off for 2 seconds (indicating Port 1D is operational but auto−partitioned) o LED 8 is the status LED for Ports 2A, 2B, 2C and 2D. In this example, it is: Blinking green for 4 seconds (indicating ports 2A and 2B are not operational), off for 2 seconds (indicating port 2C is operational but auto−partitioned), and blinking green for 2 seconds (indicating port 2D is not operational). o LED 9 is the status LED for Ports 3A, 3B, 3C and 3D. In this example, it is: Solid green for 2 seconds (indicating port 3A is operational, not auto−partitioned with media available), Blinking Green for 4 seconds (indicating ports 3B and 3C are not operational), and off for 2 seconds (indicating port 3D is operational but auto−partitioned ).” ::= { pcomLedEntry 3 }pcomLedInterestingChanges OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”This counter may be polled to determine if any


A1−6346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

interesting changes in the pcomLedTable have occurred.” ::= { pcomLed 2 }−− +−− −− Load Group.−− −− −pcomLoadAdminStatus OBJECT−TYPE SYNTAX INTEGER { other(1), start−read(2), start−write(3), cancel(4) } ACCESS read−write STATUS mandatory DESCRIPTION ”This object is used to control the program load process of a device. When read, the value other(1) is returned. When set to start−read(2) the device initiates a TFTP read operation to read a new program image. When set to start−write(3) the device is placed in such a state as to accept a new program image via a TFTP write operation. Once initiated, the status of the load attempt is reflected in pcomLoadOperStatus. A device shall always reset upon completion of a successful load attempt. It may reset upon unsuccessful completion of the load attempt. When set to cancel(4) the device will attempt to cancel an ongoing load.” ::= { pcomLoad 1 }pcomLoadOperStatus OBJECT−TYPE SYNTAX INTEGER { none(1), success(2), failure(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”The final state of the last load attempt. none(1) indicates that no load has been attempted, ever. This object is non−volatile. It’s default value is none(1).” ::= { pcomLoad 2 } pcomLoadFilename OBJECT−TYPE SYNTAX DisplayString (SIZE(0..64)) ACCESS read−write STATUS mandatory DESCRIPTION ”The name of the file in which to load. When the device is reading, this is the name of the file to be read. When the device is being written, this is the only name of the file in which writes will be accepted − provided the device can check the file name. If the device can not check the file name then this object is ignored. It is the duty of the NMS triggering the device to load this object. This object is non−volatile. The initial and default value of this object in a zero−lengthed string. In the case of multi−file loads (aka segmented loads) this object contains the name of the first file in which to load. It is an application specific issue as to how to get subsequent load files.” ::= { pcomLoad 3 } pcomLoadIpHostAddr OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”The IP address of the host from which to load. When the device is reading, this is the IP address of the host in which the read will be directed. When the device is being written, this is the IP address of the only host in which writes will be accepted.


A1−64 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

This object is non−volatile. The initial and default value of this object is 0.0.0.0. If the load is ’assisted’, and does not use IP, it is the responsibility of the assistant to write this object. (In this case, the object may be useful for debug purposes.)” ::= { pcomLoad 4 }pcomLoadDevSpecific OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”A device specific parameter which may be used to indicate detailed error information about the last attempted load. A value of zero indicates that no load has been attempted, or that there is nothing interesting to report of the last load. This object is non−volatile.” ::= { pcomLoad 5 }−− +−− −− SNMP Authentication Database.−−−− The Simple Network Management Protocol (SNMP) employs a ”trivial”−− authentication scheme based on ”community names”. Community names are−− textual strings which represent access to a set of objects with a set of−− access rights.−− −− The SNMP Authentication Group contains objects which provide access−− rights for three communities: read−only, read−write, and traps. Each−− of the three communities contain a community string object, and a−− UserTable.−− −− The community string provides the name of the community. All community−− strings are initially ”public”. The default community string may be−− changes to provide additional security. For example, the read−write−− community may be changed from ”public” to ”secret”. This only allows−− read−write access to users who know the ”secret” read−write community−− string.−− −− The UserTable is a table of authorized users of the community. By−− default, all users (who known the community string) are authorized to−− use the community. Each communities UserTable contains three object:−− UserAddr, UserMask, and UserStatus.−− −− UserAddr is the IP address of an authorized user, or a group of−− authorized users. Initially, all users are allowed access. Writing−− 16.21.16.128 to an entry of the read−only UserTable prohibits read−− access from any host but 16.21.16.128.−− −− UserMask is used to provide ’wildcard’ authorized users. This mask is−− applied to the incoming IpAddress and the value of the corresponding−− UserAddr. If the resulting incoming IpAddress and _UserAddr match, the−− message is considered authorized. (For example, UserAddr of−− 16.21.16.128 and UserMask of 0xffffff00 allows users from 16.21.16.0 to−− 16.21.16.255 to be authorized on the community.)−− −− UserStatus is used to create and delete entries. Entries are created by−− setting UserAddress. Entries are deleted by setting UserStatus to−− invalid(2). Invalid entries are removed from the UserTable.−− −− All trap, read−only, and read−write community string are non−volatile.−− All UserTable information is also non−volatile.−− −−−−− SNMP Trap User Community−−pcomSnmpAuthTrap OBJECT IDENTIFIER ::= { pcomSnmpAuth 1 }pcomSnmpAuthTrapCommunity OBJECT−TYPE SYNTAX OCTET STRING (SIZE (4..31)) ACCESS read−write STATUS mandatory DESCRIPTION ”The community string used in SNMP Trap PDUs. This value is initially ’public’.” ::= { pcomSnmpAuthTrap 1 }pcomSnmpAuthTrapUserTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomSnmpAuthTrapUserEntry ACCESS not−accessible


A1−6546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

STATUS mandatory DESCRIPTION ”A list of IP addresses to which traps will be sent and an associated row creation/deletion object.” ::= { pcomSnmpAuthTrap 2 }pcomSnmpAuthTrapUserEntry OBJECT−TYPE SYNTAX PcomSnmpAuthTrapUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Objects containing information for a given trap address. Rows are created when pcomSnmpAuthTrapAddr is set, and deleted when pcomSnmpAuthTrapUserStatus is set to invalid(2).” INDEX { pcomSnmpAuthTrapUserAddr } ::= { pcomSnmpAuthTrapUserTable 1 }PcomSnmpAuthTrapUserEntry ::= SEQUENCE { pcomSnmpAuthTrapUserAddr IpAddress, pcomSnmpAuthTrapUserStatus INTEGER }pcomSnmpAuthTrapUserAddr OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”An IP Address to which all SNMP Trap messages will be sent.” ::= { pcomSnmpAuthTrapUserEntry 1 }pcomSnmpAuthTrapUserStatus OBJECT−TYPE SYNTAX INTEGER { other(1), invalid(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1).” ::= { pcomSnmpAuthTrapUserEntry 2 }−−−− SNMP Read−only User Community−−pcomSnmpAuthReadOnly OBJECT IDENTIFIER ::= { pcomSnmpAuth 2 }pcomSnmpAuthReadOnlyCommunity OBJECT−TYPE SYNTAX OCTET STRING (SIZE (4..31)) ACCESS read−write STATUS mandatory DESCRIPTION ”The community string used to identify an SNMP community with access rights of read−only. This value is initially ’public’.” ::= { pcomSnmpAuthReadOnly 1 }pcomSnmpAuthReadOnlyUserTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomSnmpAuthReadOnlyUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of Read−only users and associated information.” ::= { pcomSnmpAuthReadOnly 2 }pcomSnmpAuthReadOnlyUserEntry OBJECT−TYPE SYNTAX PcomSnmpAuthReadOnlyUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Objects containing information for a given Read−only user. Rows are created when pcomSnmpAuthReadOnlyUserAddr is set, and deleted when pcomSnmpAuthReadOnlyUserStatus is set to invalid(2).” INDEX { pcomSnmpAuthReadOnlyUserAddr } ::= { pcomSnmpAuthReadOnlyUserTable 1 }PcomSnmpAuthReadOnlyUserEntry ::= SEQUENCE { pcomSnmpAuthReadOnlyUserAddr IpAddress, pcomSnmpAuthReadOnlyUserMask OCTET STRING, pcomSnmpAuthReadOnlyUserStatus


A1−66 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

INTEGER }pcomSnmpAuthReadOnlyUserAddr OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”An IP Address, or a set of IP addresses, which has Read−only SNMP access to this agent. If this object is used as a wildcard, bits corresponding to the zero bits in the corresponding euthReadOnlyUserMask are treated as don’t−care.” ::= { pcomSnmpAuthReadOnlyUserEntry 1 }pcomSnmpAuthReadOnlyUserMask OBJECT−TYPE SYNTAX OCTET STRING (SIZE (4)) ACCESS read−write STATUS mandatory DESCRIPTION ”UserMask is used to provide ’wildcard’ authorized users. It is a 32−bit mask which is applied to (ANDed with) the source IP address of an incoming SNMP message. If the result of the mask is equal to an address in pcomSnmpAuthReadOnlyUserAddr, the message is considered to have come from a user who has Read−only access. This allows wildcarding. For example, a user address of 16.20.0.0 and a mask of 255.255.0.0 allow access to all NMS’s on subnet 16.20. The default value for this mask is all 1’s.” ::= { pcomSnmpAuthReadOnlyUserEntry 2 }pcomSnmpAuthReadOnlyUserStatus OBJECT−TYPE SYNTAX INTEGER { other(1), invalid(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1).” ::= { pcomSnmpAuthReadOnlyUserEntry 3 }−−−− SNMP Read−Write User Community−−pcomSnmpAuthReadWrite OBJECT IDENTIFIER ::= { pcomSnmpAuth 3 }pcomSnmpAuthReadWriteCommunity OBJECT−TYPE SYNTAX OCTET STRING (SIZE (4..31)) ACCESS read−write STATUS mandatory DESCRIPTION ”The community string used to identify an SNMP community with access rights of Read−Write. Note, this object may only be read or written using the read−write community. Read−only access to this object is denied.” ::= { pcomSnmpAuthReadWrite 1 }pcomSnmpAuthReadWriteUserTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomSnmpAuthReadWriteUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of Read−Write users and associated information.” ::= { pcomSnmpAuthReadWrite 2 }pcomSnmpAuthReadWriteUserEntry OBJECT−TYPE SYNTAX PcomSnmpAuthReadWriteUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Objects containing information for a given Read−Write user. Rows are created when pcomSnmpAuthReadWriteUserAddr is set, and deleted when pcomSnmpAuthReadWriteUserStatus is set to invalid(2).” INDEX { pcomSnmpAuthReadWriteUserAddr } ::= { pcomSnmpAuthReadWriteUserTable 1 }PcomSnmpAuthReadWriteUserEntry ::= SEQUENCE { pcomSnmpAuthReadWriteUserAddr IpAddress, pcomSnmpAuthReadWriteUserMask


A1−6746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

OCTET STRING, pcomSnmpAuthReadWriteUserStatus INTEGER }pcomSnmpAuthReadWriteUserAddr OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”An IP Address, or a set of IP addresses, which has Read−Write SNMP access to this agent. If this object is used as a wildcard, bits corresponding to the zero bits in the corresponding euthReadWriteUserMask are treated as don’t−care. Note, this object may only be read or written using the read−write community. Read−only access to this object is denied.” ::= { pcomSnmpAuthReadWriteUserEntry 1 }pcomSnmpAuthReadWriteUserMask OBJECT−TYPE SYNTAX OCTET STRING (SIZE (4)) ACCESS read−write STATUS mandatory DESCRIPTION ”UserMask is used to provide ’wildcard’ authorized users. It is a 32−bit mask which is applied to (ANDed with) the source IP address of an incoming SNMP message. If the result of the mask is equal to an address in pcomSnmpAuthReadOnlyUserAddr, the message is considered to have come from a user who has Read−only access. This allows wildcarding. For example, a user address of 16.20.0.0 and a mask of 255.255.0.0 allow access to all NMS’s on subnet 16.20. The default value for this mask is all 1’s. Note, this object may only be read or written using the read−write community. Read−only access to this object is denied.” ::= { pcomSnmpAuthReadWriteUserEntry 2 }pcomSnmpAuthReadWriteUserStatus OBJECT−TYPE SYNTAX INTEGER { other(1), invalid(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1). Note, this object may only be read or written using the read−write community. Read−only access to this object is denied.” ::= { pcomSnmpAuthReadWriteUserEntry 3 }−−−− The Last N Authentication Failures−−−− Objects in this group report authentication failures which have occurred−− since the agent last reset. The objects in this group due not affect,−− and are not affected by SNMP Authentication Failure traps.−−−− The ”Last N Authentication Failures” log may only be read using the −− read−write community. Read−only access to this log is denied.−− (Allowing access via the read−only community might compromise security.)−−−− In the example below it is assumed that SNMP authentication objects have −− been set so as to allow read−only access to all nodes via the ’public’−− community, and read−write access to nodes on subnet 16.20 via community−− ’secret’. The authentication objects are as follows:−−−− readOnlyCommunity: public−− readOnlyUserTable: Empty−− readWriteCommunity secret−− readWriteUserTable−− Addr: 16.20.0.0−− Mask: 255.255.0.0 −− −− One ’Last N Authentication Failures’ log might contain:−−−− Index TimeStamp IpAddress UdpPort Community Operation Reason


A1−68 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− ===== ========= ============ ======= ========= ========= ==========−− 3 6000 16.20.16.128 1025 pubbic get−next badComUse−− 4 15420 16.210.32.64 9834 public set badComUse−− 5 15560 16.210.32.64 9834 public set badComUse−− 6 8640000 40.13.253.19 41091 foobar get−next badComUse−− 7 17280000 14.56.126.4 19043 seckret get−next badComUse−− 8 108956539 16.210.32.64 16386 public set badComUse−− 9 108957562 16.210.32.64 16386 public set badComUse−− 10 108959550 16.210.32.64 16386 secret set badComUser−−−− Indices 3−10 indicate that there have been 10 authentication failures−− since the unit last reset. Only the last 8 authentication failures were−− logged. (The size of the pcomSnmpAuthUnauthTable varies from product to−− product.) The index wraps from 65535 back to 0. −−−− Entry 3 − One minute after the device reset a user tried to access the −− agent using community ’pubbic’ rather than ’public’. Since−− ’pubbic’ is not a recognized community, a badComUse error−− is logged.−− Entry 4 − Since the readWrite community is ’secret’, the set from user−− at the transport address 16.210.32.64.98.34 using the−− ’public’ community caused this log entry.−− Entry 5 − Same as entry 4, but occurring 1.4 seconds later.−− Entry 6 − Community ’foobar’ was not recognized.−− Entry 7 − Community ’seckret’ was not recognized.−− Entry 8 − Same as entry 4, but later.−− Entry 9 − Same as entry 4, but later.−− Entry 10 − The correct read−write community was used, but the readWrite−−− UserTable prohibits access to all IP addresses which do not−− begin with 16.20. Since the set request came from IP address−− 16.210, it is not authentic. Unlike all other log entries−− which report badComUse error, this is a badComUser error.−−−− In this example, the table can only be read using the read−write −− community, which in this case is ”secret”.−−pcomSnmpAuthUnauth OBJECT IDENTIFIER ::= { pcomSnmpAuth 4 }pcomSnmpAuthUnauthTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomSnmpAuthUnauthEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of unauthorized user entries.” ::= { pcomSnmpAuthUnauth 1 }pcomSnmpAuthUnauthEntry OBJECT−TYPE SYNTAX PcomSnmpAuthUnauthEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”An unauthorized user entry containing information common to a single case where an snmp management message for not authorized.” INDEX { pcomSnmpAuthUnauthIndex } ::= { pcomSnmpAuthUnauthTable 1 }PcomSnmpAuthUnauthEntry ::= SEQUENCE { pcomSnmpAuthUnauthIndex INTEGER, pcomSnmpAuthUnauthTimeStamp TimeTicks, pcomSnmpAuthUnauthIpAddress IpAddress, pcomSnmpAuthUnauthUdpPort INTEGER, pcomSnmpAuthUnauthCommunity OCTET STRING, pcomSnmpAuthUnauthOperation INTEGER, pcomSnmpAuthUnauthReason INTEGER }pcomSnmpAuthUnauthIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION


A1−6946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

”A unique integer used to index this table.” ::= { pcomSnmpAuthUnauthEntry 1 }pcomSnmpAuthUnauthTimeStamp OBJECT−TYPE SYNTAX TimeTicks ACCESS read−only STATUS mandatory DESCRIPTION ”The value of sysUpTime when the message was unauthenticated.” ::= { pcomSnmpAuthUnauthEntry 2 }pcomSnmpAuthUnauthIpAddress OBJECT−TYPE SYNTAX IpAddress ACCESS read−only STATUS mandatory DESCRIPTION ”The IP address upon which the unauthenticated message arrived.” ::= { pcomSnmpAuthUnauthEntry 3 }pcomSnmpAuthUnauthUdpPort OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The UDP port number upon which the unauthenticated message arrived.” ::= { pcomSnmpAuthUnauthEntry 4 }pcomSnmpAuthUnauthCommunity OBJECT−TYPE SYNTAX OCTET STRING (SIZE(0..32)) ACCESS read−only STATUS mandatory DESCRIPTION ”The community string present in the unauthenticated message. Only the only the first 32 octets of the community string are kept.” ::= { pcomSnmpAuthUnauthEntry 5 }pcomSnmpAuthUnauthOperation OBJECT−TYPE SYNTAX INTEGER { other(1), getRequest(2), getNextRequest(3), getResponse(4), setRequest(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”The attempted operation.” ::= { pcomSnmpAuthUnauthEntry 6 }pcomSnmpAuthUnauthReason OBJECT−TYPE SYNTAX INTEGER { badComName(1), badComUse(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”The reason for failing to authenticate the message. A value of badComName(1) indicates that the community string in the failed message does not match a community supported by the device. This corresponds to the incrementing of the mib−ii object ’snmpInBadCommunityNames’. A value of badComUse(2) indicates that the user id (ip address and udp port) does not match a user id supported by the device. This corresponds the the incrementing of the mib−ii object ’snmpInBadCommunityUses’.” ::= { pcomSnmpAuthUnauthEntry 7 }−− +−−−− The Error Log Group. −−−− This group is optional, but highly recommended for all DEChub900 products.−− The group contains objects pertaining to system failures. Though publicly−− available, the objects are designed primarily for use by Digital Equipment−− Corporation. All objects are non−volatile: they maintain their values −− across resets.−−−− The errLogTable is a ring. If a maximum of 8 entries are supported−− then the first 8 errors are indexed 1 through 8. The 9th error−− overwrites the oldest entry, entry 1, such that the table contains−− indices 2 through 9. The index continues to increase as errors


A1−70 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− are logged. The index wraps from 65535 back to 0.−−−− −pcomErrLogNumEntries OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The number of entries in the pcomErrLogTable. The value of this object is initially zero. It is incremented as pcomErrLogEntries are added, to a maximum value. The maximum value is implementation specific.” ::= { pcomErrLog 1 }pcomErrLogTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomErrLogEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table which describes errors encountered by the system.” ::= { pcomErrLog 2 }pcomErrLogEntry OBJECT−TYPE SYNTAX PcomErrLogEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of errors logged by the system.” INDEX { pcomErrLogIndex } ::= { pcomErrLogTable 1 }PcomErrLogEntry ::= SEQUENCE { pcomErrLogIndex INTEGER, pcomErrLogTimeStamp TimeTicks, pcomErrLogResetNumber INTEGER, pcomErrLogInfo DisplayString }pcomErrLogIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The value of this object uniquely identifies an entry in the pcomErrLogTable.” ::= { pcomErrLogEntry 1 }pcomErrLogTimeStamp OBJECT−TYPE SYNTAX TimeTicks ACCESS read−only STATUS mandatory DESCRIPTION ”The value of sysUpTime at the time in which the error is logged.” ::= { pcomErrLogEntry 2 }pcomErrLogResetNumber OBJECT−TYPE SYNTAX INTEGER (1..4294967295) ACCESS read−only STATUS mandatory DESCRIPTION ”The number of resets which have occurred at the time in which the error is logged. (This is the sum of pcomEsysPowerups, pcomEsysMgmtResets, and pcomEsysUnsolicitedResets.)” ::= { pcomErrLogEntry 3 }pcomErrLogInfo OBJECT−TYPE SYNTAX DisplayString (SIZE(0..255)) ACCESS read−only STATUS mandatory DESCRIPTION ”A textual description of the error being logged.” ::= { pcomErrLogEntry 4 }−− +−−−− The extended system group. This group is optional.−−−− −pcomEsysPowerups OBJECT−TYPE SYNTAX Counter


A1−7146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times this device was powered on. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.” ::= { pcomEsys 1 }pcomEsysMgmtResets OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times the device was initialized with a management command. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.” ::= { pcomEsys 2 }pcomEsysUnsolicitedResets OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of times the device initialized itself after encountering a fatal error. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.” ::= { pcomEsys 3 }pcomEsysNVRAMfailedFlag OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”When true(1), this flag indicates that the device’s non−volatile memory store has failed. Devices whose non−volatile memory store have failed still accept SNMP sets. If the SNMP set request refers to a non−volatile object and this flag is true only the volatile copy of the object is set. If the non−volatile memory failure was detected by the power on selftest then pcomDiagFailure is non−zero.” ::= { pcomEsys 4 }pcomEsysNVRAMsize OBJECT−TYPE SYNTAX INTEGER (0..2147483647) ACCESS read−only STATUS mandatory DESCRIPTION ”The size of the non−volatile store. Note that this is the unformated size, and as such may not reflects the number usable octets provided by the store.” ::= { pcomEsys 5 }pcomEsysNVRAMavailableOctets OBJECT−TYPE SYNTAX INTEGER (0..2147483647) ACCESS read−only STATUS mandatory DESCRIPTION ”The number of octets currently available in the non−volatile store. Note that this may not provide a one−to−one mapping of user data to availableOctets. For example, in order to store a two characters in an object defined as DisplayString (SIZE( 0..128)) the device may choose to allocate 128 octets. Furthermore, directory overhead information may be allocated from the availableOctets. In other words, this object provides only a rough estimate. Your mileage may vary. Despite these shortcomings, when 0, this object conveys the fact that no non−volatile parameters may be added.” ::= { pcomEsys 6 }pcomEsysHubVersion OBJECT−TYPE SYNTAX DisplayString (SIZE(0..255)) ACCESS read−only STATUS mandatory DESCRIPTION ”The version number of the hub citizenship code that is being used in this device.” ::= { pcomEsys 7 }−− +−−


A1−72 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− The extended interface group. This group is mandatory for all−− implementations which support the MIB−2 interface group.−−−− −pcomEifTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomEifEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table which describes extensions for the mib−2 interface group.” ::= { pcomEif 1 }pcomEifEntry OBJECT−TYPE SYNTAX PcomEifEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of interface information. For each instance of MIB−2 interface group ifIndex there exists a corresponding instance of pcomEifIndex.” INDEX { pcomEifIndex } ::= { pcomEifTable 1 }PcomEifEntry ::= SEQUENCE { pcomEifIndex INTEGER, pcomEifInBroadcastPkts Counter }pcomEifIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The value of this object uniquely identifies an entry in the pcomEifTable. Each pcomEifTable corresponds to an instance of ifIndex in the MIB−2 interface group.” ::= { pcomEifEntry 1 }pcomEifInBroadcastPkts OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Interfaces which support broadcasting (e.g. ethernet−csmacd ports − ifType 6) return the number of broadcast packets delivered to a higher−layer protocol. Interfaces which do not support broadcasting (e.g. slip ports − ifType 28) return zero when queried for this object.” ::= { pcomEifEntry 2 }−− −− ===========================================================================−− ======================= T h e L i g o G r o u p =======================−− ===========================================================================−−−−pcomLigoNumEntries OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The number of entries in the LIGO table.” ::= { pcomLigo 1 }pcomLigoTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomLigoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of LIGOs (building blocks).” ::= { pcomLigo 2 }pcomLigoEntry OBJECT−TYPE SYNTAX PcomLigoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A LIGO entry containing objects which describe the building block.” INDEX { pcomLigoIndex } ::= { pcomLigoTable 1 }


A1−7346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

PcomLigoEntry ::= SEQUENCE { pcomLigoIndex INTEGER, pcomLigoType INTEGER, pcomLigoSubtypeSelect INTEGER }pcomLigoIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each LIGO. The value of this object ranges between 1 and n where n is the total number of building blocks supported by the device.” ::= { pcomLigoEntry 1 }pcomLigoType OBJECT−TYPE SYNTAX INTEGER { other(1), fddi(2), ethernet(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”A building block’s type.” ::= { pcomLigoEntry 2 }pcomLigoSubtypeSelect OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−write STATUS mandatory DESCRIPTION ”The pcomLigoSubtypeIndex into the pcomLigoSubtypeTable describes the specific LIGO type is supported. The value of this object must be a valid index in the pcomLigoTable. A value of 0 indicates that no subtype has been selected.” ::= { pcomLigoEntry 3 }pcomLigoSubtypeNumEntries OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The number of entries in the pcomLigoSubtypeTable.” ::= { pcomLigo 3 }pcomLigoSubtypeTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomLigoSubtypeEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of LIGO (building blocks) subtypes.” ::= { pcomLigo 4 }pcomLigoSubtypeEntry OBJECT−TYPE SYNTAX PcomLigoSubtypeEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”An entry containing objects which describe the building block’s specific type.” INDEX { pcomLigoSubtypeIndex } ::= { pcomLigoSubtypeTable 1 }PcomLigoSubtypeEntry ::= SEQUENCE { pcomLigoSubtypeIndex INTEGER, pcomLigoSubtypeLigoIndex INTEGER, pcomLigoSubtypeLabelIndexMask INTEGER, pcomLigoSubtypeFlavor INTEGER }pcomLigoSubtypeIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each LIGO subtype.” ::= { pcomLigoSubtypeEntry 1 }pcomLigoSubtypeLigoIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory


A1−74 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

DESCRIPTION ”The value of the LigoIndex in the pcomLigoTable that can use this subtype.” ::= { pcomLigoSubtypeEntry 2 }pcomLigoSubtypeLabelIndexMask OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”This object specifies the labels that are used by this LigoSubtype. It is a bit map of if indexes from the pcomLigoLabelTable with bit 0 corresponding to if index 1. Bits set to 1 indicate the labels which are used by the LigoSubtype.” ::= { pcomLigoSubtypeEntry 3 }pcomLigoSubtypeFlavor OBJECT−TYPE SYNTAX INTEGER { fddiRoot−Primary(1), −− A and B on the frontpanel fddiRoot−Secondary(2), fddiNonroot(3), −− SAC fddiTrunk−A−Primary(4), −− A is on backplane fddiTrunk−A−Secondary(5), fddiTrunk−B−Primary(6), −− B is on backplane fddiTrunk−B−Secondary(7), fddiTrunk−AB−Primary(8), −− A and B are on backplane fddiTrunk−AB−Secondary(9), fddiStump−Primary(10), fddiStump−Secondary(11), ethernet−front(12), ethernet−back(13), fddiNonroot−M(14), fddiNonroot−S(15), fddiNonroot−SM(16) } ACCESS read−only STATUS mandatory DESCRIPTION ”A building block’s type.” ::= { pcomLigoSubtypeEntry 4 }pcomLigoLabelNumEntries OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The number of entries in the pcomLigo label table.” ::= { pcomLigo 5 }pcomLigoLabelTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomLigoLabelEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of Labels (for ports).” ::= { pcomLigo 6 }pcomLigoLabelEntry OBJECT−TYPE SYNTAX PcomLigoLabelEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”An entry containing objects which describe the label of the port affected by the LIGO this module supports.” INDEX { pcomLigoLabelIndex } ::= { pcomLigoLabelTable 1 }PcomLigoLabelEntry ::= SEQUENCE { pcomLigoLabelIndex INTEGER, pcomLigoLabelString DisplayString }pcomLigoLabelIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each Label. The value of this object ranges between 1 and n where n is the total number of Labels supported by the device.” ::= { pcomLigoLabelEntry 1 }pcomLigoLabelString OBJECT−TYPE SYNTAX DisplayString (SIZE (0..32))


A1−7546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ACCESS read−only STATUS mandatory DESCRIPTION ”A textual description of the port number associated with a LIGO. If the device is bridge then bridge port numbers are used. If the device is a wiring concentrator then concentrator port numbers are used.” ::= { pcomLigoLabelEntry 2 }−−−− The pcomCon Group.−−−− This group allows the assignment of front panel connectors, −− docking station connectors, internal thinwire, and MACs to internal LANs.−−−− The front panel connectors, docking station connectors, internal −− thinwire, and MACs are described in the pcomConTable. The internal −− LANs are described in the pcomConIntLanSetTable. The assignments of −− the these are described in pcomBezConAssignTable.−−−− +=====+ +====+ +=====+ Front panel and docking station−− | Con | | TW | | MAC | connectors, internal thinwire,−− +=====+ +====+ +=====+ and MACs are described in the−− \ | / pcomConTable.−− \ | / −− \ | /−− \ | /−− ._______________________. Assignment of connectors, −− | pcomConAssignTable | internal thinwire, and/or MACs−− ‘_______________________’ to internal LANs are made in−− | . . . | pcomConAssignTable.−− | . . . |−− _____+__}__}__}__)___ −− ........+..}..}..)... Internal LANs, are described−− ...........+..}..)... in the pcomConIntLanTable.−− ..............+..)...−− _________________+___−− −−pcomConTotalConfigChanges OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The total number of configuration changes since power up.” ::= { pcomCon 1 }−−−−−− The pcomConTable.−−−− ._________.____________._______._________._______._______.__________.−− | Index | Technology | Class | GroupId | Group | Label | Subtype |−− | | | | | Set | | Selected |−− |_________|____________|_______|_________|_______|_______|__________|−−−−−−−− This table describes the connectors (both front panel and docking −− station), MACs, and internal thinwires.−−−− Technology − The technology type, such as Ethernet.−−−− Class − Indicates whether the entry represents connector, internal −− thinwire or MAC.−−−− GroupId − describes which connectors or MACs move together when −− assigned to an internal LAN.−−−− Group Set − The Group IDs a connector may join.−−−− Label − A string containing the connector label (on either the −− front bezel or docking station).−−−− Subtype Selected − describes which ”flavor” of connector, internal−− thinwire, or MAC chosen.−−−−−− Bit strings:−− Bit strings are fixed size OCTET STRINGS. Bit numbering is in


A1−76 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− Big Endian format; with the most significant bits first. For−− example, a 8 octet bit string has the form:−−−− octet 1 bits 63−62−61−60−59−58−57−56−− octet 2 bits 55−54−53−52−51−50−49−48−−−− .............. etc ...............−−−− octet 8 bits 7−6−5−4−3−2−1−0−−−−−−pcomConNumEntries OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The number of entries in the Connector table.” ::= { pcomCon 2 }pcomConTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomConEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of front bezel and docking station connectors, internal thinwires, and MACs on a line card.” ::= { pcomCon 3 }pcomConEntry OBJECT−TYPE SYNTAX PcomConEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A connector entry contains objects which describe a front bezel connector, docking station connector, internal thinwire, or MAC.” INDEX { pcomConIndex } ::= { pcomConTable 1 }PcomConEntry ::= SEQUENCE { pcomConIndex INTEGER, pcomConTech INTEGER, pcomConClass INTEGER, pcomConGroupId INTEGER, pcomConGroupSet OCTET STRING, pcomConLabel DisplayString, pcomConSubtypeSelect INTEGER }pcomConIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each front bezel connector, docking station connector, internal thinwire, or MAC. The value of this object ranges between 1 and n where n is the total number of front bezel connectors, docking station connectors, internal thinwires, and MACs supported by the device.” ::= { pcomConEntry 1 }pcomConTech OBJECT−TYPE SYNTAX INTEGER { ethernet(1) } ACCESS read−only STATUS mandatory DESCRIPTION ”A front bezel connector, docking station connector, internal thinwire, or MAC technology type.” ::= { pcomConEntry 2 }pcomConClass OBJECT−TYPE SYNTAX INTEGER { bezcon(1), −− Front bezel connector. extcon(2), −− External docking station con. interthinwire(3), −− Internal thinwire. mac(4) −− MAC. } ACCESS read−only STATUS mandatory DESCRIPTION ”An entry’s class. This indicates whether a entry is a front


A1−7746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

bezel connector, docking station connector, internal thinwire, or MAC.” ::= { pcomConEntry 3 }pcomConGroupId OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−write STATUS mandatory DESCRIPTION ”The identifier of a connector, internal thinwire, and/or MAC group that are only assignable together to an internal LAN. In other words if you assign one of these connectors you assign them all.” ::= { pcomConEntry 4 }pcomConGroupSet OBJECT−TYPE SYNTAX OCTET STRING (SIZE (8)) ACCESS read−only STATUS mandatory DESCRIPTION ”This object specifies the group Ids that a connector, internal thinwire, or MAC can join. It is a bit map of pcomConTable Group Ids with bit 1 corresponding to pcomConGroupId 1. Bits set to one indicate the groups that connector, internal thinwire, or MAC can join.” ::= { pcomConEntry 5 }pcomConLabel OBJECT−TYPE SYNTAX DisplayString (SIZE (0..32)) ACCESS read−only STATUS mandatory DESCRIPTION ”Text that contains the connector label on either the front bezel or docking station. If it is an internal thinwire or MAC this text describes the function. This string may change when the Subtype Selected changes.” ::= { pcomConEntry 6 }pcomConSubtypeSelect OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−write STATUS mandatory DESCRIPTION ”The pcomConSubtypeIndex points into the pcomConSubtypeTable which describes the specific media type a connector, internal thinwire, or MAC that is selected to support. The value of this object ranges between 0 and n where n is the total number of backplane subtypes described by the pcomConSubtypeTable. A value of 0 indicates that no subtype has been selected. This object in non−volatile.” ::= { pcomConEntry 7 }−− +−−−− The pcomConSubtypeTable.−−−− .___________.___________.______________.−− | Index | ConSet | Flavor |−− |___________|___________|______________|−−−− This table lists all the connector, internal thinwire and MAC subtypes −− supported by the line card.−−−− ConSet − indicates which connectors, internal thinwires and MACs, −− in the pcomConTable, that supports this set of Flavor(s)−−−− Flavor − A (or the only) possible media type for this connector.−−pcomConSubtypeNumEntries OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”The number of entries in the connector subtype table.” ::= { pcomCon 4 }pcomConSubtypeTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomConSubtypeEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of connector, internal thinwire, and MAC subtypes supported by a line card.” ::= { pcomCon 5 }


A1−78 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

pcomConSubtypeEntry OBJECT−TYPE SYNTAX PcomConSubtypeEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A backplane subtype entry containing objects which describe the subtypes supported by connectors.” INDEX { pcomConSubtypeIndex } ::= { pcomConSubtypeTable 1 }PcomConSubtypeEntry::= SEQUENCE { pcomConSubtypeIndex INTEGER, pcomConSubtypeConSet OCTET STRING, pcomConSubtypeFlavor INTEGER }pcomConSubtypeIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each Flavor supported by a the set of connectors indicated in pcomConSubtypeConSet. The value of this object ranges between 1 and n, where n is the total number of connector subtypes supported by a module.” ::= { pcomConSubtypeEntry 1 }pcomConSubtypeConSet OBJECT−TYPE SYNTAX OCTET STRING (SIZE (8)) ACCESS read−only STATUS mandatory DESCRIPTION ”This object specifies the connect indices, in the pcomConTable, which can support the specified pcomConSubtypeFlavor.” ::= { pcomConSubtypeEntry 2 }pcomConSubtypeFlavor OBJECT−TYPE SYNTAX INTEGER { default(1), −− Used when only one flavor exists thinwire(2), aui(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”The specific media type a connector supports.” ::= { pcomConSubtypeEntry 3 }−− −− The pcomConIntLanTable.−−−− ._________.___________.________.−− | Index | GroupId | Name |−− | | Mask | |−− |_________|___________|________|−−−− This table describes the internal LAN available in this module and−− which connector internal thinwire, MAC group can be assigned to the LAN−−−−−− GroupIdMask − This bit mask indicates which groups in the −− pcomConTable can be assigned to this internal LAN−−−− Name − A name given to an internal LAN by a management station−−−−−−−− Bit strings are fixed size OCTET STRINGS. Bit numbering is in−− Big Endian format; with the most significant bits first. For−− example, a 8 octet bit string has the form:−−−− octet 1 bits 63−62−61−60−59−58−57−56−− octet 2 bits 55−54−53−52−51−50−49−48−−−− ............. etc ............−−−− octet 8 bits 7−6−5−4−3−2−1−0−−−− −pcomConIntLanNumEntries OBJECT−TYPE SYNTAX INTEGER (0..65535) ACCESS read−only


A1−7946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

STATUS mandatory DESCRIPTION ”The number of entries in the internal LAN table.” ::= { pcomCon 6 }pcomConIntLanTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomConIntLanEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of internal LANs in a line card. Each line card has a pcomConIntLanTable containing one entry for each of its internal LANs.” ::= { pcomCon 7 }pcomConIntLanEntry OBJECT−TYPE SYNTAX PcomConIntLanEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”An internal LAN entry containing objects which describe a internal LAN.” INDEX { pcomConIntLanIndex} ::= { pcomConIntLanTable 1 }PcomConIntLanEntry ::= SEQUENCE { pcomConIntLanIndex INTEGER, pcomConIntLanGroupIdMask OCTET STRING, pcomConIntLanName DisplayString }pcomConIntLanIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−only STATUS mandatory DESCRIPTION ”A unique value for each internal LAN.” ::= { pcomConIntLanEntry 1 }pcomConIntLanGroupIdMask OBJECT−TYPE SYNTAX OCTET STRING (SIZE (8)) ACCESS read−only STATUS mandatory DESCRIPTION ”This object specifies the group Ids of connectors, internal thinwire, and MACs that can be connected to this internal LAN. It is a bit map of pcomConTable Group Ids with bit 1 corresponding to pcomConGroupId 1. Bits set to one indicate the groups of connector, internal thinwire, and MACs which can access this internal LAN.” ::= { pcomConIntLanEntry 2 }pcomConIntLanName OBJECT−TYPE SYNTAX DisplayString (SIZE (0..32)) ACCESS read−write STATUS mandatory DESCRIPTION ”Text that contains a name given to an internal LAN. The default value is a zero length string.” ::= { pcomConIntLanEntry 3 }−−−−−− The pcomConAssignTable.−−−− ._______.__________._________._____________.−− | Index | ConGroup | IntLan | EntryStatus |−− |_______|__________|_________|_____________|−−−−−− The pcomConAssignTable is used to create and remove connector, internal−− thinwire, MAC assignments to internal LAN assignments.−−−− ConGroup − Indicates which group of connectors, internal thinwires and/or −− MACs are assigned to an internal LAN−−−− IntLan − Indicates the internal that is assigned to the connector,−− internal thinwire, and MAC group.−−−− EntryStatus − the usual−−−− −pcomConAssignNumEntries OBJECT−TYPE SYNTAX INTEGER (0..65535)


A1−80 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ACCESS read−only STATUS mandatory DESCRIPTION ”The number of entries in the connector assignment table.” ::= { pcomCon 8 }pcomConAssignTable OBJECT−TYPE SYNTAX SEQUENCE OF PcomConAssignEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of connector, internal tw, and MAC groups to internal LAN assignments of a line card. The creation of a table entry, creates a connection of a front connector, MAC, or internal thinwire group to an internal LAN.” ::= { pcomCon 9 }pcomConAssignEntry OBJECT−TYPE SYNTAX PcomConAssignEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A connector group assignment entry contains objects which describe a line card’s connections of connectors, internal thinwires, and MACs to internal LANs.” INDEX { pcomConAssignIndex } ::= { pcomConAssignTable 1 }PcomConAssignEntry ::= SEQUENCE { pcomConAssignIndex INTEGER, pcomConAssignConGroup INTEGER, pcomConAssignIntLan INTEGER, pcomConAssignEntryStatus INTEGER }pcomConAssignIndex OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−write STATUS mandatory DESCRIPTION ”A unique value for each connector group assignment. This object in non−volatile.” ::= { pcomConAssignEntry 1 }pcomConAssignConGroup OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−write STATUS mandatory DESCRIPTION ”Specifies the id of the connector group in the pcomConTable for which the assignment applies. Together with pcomConAssignIntLan, this defines a group of connectors to LAN assignment. This object in non−volatile.” ::= { pcomConAssignEntry 2 }pcomConAssignIntLan OBJECT−TYPE SYNTAX INTEGER (1..65535) ACCESS read−write STATUS mandatory DESCRIPTION ”Specifies the index of the internal LAN described in the pcomConIntLanTable for which the assignment applies. Together with pcomConAssignConGroup, this defines a connector to LAN assignment. This object in non−volatile.” ::= { pcomConAssignEntry 3 }pcomConAssignEntryStatus OBJECT−TYPE SYNTAX INTEGER { valid(1), createRequest(2), underCreation(3), invalid(4) } ACCESS read−write STATUS mandatory DESCRIPTION ”The status of a table entry. This object in non−volatile.” ::= { pcomConAssignEntry 4 }−−−− The pcom90mgt Group.−−−− This group allows for the set up of DEChub90 management agents. This group


A1−8146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

−− is optional.−−pcom90mgtBackplaneHubMaster OBJECT−TYPE SYNTAX INTEGER { disable(1), enable(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”The desired state of the DEChub 90 manager’s hub mastership (i.e. it’s ability to directly manage repeaters, terminal servers and bridges and discover other modules which reside in the same hub as the agent). This value is retained in non−volatile storage. Its default value is

disable(1).” ::= { pcom90mgt 1 }pcom90mgtBackplaneHubMasterState OBJECT−TYPE SYNTAX INTEGER { disabled(1), enabled(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”Indicates whether the DEChub 90 manager is managing the hub (i.e.

capable of directly managing repeaters, terminal servers and bridges and discovering other modules). Its default value is disabled(1).” ::= { pcom90mgt 2 }pcom90mgtBackplaneConfig OBJECT−TYPE SYNTAX INTEGER { notConfigured(1),

standAlone(2), singleDEChub90(3), pairDEChub90(4), decStack90(5) } ACCESS read−write STATUS mandatory DESCRIPTION ”Indicates whether the DEChub 90 manager is managing the a single

DEChub 90, a pair of DEChub 90’s, a DECstack 90 or is just standalone. If this is notConfigured(1) or standAlone(2), then the DEChub

90 manager will consider its pcom90mgtBackplaneHubMasterState as disabled(1). This value is retained in non−volatile storage. It’s default value is notConfigured(1).

NOTE: A successful set to this object should be followed by a reset to current settings.” ::= { pcom90mgt 3 }−− ===========================================================================−− ======================= E n d o f M I B ============================−− =========================================================================== END


A1−82 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

10.4. DIGITAL SERVER SYSTEM MIB DEFINITION

−− Digital Server System MIB version V1.0 − svrsys.mib−−−− Description:−− This Digital−specific MIB extension describes a management−− interface to system information not defined by standard MIBs,−− and/or unique to Digital Equipment Corporation Alpha and Intel−− Server systems.−−SVRSYS−MIB DEFINITIONS ::= BEGINIMPORTS mgmt, enterprises, NetworkAddress, IpAddress, Counter, Gauge, TimeTicks FROM RFC1155−SMI OBJECT−TYPE FROM RFC−1212 DisplayString FROM RFC1213−MIB; −− DEC−MIB { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 36 } −− EMA−MIB { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 36 2 } dec OBJECT IDENTIFIER ::= { enterprises 36 } ema OBJECT IDENTIFIER ::= { dec 2 } −− textual conventions for typesKBytes ::= INTEGERBusTypes ::= INTEGER { unknown(1) , other(2) , systemBus(3) , isa(4) , eisa(5) , mca(6) , turbochannel(7) , pci(8) , vme(9) , nuBus(10) , pcmcia(11) , cBus(12) , mpi(13) , mpsa(14) , usb(15) }SystemStatus ::= INTEGER { unknown(1), ok(2) , warning(3) , failed(4) }−− This Octet String is presented least−significant byte first.MemoryAddress ::= OCTET STRING (SIZE (8))ThermUnits ::= INTEGER { unknown(1) , other(2) , degreesF(3) , degreesC(4) , tempRelative(5) }PowerUnits ::= INTEGER { unknown(1) , other(2) , milliVoltsDC(3) , milliVoltsAC(4) , voltsDC(5) , voltsAC(6) , milliAmpsDC(7) , milliAmpsAC(8) , ampsDC(9) , ampsAC(10) , relative(11) }Boolean ::= INTEGER { true(1) , false(2) }


A1−8346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

−− Digital MIB extensions for base system configuration & state information−− environmental state information−−mib−extensions−1 OBJECT IDENTIFIER ::= { ema 18 }svrSystem OBJECT IDENTIFIER ::= { mib−extensions−1 22 }svrBaseSystem OBJECT IDENTIFIER ::= { svrSystem 1 } −− groups in svrsyssvrSysMibInfo OBJECT IDENTIFIER ::= { svrBaseSystem 1 }svrBaseSysDescr OBJECT IDENTIFIER ::= { svrBaseSystem 2 }svrProcessors OBJECT IDENTIFIER ::= { svrBaseSystem 3 }svrMemory OBJECT IDENTIFIER ::= { svrBaseSystem 4 }svrBuses OBJECT IDENTIFIER ::= { svrBaseSystem 5 }svrDevices OBJECT IDENTIFIER ::= { svrBaseSystem 6 }svrConsoleKeyboard OBJECT IDENTIFIER ::= { svrDevices 4 }svrConsoleDisplay OBJECT IDENTIFIER ::= { svrDevices 5 }svrConsolePointDevice OBJECT IDENTIFIER ::= { svrDevices 6 }svrPhysicalConfiguration OBJECT IDENTIFIER ::= { svrBaseSystem 7 }svrEnvironment OBJECT IDENTIFIER ::= { svrBaseSystem 8 }svrThermalSystem OBJECT IDENTIFIER ::= { svrEnvironment 1 }svrCoolingSystem OBJECT IDENTIFIER ::= { svrEnvironment 2 }svrPowerSystem OBJECT IDENTIFIER ::= { svrEnvironment 3 }−− −− svrSysMibInfo−−svrSysMibMajorRev OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The Major Revision of this implementation of the svrSystem MIB. Will be 1.” ::= { svrSysMibInfo 1 }svrSysMibMinorRev OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The minor rev of this implementation of the svrSystem MIB. Will be 0.” ::= { svrSysMibInfo 2 }−− −− svrBaseSysDescr−− −− Description of core system configuration & state−− MandatorysvrSystemFamily OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , x86(3) , alpha(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”Major system family; i.e. Alpha or Intel or Other.” ::= { svrBaseSysDescr 1 }svrSystemModel OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Qualify SystemFamily with model, e.g. AlphaServer 2100” ::= { svrBaseSysDescr 2 }svrSystemDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”For consistency with previous versions of MIB, very general text description of system type. Starts with Digital (Intel or Alpha) Server... plus any other descriptive text.” ::= { svrBaseSysDescr 3 }svrSystemBoardFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index of the Field Replaceable Unit (FRU) in the FRU table


A1−84 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

describing the serial # and other asset info of this board. 0 if unknown.” ::= { svrBaseSysDescr 4 }svrSystemOCPDisplay OBJECT−TYPE SYNTAX DisplayString ACCESS read−write STATUS mandatory DESCRIPTION ”The content of the operator control panel (OCP). Null if unknown. Writeable on some systems.” ::= { svrBaseSysDescr 5 }svrSystemBootedOS OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , windowsNT(3) , netWare(4) , scoUnix(5) , digitalUnix(6) , openVms(7) , windows(8) } ACCESS read−only STATUS mandatory DESCRIPTION ”Current booted operating system.” ::= { svrBaseSysDescr 6 }svrSystemBootedOSVersion OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Version of the OS that’s booted on the system.” ::= { svrBaseSysDescr 7 }svrSystemShutdownReason OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The possible reason for the system shutdown.” ::= { svrBaseSysDescr 8 }svrSystemRemoteMgrNum OBJECT−TYPE SYNTAX DisplayString ACCESS read−write STATUS mandatory DESCRIPTION ”A phone number entry for a remote manager.” ::= { svrBaseSysDescr 9 }svrFirmwareTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrFirmwareEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of information about the firmware, or firmwares, that may be present on this system. It may include SRM & ARC console firmware, optionally Fail Safe Loader. On Intel−family systems, will describe the System BIOS. May also include second levels, such as PALcode and BIOS emulator versions, if they are accessible to the software.” ::= { svrBaseSysDescr 10 }svrFirmwareEntry OBJECT−TYPE SYNTAX SvrFirmwareEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry represents a single instance of firmware in the system.” INDEX { svrFirmwareIndex } ::= { svrFirmwareTable 1 }SvrFirmwareEntry ::= SEQUENCE { svrFirmwareIndex INTEGER, svrFirmwareDescr DisplayString, svrFirmwareRev


A1−8546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

DisplayString }svrFirmwareIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Locally−unique index for this entry.” ::= { svrFirmwareEntry 1 }svrFirmwareDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”e.g. SRM console, ARC console, System BIOS, etc.” ::= { svrFirmwareEntry 2 }svrFirmwareRev OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”A version number possibly of the form Vx.y or Vx.y−z.” ::= { svrFirmwareEntry 3 }svrFwSymbolTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrFwSymbolEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of soft switches and symbols maintained by the firmware. May be operating system and/or option−specific and will certainly be system−specific. This list is intended to be easily extensible and support arbitrary datatypes. It includes such switches as powerup options, default dump device, etc. Note − the string comparision for svrFwSymbolName is case insensitive.” ::= { svrBaseSysDescr 11 }svrFwSymbolEntry OBJECT−TYPE SYNTAX SvrFwSymbolEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ” Each entry represents one variable or symbol maintained by or stored by some instance of firmware in the system.” INDEX { svrFwSymbolName } ::= { svrFwSymbolTable 1 }SvrFwSymbolEntry ::= SEQUENCE { svrFwSymbolName DisplayString, svrFwSymbolValue OCTET STRING }svrFwSymbolName OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The symbol name as visible at the console.” ::= { svrFwSymbolEntry 1 }svrFwSymbolValue OBJECT−TYPE SYNTAX OCTET STRING ACCESS read−only STATUS mandatory DESCRIPTION ”The symbol value. Null if none or unknown.” ::= { svrFwSymbolEntry 2 }−− −− svrProcessors−− −− Description of system processor configuration and utilization −− information. Mandatory.−−svrCpuPollInterval OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory


A1−86 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

DESCRIPTION ”In seconds, interval between polls for utilization. Values less than svrCpuMinPollInterval are erroneous except for 0, which disables polling.” ::= { svrProcessors 1 }svrCpuMinPollInterval OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”In seconds, minimum allowable time between polls for this implementation. Must be greater than 0. ” ::= { svrProcessors 2 }svrCpuTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrCpuEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of central processors on this system and their base configuration data. This is an extension to the hrDeviceTable of the Host Resources MIB; RFC1514. The cache and utilization data are conceptual dimensions added to this table.” ::= { svrProcessors 3 }svrCpuEntry OBJECT−TYPE SYNTAX SvrCpuEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry represents one distinct processor in the system.” INDEX { svrCpuIndex } ::= { svrCpuTable 1 }SvrCpuEntry ::= SEQUENCE { svrCpuIndex INTEGER, svrCpuType INTEGER, svrCpuManufacturer DisplayString, svrCpuRevision DisplayString, svrCpuFruIndex INTEGER, svrCpuSpeed INTEGER, svrCpuUtilCurrent INTEGER, svrCpuAvgNextIndex INTEGER, svrCpuHrIndex INTEGER }svrCpuIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Locally−unique index value for this CPU entry.” ::= { svrCpuEntry 1 }svrCpuType OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , i386(3) , i486(4) , pentium(5) , pentiumPro(6) , alpha21064(7) , alpha21164(8) } ACCESS read−only STATUS mandatory DESCRIPTION ”The processor type.” ::= { svrCpuEntry 2 }


A1−8746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

svrCpuManufacturer OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The manufacturer of this processor. ” ::= { svrCpuEntry 3 }svrCpuRevision OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Version information in processor−specific format.” ::= { svrCpuEntry 4 }svrCpuFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index of the FRU entry in the FRU table describing the asset info of the component containing this processor. 0 if unknown.” ::= { svrCpuEntry 5 }svrCpuSpeed OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”in MHz, 0 if unknown” ::= { svrCpuEntry 6 }svrCpuUtilCurrent OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Percentage of cpu utilization over the last svrCpuPollInterval.” ::= { svrCpuEntry 7 }svrCpuAvgNextIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Next available index for creating a cpu utilization averaging interval.” ::= { svrCpuEntry 8 }svrCpuHrIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Reference to index of hrDeviceEntry for this cpu in Host Resources MIB. 0 if unknown.” ::= { svrCpuEntry 9 }svrCpuAvgTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrCpuAvgEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Extension to svrCpuTable, this table contains utilization averages maintained over a set of manager−settable intervals.” ::= { svrProcessors 4 }svrCpuAvgEntry OBJECT−TYPE SYNTAX SvrCpuAvgEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Entry describes a CPU, an interval over which CPU utilization is averaged, and average utilization measured at the last interval” INDEX { svrCpuIndex, svrCpuAvgIndex } ::= { svrCpuAvgTable 1 }SvrCpuAvgEntry ::= SEQUENCE { svrCpuAvgIndex INTEGER, svrCpuAvgInterval


A1−88 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

INTEGER, svrCpuAvgStatus INTEGER, svrCpuAvgPersist Boolean, svrCpuAvgValue INTEGER }svrCpuAvgIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Local index. May have implementation max.” ::= { svrCpuAvgEntry 1 }svrCpuAvgInterval OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”In minutes, averaging interval for this entry.” ::= { svrCpuAvgEntry 2 }svrCpuAvgStatus OBJECT−TYPE SYNTAX INTEGER { underCreation(1) , rowInvalid(2) , rowEnabled(3) , rowDisabled(4) , rowError(5) } ACCESS read−write STATUS mandatory DESCRIPTION ” This variable describes the status of the row. When the row is created with the initial set, svrCpuAvgStatus must be set to underCreation. When the management console has completed row setup, it should set this variable to rowEnabled. Variables in the row may only be written if svrCpuAvgStatus is in the initial underCreation state or has been set to rowDisabled. To delete the row, set the status to rowInvalid. It is a local implementation matter whether the row is actually removed from the table. Management applications must be prepared to ignore rows with a status of rowInvalid. Errors in cpu utilization polling and averaging that are determined by local implementation to be non−correctable will cause a row status change to rowError.” ::= { svrCpuAvgEntry 3 }svrCpuAvgPersist OBJECT−TYPE SYNTAX Boolean ACCESS read−write STATUS mandatory DESCRIPTION ”True if this row is to persist across agent restarts.” ::= { svrCpuAvgEntry 4 }svrCpuAvgValue OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Averaged load over the last measured interval. First set to instantaneous utilization.” ::= { svrCpuAvgEntry 5 }svrCpuCacheTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrCpuCacheEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Extension of svrCpuTable describing the caches used by each of the system processors.” ::= { svrProcessors 5 }svrCpuCacheEntry OBJECT−TYPE SYNTAX SvrCpuCacheEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”An entry describes a single cache for a single cpu.” INDEX { svrCpuIndex,


A1−8946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

svrCpuCacheIndex } ::= { svrCpuCacheTable 1 }SvrCpuCacheEntry ::= SEQUENCE { svrCpuCacheIndex INTEGER, svrCpuCacheLevel INTEGER, svrCpuCacheType INTEGER, svrCpuCacheSize KBytes, svrCpuCacheSpeed INTEGER, svrCpuCacheStatus INTEGER }svrCpuCacheIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Local index value.” ::= { svrCpuCacheEntry 1 }svrCpuCacheLevel OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , primary(3) , secondary(4) , tertiary(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”Level 1 or Level 2 or Level 3 cache. Or other or unknown.” ::= { svrCpuCacheEntry 2 }svrCpuCacheType OBJECT−TYPE SYNTAX INTEGER { internal(1) , external(2) , internalI(3) , internalD(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”Type of cache − Internal, external, internal instruction or internal data.” ::= { svrCpuCacheEntry 3 }svrCpuCacheSize OBJECT−TYPE SYNTAX KBytes ACCESS read−only STATUS mandatory DESCRIPTION ”Cache size in KBytes. ” ::= { svrCpuCacheEntry 4 }svrCpuCacheSpeed OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”In nanoseconds, cache speed. 0 if unknown.” ::= { svrCpuCacheEntry 5 }svrCpuCacheStatus OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , enabled(3) , disabled(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”Current status of the cache − enabled, disabled, other or unknown.” ::= { svrCpuCacheEntry 6 }


A1−90 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− −− svrMemory−− −− Description of memory configuration. Mandatory.−−svrPhysicalMemorySize OBJECT−TYPE SYNTAX KBytes ACCESS read−only STATUS mandatory DESCRIPTION ”In KBytes, total amount of physical memory as seen by the OS.” ::= { svrMemory 1 }svrPhysicalMemoryFree OBJECT−TYPE SYNTAX KBytes ACCESS read−only STATUS mandatory DESCRIPTION ”In KBytes, amount of free physical memory.” ::= { svrMemory 2 }svrPagingMemorySize OBJECT−TYPE SYNTAX KBytes ACCESS read−only STATUS mandatory DESCRIPTION ”In KBytes, total virtual memory available from the OS.” ::= { svrMemory 3 }svrPagingMemoryFree OBJECT−TYPE SYNTAX KBytes ACCESS read−only STATUS mandatory DESCRIPTION ”In KBytes, available paging memory.” ::= { svrMemory 4 }svrMemComponentTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrMemComponentEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table describing hardware configuration of memory” ::= { svrMemory 5 }svrMemComponentEntry OBJECT−TYPE SYNTAX SvrMemComponentEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Entries describe physical memory hardware component.” INDEX { svrMemIndex } ::= { svrMemComponentTable 1 }SvrMemComponentEntry ::= SEQUENCE { svrMemIndex INTEGER, svrMemType INTEGER, svrMemSize KBytes, svrMemStartAddress MemoryAddress, svrMemPhysLocation INTEGER, svrMemEdcType INTEGER, svrMemElementSlots INTEGER, svrMemElementSlotsUsed INTEGER, svrMemInterleafFactor INTEGER, svrMemInterleafElement INTEGER, svrMemFruIndex INTEGER }svrMemIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only


A1−9146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

STATUS optional DESCRIPTION ”Unique index for this entry” ::= { svrMemComponentEntry 1 }svrMemType OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , systemMemory(3) , shadowMemory(4) , videoMemory(5) , flashMemory(6) , nvram(7) , expansionRam(8) , expansionROM(9) } ACCESS read−only STATUS optional DESCRIPTION ”Type of memory may be system, shadow, bios, video, ....” ::= { svrMemComponentEntry 2 }svrMemSize OBJECT−TYPE SYNTAX KBytes ACCESS read−only STATUS optional DESCRIPTION ”In KBytes, length of memory range” ::= { svrMemComponentEntry 3 }svrMemStartAddress OBJECT−TYPE SYNTAX MemoryAddress ACCESS read−only STATUS optional DESCRIPTION ”64−bit starting address of memory contained on or controlled by this component.” ::= { svrMemComponentEntry 4 }svrMemPhysLocation OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , systemBoard(3) , memoryBoard(4) , processorBoard(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”Location of the memory.” ::= { svrMemComponentEntry 5 }svrMemEdcType OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , none(3) , parity(4) , singleBitECC(5) , multiBitECC(6) } ACCESS read−only STATUS mandatory DESCRIPTION ”Type of error detection & correction(EDC) provided for memory contained on or controlled by this component.” ::= { svrMemComponentEntry 6 }svrMemElementSlots OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Total number of slots for removeable memory elements (simms, dimms, etc). 0 if unknown.” ::= { svrMemComponentEntry 7 }svrMemElementSlotsUsed OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Total number of slots occupied by removable memory elements. 0 if


A1−92 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

unknown.” ::= { svrMemComponentEntry 8 }svrMemInterleafFactor OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Interleaving factor. 0 if unknown, 1 if none, 2 if 2−way, etc...” ::= { svrMemComponentEntry 9 }svrMemInterleafElement OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Which element this is in interleaving. 0 if non−interleaved.” ::= { svrMemComponentEntry 10 }svrMemFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Index of the FRU entry in the FRU table on which this memory resides, if known. 0 if unknown.” ::= { svrMemComponentEntry 11 }svrMemElementTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrMemElementEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”An extension to the svrMemComponentTable, this table describes the actual memory hardware elements. If the memory component does not lend itself to decomposition by element, there may be a generic element entry listed to hold the attributes.” ::= { svrMemory 6 }svrMemElementEntry OBJECT−TYPE SYNTAX SvrMemElementEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A chunk of memory which may be non−removable, a SIMM, a DIMM or some undefined piece.” INDEX { svrMemIndex, svrMemElementIndex } ::= { svrMemElementTable 1 }SvrMemElementEntry ::= SEQUENCE { svrMemElementIndex INTEGER, svrMemElementType INTEGER, svrMemElementSlotNo INTEGER, svrMemElementWidth INTEGER, svrMemElementDepth KBytes, svrMemElementSpeed INTEGER, svrMemElementStatus SystemStatus }svrMemElementIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A local index value.” ::= { svrMemElementEntry 1 }svrMemElementType OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , nonremoveable(3) , simm(4) , dimm(5) }


A1−9346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ACCESS read−only STATUS mandatory DESCRIPTION ”Whether non−removable, SIMM, DIMM, etc.” ::= { svrMemElementEntry 2 }svrMemElementSlotNo OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”If removeable, the slot number in which it resides. 0 if unknown.” ::= { svrMemElementEntry 3 }svrMemElementWidth OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”In bytes, width if known. 0 if unknown.” ::= { svrMemElementEntry 4 }svrMemElementDepth OBJECT−TYPE SYNTAX KBytes ACCESS read−only STATUS mandatory DESCRIPTION ”In KBytes, depth if known. 0 if unknown.” ::= { svrMemElementEntry 5 }svrMemElementSpeed OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”In nanoseconds, speed as used. May be less than maximum possible speed. 0 if unknown.” ::= { svrMemElementEntry 6 }svrMemElementStatus OBJECT−TYPE SYNTAX SystemStatus ACCESS read−only STATUS mandatory DESCRIPTION ”Current status of the element.” ::= { svrMemElementEntry 7 }−− −− svrBuses−− −− Bus & slot information, primarily for EISA and PCI today.−− Mandatory.−−svrBusCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of buses seen by the system.” ::= { svrBuses 1 }svrBusTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrBusEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry represents a bus as seen by the OS.” ::= { svrBuses 2 }svrBusEntry OBJECT−TYPE SYNTAX SvrBusEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Entry describing a single bus.” INDEX { svrBusIndex } ::= { svrBusTable 1 }SvrBusEntry ::= SEQUENCE { svrBusIndex INTEGER, svrBusType BusTypes, svrBusNumber


A1−94 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

INTEGER, svrBusSlotCount INTEGER }svrBusIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A locally−unique index value.” ::= { svrBusEntry 1 }svrBusType OBJECT−TYPE SYNTAX BusTypes ACCESS read−only STATUS mandatory DESCRIPTION ”Type of bus this represents.” ::= { svrBusEntry 2 }svrBusNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The bus number, unique among buses of this type” ::= { svrBusEntry 3 }svrBusSlotCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of physical slots on this bus. 0 if unknown.” ::= { svrBusEntry 4 }svrLogicalSlotTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrLogicalSlotEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table on logical bus slots. Indexed by busIndex & slot number. May be more logical slots than physical slots.” ::= { svrBuses 3 }svrLogicalSlotEntry OBJECT−TYPE SYNTAX SvrLogicalSlotEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Represents a slot as seen by OS. May not have associated physical slot.” INDEX { svrBusIndex, svrLogicalSlotNumber } ::= { svrLogicalSlotTable 1 }SvrLogicalSlotEntry ::= SEQUENCE { svrLogicalSlotNumber INTEGER, svrLogicalSlotDescr DisplayString, svrLogicalSlotDeviceID INTEGER, svrLogicalSlotVendor DisplayString, svrLogicalSlotRevision DisplayString, svrLogicalSlotFnCount INTEGER }svrLogicalSlotNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Unique logical slot number on a given bus.” ::= { svrLogicalSlotEntry 1 }svrLogicalSlotDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−write STATUS mandatory


A1−9546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

DESCRIPTION ”Device description derived from ID, or as set by mgt station.” ::= { svrLogicalSlotEntry 2 }svrLogicalSlotDeviceID OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Vendor−supplied ID of device.” ::= { svrLogicalSlotEntry 3 }svrLogicalSlotVendor OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Name of manufacturer derived from vendor ID, the vendor ID itself or null if unknown.” ::= { svrLogicalSlotEntry 4 }svrLogicalSlotRevision OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Vendor supplied major and minor revision of device in this slot.” ::= { svrLogicalSlotEntry 5 }svrLogicalSlotFnCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of functions for multi−function device. Usually 1 for PCI devices.” ::= { svrLogicalSlotEntry 6 }svrSlotFunctionTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrSlotFunctionEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”An extension to the logical slot table, describes the functions on the device. Often, there will be only 1.” ::= { svrBuses 4 }svrSlotFunctionEntry OBJECT−TYPE SYNTAX SvrSlotFunctionEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry describes a device function at this logical slot.” INDEX { svrBusIndex, svrLogicalSlotNumber, svrSlotFnIndex } ::= { svrSlotFunctionTable 1 }SvrSlotFunctionEntry ::= SEQUENCE { svrSlotFnIndex INTEGER, svrSlotFnDevType DisplayString, svrSlotFnRevision DisplayString }svrSlotFnIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A local index value.” ::= { svrSlotFunctionEntry 1 }svrSlotFnDevType OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Device type represented by this function. May be derived by table lookup of device id.” ::= { svrSlotFunctionEntry 2 }


A1−96 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

svrSlotFnRevision OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Revision of the device function.” ::= { svrSlotFunctionEntry 3 }−− −− svrDevices−− −− Peripheral device descriptions. This group contains extensions to the −− information available in the host hrDevices group−−svrDeviceCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of entries in svrDeviceTable” ::= { svrDevices 1 }svrSerialPortCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of entries in svrSerialPortTable” ::= { svrDevices 2 }svrParallelPortCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of entries in svrParallelPortTable” ::= { svrDevices 3 }−− −− svrConsoleKeyboard−−svrKeybdHrIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Index of the hrDeviceEntry in Host Resources MIB. 0 if unknown.” ::= { svrConsoleKeyboard 1 }svrKeybdDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Textual description provide by OS.” ::= { svrConsoleKeyboard 2 }−− −− svrConsoleDisplay−−svrVideoHrIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Index in Host Devices table. 0 if unknown.” ::= { svrConsoleDisplay 1 }svrVideoDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Text description supplied by OS” ::= { svrConsoleDisplay 2 }svrVideoXRes OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”X−axis resolution.” ::= { svrConsoleDisplay 3 }svrVideoYRes OBJECT−TYPE SYNTAX INTEGER ACCESS read−only


A1−9746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

STATUS mandatory DESCRIPTION ”Y−axis resolution.” ::= { svrConsoleDisplay 4 }svrVideoNumColor OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of colors (converted, if necessary, from bits−per−pixel).” ::= { svrConsoleDisplay 5 }svrVideoRefreshRate OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”In Hz, current refresh rate. 0 if unavailable, 1 if hardware default rate.” ::= { svrConsoleDisplay 6 }svrVideoScanMode OBJECT−TYPE SYNTAX INTEGER { unknown(1) , interlaced(2) , nonInterlaced(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”Whether or not this is interlaced, if we know.” ::= { svrConsoleDisplay 7 }svrVideoMemory OBJECT−TYPE SYNTAX KBytes ACCESS read−only STATUS mandatory DESCRIPTION ”Amount of video memory available or in use, in KBytes.” ::= { svrConsoleDisplay 8 }−− −− svrConsolePointDevice−− −− Description of console pointing device (generally, mouse)svrPointingHrIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Index in host devices table. 0 if unknown.” ::= { svrConsolePointDevice 1 }svrPointingDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Description provided by host OS.” ::= { svrConsolePointDevice 2 }svrNumButtons OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of buttons on this mouse.” ::= { svrConsolePointDevice 3 }svrSerialPortTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrSerialPortEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Serial port information.” ::= { svrDevices 7 }svrSerialPortEntry OBJECT−TYPE SYNTAX SvrSerialPortEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry describes a serial port in this system.” INDEX { svrSerialIndex


A1−98 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

} ::= { svrSerialPortTable 1 }SvrSerialPortEntry ::= SEQUENCE { svrSerialIndex INTEGER, svrSerialPortDescr DisplayString, svrSerialHrIndex INTEGER }svrSerialIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Locally−unique index value.” ::= { svrSerialPortEntry 1 }svrSerialPortDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Text description of port.” ::= { svrSerialPortEntry 2 }svrSerialHrIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The hrDeviceIndex value from the hrDeviceEntry in the Host Resources MIB describing this port. 0 if unknown.” ::= { svrSerialPortEntry 3 }svrParallelPortTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrParallelPortEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Parallel port information.” ::= { svrDevices 8 }svrParallelPortEntry OBJECT−TYPE SYNTAX SvrParallelPortEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry describes a parallel port in this system.” INDEX { svrParallelIndex } ::= { svrParallelPortTable 1 }SvrParallelPortEntry ::= SEQUENCE { svrParallelIndex INTEGER, svrParallelPortDescr DisplayString, svrParallelHrIndex INTEGER }svrParallelIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Locally−unique index value.” ::= { svrParallelPortEntry 1 }svrParallelPortDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Text description of port device as seen by OS.” ::= { svrParallelPortEntry 2 }svrParallelHrIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION


A1−9946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

”Reference to index of hrDeviceEntry for this port in Host Resources MIB. 0 if unknown.” ::= { svrParallelPortEntry 3 }svrDeviceTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrDeviceEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Device configuration or adapter device as seen by the Host OS.” ::= { svrDevices 9 }svrDeviceEntry OBJECT−TYPE SYNTAX SvrDeviceEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry represents one resource as seen by the Host OS.” INDEX { svrDevIndex } ::= { svrDeviceTable 1 }SvrDeviceEntry ::= SEQUENCE { svrDevIndex INTEGER, svrDevDescr DisplayString, svrDevBusInterfaceType BusTypes, svrDevBusNumber INTEGER, svrDevSlotNumber INTEGER, svrDevFruIndex INTEGER, svrDevCPUAffinity INTEGER, svrDevHrIndex INTEGER }svrDevIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Local unique integer value for this entry” ::= { svrDeviceEntry 1 }svrDevDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”String description of the device as seen by the OS.” ::= { svrDeviceEntry 2 }svrDevBusInterfaceType OBJECT−TYPE SYNTAX BusTypes ACCESS read−only STATUS mandatory DESCRIPTION ”Type of bus for this interface.” ::= { svrDeviceEntry 3 }svrDevBusNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index of bus on which this device resides (0=internal)” ::= { svrDeviceEntry 4 }svrDevSlotNumber OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The logical slot number where this device resides. 0 if unknown.” ::= { svrDeviceEntry 5 }svrDevFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory


A1−100 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

DESCRIPTION ”The index of the FRU entry in the FRU table that contains this device. 0 if unknown.” ::= { svrDeviceEntry 6 }svrDevCPUAffinity OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Bit map describing processors to which interrupts are dispatched. Use first IRQL entry if they are different. Bit position = cpu # starting from Least Significant Bit (LSB).” ::= { svrDeviceEntry 7 }svrDevHrIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Index of the device in the Host Resources MIB device table. 0 if unknown.” ::= { svrDeviceEntry 8 }svrDevInterruptTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrDevIntEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of interrupt configurations for this device. Extension to svrDeviceTable.” ::= { svrDevices 10 }svrDevIntEntry OBJECT−TYPE SYNTAX SvrDevIntEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry describes one interrupt for the device.” INDEX { svrDevIndex, svrDevIntIndex } ::= { svrDevInterruptTable 1 }SvrDevIntEntry ::= SEQUENCE { svrDevIntIndex INTEGER, svrDevIntLevel INTEGER, svrDevIntVector INTEGER, svrDevIntShared Boolean, svrDevIntTrigger INTEGER }svrDevIntIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Implementation−specific index of entry” ::= { svrDevIntEntry 1 }svrDevIntLevel OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”OS interrupt−level for which this device is configured. IRQL in Windows NT.” ::= { svrDevIntEntry 2 }svrDevIntVector OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Interrupt vector.” ::= { svrDevIntEntry 3 }svrDevIntShared OBJECT−TYPE SYNTAX Boolean ACCESS read−only


A1−10146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

STATUS mandatory DESCRIPTION ”True if interrupt is shared.” ::= { svrDevIntEntry 4 }svrDevIntTrigger OBJECT−TYPE SYNTAX INTEGER { level(1) , latch(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”Trigger type − level or edge” ::= { svrDevIntEntry 5 }svrDevMemTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrDevMemEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of memory configuration used by this adapter device. Extension to svrDeviceTable.” ::= { svrDevices 11 }svrDevMemEntry OBJECT−TYPE SYNTAX SvrDevMemEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A single memory address configuration for this device.” INDEX { svrDevIndex, svrDevMemIndex } ::= { svrDevMemTable 1 }SvrDevMemEntry ::= SEQUENCE { svrDevMemIndex INTEGER, svrDevMemAddress MemoryAddress, svrDevMemLength INTEGER, svrDevMemMapping INTEGER }svrDevMemIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Implementation−specific index value.” ::= { svrDevMemEntry 1 }svrDevMemAddress OBJECT−TYPE SYNTAX MemoryAddress ACCESS read−only STATUS mandatory DESCRIPTION ”Physical address of the start of the memory range.” ::= { svrDevMemEntry 2 }svrDevMemLength OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”In bytes, size of the memory range.” ::= { svrDevMemEntry 3 }svrDevMemMapping OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , memoryMapped(3) , ioSpaceMapped(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”Whether this is memory mapped or I/O mapped address space.” ::= { svrDevMemEntry 4 }


A1−102 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

svrDevDmaTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrDevDmaEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of DMA configurations for this device.” ::= { svrDevices 12 }svrDevDmaEntry OBJECT−TYPE SYNTAX SvrDevDmaEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry describes use of a DMA channel.” INDEX { svrDevIndex, svrDevDmaIndex } ::= { svrDevDmaTable 1 }SvrDevDmaEntry ::= SEQUENCE { svrDevDmaIndex INTEGER, svrDevDmaChannel INTEGER }svrDevDmaIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Implementation−specific index value” ::= { svrDevDmaEntry 2 }svrDevDmaChannel OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Channel on DMA controller” ::= { svrDevDmaEntry 3 }−− −− svrPhysicalConfiguration−− −− Description of the box. −−svrChassisType OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , desktop(3) , tower(4) , miniTower(5) , rackMount(6) , laptop(7) } ACCESS read−only STATUS mandatory DESCRIPTION ”A description of the type of box in which this system resides.” ::= { svrPhysicalConfiguration 1 }svrChassisFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index of the chassis FRU descriptor in the FRU table. 0 if unknown.” ::= { svrPhysicalConfiguration 2 }svrFruTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrFruEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of Field Replaceable Units of system, providing inventory and asset control information. This table is referenced from logical hardware descriptions elsewhere in the MIB.” ::= { svrPhysicalConfiguration 3 }


A1−10346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

svrFruEntry OBJECT−TYPE SYNTAX SvrFruEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry represents a Field Replaceable Unit (FRU) of hardware.” INDEX { svrFruIndex } ::= { svrFruTable 1 }SvrFruEntry ::= SEQUENCE { svrFruIndex INTEGER, svrFruType INTEGER, svrFruDescr DisplayString, svrFruVendor DisplayString, svrFruPartNumber DisplayString, svrFruRevision DisplayString, svrFruFirmwareRevision DisplayString, svrFruSerialNumber DisplayString, svrFruAssetNo DisplayString, svrFruClass INTEGER }svrFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A locally−unique index value.” ::= { svrFruEntry 1 }svrFruType OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , motherBoard(3) , processor(4) , memoryCard(5) , memoryModule(6) , peripheralDevice(7) , systemBusBridge(8) , powerSupply(9) , chassis(10) , fan(11) , ioCard(12) } ACCESS read−only STATUS mandatory DESCRIPTION ”General category of the type of FRU that this is.” ::= { svrFruEntry 2 }svrFruDescr OBJECT−TYPE SYNTAX DisplayString ACCESS read−write STATUS mandatory DESCRIPTION ”More detailed description of FRU type, if known.” ::= { svrFruEntry 3 }svrFruVendor OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Manufacturer name or ID.” ::= { svrFruEntry 4 }svrFruPartNumber OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory


A1−104 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

DESCRIPTION ”Number by which this unit is orderable.” ::= { svrFruEntry 5 }svrFruRevision OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”Version number of this unit. If artwork level is available, it will appear as ’Artwork: XXX’ following FRU version portion.” ::= { svrFruEntry 6 }svrFruFirmwareRevision OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The revision of the firmware, if any. Otherwise null.” ::= { svrFruEntry 7 }svrFruSerialNumber OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”The serial number of this unit’s instance.” ::= { svrFruEntry 8 }svrFruAssetNo OBJECT−TYPE SYNTAX DisplayString ACCESS read−write STATUS mandatory DESCRIPTION ”The asset number for unit.” ::= { svrFruEntry 9 }svrFruClass OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , currentBoardInSlot(3) , priorBoardInSlot(4) , parentBoard(5) , priorParentBoard(6) , priorParentSystem(7) } ACCESS read−only STATUS mandatory DESCRIPTION ”Represents the status category of the unit. ” ::= { svrFruEntry 10 }−− −− svrEnvironment−−−− −− svrThermalSystem−−svrThermalSensorCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of thermal sensors present and readable in this system. ” ::= { svrThermalSystem 1 }svrThermalSensorTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrThermalSensorEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of thermal sensors in the system. May be gauges or status indicators. Not present if svrThermalSensorCount = 0.” ::= { svrThermalSystem 2 }svrThermalSensorEntry OBJECT−TYPE SYNTAX SvrThermalSensorEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A single temperature gauge or status indicator.” INDEX { svrThSensorIndex } ::= { svrThermalSensorTable 1 }


A1−10546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

SvrThermalSensorEntry ::= SEQUENCE { svrThSensorIndex INTEGER, svrThSensorLocation DisplayString, svrThSensorReading INTEGER, svrThSensorReadingUnits ThermUnits, svrThSensorLowThresh INTEGER, svrThSensorHighThresh INTEGER, svrThSensorShutSoonThresh INTEGER, svrThSensorShutNowThresh INTEGER, svrThSensorThreshUnits ThermUnits, svrThSensorStatus INTEGER, svrThSensorFruIndex INTEGER }svrThSensorIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A locally−unique index value.” ::= { svrThermalSensorEntry 1 }svrThSensorLocation OBJECT−TYPE SYNTAX DisplayString ACCESS read−write STATUS mandatory DESCRIPTION ”May be system box, main CPU, etc. Null if unknown.” ::= { svrThermalSensorEntry 2 }svrThSensorReading OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The current value read by the sensor, in units described by svrThSensorReadingUnits.” ::= { svrThermalSensorEntry 3 }svrThSensorReadingUnits OBJECT−TYPE SYNTAX ThermUnits ACCESS read−only STATUS mandatory DESCRIPTION ”Whether this sensor reads degrees Fahrenheit, Celsius, or relative value. If no reading is available, value will be unknown.” ::= { svrThermalSensorEntry 4 }svrThSensorLowThresh OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Default value for low temperature threshold. Units are as described in svrThSensorThreshUnits.” ::= { svrThermalSensorEntry 5 }svrThSensorHighThresh OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Default value for high temperature threshold. Units are as described in svrThSensorThreshUnits.” ::= { svrThermalSensorEntry 6 }svrThSensorShutSoonThresh OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Default value for Shutdown Soon temperature threshold. Units are as


A1−106 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

described in svrThSensorThreshUnits.” ::= { svrThermalSensorEntry 7 }svrThSensorShutNowThresh OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Default value for Shutdown Now temperature threshold. Units are as described in svrThSensorThreshUnits.” ::= { svrThermalSensorEntry 8 }svrThSensorThreshUnits OBJECT−TYPE SYNTAX ThermUnits ACCESS read−only STATUS mandatory DESCRIPTION ”Represents how all the threshold values should be interpreted. If default thresholds not supported, value will be unknown.” ::= { svrThermalSensorEntry 9 }svrThSensorStatus OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , low(3) , lowWarning(4) , statusOk(5) , highWarning(6) , high(7) } ACCESS read−only STATUS mandatory DESCRIPTION ”Status value of the sensor. ” ::= { svrThermalSensorEntry 10 }svrThSensorFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Index to the FRU entry in the FRU table on which this sensor resides, if known. 0 if unknown.” ::= { svrThermalSensorEntry 11 }−− −− svrCoolingSystem−−svrFanCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Number of fans whose state is detectable. ” ::= { svrCoolingSystem 1 }svrFanTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrFanEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of fans in system. Not present if svrFanCount = 0.” ::= { svrCoolingSystem 2 }svrFanEntry OBJECT−TYPE SYNTAX SvrFanEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”One per detectable fan.” INDEX { svrFanIndex } ::= { svrFanTable 1 }SvrFanEntry ::= SEQUENCE { svrFanIndex INTEGER, svrFanLocation DisplayString, svrFanStatus INTEGER, svrFanBackup INTEGER,


A1−10746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

svrFanFruIndex INTEGER }svrFanIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A locally−unique index value.” ::= { svrFanEntry 1 }svrFanLocation OBJECT−TYPE SYNTAX DisplayString ACCESS read−write STATUS mandatory DESCRIPTION ”Location of the fan. Null if unknown.” ::= { svrFanEntry 2 }svrFanStatus OBJECT−TYPE SYNTAX INTEGER { unknown(1) , running(2) , backup(3) , failed(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”Current status of fan.” ::= { svrFanEntry 3 }svrFanBackup OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index of the fan for which this is backup. 0 if unknown or n/a.” ::= { svrFanEntry 4 }svrFanFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index of the FRU entry in the FRU table containing this fan, if known. 0 if unknown.” ::= { svrFanEntry 5 }−− −− svrPowerSystem−−svrPowerRedunEnable OBJECT−TYPE SYNTAX Boolean ACCESS read−only STATUS mandatory DESCRIPTION ”Is redunancy enabled in this power supply subsystem?” ::= { svrPowerSystem 1 }svrPowerSensorCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of detectable voltage sensors represented in svrVoltageSensorTable.” ::= { svrPowerSystem 2 }svrPowerSupplyCount OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of detectable power supplies reflected as entries in the svrPowerSupplyTable.” ::= { svrPowerSystem 3 }svrPowerSensorTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrPowerSensorEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of power supplies − voltage or current. Not present if svrPowerSensorCount = 0.” ::= { svrPowerSystem 4 }


A1−108 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

svrPowerSensorEntry OBJECT−TYPE SYNTAX SvrPowerSensorEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”One entry per detectable voltage or current sensor.” INDEX { svrPowerSensorIndex } ::= { svrPowerSensorTable 1 }SvrPowerSensorEntry ::= SEQUENCE { svrPowerSensorIndex INTEGER, svrPowerSensorLocation DisplayString, svrPowerSensorRating INTEGER, svrPowerSensorReading INTEGER, svrPowerSensorReadingUnits PowerUnits, svrPowerSensorNeedPwrThresh INTEGER, svrPowerSensorLowThresh INTEGER, svrPowerSensorHighThresh INTEGER, svrPowerSensorShutNowThresh INTEGER, svrPowerSensorThreshUnits PowerUnits, svrPowerSensorStatus INTEGER, svrPowerSensorFruIndex INTEGER }svrPowerSensorIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A locally−unique index value.” ::= { svrPowerSensorEntry 1 }svrPowerSensorLocation OBJECT−TYPE SYNTAX DisplayString ACCESS read−write STATUS mandatory DESCRIPTION ”Description of physical location in system if known. Null if unknown. ” ::= { svrPowerSensorEntry 2 }svrPowerSensorRating OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Nominal rating for this sensor, in units expressed by svrPowerSensorReadingUnits. If not supported, value will be unknown.” ::= { svrPowerSensorEntry 3 }svrPowerSensorReading OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Current state of voltage or current as detected by this sensor in units described by svrPowerSensorReadingUnits.” ::= { svrPowerSensorEntry 4 }svrPowerSensorReadingUnits OBJECT−TYPE SYNTAX PowerUnits ACCESS read−only STATUS mandatory DESCRIPTION ”Volts AC, DC, amperes AC, DC, ... If not supported, value will be unknown.” ::= { svrPowerSensorEntry 5 }svrPowerSensorNeedPwrThresh OBJECT−TYPE SYNTAX INTEGER


A1−10946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ACCESS read−only STATUS mandatory DESCRIPTION ”Default value for Need More Power voltage threshold. Units are as described in svrPowerSensorThreshUnits.” ::= { svrPowerSensorEntry 6 }svrPowerSensorLowThresh OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Default value for low voltage threshold. Units are as described in svrPowerSensorThreshUnits.” ::= { svrPowerSensorEntry 7 }svrPowerSensorHighThresh OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Default value for high voltage threshold. Units are as described in svrPowerSensorThreshUnits.” ::= { svrPowerSensorEntry 8 }svrPowerSensorShutNowThresh OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Default value for Shutdown Now voltage threshold. Units are as described in svrPowerSensorThreshUnits.” ::= { svrPowerSensorEntry 9 }svrPowerSensorThreshUnits OBJECT−TYPE SYNTAX PowerUnits ACCESS read−only STATUS mandatory DESCRIPTION ”Represents how all the threshold values should be interpreted. If default thresholds not supported, value will be unknown.” ::= { svrPowerSensorEntry 10 }svrPowerSensorStatus OBJECT−TYPE SYNTAX INTEGER { unknown(1) , other(2) , low(3) , lowWarning(4) , statusOk(5) , highWarning(6) , high(7) } ACCESS read−only STATUS mandatory DESCRIPTION ”Status value of the sensor. ” ::= { svrPowerSensorEntry 11 }svrPowerSensorFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index of the FRU entry in the FRU table containing this sensor, if known. 0 if unknown.” ::= { svrPowerSensorEntry 12 }svrPowerSupplyTable OBJECT−TYPE SYNTAX SEQUENCE OF SvrPowerSupplyEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Table of power supply information. Not present if svrPowerSupplyCount = 0.” ::= { svrPowerSystem 5 }svrPowerSupplyEntry OBJECT−TYPE SYNTAX SvrPowerSupplyEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”One entry per detectable power supply.” INDEX { svrPowerSupplyIndex


A1−110 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

} ::= { svrPowerSupplyTable 1 }SvrPowerSupplyEntry ::= SEQUENCE { svrPowerSupplyIndex INTEGER, svrPowerSupplyStatus INTEGER, svrPowerSupplyFruIndex INTEGER }svrPowerSupplyIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”A locally−unique index value.” ::= { svrPowerSupplyEntry 1 }svrPowerSupplyStatus OBJECT−TYPE SYNTAX INTEGER { unknown(1) , running(2) , backup(3) , warning(4) , failed(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”Current state of the power supply.” ::= { svrPowerSupplyEntry 2 }svrPowerSupplyFruIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index of the FRUentry in the FRU table containing this power supply, if known. 0 if unknown.” ::= { svrPowerSupplyEntry 3 }END


A1−11146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

10.5. DEC ELAN MIB DEFINITION DEC−ELAN−MIB DEFINITIONS ::= BEGIN

IMPORTS Counter, enterprises, IpAddress FROM RFC1155−SMI OBJECT−TYPE FROM RFC−1212 DisplayString FROM RFC1213−MIB;

−− DEC−MIB { iso org(3) dod(6) internet(1) private (4) enterprises(1) 36 }

dec OBJECT IDENTIFIER ::= { enterprises 36 } ema OBJECT IDENTIFIER ::= { dec 2 } decMIBextension OBJECT IDENTIFIER ::= { ema 18 } elanext OBJECT IDENTIFIER ::= { decMIBextension 1 } efddi OBJECT IDENTIFIER ::= { elanext 1 } esystem OBJECT IDENTIFIER ::= { elanext 2 } einterfaces OBJECT IDENTIFIER ::= { elanext 3 } ebridge OBJECT IDENTIFIER ::= { elanext 4 } eauth OBJECT IDENTIFIER ::= { elanext 5 }

−− −− efddi − groups in the extended FDDI module −− −− objects in the Digital FDDI implementation over and above −− those in the FDDI MIB.

efddiSMT OBJECT IDENTIFIER ::= { efddi 1 } efddiMAC OBJECT IDENTIFIER ::= { efddi 2 } efddiPORT OBJECT IDENTIFIER ::= { efddi 3 } efddiFDX OBJECT IDENTIFIER ::= { efddi 4 }

−− efddiSMTTable − the extended SMT table −− these are objects implemented in Digital implementations over −− and above the standard SMT group in the IETF FDDI MIB.

efddiSMTTable OBJECT−TYPE SYNTAX SEQUENCE OF EfddiSMTEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of SMT entries. The number of entries is given by smtNumber, defined in the FDDI MIB.” ::= { efddiSMT 1 }

efddiSMTEntry OBJECT−TYPE SYNTAX EfddiSMTEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given SMT link.” INDEX { eSMTIndex } ::= { efddiSMTTable 1 }

EfddiSMTEntry ::= SEQUENCE { eSMTIndex INTEGER, eSMTStationType INTEGER, eSMTTracesReceived Counter }

eSMTIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the SMT Index. The value of this object is


A1−112 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

the same as the snmpFddiSMTIndex, defined in the FDDI MIB, for this smt entity.” ::= { efddiSMTEntry 1 }

eSMTStationType OBJECT−TYPE SYNTAX INTEGER { sas(1), dac(2), sac(3), nac(4), das(5) } ACCESS read−only STATUS mandatory DESCRIPTION ”The Station Type Identification.” ::= { efddiSMTEntry 2 }

eSMTTracesReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of PC Traces received by this station.” ::= { efddiSMTEntry 3 }

−− efddiMACTable − the extended MAC table −− these are objects implemented in Digital implementations over −− and above the standard MAC group in the IETF FDDI MIB.

efddiMACTable OBJECT−TYPE SYNTAX SEQUENCE OF EfddiMACEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of MAC entries. The number of entries is given by macNumber, defined in the FDDI MIB.” ::= { efddiMAC 1 }

efddiMACEntry OBJECT−TYPE SYNTAX EfddiMACEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given MAC entity.” INDEX { eMACSMTIndex, eMACIndex } ::= { efddiMACTable 1 }

EfddiMACEntry ::= SEQUENCE { eMACSMTIndex INTEGER, eMACIndex INTEGER, eMACLinkIndex INTEGER, eMACLinkState INTEGER, eMACRingPurgerState INTEGER, eMACRingPurgerEnable INTEGER, eMACRingPurgeErrors Counter, eMACFrameStripMode INTEGER, eMACFCIStripErrors Counter, eMACRingErrorReason INTEGER, eMACRingInitializationsInitiated Counter, eMACRingInitializationsReceived Counter,


A1−11346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

eMACRingBeaconingInitiated Counter, eMACDuplicateAddressTestFailures Counter, eMACDuplicateTokensDetected Counter, eMACUpstreamNbrDuplAddressFlag INTEGER, eMACTracesInitiated Counter, eMACRestrictedTokenTimeout INTEGER, eMACFrameStatusErrors Counter, eMACFrameAlignmentErrors Counter, eMACTransmitUnderruns Counter }

eMACSMTIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The value of the SMT index associated with this MAC. The value of this object is the same as the snmpFddiMACSMTIndex, defined in the FDDI MIB, for this MAC entity.” ::= { efddiMACEntry 1 }

eMACIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the MAC Index. The value of this object is the same as the snmpFddiMACIndex, defined in the FDDI MIB, for this MAC entity.” ::= { efddiMACEntry 2 }

eMACLinkIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The SMT Resource Index.” ::= { efddiMACEntry 3 }

eMACLinkState OBJECT−TYPE SYNTAX INTEGER { offMaint(1), offReady(2), offFaultRecovery(3), onRingInit(4), onRingRun(5), broken(6) } ACCESS read−only STATUS mandatory DESCRIPTION ”The current state of the link.” ::= { efddiMACEntry 4 }

eMACRingPurgerState OBJECT−TYPE SYNTAX INTEGER { purgerOff(1), candidate(2), nonPurger(3), purger(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”The current Ring Purger state.” ::= { efddiMACEntry 5 }


A1−114 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

eMACRingPurgerEnable OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”If true, this Link will participate in the Ring Purger Election and, if elected, perform the Ring Purger function.” ::= { efddiMACEntry 6 }

eMACRingPurgeErrors OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times the MAC PurgeError Event bit was set.” ::= { efddiMACEntry 7 }

eMACFrameStripMode OBJECT−TYPE SYNTAX INTEGER { saMatch(1), bridgeStrip(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”Method of frame removal used by this station.” ::= { efddiMACEntry 8 }

eMACFCIStripErrors OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times a Frame Content Independent Strip operation was terminated by receipt of a token.” ::= { efddiMACEntry 9 }

eMACRingErrorReason OBJECT−TYPE SYNTAX INTEGER { noReason(1), ringInitInitiated(6), ringInitReceived(7), ringBeaconingInitiated(8), daDetected(9), duplicateTokenDetected(10), ringPurgeError(11), bridgeStripError(12), ringOpOscillation(13), directedBeaconReceived(14), pcTraceInitiated(15), pcTraceReceived(16) } ACCESS read−only STATUS mandatory DESCRIPTION ”Reason for last ring disturbance.” ::= { efddiMACEntry 10 }

eMACRingInitializationsInitiated OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of Ring Claim Processes initiated by this link entity.” ::= { efddiMACEntry 11 }

eMACRingInitializationsReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of Ring Claim Processes or Ring Beaconing Processes initiated by a remote link entity and detected by this link entity.”


A1−11546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

::= { efddiMACEntry 12 }

eMACRingBeaconingInitiated OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of Ring Beacon Processes initiated by this link entity.” ::= { efddiMACEntry 13 }

eMACDuplicateAddressTestFailures OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times the duplicate address test failed.” ::= { efddiMACEntry 14 }

eMACDuplicateTokensDetected OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times this link entity detected a duplicate token.” ::= { efddiMACEntry 15 }

eMACUpstreamNbrDuplAddressFlag OBJECT−TYPE SYNTAX INTEGER { true(1), false(2), unknown(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”The upstream neighbor’s duplicate address status, as reported by the NIF frame. Unknown if no NIF frame has been received yet.” ::= { efddiMACEntry 16 }

eMACTracesInitiated OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of PC Traces initiated by this station.” ::= { efddiMACEntry 17 }

eMACRestrictedTokenTimeout OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The restricted token timeout, which limits how long a single restricted mode dialog may last before being terminated.” ::= { efddiMACEntry 18 }

eMACFrameStatusErrors OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames received on the line that had the E (error detected) indicator set or a missing E indicator.” ::= { efddiMACEntry 19 }

eMACFrameAlignmentErrors OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames received on the line that contained an odd number of symbols; that is, a non−integral number of octets.” ::= { efddiMACEntry 20 }


A1−116 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

eMACTransmitUnderruns OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times an underrun occured because the device’s transmit FIFO became empty due to insufficient memory. In other words, the device was trying to transmit but could not get into memory fast enough.” ::= { efddiMACEntry 21 }

−− efddiPORTTable − the extended PORT table −− these are objects implemented in Digital implementations over −− and above the standard PORT group in the IETF FDDI MIB.

efddiPORTTable OBJECT−TYPE SYNTAX SEQUENCE OF EfddiPORTEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of PORT entries. The number of entries is given by portNumber, defined in the FDDI MIB.” ::= { efddiPORT 1 }

efddiPORTEntry OBJECT−TYPE SYNTAX EfddiPORTEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given PORT entity.” INDEX { ePORTSMTIndex, ePORTIndex } ::= { efddiPORTTable 1 }

EfddiPORTEntry ::= SEQUENCE { ePORTSMTIndex INTEGER, ePORTIndex INTEGER, ePORTPHYIndex INTEGER, ePORTPMDType INTEGER, ePORTPHYState INTEGER, ePORTRejectReason INTEGER, ePORTConnectionsCompleted Counter, ePORTTNEExpRejects Counter, ePORTElasticityBufferErrors Counter }

ePORTSMTIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The value of the SMT index associated with this port. The value of this object is the same as the snmpFddiPORTSMTIndex, defined in the FDDI MIB, for this PORT entity.” ::= { efddiPORTEntry 1 }

ePORTIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the PORT Index. The value of this object is the same as the snmpFddiPORTIndex, defined in the FDDI MIB, for this PORT entity.” ::= { efddiPORTEntry 2 }


A1−11746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ePORTPHYIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The SMT Resource index. Index of the PHY resource used to identify the PHY PORT in ANSI SMT frames.” ::= { efddiPORTEntry 3 }

ePORTPMDType OBJECT−TYPE SYNTAX INTEGER { pmdNone(1), pmdMM(2), pmdSM(3), pmdLC(4), pmdTHN(5), pmdSTP(6), pmdUTP(7) } ACCESS read−only STATUS mandatory DESCRIPTION ”The physical media type of the PORT.” ::= { efddiPORTEntry 4 }

ePORTPHYState OBJECT−TYPE SYNTAX INTEGER { offmaintenance(1), broken(2), offready(3), wait(4), starting(5), failed(6), watch(7), inuse(8) } ACCESS read−only STATUS mandatory DESCRIPTION ”The PHY state.” ::= { efddiPORTEntry 5 }

ePORTRejectReason OBJECT−TYPE SYNTAX INTEGER { noReason(1), lctLocal(2), lctRemote(3), lctBoth(4), lemFailure(5), topologyRules(6), tneExpired(7), remoteReject(8), tracesInProgress(9), tracesReceived(10), standby(11), lctProtocol(12) } ACCESS read−only STATUS mandatory DESCRIPTION ”The current reject reason.” ::= { efddiPORTEntry 6 }

ePORTConnectionsCompleted OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of Physical Connections established for this PHY PORT.” ::= { efddiPORTEntry 7 }

ePORTTNEExpRejects OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times a physical disconnection took place


A1−118 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

because the TNE Noise Timer expired.” ::= { efddiPORTEntry 8 }

ePORTElasticityBufferErrors OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of ELM Chip EBUFF_ERROR events.” ::= { efddiPORTEntry 9 }

−− −− FDDI FDX objects −− −− This is part of the MAC object. However this is an optional group −− to be implemented only for FDX links. −−

efddiFDXTable OBJECT−TYPE SYNTAX SEQUENCE OF EfddiFDXEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of FDX entries.” ::= { efddiFDX 1 }

efddiFDXEntry OBJECT−TYPE SYNTAX EfddiFDXEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given FDX MAC entity.” INDEX { eFDXSMTIndex, eFDXMACIndex } ::= { efddiFDXTable 1 }

EfddiFDXEntry ::= SEQUENCE { eFDXSMTIndex INTEGER, eFDXMACIndex INTEGER, eFDXEnable INTEGER, eFDXOp INTEGER, eFDXState INTEGER }

eFDXSMTIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The value of the SMT index associated with this FDX MAC.” ::= { efddiFDXEntry 1 }

eFDXMACIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The value of the MAC index associated with this FDX MAC.” ::= { efddiFDXEntry 2 }

eFDXEnable OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”When true, this link will participate in the full duplex auto−configuration and, if this is successful, will operate in the full duplex mode.”


A1−11946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

::= { efddiFDXEntry 3 }

eFDXOp OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”When true, this link is operating in the full duplex mode.” ::= { efddiFDXEntry 4 }

eFDXState OBJECT−TYPE SYNTAX INTEGER { fdxIdle(1), fdxRequest(2), fdxConfirm(3), fdxOperation(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”The state of the full duplex Control process.” ::= { efddiFDXEntry 5 }

−− −− esystem − groups in the extended system module −− −− these are system objects implemented in Digital bridges and −− concentrators manageable by ELMS. −−

esysChar OBJECT IDENTIFIER ::= { esystem 1 } esysStatus OBJECT IDENTIFIER ::= { esystem 2 } esysCounters OBJECT IDENTIFIER ::= { esystem 3 } esysConcConfig OBJECT IDENTIFIER ::= { esystem 4 }

−− esysChar − the system Characteristics group −− this group consists of information about the device’s hardware −− and firmware. It also displays information about hardware and −− software switches that contrrol device operation.

esysRomVersion OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The version number of the software stored in ROM.” ::= { esysChar 1 } esysInitSwitch OBJECT−TYPE SYNTAX INTEGER { other(1), reset(2), resetWithDefaults(3) } ACCESS read−write STATUS mandatory DESCRIPTION ”This object allows the management action of initializing a device and forcing it to run selftest. It can also be used to reset all information added to the device’s NVRAM. When read, it returns a value of other(1).” ::= { esysChar 2 }

esysResetDefaultsSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”This object is the state of a hardware switch which, when true, causes the device to reset its parameters


A1−120 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

to the factory defaults when initialized.” ::= { esysChar 3 }

esysGatewayAddress OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”This object allows the setting of a default gateway address for this device.” ::= { esysChar 4 }

esysTrapAddressTable OBJECT−TYPE SYNTAX SEQUENCE OF EsysTrapEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table of IP Addresses to which this device will send traps.” ::= { esysChar 5 } esysTrapEntry OBJECT−TYPE SYNTAX EsysTrapEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Each entry contains an IP Address to which all SNMP Traps will be sent by this device.” INDEX { esysTrapAddress } ::= { esysTrapAddressTable 1 } EsysTrapEntry ::= SEQUENCE { esysTrapAddress IpAddress } esysTrapAddress OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”An IP Address to which all SNMP traps generated by this device will be sent.” ::= { esysTrapEntry 1 }

esysUpdateSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”A software switch that, when set to true, instructs the device to accept a down−line loaded firmware upgrade. If false, the device will not accept upgrades.” ::= { esysChar 6 } esysLastLoadHost OBJECT−TYPE SYNTAX OCTET STRING (SIZE (6)) ACCESS read−only STATUS mandatory DESCRIPTION ”The physical address of the last host, if any, that responded to the device’s request for a downline load of software.” ::= { esysChar 7 }

−− esysStatus − the system Status group −− this group consists of operational status of the device.

esysDeviceState OBJECT−TYPE SYNTAX INTEGER { init(1), operate(2),


A1−12146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

broken(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”The operational state of the device.” ::= { esysStatus 1 }

esysDeviceBrokenReason OBJECT−TYPE SYNTAX INTEGER { none(1), selftestFail(2), onlineDiagFail(3), firmwareFail(4) } ACCESS read−only STATUS mandatory DESCRIPTION ”The reason that the Device State is BROKEN. If current state is not BROKEN and the Unsolicited Resets counter is nonzero, this object show reason for last failure.” ::= { esysStatus 2 }

esysNvramFailed OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”A flag, that, when set to True, indicates that the NVRAM failed selftest following the last initialization of the device.” ::= { esysStatus 3 }

−− esysCounters − the system Counter group −− this group consists of counters that measure operational −− events and errors.

esysPowerups OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times this device was powered on. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.” ::= { esysCounters 1 }

esysMgmtResets OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of times the device was initialized with a management command using esysInitSwitch. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.” ::= { esysCounters 2 }

esysUnsolicitedResets OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of times the device initialized itself after encountering a fatal error. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.” ::= { esysCounters 3 }

−− −− esysConcConfig − Optional group, applicable only to −− FDDI Concentrator −− −− this group consists of a FRU (Field Replaceable Unit) Configuration


A1−122 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

−− Table applicable to the FDDI concentrator, and a switch to enable −− or disable port up/down traps. −−

esysFRUConfigTable OBJECT−TYPE SYNTAX SEQUENCE OF EsysFRUConfigEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of configuration table entries.” ::= { esysConcConfig 1 }

esysFRUConfigEntry OBJECT−TYPE SYNTAX EsysFRUConfigEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given configuration entry.” INDEX { esysFRUIndex } ::= { esysFRUConfigTable 1 }

EsysFRUConfigEntry ::= SEQUENCE { esysFRUIndex INTEGER, esysFRUSlot INTEGER, esysFRUDesc DisplayString, esysFRUType INTEGER, esysFRURev INTEGER, esysFRUState INTEGER }

esysFRUIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”This object is used for indexing the FRU configuration table.” ::= { esysFRUConfigEntry 1 }

esysFRUSlot OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The physical slot number in which the module resides, if applicable. If not applicable, this is reported as ’0’.” ::= { esysFRUConfigEntry 2 }

esysFRUDesc OBJECT−TYPE SYNTAX DisplayString ACCESS read−only STATUS mandatory DESCRIPTION ”A textual description of this FRU.” ::= { esysFRUConfigEntry 3 }

esysFRUType OBJECT−TYPE SYNTAX INTEGER { empty(1), ansiMgmtCard(2), ansiPortCard4line(3), fan(4), apCard(5), niCard(6), fddiCard(7), controllerBackplane(8), qmCard(9), lowPowerPortCard4line(10), singleModeAnsiPortCard4line(11), thinwirePortCard6line(12),


A1−12346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

lowPowerPortCard6line(13), stpCopperPortCard6line(14), singleModeMgmtCard(15), ansi−SingleModeMgmtCard(16), singleMode−ANSIMgmtCard(17), upgradeApCard(19), threeNiCard(20), dasAnsiFddiCard(21), dasAnsiASingleModeBfiCard(22), dasSingleModeAAnsiBfiCard(23), dasSingleModeFddiCard(24), sasSingleModeFddiCard(25), opticalBypass(26), obmUartCard(27), ansiPortCard6line(29) } ACCESS read−only STATUS mandatory DESCRIPTION ”Integer representation for the FRU type. This is the machine−readable form of the descriptor object.” ::= { esysFRUConfigEntry 4 }

esysFRURev OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”This object represents the FRU revision number.” ::= { esysFRUConfigEntry 5 }

esysFRUState OBJECT−TYPE SYNTAX INTEGER { empty(1), −− no FRU present in this slot working(2), −− FRU is working marginal(3), −− FRU is marginal broken(4), −− FRU is broken obrNotSupported(5) −− only for optical bypass card } ACCESS read−only STATUS mandatory DESCRIPTION ”The operational state of the FRU, if present.” ::= { esysFRUConfigEntry 6 }

esysFddiPortTrapSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”This is a switch to enable or diable FDDI port up and port down traps. When set to true, the concentrator will send a trap when one of its ports comes up or goes down.” ::= { esysConcConfig 2 }

−− −− eifTable − groups in the extended interface module −− −− these are interface objects implemented in Digital bridges and −− concentrators manageable by ELMS, over and above what is −− available via MIB−II. −−

eifTable OBJECT−TYPE SYNTAX SEQUENCE OF EifEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of interface entries. The number of entries is given by ifNumber, defined in MIB−II.” ::= { einterfaces 1 }

eifEntry OBJECT−TYPE SYNTAX EifEntry


A1−124 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given interface.” INDEX { eifIndex } ::= { eifTable 1 }

EifEntry ::= SEQUENCE { eifIndex INTEGER, eifBadFramesReceived Counter, eifReceiveOverrun Counter, eifOversizeFrames Counter, eifTransmitFramesError Counter, eifMgmtSetsAllowedSwitch INTEGER }

eifIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB−II, for this interface.” ::= { eifEntry 1 }

eifBadFramesReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of frames received with a bad frame check sequence.” ::= { eifEntry 2 }

eifReceiveOverrun OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of times that the device received a frame loss indication from the hardware on the interface.” ::= { eifEntry 3 }

eifOversizeFrames OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of frames received on the interface that were larger than the maximum legal size.” ::= { eifEntry 4 }

eifTransmitFramesError OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”Number of frames that were transmitted with an error on the line.” ::= { eifEntry 5 }

eifMgmtSetsAllowedSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”This hardware switch, when true, allows write


A1−12546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

access to the device. This object has meaning only when the corresponding functionality is present.” ::= { eifEntry 6 }

−− −− ebridge − groups in the extended bridge module −− −− these are bridge objects implemented in Digital bridges −− over and above what is required by the Bridge MIB −−

ebrChar OBJECT IDENTIFIER ::= { ebridge 1 } ebrStat OBJECT IDENTIFIER ::= { ebridge 2 } ebrCoun OBJECT IDENTIFIER ::= { ebridge 3 } ebrSpan OBJECT IDENTIFIER ::= { ebridge 4 } ebrInterfaces OBJECT IDENTIFIER ::= { ebridge 5 } ebrTwoPortStatic OBJECT IDENTIFIER ::= { ebridge 6 } ebrMultiPortStatic OBJECT IDENTIFIER ::= { ebridge 7 } ebrTwoProtoFilt OBJECT IDENTIFIER ::= { ebridge 8 } ebrMultiProtoFilt OBJECT IDENTIFIER ::= { ebridge 9 } ebrMultiFiltSw OBJECT IDENTIFIER ::= { ebridge 10 } ebrNTP OBJECT IDENTIFIER ::= { ebridge 11 } ebrRateLimiting OBJECT IDENTIFIER ::= { ebridge 12 }

−− ebrChar − the Bridge Characteristics group −− this group consists of information about the bridge’s hardware −− and firmware. It also displays information about hardware and −− software switches that contrrol device operation.

ebrLB100SpanningTreeVer OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The version number of the Spanning Tree algorithm used by the bridge when in the LAN Bridge 100 Spanning Tree mode.” ::= { ebrChar 1 }

ebr802SpanningTreeVer OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The version number of the Spanning Tree algorithm used by the bridge when in the 802.1d Spanning Tree mode.” ::= { ebrChar 2 }

ebrMaxForwardingDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The maximum number of address entries that the bridge can store in its volatile memory.” ::= { ebrChar 3 } ebrMaxNVForwardingDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The maximum number of permanent address entries that the bridge canstore in its NVRAM.” ::= { ebrChar 4 }

ebrMaxProtocolDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The maximum number of protocol entries that the bridge can store in its protocol database. These entries control the handling of frames based on their Ethernet PT, IEEE 802.2 DSAP or IEEE 802 SNAP Protocol ID.” ::= { ebrChar 5 }


A1−126 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ebrMaxNVProtocolDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The maximum number of protocol entries that the bridge can store in its nonvolatile memory. These are retained after a power−down.” ::= { ebrChar 6 }

ebrForwardingDBPurgeThreshold OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The total number of active and inactive address entries that will trigger a purge of the inactive entries.” ::= { ebrChar 7 }

ebrPortTestPassedThreshold OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The number of consecutive successful self−tests needed before the bridge considers a line to be operational.” ::= { ebrChar 8 }

ebrPortTestInterval OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The interval, in seconds, at which the bridge will run selftests on a line that is in the BROKEN state.” ::= { ebrChar 9 }

ebrTopologyChangeTimer OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of seconds remaining, if this is the Root, for which Topology Change will be propagated in Hello messages. Otherwise this value will be reported as 0.” ::= { ebrChar 10 }

ebrManualFilterSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”A switch that controls address filtering. When true, the bridge purges the learned entries from its forwarding database, stops its learning process, and forwards only frames with destination and source addresses that have been specified via management.” ::= { ebrChar 11 }

ebrFragmentationSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”A switch that controls whether fragmentation is performed by the bridge when a large IP frame is received on a datalink


A1−12746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

that supports a higer frame size than the other datalink.” ::= { ebrChar 12 } ebrRemoveMgmtAddress OBJECT−TYPE SYNTAX INTEGER { other(1), true(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”This object allows the action of removing all management entered addresses from the forwarding database when set to true(2). When read, it returns a value of other(1).” ::= { ebrChar 13 }

ebrRemoveMgmtProto OBJECT−TYPE SYNTAX INTEGER { other(1), true(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”This object allows the action of removing all management entered protocols from the protocol database when set to true(2). When read, it returns a value of other(1).” ::= { ebrChar 14 }

−− ebrStat − the Bridge Status group −− this group consists of operational status of the bridge. ebrCurrForwardingDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of address entries in the bridge’s volatile memory. These will be lost upon loss of power.” ::= { ebrStat 1 }

ebrCurrNVForwardingDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of address entries in the bridge’s NVRAM. These will be retained after loss of power.” ::= { ebrStat 2 }

ebrCurrProtocolDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of protocol entries that are stored in the bridge’s protocol database. These control the handling of frames based on their Ethernet protocol type, IEEE 802.2 DSAP, or 802 SNAP Protocol ID.” ::= { ebrStat 3 }

ebrCurrNVProtocolDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of protocol entries in the bridge’s NVRAM. These are retained after a power loss.” ::= { ebrStat 4 }

ebrMgmtHeardPort OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The port on which this command was received.” ::= { ebrStat 5 }


A1−128 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ebrLB100BeingPolled OBJECT−TYPE SYNTAX OCTET STRING (SIZE (6)) ACCESS read−only STATUS mandatory DESCRIPTION ”The address of the LAN Bridge 100 mode bridge that sent this bridge into the LAN Bridge 100 Spanning Tree mode. If this bridge is the Root, this object indicates the bridge that will be polled periodically to determine if it is still necessary to stay in this Spanning Tree mode.” ::= { ebrStat 6 }

ebrInactiveForwardingDBEntries OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of inactive address entries in the bridge’s forwarding database. The bridge marks an address entry inactive when the entry is aged out.” ::= { ebrStat 7 }

ebrTimeSinceForwardingDBPurged OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of seconds since the bridge cleared the forwarding database of inactive entries.” ::= { ebrStat 8 }

ebrTimeSinceLastHello OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The number of seconds since the bridge last sent a Hello message.” ::= { ebrStat 9 }

−− ebrCoun − the Bridge Counters group −− this group consists of counters that measure operational −− events and errors. ebrDeviceFramesLost OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames addressed to the bridge itself that the bridge discarded because it did not have sufficient receive buffers available.” ::= { ebrCoun 1 }

ebrSpanningTreeModeChanges OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times that the bridge switched from the 802.1d Spanning Tree mode to the LB100 Spanning Tree mode.” ::= { ebrCoun 2 }

−− ebrSpan − the Bridge Spanning Tree group −− this group consists of Spanning Tree characteristics over and −− above what is required by the Bridge MIB.

ebrBestRootAge OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The age, in hundereths of seconds, of the Hello message that established the best root.” ::= { ebrSpan 1 }


A1−12946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ebrTopologyChangeFlag OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”A flag that indicates whether a Topology Change is currently in effect on the extended LAN.” ::= { ebrSpan 2 }

ebrTellParentFlag OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”A flag that indicates if the bridge is attempting to propagate a topology change towards the Root.” ::= { ebrSpan 3 }

ebrForwardingDBShortAgingTime OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The number of seconds that the bridge keeps learned entries active while a topology change is in effect.” ::= { ebrSpan 4 }

ebrBadHelloLimit OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The number of hello intervals during which the bridge receives one or more bad hellos on a line, before the bridge performs a test on the link. A bad Hello message is one that contains inferior information that is received on a port on which this bridge is Designated.” ::= { ebrSpan 5 }

ebrBadHelloResetTimer OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The number of Hello intervals without bad Hellos that the bridge will wait before it resets its bad Hello count to zero.” ::= { ebrSpan 6 }

ebrNoFrameInterval OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The The number of seconds of inactivity on a line that will cause the bridge to run a test on that line. The bridge considers a line to be inactive if it does not receive any frames on that line.” ::= { ebrSpan 7 }

ebrLB100PollTime OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The number of seconds that a Root bridge in LAN Bridge 100 mode waits between polling the LAN Bridge 100 that is keeping it in this mode. This polling is done to determine whether the LB100 is still present on the extended LAN.” ::= { ebrSpan 8 }


A1−130 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ebrLB100ResponseTimeout OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The number of seconds that a Root in LAN Bridge 100 Spanning Tree mode will wait for a response from the LAN Bridge 100 which is keeping it in this mode, before which it will assume that the LB100 is no longer on the extended LAN.” ::= { ebrSpan 9 }

ebrLB100SpanningTreeCompat OBJECT−TYPE SYNTAX INTEGER { autoSelect(1), ieee802(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”A switch that controls the Spanning Tree mode used by the bridge. If in Auto−Select mode, the bridge will go into 802 Spanning Tree mode by default, but will switch to LB100 mode as soon as a LB100 is detected. In 802 Spanning Tree mode, the bridge will stay in 802 mode.” ::= { ebrSpan 10 }

−− ebrIfTable − the extended bridge port table −− this group consists of generic port objects for the bridge

ebrIfTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrIfEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of interface entries. The number of entries is given by ifNumber, defined in MIB−II.” ::= { ebrInterfaces 1 }

ebrIfEntry OBJECT−TYPE SYNTAX EbrIfEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given interface.” INDEX { ebrIfIndex } ::= { ebrIfTable 1 }

EbrIfEntry ::= SEQUENCE { ebrIfIndex INTEGER, ebrIfLinkBrokenReason INTEGER, ebrIfPortRestarts Counter, ebrIfUnknownDAReceived Counter, ebrIfFramesAddrFiltered Counter, ebrIfMultiFramesFiltered Counter, ebrIfFramesProtocolFiltered Counter, ebrIfDeviceFramesSent Counter, ebrIfDeviceFramesReceived Counter, ebrIfDeviceBytesSent Counter, ebrIfDeviceBytesReceived Counter, ebrIfDeviceFramesLost Counter, ebrIfMultiBytesSent Counter,


A1−13146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ebrIfMultiBytesReceived Counter, ebrIfMultiDeviceFramesSent Counter, ebrIfMultiDeviceFramesReceived Counter, ebrIfMultiDeviceBytesSent Counter, ebrIfMultiDeviceBytesReceived Counter, ebrIfBadBytesReceived Counter, ebrIfBadHelloLimitExceeded Counter } ebrIfIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB−II, for this interface.” ::= { ebrIfEntry 1 } ebrIfLinkBrokenReason OBJECT−TYPE SYNTAX INTEGER { noFault(1), possibleInternalFault(2), possibleExternalFault(3) } ACCESS read−only STATUS mandatory DESCRIPTION ”The reason why the link was last broken. A possible internal fault(1) indicates a problem with the bridge line itself, a possible external fault(2), indicates a problem with the transmission medium to which the line is attached.” ::= { ebrIfEntry 2 } ebrIfPortRestarts OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times the bridge restarted the line.” ::= { ebrIfEntry 3 } ebrIfUnknownDAReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames received on this line for which the bridge had no address entry in its forwarding database.” ::= { ebrIfEntry 4 } ebrIfFramesAddrFiltered OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames filtered by the bridge on this port because of address entries in the forwarding database.” ::= { ebrIfEntry 5 } ebrIfMultiFramesFiltered OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames with multicast destination addresses that were received on the line on the line and filtered by the bridge.” ::= { ebrIfEntry 6 }


A1−132 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ebrIfFramesProtocolFiltered OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames received on this line that the bridge discarded because of entries set by management in the protocol database.” ::= { ebrIfEntry 7 } ebrIfDeviceFramesSent OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames originating from the bridge itself that were transmitted on this line.” ::= { ebrIfEntry 8 } ebrIfDeviceFramesReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames addressed to the bridge itself that were received on this line.” ::= { ebrIfEntry 9 } ebrIfDeviceBytesSent OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of bytes in the frames originating from the bridge that were transmitted on this line.” ::= { ebrIfEntry 10 } ebrIfDeviceBytesReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of bytes in the frames addressed to the bridge itself that were received on this line.” ::= { ebrIfEntry 11 } ebrIfDeviceFramesLost OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames received on the line addressed to the bridge itself discarded by the bridge because it did not have internal buffers to store them.” ::= { ebrIfEntry 12 } ebrIfMultiBytesSent OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of bytes in Multicast Frames sent, as reported in ifOutNUcastPkts, defined in MIB−II.” ::= { ebrIfEntry 13 } ebrIfMultiBytesReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of bytes in Multicast Frames received, as reported in ifInNUcastPkts, defined in MIB−II.” ::= { ebrIfEntry 14 } ebrIfMultiDeviceFramesSent OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory


A1−13346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

DESCRIPTION ”The number of frames with multicast destination addresses transmitted by the bridge itself on the line.” ::= { ebrIfEntry 15 } ebrIfMultiDeviceFramesReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of frames with multicast destination addresses received by the bridge itslef on the line.” ::= { ebrIfEntry 16 } ebrIfMultiDeviceBytesSent OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of bytes in ebrIfMultiDeviceFramesSent.” ::= { ebrIfEntry 17 } ebrIfMultiDeviceBytesReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of bytes in ebrIfMultiDeviceFramesReceived.” ::= { ebrIfEntry 18 } ebrIfBadBytesReceived OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of bytes in frames received that had a bad frame check sequence.” ::= { ebrIfEntry 19 } ebrIfBadHelloLimitExceeded OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times that the Bad Hellos on the line exceeded the Bad Hello limit.” ::= { ebrIfEntry 20 } −− ebrIfEtherTable − the extended bridge Ethernet port table −− this optional group consists of Ethernet port objects for the bridge

ebrIfEtherTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrIfEtherEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of interface entries for an Ethernet port.” ::= { ebrInterfaces 2 }

ebrIfEtherEntry OBJECT−TYPE SYNTAX EbrIfEtherEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given interface.” INDEX { ebrIfIndex } ::= { ebrIfEtherTable 1 }

EbrIfEtherEntry ::= SEQUENCE { ebrIfEthIndex INTEGER, ebrIfEthPhysicalMediumType INTEGER, ebrIfEthCollisionPresenceTestSwitch INTEGER,


A1−134 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ebrIfEthCollisionTestFailed Counter, ebrIfEthFramingError Counter, ebrIfEthLengthError Counter, ebrIfEthTransmitMultipleCollisions Counter, ebrIfEthCarrierLoss Counter, ebrIfEthCollisionLimitExceeded Counter }

ebrIfEthIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB−II, for this interface.” ::= { ebrIfEtherEntry 1 } ebrIfEthPhysicalMediumType OBJECT−TYPE SYNTAX INTEGER { stdAUIInterface(1), thinwireInterface(2), ieeeFiberInterRepeaterLink(6), fiberOpticLink850nmNoIdle(7), fiberOpticLink850nmDualIdle(8), dConnAuiIf(9), thinwireInterfaceNoLoop(10), twistedPairInterface(11), fullDuplexFiberOptic1300nm(24) } ACCESS read−only STATUS mandatory DESCRIPTION ”The type of physical medium to which this line is attached.” ::= { ebrIfEtherEntry 2 } ebrIfEthCollisionPresenceTestSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”A switch that informs the bridge whether the transceiver on this line is using the Collision Presence Test (CPT), commonly known as heartbeat. It must be enabled if the line’s transceiver has CPT.” ::= { ebrIfEtherEntry 3 } ebrIfEthCollisionTestFailed OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times that a Collision Presence Test (CPT) signal was not detected within 4 microseconds after a transmission on the line. This counter is valid only if ebrIfEthCollisionPresenceTestSwitch is set to true for this line.” ::= { ebrIfEtherEntry 4 } ebrIfEthFramingError OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times that a frame received on the line contained both a noninteger multiple of 8 bits and a CRC error.” ::= { ebrIfEtherEntry 5 }


A1−13546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ebrIfEthLengthError OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of 802.3 frames received that contained a Length field inconsistent with the actual number of data bytes in the packet.” ::= { ebrIfEtherEntry 6 } ebrIfEthTransmitMultipleCollisions OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times that the bridge had to retry transmission of a frame on the line. This was because of collisions during transmission due to congestion on the physical medium.” ::= { ebrIfEtherEntry 7 } ebrIfEthCarrierLoss OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times that the bridge detected a loss of the carrier signal while transmitting a frame on the line.” ::= { ebrIfEtherEntry 8 } ebrIfEthCollisionLimitExceeded OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times that the bridge failed to transmit a frame on this line after 16 attempts, the collision limit.” ::= { ebrIfEtherEntry 9 } −− ebrIfFddiTable − the extended bridge FDDI port table −− this group consists of FDDI port objects for the bridge

ebrIfFddiTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrIfFddiEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of interface entries for an FDDI port.” ::= { ebrInterfaces 3 }

ebrIfFddiEntry OBJECT−TYPE SYNTAX EbrIfFddiEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given interface.” INDEX { ebrIfIndex } ::= { ebrIfFddiTable 1 }

EbrIfFddiEntry ::= SEQUENCE { ebrIfFddiIndex INTEGER, ebrIfFddiUnprocessedErrorPackets Counter, ebrIfFddiIpDatagramsFragmented Counter, ebrIfFddiIpDontFragment Counter, ebrIfFddiIpIllegalHeaderLength Counter, ebrIfFddiIpIllegalSize Counter }


A1−136 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ebrIfFddiIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB−II, for this interface.” ::= { ebrIfFddiEntry 1 }

ebrIfFddiUnprocessedErrorPackets OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of times that an error frame was received on thisline but the bridge did not have time to decipher it.” ::= { ebrIfFddiEntry 2 } ebrIfFddiIpDatagramsFragmented OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number or large IP Datagrams that were fragmented into smaller frames because they did not fit into legal size packets on the smaller datalink after translation.” ::= { ebrIfFddiEntry 3 } ebrIfFddiIpDontFragment OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of large IP datagrams that could not be fragmented because the DONT−FRAGMENT bit was set in the IP header.” ::= { ebrIfFddiEntry 4 } ebrIfFddiIpIllegalHeaderLength OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of large IP datagrams that were discarded instead of being fragmented because the IP header was of illegal length.” ::= { ebrIfFddiEntry 5 } ebrIfFddiIpIllegalSize OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of large IP datagrams that were discarded instead of being fragmented because the IP header indicated a length greater than the number of actual bytes in the received datagram.” ::= { ebrIfFddiEntry 6 }

−− ebrIfSpanTable − the extended bridge Spanning Tree port table −− this group consists of port Spanning Tree objects for the bridge

ebrIfSpanTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrIfSpanEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of interface entries for an FDDI port.” ::= { ebrInterfaces 4 }

ebrIfSpanEntry OBJECT−TYPE SYNTAX EbrIfSpanEntry ACCESS not−accessible STATUS mandatory


A1−13746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

DESCRIPTION ”A collection of objects containing information for a given interface.” INDEX { ebrIfIndex } ::= { ebrIfSpanTable 1 }

EbrIfSpanEntry ::= SEQUENCE { ebrIfSpIndex INTEGER, ebrIfSpDesigRootAge INTEGER, ebrIfSpForwardDelayTimer INTEGER, ebrIfSpBadHelloCount Counter, ebrIfSpPossibleLoopFlag INTEGER, ebrIfSpTopologyChangeAckFlag INTEGER }

ebrIfSpIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB−II, for this interface.” ::= { ebrIfSpanEntry 1 } ebrIfSpDesigRootAge OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The age, in hundreths of seconds, of the last Hello message received from the designated bridge on the line.” ::= { ebrIfSpanEntry 2 } ebrIfSpForwardDelayTimer OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The time remaining, in hundreths of seconds, before the bridge will leave the Preforwarding state (listening or learning), and enter the Forwarding State. If not in preforwarding, this value will be reported as 0.” ::= { ebrIfSpanEntry 3 } ebrIfSpBadHelloCount OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”The number of Hello intervals during which at least one Bad Hello was received.” ::= { ebrIfSpanEntry 4 } ebrIfSpPossibleLoopFlag OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−only STATUS mandatory DESCRIPTION ”A flag that indicates whether the bridge detected a loop condition on this line.” ::= { ebrIfSpanEntry 5 } ebrIfSpTopologyChangeAckFlag OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) }


A1−138 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ACCESS read−only STATUS mandatory DESCRIPTION ”A flag that indicates whether a topology change notification received on a link that we are designated on needs to be acknowledged.” ::= { ebrIfSpanEntry 6 }

−− Static Address Database for 2−port Bridges

ebrTwoPortStaticTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrTwoPortStaticEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains static destination and source address filtering information about unicast and multicast addresses for 2−port bridges.” ::= { ebrTwoPortStatic 1 } ebrTwoPortStaticEntry OBJECT−TYPE SYNTAX EbrTwoPortStaticEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Information about a specific MAC address for which the bridge has some static forwarding and/or filtering information.” INDEX { ebrTwoPortAddress } ::= { ebrTwoPortStaticTable 1 } EbrTwoPortStaticEntry ::= SEQUENCE { ebrTwoPortAddress OCTET STRING, ebrTwoPortPortNum INTEGER, ebrTwoPortStatus INTEGER } ebrTwoPortAddress OBJECT−TYPE SYNTAX OCTET STRING (SIZE (6)) ACCESS read−write STATUS mandatory DESCRIPTION ”The destination/source MAC Address in a frame to which this entry’s filtering information applies.” ::= { ebrTwoPortStaticEntry 1 } ebrTwoPortPortNum OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The Port Number to which this address will be locked−down, if the status is lockDown. Otherwise, this field has a value of 0.” ::= { ebrTwoPortStaticEntry 2 } ebrTwoPortStatus OBJECT−TYPE SYNTAX INTEGER { lockDown(1), hello(2), invalid(3), filter(4), forward(5), rateLimit(6) } ACCESS read−write STATUS mandatory DESCRIPTION ”The status of this entry. The meanings of the values are: lockDown(1) : This address is ’locked−down’ to the port specified by the ebrTwoPortPortNum field.


A1−13946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

This address will be allowed to source frames only from the specified port, and frames destined to this address will be sent out only on the specified port.

hello(2) : This is the address used by the bridge in the destination field of Spanning Tree Hellos. It is not a writeable value.

invalid(3) : Writing this value to the object removes the corresponding entry.

filter(4) : Frames with this address in the source or destination field will be filtered by the bridge.

forward(5) : Frames with this address in the destination field will be forwarded by the bridge.

rateLimit(6) : Frames with this address in the destination field will be rate−limited by the bridge, if it supports rate limiting. Applicable only to multicast addresses. For more detail, please see the ebrRateLimiting group.” ::= { ebrTwoPortStaticEntry 3 }

−− Static Database for multi−port bridges ebrMultiPortStaticTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrMultiPortStaticEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains static destination and source address filtering information about unicast and multicast addresses for multi−port bridges.” ::= { ebrMultiPortStatic 1 } ebrMultiPortStaticEntry OBJECT−TYPE SYNTAX EbrMultiPortStaticEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Information about a specific MAC address for which the bridge has some static forwarding and/or filtering information.” INDEX { ebrMultiPortAddress, ebrMultiPortReceivePort } ::= { ebrMultiPortStaticTable 1 } EbrMultiPortStaticEntry ::= SEQUENCE { ebrMultiPortAddress OCTET STRING, ebrMultiPortReceivePort INTEGER, ebrMultiPortAllowedToGoTo OCTET STRING, ebrMultiPortPortNum INTEGER, ebrMultiPortStatus INTEGER } ebrMultiPortAddress OBJECT−TYPE SYNTAX OCTET STRING (SIZE (6)) ACCESS read−write STATUS mandatory DESCRIPTION ”The destination/source MAC Address in a frame to which this entry’s filtering information applies.” ::= { ebrMultiPortStaticEntry 1 } ebrMultiPortReceivePort OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The port from which a frame must be received to use


A1−140 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

the corresponding ebrMultiPortAllowedToGoTo field. A value of zero indicates that this entry applies on all ports of the bridge.” ::= { ebrMultiPortStaticEntry 2 } ebrMultiPortAllowedToGoTo OBJECT−TYPE SYNTAX OCTET STRING ACCESS read−write STATUS mandatory DESCRIPTION ”The set of ports to which frames received from a specific port and sourced from or destined to the address specified by ebrMultiPortAddress are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of ’1’, then the corresponding port is included in the set of ports; the port is not included if its bit has a value of ’0’.” ::= { ebrMultiPortStaticEntry 3 } ebrMultiPortPortNum OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The Port Number to which this address will be locked−down, if the status is lockDown. Otherwise, this field has a value of zero.” ::= { ebrMultiPortStaticEntry 4 } ebrMultiPortStatus OBJECT−TYPE SYNTAX INTEGER { portMask(1), lockDown(2), maskAndLock(3), hello(4), filter(5), invalid(6), rateLimit(7) } ACCESS read−write STATUS mandatory DESCRIPTION ”The status of this entry. The meanings of the values are: portMask(1) : The static filtering for this address is specified by the MultiPortAllowedToGoTo field.

lockDown(2) : The static filtering for this address is specified as ’locked−down’ to the port specified by the ebrMultiPortPortNum field. This address will be allowed to source frames only from the specified port, and frames destined to this address will be sent out only on the specified port.

maskAndLock(3) : The static filtering for this address is specified by both the ebrMultiPortAllowedToGoTo as well as ’locked−down’ as explained above for ’lockDown(2)’.

hello(4) : This is the address used by the bridge in the destination field of Spanning Tree Hellos. It is not a writeable value.

filter(5) : This address will be filtered on all ports.


rateLimit(7) : Frames with this address in the destination field will be rate−limited by the bridge, if it supports rate limiting. Applicable


A1−14146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

only to multicast addresses. For more detail, please see the ebrRateLimiting group.” ::= { ebrMultiPortStaticEntry 5 }

−− Protocol Database for two−port bridges ebrTwoProtoEnetFilterOther OBJECT−TYPE SYNTAX INTEGER { forward(1), filter(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by the bridge on Ethernet protocol types

other than those specified in the ebrTwoEnetProtoTable. ” ::= { ebrTwoProtoFilt 1 }

ebrTwoProtoSapFilterOther OBJECT−TYPE SYNTAX INTEGER { forward(1), filter(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by the bridge on 802.2 DSAPs other than those specified in the ebrTwoSapProtoTable. ” ::= { ebrTwoProtoFilt 2 }

ebrTwoProtoSnapFilterOther OBJECT−TYPE SYNTAX INTEGER { forward(1), filter(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by the bridge on the 5−byte SNAP PIDs other

than those specified in the ebrTwoSnapProtoTable. ” ::= { ebrTwoProtoFilt 3 } ebrTwoEnetProtoTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrTwoEnetProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about Ethernet protocol types for 2−port bridges.” ::= { ebrTwoProtoFilt 4 } ebrTwoEnetProtoEntry OBJECT−TYPE SYNTAX EbrTwoEnetProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about Ethernet protocol types for 2−port bridges.” INDEX { ebrTwoEnetProtoType } ::= { ebrTwoEnetProtoTable 1 }

EbrTwoEnetProtoEntry ::= SEQUENCE { ebrTwoEnetProtoType OCTET STRING, ebrTwoEnetProtoStatus INTEGER }

ebrTwoEnetProtoType OBJECT−TYPE SYNTAX OCTET STRING (SIZE (2)) ACCESS read−write STATUS mandatory DESCRIPTION ”The protocol type in a frame to which this entry’s filtering information applies.” ::= { ebrTwoEnetProtoEntry 1 }


A1−142 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

ebrTwoEnetProtoStatus OBJECT−TYPE SYNTAX INTEGER { forward(1), filter(2), invalid(3), rateLimit(4) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by bridge when it sees this ethernet protocol type in a received frame. The meanings of the values are:

forward(1) : Frames received with this protocol type are allowed to be forwarded.

filter(2) : Frames received with this protocol type should be filtered.


rateLimit(4) : Frames received with this protocol type will be rate−limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group.” ::= { ebrTwoEnetProtoEntry 2 } ebrTwoSapProtoTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrTwoSapProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about 802.2 SAPs in the DSAP field for 2−port bridges.” ::= { ebrTwoProtoFilt 5 } ebrTwoSapProtoEntry OBJECT−TYPE SYNTAX EbrTwoSapProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about 802.2 SAPs in the DSAP field for 2−port bridges.” INDEX { ebrTwoSapIndex } ::= { ebrTwoSapProtoTable 1 }

EbrTwoSapProtoEntry ::= SEQUENCE { ebrTwoSapIndex INTEGER, ebrTwoSapValue OCTET STRING, ebrTwoSapStatus INTEGER }

ebrTwoSapIndex OBJECT−TYPE SYNTAX INTEGER (1..256) ACCESS read−only STATUS mandatory DESCRIPTION ”Index of the SAP table.” ::= { ebrTwoSapProtoEntry 1 }

ebrTwoSapValue OBJECT−TYPE SYNTAX OCTET STRING (SIZE (1)) ACCESS read−write STATUS mandatory DESCRIPTION ”The 802.2 DSAP in a frame to which this entry’s filtering information applies.” ::= { ebrTwoSapProtoEntry 2 } ebrTwoSapStatus OBJECT−TYPE SYNTAX INTEGER {


A1−14346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

forward(1), filter(2), invalid(3), rateLimit(4) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by bridge when it sees this 802.2 SAP in the DSAP field of a received frame. The meanings of the values are:

forward(1) : Frames received with this sap are allowed to be forwarded.

filter(2) : Frames received with this sap should be filtered.


rateLimit(4) : Frames received with this sap will be rate−limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group.” ::= { ebrTwoSapProtoEntry 3 } ebrTwoSnapProtoTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrTwoSnapProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about 5−byte SNAP PIDs for 2−port bridges.” ::= { ebrTwoProtoFilt 6 } ebrTwoSnapProtoEntry OBJECT−TYPE SYNTAX EbrTwoSnapProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about 5−byte SNAP PIDs for 2−port bridges.” INDEX { ebrTwoSnapIndex } ::= { ebrTwoSnapProtoTable 1 }

EbrTwoSnapProtoEntry ::= SEQUENCE { ebrTwoSnapIndex INTEGER, ebrTwoSnapValue OCTET STRING, ebrTwoSnapStatus INTEGER }

ebrTwoSnapIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The index into the SNAP table.” ::= { ebrTwoSnapProtoEntry 1 }

ebrTwoSnapValue OBJECT−TYPE SYNTAX OCTET STRING (SIZE (5)) ACCESS read−write STATUS mandatory DESCRIPTION ”The SNAP PID in an 802 frame to which this entry’s filtering information applies.” ::= { ebrTwoSnapProtoEntry 2 } ebrTwoSnapStatus OBJECT−TYPE SYNTAX INTEGER { forward(1), filter(2), invalid(3),


A1−144 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

rateLimit(4) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by bridge when it sees this SNAP PID in a received 802 frame. The meanings of the values are:

forward(1) : Frames received with this snap pid are allowed to be forwarded.

filter(2) : Frames received with this snap pid should be filtered.


rateLimit(4) : Frames received with this snap pid will be rate−limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group.” ::= { ebrTwoSnapProtoEntry 3 }

−− Protocol Database for multi−port bridges ebrMultiEnetProtoTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrMultiEnetProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about Ethernet protocol types for multi−port bridges.” ::= { ebrMultiProtoFilt 1 } ebrMultiEnetProtoEntry OBJECT−TYPE SYNTAX EbrMultiEnetProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about Ethernet protocol types for multi−port bridges.” INDEX { ebrMultiEnetProtoType, ebrMultiEnetReceivePort } ::= { ebrMultiEnetProtoTable 1 }

EbrMultiEnetProtoEntry ::= SEQUENCE { ebrMultiEnetProtoType OCTET STRING, ebrMultiEnetReceivePort INTEGER, ebrMultiEnetAllowedToGoTo OCTET STRING, ebrMultiEnetStatus INTEGER }

ebrMultiEnetProtoType OBJECT−TYPE SYNTAX OCTET STRING (SIZE (2)) ACCESS read−write STATUS mandatory DESCRIPTION ”The protocol type in a frame to which this entry’s filtering information applies.” ::= { ebrMultiEnetProtoEntry 1 } ebrMultiEnetReceivePort OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The port from which a frame must be received to use the corresponding ebrMultiPortEnetProtoType field. A value of zero indicates that this entry applies on all ports of the bridge.” ::= { ebrMultiEnetProtoEntry 2 }


A1−14546 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ebrMultiEnetAllowedToGoTo OBJECT−TYPE SYNTAX OCTET STRING ACCESS read−write STATUS mandatory DESCRIPTION ”The set of ports to which frames received from a specific port and containing the protocol type specified by ebrMultiEnetProtoType are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of ’1’, then the corresponding port is included in the set of ports; the port is not included if its bit has a value of ’0’.” ::= { ebrMultiEnetProtoEntry 3 }

ebrMultiEnetStatus OBJECT−TYPE SYNTAX INTEGER { portMask(1), invalid(2), filter(3), forward(4), rateLimit(5) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by bridge when it sees this ethernet protocol type in a received frame. The meanings of the values are:

portMask(1) : The static filtering for this address is specified by the MultiEnetAllowedToGoTo field.




rateLimit(5) : Frames received with this protocol type will be rate−limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group.” ::= { ebrMultiEnetProtoEntry 4 }

ebrMultiSapProtoTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrMultiSapProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about 802.2 SAPs in the DSAP field for multi−port bridges.” ::= { ebrMultiProtoFilt 2 } ebrMultiSapProtoEntry OBJECT−TYPE SYNTAX EbrMultiSapProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about 802.2 SAPs in the DSAP field for multi−port bridges.” INDEX { ebrMultiSapValue, ebrMultiSapReceivePort } ::= { ebrMultiSapProtoTable 1 }

EbrMultiSapProtoEntry ::= SEQUENCE { ebrMultiSapValue OCTET STRING, ebrMultiSapReceivePort


A1−146 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

INTEGER, ebrMultiSapAllowedToGoTo OCTET STRING, ebrMultiSapStatus INTEGER }

ebrMultiSapValue OBJECT−TYPE SYNTAX OCTET STRING (SIZE (1)) ACCESS read−write STATUS mandatory DESCRIPTION ”The 802.2 DSAP in a frame to which this entry’s filtering information applies.” ::= { ebrMultiSapProtoEntry 1 } ebrMultiSapReceivePort OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The port from which a frame must be received to use the corresponding ebrMultiPortSapProtoType field. A value of zero indicates that this entry applies on all ports of the bridge.” ::= { ebrMultiSapProtoEntry 2 } ebrMultiSapAllowedToGoTo OBJECT−TYPE SYNTAX OCTET STRING ACCESS read−write STATUS mandatory DESCRIPTION ”The set of ports to which frames received from a specific port and containing the DSAP in an 802 frame specified by ebrMultiSapValue are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of ’1’, then the corresponding port is included in the set of ports; the port is not included if its bit has a value of ’0’.” ::= { ebrMultiSapProtoEntry 3 }

ebrMultiSapStatus OBJECT−TYPE SYNTAX INTEGER { portMask(1), invalid(2), filter(3), forward(4), rateLimit(5) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by bridge when it sees this 802.2 SAP in the DSAP field of a received frame. The meanings of the values are:

portMask(1) : The static filtering for this address is specified by the MultiSapAllowedToGoTo field.




rateLimit(5) : Frames received with this protocol type will be rate−limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group.”


A1−14746 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

::= { ebrMultiSapProtoEntry 4 }

ebrMultiSnapProtoTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrMultiSnapProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about 5−byte SNAP PIDs for multi−port bridges.” ::= { ebrMultiProtoFilt 3 } ebrMultiSnapProtoEntry OBJECT−TYPE SYNTAX EbrMultiSnapProtoEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table that contains filtering information about 5−byte SNAP PIDs for multi−port bridges.” INDEX { ebrMultiSnapValue, ebrMultiSnapReceivePort } ::= { ebrMultiSnapProtoTable 1 }

EbrMultiSnapProtoEntry ::= SEQUENCE { ebrMultiSnapValue OCTET STRING, ebrMultiSnapReceivePort INTEGER, ebrMultiSnapAllowedToGoTo OCTET STRING, ebrMultiSnapStatus INTEGER }

ebrMultiSnapValue OBJECT−TYPE SYNTAX OCTET STRING (SIZE (5)) ACCESS read−write STATUS mandatory DESCRIPTION ”The SNAP PID in an 802 frame to which this entry’s filtering information applies.” ::= { ebrMultiSnapProtoEntry 1 } ebrMultiSnapReceivePort OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION ”The port from which a frame must be received to use the corresponding ebrMultiPortSnapProtoType field. A value of zero indicates that this entry applies on all ports of the bridge.” ::= { ebrMultiSnapProtoEntry 2 } ebrMultiSnapAllowedToGoTo OBJECT−TYPE SYNTAX OCTET STRING ACCESS read−write STATUS mandatory DESCRIPTION ”The set of ports to which frames received from a specific port and containing the SNAP PID in an 802 frame specified by ebrMultiSnapValue are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of ’1’, then the corresponding port is included in the set of ports; the port is not included if its bit has a value of ’0’.” ::= { ebrMultiSnapProtoEntry 3 }

ebrMultiSnapStatus OBJECT−TYPE SYNTAX INTEGER { portMask(1), invalid(2), filter(3),


A1−148 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

forward(4), rateLimit(5) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by bridge when it sees this SNAP PID in a received 802 frame. The meanings of the values are:

portMask(1) : The static filtering for this address is specified by the MultiSnapAllowedToGoTo field.




rateLimit(5) : Frames received with this protocol type will be rate−limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group.” ::= { ebrMultiSnapProtoEntry 4 }

−− ebrMultiFiltSw − this optional group consists of per−port −− address and protocol filtering switches for multiport bridges

ebrMultiSwTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrMultiSwEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of interface entries. The number of entries is given by ifNumber, defined in MIB−II.” ::= { ebrMultiFiltSw 1 }

ebrMultiSwEntry OBJECT−TYPE SYNTAX EbrMultiSwEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A collection of objects containing information for a given interface.” INDEX { ebrMultiSwIndex } ::= { ebrMultiSwTable 1 }

EbrMultiSwEntry ::= SEQUENCE { ebrMultiSwIndex INTEGER, ebrMultiSwManualFilter INTEGER, ebrMultiSwProtoEnetOther INTEGER, ebrMultiSwProtoSapOther INTEGER, ebrMultiSwProtoSnapOther INTEGER }

ebrMultiSwIndex OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”Identifies the Interface to which this entry applies.” ::= { ebrMultiSwEntry 1 }

ebrMultiSwManualFilter OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) }


A1−14946 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

ACCESS read−write STATUS mandatory DESCRIPTION ”A switch that controls address filtering. When true, the bridge purges the learned entries from its forwarding database, stops its learning process, and forwards only frames with destination and source addresses that have been specified via management.” ::= { ebrMultiSwEntry 2 }

ebrMultiSwProtoEnetOther OBJECT−TYPE SYNTAX INTEGER { forward(1), filter(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by the bridge on Ethernet protocol types other than those specified in the ebrMultiEnetProtoTable.” ::= { ebrMultiSwEntry 3 }

ebrMultiSwProtoSapOther OBJECT−TYPE SYNTAX INTEGER { forward(1), filter(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by the bridge on 802.2 DSAPs other

than those specified in the ebrMultiSapProtoTable.” ::= { ebrMultiSwEntry 4 }

ebrMultiSwProtoSnapOther OBJECT−TYPE SYNTAX INTEGER { forward(1), filter(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Action taken by the bridge on the 5−byte SNAP PIDs other

than those specified in the ebrMultiSnapProtoTable.” ::= { ebrMultiSwEntry 5 }

−− −− ebrNTP − the Non−Translated Protocol table. −− −− this optional group is implemented by FDDI to Ethernet bridges which −− support this feature. Selected Ethernet Protocol types are −− subjected to a different algorithm than the standard translation −− algorithm used by transparent FDDI to Ethernet bridges. It is −− used for protocol types that may be used in both Ethernet packets −− as well as IEEE 802.3 packets with a 1042−style PID. An example −− of a protocol type that should be in this table is AARP. −−

ebrNTPTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrNTPEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table of Ethernet protocol types which will selectively be translated in such a way as to guarantee that the form in which a packet was received − Ethernet PT or 802.3 with 1042 format and this PT − will be retained across a pair of these bridges.” ::= { ebrNTP 1 }

ebrNTPEntry OBJECT−TYPE SYNTAX EbrNTPEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of NTP protocol type entries.” INDEX { ebrNTPtype } ::= { ebrNTPTable 1 }


A1−150 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

EbrNTPEntry ::= SEQUENCE { ebrNTPtype OCTET STRING, ebrNTPStatus INTEGER }

ebrNTPtype OBJECT−TYPE SYNTAX OCTET STRING (SIZE (2)) ACCESS read−write STATUS mandatory DESCRIPTION ”A protocol type in the NTP table.” ::= { ebrNTPEntry 1 }

ebrNTPStatus OBJECT−TYPE SYNTAX INTEGER { other(1), invalid(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1).” ::= { ebrNTPEntry 2 }

esysIPXSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”A software switch that, when set to true, causes the bridge to translate IPX ’raw 802.3’ packets into SNAP encapsulated packets on the FDDI. Note that this works only in environments where all IPX stations use only this particular format. It is recommended that the Ethernet v2 format be used on IPX stations for full connectivity of IPX stations across Ethernet as well as FDDI bridged and routed networks.” ::= { ebrNTP 2 }

−− −− ebrRateLimit − the Rate Limit group −− −− this optional group is implemented by bridges which perform rate −− limiting of multicast frames received on bridge ports. A typical −− application of this might be to limit a broadcast storm from −− to the confines of the LAN connected by the bridge. −− −− Rate limiting may be specified by address or protocol, via the −− appropriate static address or protocol database, through the use −− of the ’rateLimit’ status. −−

ebrRateLimitSwitch OBJECT−TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”By default, rate limiting will be disabled. It can be enabled by setting this object to ’true(1)’.” ::= { ebrRateLimiting 1 }

ebrRateLimit OBJECT−TYPE SYNTAX INTEGER ACCESS read−write STATUS mandatory DESCRIPTION


A1−15146 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

”This is the maximum number of rate−limited frames per second that the bridge will forward per second.” ::= { ebrRateLimiting 2 }

ebrRateLimitCounterTable OBJECT−TYPE SYNTAX SEQUENCE OF EbrRateLimitCounterEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A table of the count of frames that were dropped by the bridge due to rate limiting on each port.” ::= { ebrRateLimiting 3 }

ebrRateLimitCounterEntry OBJECT−TYPE SYNTAX EbrRateLimitCounterEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of rate limited frame counter entries.” INDEX { ebrRateLimitPort } ::= { ebrRateLimitCounterTable 1 }

EbrRateLimitCounterEntry ::= SEQUENCE { ebrRateLimitPort INTEGER, ebrRateLimitAddressFrames Counter, ebrRateLimitProtocolFrames Counter }

ebrRateLimitPort OBJECT−TYPE SYNTAX INTEGER ACCESS read−only STATUS mandatory DESCRIPTION ”The port for which this entry contains rate limit counters information.” ::= { ebrRateLimitCounterEntry 1 }

ebrRateLimitAddressFrames OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”This is the number of frames per second that were filtered due to address rate limiting.” ::= { ebrRateLimitCounterEntry 2 }

ebrRateLimitProtocolFrames OBJECT−TYPE SYNTAX Counter ACCESS read−only STATUS mandatory DESCRIPTION ”This is the number of frames per second that were filtered due to protocol rate limiting.” ::= { ebrRateLimitCounterEntry 3 }

−− −− eauth − groups in the SNMP Authentication module −− eauth1 OBJECT IDENTIFIER ::= { eauth 1 }

−− −− eauth1 is a group of objects supporting simple SNMP Authentication. −−

−− −− SNMP Trap User Community −−

eauthTrapCommunity OBJECT−TYPE SYNTAX OCTET STRING (SIZE (32)) ACCESS read−write


A1−152 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

STATUS mandatory DESCRIPTION ”The community string used in SNMP Trap PDUs.” ::= { eauth1 1 }

eauthTrapUserTable OBJECT−TYPE SYNTAX SEQUENCE OF EauthTrapUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of addresses to which traps will be sent and associated information.” ::= { eauth1 2 }

eauthTrapUserEntry OBJECT−TYPE SYNTAX EauthTrapUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Objects containing information for a given trap address.” INDEX { eauthTrapUserAddr } ::= { eauthTrapUserTable 1 }

EauthTrapUserEntry ::= SEQUENCE { eauthTrapUserAddr IpAddress, eauthTrapUserStatus INTEGER }

eauthTrapUserAddr OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”An IP Address to which all SNMP Trap messages will be sent.” ::= { eauthTrapUserEntry 1 }

eauthTrapUserStatus OBJECT−TYPE SYNTAX INTEGER { other(1), invalid(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1).” ::= { eauthTrapUserEntry 2 }

−− −− SNMP Read−only User Community −−

eauthReadOnlyCommunity OBJECT−TYPE SYNTAX OCTET STRING (SIZE (32)) ACCESS read−write STATUS mandatory DESCRIPTION ”The community string used to identify an SNMP community with access rights of Read−only.” ::= { eauth1 3 }

eauthReadOnlyUserTable OBJECT−TYPE SYNTAX SEQUENCE OF EauthReadOnlyUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of Read−only users and associated information.” ::= { eauth1 4 }

eauthReadOnlyUserEntry OBJECT−TYPE SYNTAX EauthReadOnlyUserEntry ACCESS not−accessible STATUS mandatory


A1−15346 127 300 − 506 / V7.2 / 11.11.2005COMSOFT

DESCRIPTION ”Objects containing information for a given Read−only user.” INDEX { eauthReadOnlyUserAddr } ::= { eauthReadOnlyUserTable 1 }

EauthReadOnlyUserEntry ::= SEQUENCE { eauthReadOnlyUserAddr IpAddress, eauthReadOnlyUserMask OCTET STRING, eauthReadOnlyUserStatus INTEGER }

eauthReadOnlyUserAddr OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”An IP Address, or a set of IP addresses, which has Read−only SNMP access to this agent. If this object is used as a wildcard, bits corresponding to the zero bits in the corresponding euthReadOnlyUserMask are treated as don’t−care.” ::= { eauthReadOnlyUserEntry 1 }

eauthReadOnlyUserMask OBJECT−TYPE SYNTAX OCTET STRING (SIZE (4)) ACCESS read−write STATUS mandatory DESCRIPTION ”A 32−bit mask which is applied to (ANDed with) the source IP address of an incoming SNMP message. If the result of the mask is equal to eauthReadOnlyUserAddr, the message is considered to have come from a user who has Read−only access. This allows wildcarding, for example, for all NMS’s on a given subnet. For fully specified IP addresses required to be in this community, this mask may be set to all 1’s.” ::= { eauthReadOnlyUserEntry 2 }

eauthReadOnlyUserStatus OBJECT−TYPE SYNTAX INTEGER { other(1), invalid(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1).” ::= { eauthReadOnlyUserEntry 3 }

−− −− SNMP Read−Write User Community −−

eauthReadWriteCommunity OBJECT−TYPE SYNTAX OCTET STRING (SIZE (32)) ACCESS read−write STATUS mandatory DESCRIPTION ”The community string used to identify an SNMP community with access rights of Read−Write.” ::= { eauth1 5 }

eauthReadWriteUserTable OBJECT−TYPE SYNTAX SEQUENCE OF EauthReadWriteUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”A list of Read−Write users and associated information.” ::= { eauth1 6 }

eauthReadWriteUserEntry OBJECT−TYPE


A1−154 46 127 300 − 506 / V7.2 / 11.11.2005 COMSOFT

SYNTAX EauthReadWriteUserEntry ACCESS not−accessible STATUS mandatory DESCRIPTION ”Objects containing information for a given Read−Write user.” INDEX { eauthReadWriteUserAddr } ::= { eauthReadWriteUserTable 1 }

EauthReadWriteUserEntry ::= SEQUENCE { eauthReadWriteUserAddr IpAddress, eauthReadWriteUserMask OCTET STRING, eauthReadWriteUserStatus INTEGER }

eauthReadWriteUserAddr OBJECT−TYPE SYNTAX IpAddress ACCESS read−write STATUS mandatory DESCRIPTION ”An IP Address, or a set of IP addresses, which has Read−Write SNMP access to this agent. If this object is used as a wildcard, bits corresponding to the zero bits in the corresponding euthReadWriteUserMask are treated as don’t−care.” ::= { eauthReadWriteUserEntry 1 }

eauthReadWriteUserMask OBJECT−TYPE SYNTAX OCTET STRING (SIZE (4)) ACCESS read−write STATUS mandatory DESCRIPTION ”A 32−bit mask which is applied to (ANDed with) the source IP address of an incoming SNMP message. If the result of the mask is equal to eauthReadWriteUserAddr, the message is considered to have come from a user who has Read−Write access. This allows wildcarding, for example, for all NMS’s on a given subnet. For fully specified IP addresses required to be in this community, this mask may be set to all 1’s.” ::= { eauthReadWriteUserEntry 2 }

eauthReadWriteUserStatus OBJECT−TYPE SYNTAX INTEGER { other(1), invalid(2) } ACCESS read−write STATUS mandatory DESCRIPTION ”Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1).” ::= { eauthReadWriteUserEntry 3 }

END