Français dropdown-ico

Paradyne 8820 manuel d'utilisation

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108

Aller à la page of

Les manuels d’utilisation similaires

Un bon manuel d’utilisation

Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Paradyne 8820. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Paradyne 8820 ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.

Qu'est ce que le manuel d’utilisation?

Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Paradyne 8820 décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.

Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.

Donc, ce qui devrait contenir le manuel parfait?

Tout d'abord, le manuel d’utilisation Paradyne 8820 devrait contenir:
- informations sur les caractéristiques techniques du dispositif Paradyne 8820
- nom du fabricant et année de fabrication Paradyne 8820
- instructions d'utilisation, de réglage et d’entretien de l'équipement Paradyne 8820
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes

Pourquoi nous ne lisons pas les manuels d’utilisation?

Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Paradyne 8820 ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Paradyne 8820 et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Paradyne en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Paradyne 8820, comme c’est le cas pour la version papier.

Pourquoi lire le manuel d’utilisation?

Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Paradyne 8820, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.

Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Paradyne 8820. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.

Table des matières du manuel d’utilisation

  • Page 1

    Hotwire 8620 and 8820 GranDSLAM SNMP Reference Document No. 8000-A2-GB30-10 Nov ember 2003[...]

  • Page 2

    A November 2003 8000-A2-GB30-10 Copyright © 2003 Paradyne Corporation. All rights reser ved. Printed in U .S.A. Notice This publication is protected b y federal cop yright law . No par t of this publication ma y be copied or distributed, transmitted, transcribed, stored in a retr ie v al system, or translate d into any human or computer languag e [...]

  • Page 3

    8000-A2-GB30-10 November 2003 i Contents About This Guide  Document Pur pose and Inte nded Audienc e . . . . . . . . . . . . . . . . . . . . iii  Document Sum mary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii  Product-Rela ted Docume nts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv 1[...]

  • Page 4

    Contents ii November 2003 8000-A2-GB30-10[...]

  • Page 5

    8000-A2-GB30-10 November 2003 iii About This Guide Document Purpose and Intended A udience This ref erence manual contains th e network management specification f or the Hotwire GranDSLAM 8620 a nd 8820 R elease 3. 2 and above . It is desig ned for network managers who use SNMP in the course of insta lling, configuring, monitoring, and troub leshoo[...]

  • Page 6

    About This Guide iv November 2003 8000-A2-GB30-10 Pr oduct-Related Documents Complete document ation for this prod uct is av ailab le online at www .paradyne.com . Select Suppor t → T echnical Manuals → Hotwire DSL Systems . T o order a paper co p y of a Par a dyne docum ent, or to speak with a sales representat ive, plea se call 1-727-530-2000[...]

  • Page 7

    8000-A2-GB30-10 November 2003 1 Network Management Specification 1. GranDSLAM 3.2 Network Managem ent Interface This document describes the SNMP suppor t for the GranDSLAM R3.2 product. Th e product includes t he following models: These GranDSLAM R3.2 model units are configurable from SNMP or through the TL1 Command Line Interface using the fo llow[...]

  • Page 8

    2 November 2003 8000-A2-GB3 0-10 2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface T ypes Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Ty p e s [dsx1ConfigEntry_t], [dsx1CurrentEntry_t], [dsx1IntervalEntry_t], [dsx1 T otalEntry_t], [dsx1ChanMappingEntry_t], [dsx1F arEndCu rrent Entry _t], [dsx1FarEndI[...]

  • Page 9

    8000-A2-GB30-10 November 2003 3 N/A SNMP M4 Network Element V iew MIB [atmfM4MIB] AF-NM-0095.001 (http://www .atmforum.com/atmforum /s pecs/ap proved .html) A TM F orum SNMP M4 Network Element V iew [atmfM4MIBObjects_t],[at mfM4T cAdapterEntry_t], [atmfM4A TMLayerEntry_t], [atmfM4VpNextVpiEntry_t], [atmfM4VcNextVciEntry_t],[a tmfM4CellProtoCurr Ent[...]

  • Page 10

    4 November 2003 8000-A2-GB3 0-10 enterprise pdn_SonetExt.m ib Paradyne Enterprise Sonet Extension MIB devSonetConfigEntry_t enterprise PDN-ENTITY -RED UNDANCY -MIB. mib Paradyne Enterprise En tity Redundancy MIB pdnEntityRedundancySelection, pdnRedunCmdEntry , pdnRedunS tatusEntry enterprise PDN-LINK-F AUL T -MGMT -MIB.mib Paradyne Enterprise Link [...]

  • Page 11

    8000-A2-GB30-10 November 2003 5 enterprise pdn_spectrummgm t.mib Paradyne spectrum ma nagement specific mib. newSpectrumMgmtGeneralCon figEntry , newSpectrumMgmtConfEntry , newSpectrumMgmtLineInfoEntry enterprise pdn_reachDSL.mib Para dyne ReachDSL specific mib. reachDSLSpectrumMgmt Selection reachDSLSpectrumMgmtConfEntry reachDSLSpectrum Mg mtLine[...]

  • Page 12

    6 November 2003 8000-A2-GB3 0-10 T able 1-3. Other Supported RFCs Us ed as Guidelines for Implementation RFC Name/Description 768 User Datagram Protocol 791 Internet Protocol 792, 950 Internet Control Messa ge Protocol; Internet Sta ndard Subnetting Procedure 793 T ransmission Control Protocol 826 Ethernet Address Resolution Prot ocol: Or convertin[...]

  • Page 13

    8000-A2-GB30-10 November 2003 7 2. Standards Com plian ce for SNMP Traps This section describes the standards compliance and any special operational features/options for the SNMP Traps supp orted by the GranDSLAM R3.2 products. The following traps are support ed. T able 1-4. Summary of T raps (1 of 7) T rap Description V arBind(s) S tandard T raps [...]

  • Page 14

    8 November 2003 8000-A2-GB3 0-10 atmfM4IfLofAlarm LOF (Loss of Frame) condition has occurred. ifIndex, ifOperStatus, atmfM4T rapAlarmSeverit y devLastT rapString atmfM4VclXConnCreated Indicates that the VC L cross-connection has jus t been created. When a cross-connection is created along with its VCL endpoints, this trap should be emitted to indic[...]

  • Page 15

    8000-A2-GB30-10 November 2003 9 hdsl2ShdslPerfSESThresh This not ification indicate s that the severely errored se conds threshold has been reached/exceede d for the HDSL2/SHDSL segment endpoint. hdsl2ShdslEndpointCurr15MinSES, hdsl2ShdslEndpointThreshSES devLastT rapString hdsl2ShdslPerfCRCanomaliesThresh This notification indicates that the CRC a[...]

  • Page 16

    10 November 2003 8000-A2-GB3 0-10 hdsl2ShdslprotocolIn itFailure This notification indicates that the bit setting forprotocolInitFailu re in the hdsl2ShdslEndpointCu rrS tatus object for this endpoint has changed. hdsl2ShdslEndpointCurrStatus devLastT rapString hdsl2ShdslnoNeighborPresent This notif ication indicates that the bit setting for noNeig[...]

  • Page 17

    8000-A2-GB30-10 November 2003 11 devSonetStatusChange A devSonetS tatusChan ge trap is sent when the value of an instance of sonetSectionCurre ntStatus or sonetLineCurrentStatus or sonetPathCurrentStatus changes. devSonetS t atusLastChange sonetSectionCurrentStatus, sonetLineCurrentStatus, sonetPathCurrentStatus devLastT rapString pdnRedunEventNoAc[...]

  • Page 18

    12 November 2003 8000-A2-GB3 0-10 adslAtucPerfLolsThreshT rap Loss of Link 15-minute in terval threshold reached ifIndex adslAtucPerfCurr15MinLols adslAtucT hresh15MinLols devLastT rapString adslAtucInitFailureT rap A TUC initialization failed. See adslAtucCurrStatus fo r potential reasons ifIndex adslAtucCurrS tatus devLastT rapString adslAturPerf[...]

  • Page 19

    8000-A2-GB30-10 November 2003 13 adslAturSesL ThreshT rap Severl y errored seconds 15 minutes threshold reached ifIndex adslAturPerfCurr15MinSesL devLastT rapString adslAturUasL ThreshT rap Unavailabl e seconds 15 minutes threshold reached ifIndex adslAturPerfCurr15MinUasL devLastT rapString IMA T raps imaFailureAlarm The imaFa ilureAlarm provides [...]

  • Page 20

    14 November 2003 8000-A2-GB3 0-10 3. Standards Complia nce to SNMP MIB s This section describes the standards compliance and any special operational features/options for the SNMP MIBs supp orted on the GranDSLAM R3.2 product. The term NO_SUCH_NAME_ERROR will be used to say that either: a) a whole table does not exist in the MIB tree or b) a particu[...]

  • Page 21

    8000-A2-GB30-10 November 2003 15 Figure 1-1. GranDSLAM Interfaces ATM DSL Chan ADSL Port Cards Slot 1 Slot 2 Slot 18 ATM DSL Chan ReachDSL ATM SHDSL DS1 Sonet SonetPath ATM IMA AAL5 ETH rs-232 T1/E1 IMA Child-card DS1 Sonet SonetPath ATM IMA AAL5 ETH T1/E1 IMA Child-card ACTIVE SCP card on slot 19 STANDBY SCP card sl ot 20 entPhysicalIndex=01010001[...]

  • Page 22

    16 November 2003 8000-A2-GB3 0-10 3.1 Management Information Base (MIB)-II - RFC 1 213. The objects defined by MIB-II are or ganized into 10 different groups. The GranDSLAM R3.2 will implement only thos e groups where the semantics of the group are applicable to the implementation of th e stack (for example, if EGP is not implemented the EGP group [...]

  • Page 23

    8000-A2-GB30-10 November 2003 17 3.2.2 “sysObjectID” Object (system 2) This object provides the authoritati ve identifi cation of th e network management subsyst em contained in the unit. This object will be set to display the fol lowing object identifier: sme-chassis-8820[Company Enterprise OID ].1.14.9.14.5.1 sme-chassis-8620[Company Enterpri[...]

  • Page 24

    18 November 2003 8000-A2-GB3 0-10 Therefore this object will be set to the value of 127. 4. Evolution of the Interfaces Group of MIB-II (R FC 2863) The interfaces group consists of an ob ject i ndicating the number of interfaces suppo rted by the unit and an interface table containing an entry for each interface in the GranDSLAM R3.2. Since RFC 286[...]

  • Page 25

    8000-A2-GB30-10 November 2003 19 a The console will not be listed in the interface gr oup, but it will be in the entPhysicalT able of the entityMIB. b A TM Link refers to the A TM layer suppo rted over the T1/E1 or OC3 interfaces. c DSL A T M Links refers to the A TM la yer supported over the DSL interface. The following table shows how the dif f e[...]

  • Page 26

    20 November 2003 8000-A2-GB3 0-10 4.1.1.1.1 Interface indexes (ifIndex). A unique value, greater than zero number will be assigned to each interface. The following ifIndex scheme was developed by a commit tee to solve a general stack hierarchy and it is shown in Figure 1 -2 : Figure 1-2. ifIndex Scheme Where: - RR: Reserved for future use. - C C : [...]

  • Page 27

    8000-A2-GB30-10 November 2003 21 * Please refer to T able 1-6, GranDSLAM R3.2 Interface Lis t , for the exact number of interfaces supported of each cl ass in the current release. ** Console interface will not be di splayed in the ifT able. On ly in the entPhysicalT able. 4.1.2 “ifDescr” Object (ifEntry 2) This object provides the textual infor[...]

  • Page 28

    22 November 2003 8000-A2-GB3 0-10 4.1.3 “ifType” Object (ifEntry 3) This object identifies the type of the interf ace based on the physical/ link protocol(s). The IfT ype values in T able 1-8, ifIndex Assignments are su pported. 4.1.4 “ifMtu” Obj ect (ifEntry 4) This object identifies the lar gest datagram, a ssociated with a management lin[...]

  • Page 29

    8000-A2-GB30-10 November 2003 23 4.1.5 “ifSpeed” Object (ifEntry 5) This object provides the interfaces ’ s current bandwidth in bits per second. The value of this object for each interface will be specified as follows: 4.1.6 “ifPhysAddress” Object (ifEntry 6) This object is used to specify the interface’ s ad dress at its protocol sub-[...]

  • Page 30

    24 November 2003 8000-A2-GB3 0-10 4.1.8 “ifOperStatus” Object (ifEntry 8) This object is used to specify the current operational state of the interface. The value of this object for each interface will be defined as follows: T able 1-1 1. ifAdminS tatus Interface ifAdmin S tatus AAL5 Up(1) A TMUP Up(1) DSL Up(1), Down(2) DSLA TM Up(1) DSLChan U[...]

  • Page 31

    8000-A2-GB30-10 November 2003 25 4.1.9 “ifLastChange” Ob ject (ifEntry 9) This object contains the value of “sysUpT ime” at the time the interface entered its current operational state. 4.1.10 ATM and ATM Cell Management Inpu t and Output counter explanations: • ifInOctets – The number of received octets over the in terface, that is, th[...]

  • Page 32

    26 November 2003 8000-A2-GB3 0-10 4.1.11.2 “ifInUcastPkts” Object (ifEntry 11) 4.1.11.3 “ifInUncastPkts” Object (ifE ntry 12) T able 1-14. ifInUncastPkt s Interface ifInUcastPk ts AAL5 PDUs inbound:The number of AA L5 CPCS PDUs passed to a higher layer AT M U P 0 DSL 0 DSLA TM 0 DSLChan 0 E1 0 ETH1 0 IMA 0 SONET 0 SONETPath 0 T1 0 T able 1-[...]

  • Page 33

    8000-A2-GB30-10 November 2003 27 4.1.11.4 “ifInDiscards” Object (ifEntry 1 3) 4.1.11.5 “ifInErrors” Object (ifE ntry 14) T able 1-16. ifInDiscards Interface ifInDiscards AAL5 Number of AAL5 CP CS PDUs discarded AT M U P 0 DSL Number of Octets received for discard DSLA TM 0 DSLChan 0 E1 0 ETH1 0 IMA 0 SONET 0 SONETPath 0 T1/E1 0 T able 1-17.[...]

  • Page 34

    28 November 2003 8000-A2-GB3 0-10 4.1.11.6 “ifInUnknownP rotos” Object (ifEntry 15 ) 4.1.12 Output Counters (object s ifEntry 16 to ifEntry 20) 4.1.12.1 “ifOutOctets” Object (ifEntry 16) T able 1-18. ifInUnknown Protos Interface ifInUnknownPr otos AAL5 0 AT M U P 0 DSL 0 DSLA TM Number of cells dropped duri ng header validation, and cells w[...]

  • Page 35

    8000-A2-GB30-10 November 2003 29 4.1.12.2 “ifOutUcastPkts” Object (ifEntry 17) 4.1.12.3 “ifOutNUcasts” Object (ifEntry 18) T able 1-20. ifOutUcastPkt s Interface ifOutUcastPkts AAL5 PDUs outbound: The number of AAL5 CPCS PDUs received from a higher layer for transmission. AT M U P 0 DSL 0 DSLA TM 0 DSLChan 0 E1 0 ETH1 0 IMA 0 SONET 0 SONETP[...]

  • Page 36

    30 November 2003 8000-A2-GB3 0-10 4.1.12.4 “ifOutDiscards” Object (ifEntry 19) 4.1.12.5 “ifOutErrors” Object (ifEntry 20) 4.1.13 “ifOutQLen” (ifEntry 21) This object contains the length of th e output packet queue. It will contain a value assigned by the unit which is used for each interface.This object is no t supported and will return[...]

  • Page 37

    8000-A2-GB30-10 November 2003 31 4.1.14 “ifSpecific” (ifEntry 22) This object contains a referenc e to MIB definitions specific to th e particular media being used. This object is not su pported and will return a value o f 0.0 (that is, no MIB definition specific to the particular media is available). 4.2 Extension to the In tf. Table (ifXTable[...]

  • Page 38

    32 November 2003 8000-A2-GB3 0-10 4.3 Interface Stack Group - (RFC 2863) The interface stack group consists of an object containing informati on on the relationships between the multiple sub-layers of networ k interfaces. In the GranDSLAM R3.2, the interface stack group will be used to show the relationship between the multiple logical and physical[...]

  • Page 39

    8000-A2-GB30-10 November 2003 33 4.3.2 “ifStackLowerLayer” Object (ifStackEn try 2) This object provides the ifIndex corresponding t o the lower sub-layer runn ing on ‘below’ the interface specified in the co rresponding ifStackHigherLayer . * If the associated ATM link is part of an IMA gr oup ** If the associated A TM link is not part of [...]

  • Page 40

    34 November 2003 8000-A2-GB3 0-10 • snmpInP kts (snmp 1) • snmpOutPkts (snmp 2) • snmpInBadV ersions (snmp 3) • snmpInBadCommunit yUses (snmp 5) • snmpInASNParseErrs (snmp 6) • snmpInT otalReqV ars (snmp 13) • snmpInT otalSe tV ars (snmp 14 ) • snmpInGetRequests (snmp 1 5) • snmpInGetNexts (snmp 16) • snmpInSetRequests (snmp 17)[...]

  • Page 41

    8000-A2-GB30-10 November 2003 35 5. Physical Layer 5.1 ADSL MIB (RFC 2662) 5.2 ADSL-EXT MIB (draft-iet f-adslmib-adslext-xx.t xt) T able 1-28. ADSL MIB T able Comme nts adslLineEntry Suppor ted as is adslAtucPhysEntry Supported as is adslAturPhysEntry Supported as is adslAtucChanEntry Supported as is adslAturChanEntry Supported as is adslAtucPerfDa[...]

  • Page 42

    36 November 2003 8000-A2-GB3 0-10 5.3 PDN-ADSL-EXT-MIB (PDN-A DSL-LINE-EXT-MIB.mib) The objects in the pdnAdslLineEx tT abl e with a textual conventio n of PdnAdslTransmissionModeT ype are a super set of the objects in the adslLineExtT able with a textual co nvention of AdslTransmissionModeT yp e. The PdnAdslTransmissionModeT ype textual con ven ti[...]

  • Page 43

    8000-A2-GB30-10 November 2003 37 5.5 DS1 MIB (RFC 2495) 5.6 Paradyne DS1-EXT MIB (PDN-DS1E XT-MIB). This Paradyne MIB is an extension to the standard DS1 MIB (RFC 2495). This MIB provides additional DS1 and G .703 (E1) co nf iguration objects no t provided by RFC 2495. The various objects supported are shown in the fo llowing table. 5.6.1 pdnDs1Ext[...]

  • Page 44

    38 November 2003 8000-A2-GB3 0-10 5.6.3 pdnDs1ExtConfLineBuildOut (RW): This entry specifies the line build out, in d ecibel s, for a long-haul DS1 line. The possible values are: dB0Pnt0(1), dB 7Pnt5( 2), dB15Pnt0(3), dB22Pnt5(4). The default value is dB0Pnt0(1) . This object only ap plies to DS1 interfaces. 5.6.4 pdnDs1ExtConfConnector (RW): This [...]

  • Page 45

    8000-A2-GB30-10 November 2003 39 5.7 SONET-MIB (RFC 2558) 5.7.1 sonetMediumEntry 5.7.2 sonetSESthresholdSet This scalar object will be supported read-only . 5.7.3 sonetPathCurrentWidth This scalar object will be supported read-only . T able 1-34 . SONET -MIB T able Comme nts sonetMediumEntry Some objects are supported read-only sonetSectionCurrent [...]

  • Page 46

    40 November 2003 8000-A2-GB3 0-10 5.8 Paradyne SONET-EXT MI B (pdn_SonetExt.mib). 5.8.1 devSonetXmitClkSrc. This MIB object is used to configure the clock source to be used for the Sonet interface in the transmit direction. The default value is loopTiming (1) . 5.8.2 devSonetStatusLastChange. This MIB object corresponds to the sysUpT ime since this[...]

  • Page 47

    8000-A2-GB30-10 November 2003 41 5.9 SHDSL MIB (RFC 3276) 5.10 Spectrum Management (pdn_spectrummgmt.mib) This MIB is a common MIB supporte d for both ReachDSL and SHDSL ports. 5.10.1 newSpectrumMgmtGeneralConfigEntry This table is indexed by t he entPhysicalIndex and ifT ype of the ports con tained in the entity module (DSL port card). An entry in[...]

  • Page 48

    42 November 2003 8000-A2-GB3 0-10 6. Link Layer 6.1 ATM (AtoM) MIB (RFC 2515) The A TM MIB provides objects for management of the A TM Cell and AAL5 interfaces. Although primarily associ ated with mib-2 37, RFC 2515 provides 9 gro ups for support of A TM. The following table indicates the support fo r these groups. The related MIB objects are suppo[...]

  • Page 49

    8000-A2-GB30-10 November 2003 43 6.1.1.2 “atmInterfaceMaxVccs” Obj ect (atmInterfaceConfEntry 2) This object contains the maximum number of VCCs supported at this A TM interface. The only valid values for this object are: 6.1.1.3 “atmInterfaceConfVpcs” Ob ject (atmInterfaceConfEntry 3) This object contains the num ber of VPC s configured fo[...]

  • Page 50

    44 November 2003 8000-A2-GB3 0-10 6.1.1.6 “atmInterfaceMaxAct iveVciBits” Object (atm InterfaceConfEntry 6) This object contains the maximu m numb er of active VCI bits configured for use at this A TM interface. 6.1.1.7 “atmInterfaceIlmiVpi” Obj ect (atmInterfaceConfEntry 7) 6.1.1.8 This object contains the VPI value of the VCC supporting t[...]

  • Page 51

    8000-A2-GB30-10 November 2003 45 W rite access to this object is not supported 6.1.1.10 “atmInterfaceMyNeighborIfName” Object (atmInterfaceConfEntry 12) In Hybrid Management Model, the value of th is object contains the textual nam e of the interface on the neighbor system on the far end of this interface, and to which this interface connects. [...]

  • Page 52

    46 November 2003 8000-A2-GB3 0-10 6.1.1.12 “atmInterfaceCurrentMaxVciBits” Object (atmInterf aceConfEntry 14) The maximum number of VCI Bits that may currently be used at this A TM interface. 6.1.1.13 “atmInterfaceSubscrAddress” Object (atmInterfaceConfEntry 15) The identifier assigned by a serv ice provider to t he network side of a public[...]

  • Page 53

    8000-A2-GB30-10 November 2003 47 6.2 ATM Traffic Descri ptor Group (RFC 2515) This table contains a set of self-consistent A TM traffic parameters including the A TM traffic service category , The A T M virtual l ink tables (that is, VPL and VCL t ables), will use this A TM Traf fic Descriptor table to assign traf fic parameters and service categor[...]

  • Page 54

    48 November 2003 8000-A2-GB3 0-10 6.2.1.1 “atmVclOperStatus” Object (atmVclEntry 4) This object indicates the curr ent op erational status of th e VCL. Possible values are: atmVclOperStatus = up(1) - VCL is currently Operational. down(2) - VCL is currently Not Operational. unknown(3) - The state of the VCL can’t be determined. For example-all[...]

  • Page 55

    8000-A2-GB30-10 November 2003 49 6.2.2 Virtual Channel Cross Connect Group (RFC 2515) This table contains conf iguration and state inform ation of po int-to-point, point-to-multipoint or mu ltipoint-to-multipoin t VC cross-connects for PVCs. This table has read-create access and is used to cross-connect the VCLs toge ther in an A TM switch or netwo[...]

  • Page 56

    50 November 2003 8000-A2-GB3 0-10 • active • createAndGo •d e s t r o y 6.3 atmfM4MIB- SNMP M4 Network Element View MIB - [at mfM4MIB] The A TM Forum MIB - (atmfM4MIB.MIB). As defined in the A TM Forum SNMP M4 Network Element V iew MIB (AF-NM-0095.001) document. The table below shows the object of this MIB that are supported. For the GranDSLA[...]

  • Page 57

    8000-A2-GB30-10 November 2003 51 6.3.1.2 ATM Cell Layer Table (atmfM4ATMLayerEntry ) These are the A TM Forum M4 interface Confi guration table extensi ons for the A TM cell layer . The default configuration of an entry in this table is used wh enever the entries for the physical path TP , etc., are created. The manage ment system configures a UNI,[...]

  • Page 58

    52 November 2003 8000-A2-GB3 0-10 6.4 Paradyne Extensions to the ATM Int erface Config Table and ATM Forum M4. The following MIBs are intended to augment A TM Interface Config T able and A TM Forum M4 MIBs. pdn_A TMM 4Ext.mib. T able 1-57. Paradyne Extensions to A TM MIBs (1 of 2) T able Object T ype Sup- ported pdnA TMIfConfExtEntry pdn_A TMM4Ext.[...]

  • Page 59

    8000-A2-GB30-10 November 2003 53 6.5 ATM Loopback pdnA TMfM4VcLoopback T estT able in pdn_atm M4Ext.mib is suppo rted to provide detailed test results on A TM F5 loopback test. This tabul ar object augments atmfM4VcT estT able (see Section 3.15). In order to distinguish a single-cell loopback test from a multi-cell loopback test, In addition to A T[...]

  • Page 60

    54 November 2003 8000-A2-GB3 0-10 get (atmfM4TestId, atmfM4TestStatus) } /* * Is not being used right now -- let’s compete * to see who gets it. */ lock_value = atmfM4TestId if ( set(atmfM4 TestId = lock_value, atmfM4TestStatus = inUse, atmfM4TestOwner = ’my-IP-addre ss’) == FAILURE) /* * A nother manager got the atmfM4 TestEntry -- go * try [...]

  • Page 61

    8000-A2-GB30-10 November 2003 55 6.6 IMA MIB (AF-PHY-0086.001) T able 1-59. IMA MIB T able Object imaGroupNumber Supported as is (a max of 8 IMA groups) imaGroupEntry Supported as is imaGroupMappingEntry Supported as is ImaLinkEntry Supported as is ImaAlarmStatu s Supported as is imaAlarmT ype Supported as is imaGroupCurrentEntry Supported as is Im[...]

  • Page 62

    56 November 2003 8000-A2-GB3 0-10 7. Configuration Management 7.1 Entity MIB Version 2 - (RFC 2737) 7.1.1 MIB Structure. The Entity MIB (version 2) contains fiv e groups of MIB objects: - entityPhysical group Describes the physical en tities managed by a single agent. - entityLogical group Describes the logical entities managed by a single agent. -[...]

  • Page 63

    8000-A2-GB30-10 November 2003 57 7.1.2.1.1 entPhysicalIndex The index for this entry . V alid Ob ject V alue(s): The value of this object is based on the if Index in the Interfaces Group. Refer to Evolution of the Interfaces Gr oup of MI B-II (RFC 2863) on page 1-18 for further details of these indexes. The following are the values for the entPhysi[...]

  • Page 64

    58 November 2003 8000-A2-GB3 0-10 V alid Ob ject V alue(s): a. Refers to the sysDescr in the MIB- II’s System Group for clarification on Company Name. b. n is the unit number that ranges between 1..8 c. x is the sensor number that ranges between 1..3 d. y is the fan num ber that ranges between 1..1 e. z is the power supply number that rang es bet[...]

  • Page 65

    8000-A2-GB30-10 November 2003 59 .3 sme-scp-8414-card (SCP w/OC3/ STM1 SM long ATM Uplink) .4 sme-scp-8416-card (SCP w/8 port T1 IMA uplink) .5 sme-scp-8417-card (SCP w/8 port E1 IMA uplink 75 ohm) .6 sme-scp-8418-card (SCP w/8 port E1 IMA uplink 120 ohm) Company Enterprise.1.14.9.14.4 (sme -portcards) .1 sme-8965-card .2 sme-8955-card .3 sme-8985-[...]

  • Page 66

    60 November 2003 8000-A2-GB3 0-10 7.1.2.1.4 entPhysicalContainedIn The value of entPhysicalIndex for the physical entity which “contains” this physical entity . A value of zero indicates this ph ysical entity is not contained in any other physical entity . Note that the set of “containment” relationships define a strict hierarch y; that is [...]

  • Page 67

    8000-A2-GB30-10 November 2003 61 7.1.2.1.5 entPhysicalClass An indication of the general hardware type of the physical enti ty . V alid Ob ject V alue(s): The following table shows the different cla sses identified for the A TM stackable DSLAM’ s entities. 7.1.2.1.6 entPhysicalParentRelPos An indication of the relative position of this “child?[...]

  • Page 68

    62 November 2003 8000-A2-GB3 0-10 7.1.2.1.7 entPhysicalName The textual name of the physical entity . V alid Ob ject V alue(s): 7.1.2.1.8 entPhysicalHardwareRev The vendor-specific hardware revision string for the physical entity . V alid Ob ject V alue(s): T1/E1 port A value between [3..1 1] OC3 port 3 Console port 1 Ethernet Mgmt port 2 T emp Sen[...]

  • Page 69

    8000-A2-GB30-10 November 2003 63 The following table shows the entPhysi calHardwareRev defined for each entity . 7.1.2.1.9 entPhysicalSoftwareRev: The vendor-specific software revision string fo r the physical entity . If no specific firm ware programs are associated with the physical comp onent, or t his information is unknown to the agent, then t[...]

  • Page 70

    64 November 2003 8000-A2-GB3 0-10 7.1.2.1.11 entPhysicalSerialNum The vendor-specific serial number string for th e physical entity . V alid Object V alue(s): The following table shows the entPhysi calSerialNum identified for the entities su pported. 7.1.2.1.12 entPhysicalMfgName The name of the manufacturer of this phys ical component. The pr efer[...]

  • Page 71

    8000-A2-GB30-10 November 2003 65 The following table shows the entPhysi calMfgName designated for the entities. 7.1.2.1.13 entPhysicalModelName The vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number , which may be printed on the component itself. If the model[...]

  • Page 72

    66 November 2003 8000-A2-GB3 0-10 7.1.2.1.14 entPhysicalAlias This object is an 'alias' name for the physical entity as specified by a network manager , and provides a non-volatilehand le' for the physical entity . On the first instanti ation of an physical entity , the valueof entPhysicalAlias a ssociated with that en tity is set to[...]

  • Page 73

    8000-A2-GB30-10 November 2003 67 7.1.2.1.15 entP hysicalA ssetID This object is a user-assigned as set tracking identi fier for the physical entity as specified by a network manager, and provides non-volatile storage of this inform ation. I f no asset tracking informatio n is associated w ith the physi cal component, then this object will contain a[...]

  • Page 74

    68 November 2003 8000-A2-GB3 0-10 7.1.2.2 entityLogical Group. The entLogicalT able { en tityLogi cal 1} described below shows the attributes supported for each the physical entities. For the GranDSLAM R3 .2 product, there will be 1 ro w associated to the MCP if it is physical ly coexisting in the same chassis with the SCP card. The SCP will not be[...]

  • Page 75

    8000-A2-GB30-10 November 2003 69 The value of this object will be mib-2. 7.1.2.2.4 entLogicalTAddress. The value of this object will be the IpAddress and UDP port used to access the MC P card. 7.1.2.2.5 entLogicalIPDomain. The value of this object will be the kind of transport service by which the MCP card can receive management traffic. This value[...]

  • Page 76

    70 November 2003 8000-A2-GB3 0-10 7.1.2.5 entityGeneral Group. This group will be supported as specified in RFC 2737. 7.1.2.6 entityNotif ications Group An entConfigChange notification is genera ted when the value of entLastChangeT ime changes. It can be utilized by an NMS to tr igger logical/physical en tity table maintenance polls. This trap will[...]

  • Page 77

    8000-A2-GB30-10 November 2003 71 7.2.2 mpeEntPhysicalExtOperStatus This is a read-only object that allows managers to determine the operational status of the entities in the m anaged device. The possib le s values are ’up’, ’down’ and ’ testing’. 7.3 Entity Sensor MIB (RFC 3433): This MIB has only one group (entitySensorV alueGroup) whi[...]

  • Page 78

    72 November 2003 8000-A2-GB3 0-10 7.4.1.1 ifMauIfIndex (RO): This variable uniquely identifies the in terface to which the MAU described b y this entry is connected. This value corresponds to the ifIndex of the interface. 7.4.1.2 ifMauIndex (RO): This variable uniquely identifies the MAU described by this entry from among ot her MAUs connected to t[...]

  • Page 79

    8000-A2-GB30-10 November 2003 73 dot3MauT ype100BaseFXHD, dot3MauT ype100BaseFXFD, dot3MauT y pe100BaseT2HD, dot3MauT ype100BaseT2FD, etc. 7.4.1.4 ifMauSt atus (RO): The current state of the MAU. 7.4.1.5 ifMauDefaultType (RW): This object identifies the default administrative baseba nd MAU type, to be used in conjunction with the operational MAU ty[...]

  • Page 80

    74 November 2003 8000-A2-GB3 0-10 7.6.1 pdnMgmtIpPortTable This is the IP Port T able. There is one entr y per IP port/interface in the system.This table contains the configuration deta ils of each Ip port. This tabl e is indexed on the interface index of the IP port. 7.6.1.1 pdnMgmtIpPortIndex (NA) The index assigned to the IP Po rt. Currently , n[...]

  • Page 81

    8000-A2-GB30-10 November 2003 75 7.6.1.2 pdnMgmtIpAddress (RW). The IP address assigned to this port. If the pdnMgmtIpConfig Mode is set to modes other than ’manual’, then the MAX-ACCESS for this object is read-only and the value of the object represents the actual IP address assigned to the port by th e DHCP client (or 0.0. 0.0, if none assign[...]

  • Page 82

    76 November 2003 8000-A2-GB3 0-10 7.6.2 pdnMgmtAtmInvArpTable. This table contains one row per Inverse A TM AR P entry in the system. This table maps the <ifIndex, vpi, vci> index to corresponding <i pPortIndex, remoteIp> of the pdnMgmtIpPortT able in 3.30.1. 7.6.2.1 pdnMgmtAtmIfIndex (NA) The interface index associated with the A TM PV[...]

  • Page 83

    8000-A2-GB30-10 November 2003 77 7.7.2 Supporting MIBs. 7.7.3 SNMP-MPD-MIB (RFC 3412) This MIB provides statistics for message pro cessing. The following scalar MIB objects will be supported to provid e statistics about invalid or unknown conditions in th e message processing: 7.7.3.1 snmpUnknownSecurityModels 7.7.3.2 snmpInvalidMsgs 7.7.3.3 snmpUn[...]

  • Page 84

    78 November 2003 8000-A2-GB3 0-10 7.7.4.5.3 snmpTargetParmsTable: It is used to configure target parameters (messa ge processing level, secu rity model, etc.) that will be used in the generation of SNMP no tification messages. This table will be supported read-only with default entries as indicat ed in section 7.7.4.6.4 and 7.7.4.6.5 7.7.4.5.4 snmp[...]

  • Page 85

    8000-A2-GB30-10 November 2003 79 7.7.5 User-based Security Model (USM) RFC 34 14 RFC 3414 discusses the “User-based security model” for SNMPv3. It defines the elements of procedure for providing SNMP message-l evel security . The mechanisms to be implemented related to this feature are Disc overy and T imeliness, Auth entication, Privacy and Ke[...]

  • Page 86

    80 November 2003 8000-A2-GB3 0-10 7.7.6.1.1 vacmContextTable. It defines the locally av ailable contexts. This table is r ead-only and can not be configured by SNMP . 7.7.6.1.2 vacmSecurityToGroupTable. It maps a securityModel and securityName to a groupNam e. Supported read-only with default values. 7.7.6.1.3 vacmAccessTable. It maps a groupName, [...]

  • Page 87

    8000-A2-GB30-10 November 2003 81 7.8 Link Fault Management. This sections describes the mibs associated with the Automatic Protection Sw itching (APS), Manual Dual Link Load Sharing (DLLS) and Redund ancy Features. 7.8.1 Automatic Protection Switching (APS) - draft-ietf-atomm ib-sonetaps-mib-xx.txt This MIB objects are used to control and manage SO[...]

  • Page 88

    82 November 2003 8000-A2-GB3 0-10 7.8.2 Link Load Sharing (LLS) - ( PDN-LINK-LOAD-S HARING-MIB.mib ) The object pdnLinkLoadSharingSelection is used to enable Load Sharin g in the device. By default Load Sharing is disabled . 7.8.2.1 pdnLLSConfigGroupName. This object contains a text describing a gro up configured for load sharing. 7.8.2.2 pdnLLSCon[...]

  • Page 89

    8000-A2-GB30-10 November 2003 83 7.8.4.1 pdnRedunCommand. This MIB object allows managers to command an action t o an entity module (given by the entPhysicalIndex), configured for redundancy . The supported commands are switch(2) and forceswitch (3). The value no Cmd (1) will be returned when no previous command had been issued. Users should specif[...]

  • Page 90

    84 November 2003 8000-A2-GB3 0-10 8. Timing and Clocking 8.1 Paradyne mpe_Config MIB (mpe_Config.mib ) The tabular object m peDevConfigClockSrcEn try defined i n mpe_Config.mib provides the capability of choosing network timing reference source on the GranDSLAM. The mpeDevCfgClkWhichSrc object takes the followi ng two values: • primary(1), this c[...]

  • Page 91

    8000-A2-GB30-10 November 2003 85 disable(1) - T ests will not be terminated based on a timer and enable(2) - T e sts will be terminated after the durati on specified by devConfigT estDuration. This object specifies whether tests are to be te rminated after a defined duration. If the value is enable(2), the duration is defined by devConfigT estDurat[...]

  • Page 92

    86 November 2003 8000-A2-GB3 0-10 8.3.5 devNTPEnable (RW): .Indicates whether or not th e local clock is synchronized via NTP/ SNTP . When set to enabled(1), NTP/SNTP is operational and will attempt to synchronize the local clock based on the message(s) received from an NTP/SN TP server . Default value is enabled(1). 8.3.6 devNTPOffsetFromUTC: .Off[...]

  • Page 93

    8000-A2-GB30-10 November 2003 87 9. Access Control and Security. 9.1 Paradyne DSLAM System Mib [ pdn_dsla m.mib] (pdn- common 24) . Support for the pd n_dslam MIB is provided to enable a n NMS access certain objects that are specific to this product. The various object s are described in the abov e table. 9.1.1 sysDevUserAccountTable: This table co[...]

  • Page 94

    88 November 2003 8000-A2-GB3 0-10 9.2 Paradyne Security MIB (pdn_Security.mib): The pdn_security MIB is used for enabling appli cations control security aspects of the unit for the purpose of T elnet, FTP , and so on. The various objects suppo rted are as follows: 9.2.1 devSecurityMgrVali dation (RW): This object is used to either enable or disable[...]

  • Page 95

    8000-A2-GB30-10 November 2003 89 9.2.4.4 securityMgrTelnetAccess(RW): This is used to specify the telnet access to the device. This object is tied with the securityMgrSnmpAccess and secu rityMgrFtpAccess. That is , changing the T elnetAccess will also change those two objects. 9.2.4.5 securityMgrFtpAccess (RW): This is used to specify the ftp acces[...]

  • Page 96

    90 November 2003 8000-A2-GB3 0-10 9.3 Paradyne Control MIB (mpe_Control.mib) T able 1-96. mpe_Control.mib (1 of 2) T able Object T ype Supported mpeDevControlT able Ye s mpeDevControlRes et(1) ResetStat es Y es entPhysicalIndex PhysicalIndex Y es mpeDevFileXferConfigT able Ye s entPhysicalIndex Integer32 Y es mpeDevFileXferFileName(1) DisplayString[...]

  • Page 97

    8000-A2-GB30-10 November 2003 91 9.3.1 mpeDevControlTable: This table is indexed on the entPhysicalIndex and contains mpeD evControlReset object which is used to reset the associated entity (for example, card). W riting the val ue reset (2) to this object initiates a Hardware power-on reset of the entity . Writing the value resetT oFactoryDefaults [...]

  • Page 98

    92 November 2003 8000-A2-GB3 0-10 9.3.2 mpeDevFirmwareControlTable : This table contains a list of th e current Firmware Releases and their associated status. Each Firmware Release will be indexed by a number from 1 to N. The user will be able to view the Firmware Release S tring and Operational Stat us of the release (valid or invalid) and activat[...]

  • Page 99

    8000-A2-GB30-10 November 2003 93 10. Status and Ala rms. 10.1 Paradyne Syslog MIB (pdn_syslog.mib): The pdn_syslog MIB defines a collection of objects for managing sy slog messages. The objects are used to configure both syslog functi ons and syslog daemons. This MIB also allows one to retrieve syslog message from a device. 10.1.1 pdnSyslogStatus ([...]

  • Page 100

    94 November 2003 8000-A2-GB3 0-10 10.1.5 pdnSyslogSeverityThreshold (RW) : The valid values are emerg (0), alert (1), cr itical (2), error (3), warning (4), notice (5), info (6), debug (7). This value corresponds to a minimum severi ty level that a sysl og messages can be set. All syslog message with an enum value greater than the threshold will no[...]

  • Page 101

    8000-A2-GB30-10 November 2003 95 10.1.12 pdnSyslogRateLimiti ng (RW): V alid values are disable (1), enable (2). This allows one to enable or disabl e rate limitiming. When rate limiting is enabled, it prevents th e exact same message from being resent within a fixed amount of t ime. 10.2 Paradyne Health and Status MIB (mpe_HealthAndStatus.mib) The[...]

  • Page 102

    96 November 2003 8000-A2-GB3 0-10 DSX T raps dsx1LineSt atusChange "The dsx1LineS tatu s has changed on a dsx1 interface." A TM-M4 T raps atmfM4IfAisAlarm "AIS alarm det ected." atmfM4IfLcdAlarm "Los s of Ce ll delineation detected." atmfM4IfLosAlarm "Loss of Signal detected." atmfM4IfLofAlarm "Loss of F[...]

  • Page 103

    8000-A2-GB30-10 November 2003 97 hdsl2ShdslnoNeighborPresent "No Neighbor Present status has changed for this Endpoint." hdsl2ShdslLocalPowerLoss " Impending unit failure due to loss of lo cal power condition has been detected ." SONET LINEAR APS MIB T raps: apsEventSwitchover "Switchove r status has changed." apsEvent[...]

  • Page 104

    98 November 2003 8000-A2-GB3 0-10 IMA T raps imaFailureAlarm "Alarm c ondition on Ima interface." T able 1-99. devLastT rapS tring (4 of 4) T rap devL astT rapS tring[...]

  • Page 105

    8000-A2-GB30-10 November 2003 IN-1 Index A Access Control, 187 ADSL extension MIB, 135 MIB, 135 traps, 111, 197 adslAtucInitFailureTrap, 112 adslAtucPerfESsThreshTrap, 111 adslAtucPerfLofsThreshTrap, 111 adslAtucPerfLolsThreshTrap, 112 adslAtucPerfLossThreshTrap, 111 adslAtucRateChangeTrap, 111 adslAtucSesLThreshTrap, 112 adslAtucUasLThreshTrap, 11[...]

  • Page 106

    Index IN-2 November 2003 8000-A2-GB30-10 Enterprise-Specific MIB, 173 traps, 110, 197 Entity MIB, 156 extension, 170 traps, 196 Entity Redundancy, 182 Entity Sensor MIB, 171 entityLogical Group, 168 entPhySensorEntry, 171 entPhysicalAlias, 166 entPhysicalAssetID, 167 entPhysicalChildIndex, 170 entPhysicalClass, 161 entPhysicalContainedIn, 1 60 entP[...]

  • Page 107

    Index 8000-A2-GB30-10 November 2003 IN-3 MIB standards compl iance, 114 supported, 11 MIB-II organization, 116 SNMP Group, 133 Transmission Group, 133 model numbers, 11 mpe_Control.mib, 190 mpe_HealthAndStatus.mib, 195 mpeCcn, 110 mpeDevConfigClockSrcEntry, 18 4 mpeDevControlTable, 190 mpeDevHealthAndStatusEn try, 195 mpeEntPhysicalExtEntry, 170 mp[...]

  • Page 108

    Index IN-4 November 2003 8000-A2-GB30-10 sysDevUserAccountTable, 187 Syslog MIB, 193 sysObjectID, 117 sysServices, 117 System Group, 116 T TC Adapter Layer table, 150 TC Sublayer Group, 146 Timing, 184 Traffic Descriptor Types, 147 Transmission Group, 133 traps ADSL, 197 ATM-M4, 196 devLastTrapString, 195 DSX, 196 Enterprise-Specific, 197 Entity MI[...]