Hotwire GranDSLAM Reference Manual

ManualsBrandsParadyne ManualsPower SupplyBroadband Access Concentrator 8820

Hotwire 8620 and 8820

GranDSLAM

SNMP Reference

Document No. 8000-A2-GB30-00

June 2003

Summary of content (108 pages)

PAGE 1
Hotwire 8620 and 8820 GranDSLAM SNMP Reference Document No.
PAGE 2
Copyright © 2003 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of Paradyne Corporation, 8545 126th Ave. N.
PAGE 3
Contents About This Guide 1 Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . iii Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Network Management Specification GranDSLAM 3.0 Network Management Interface . . . . . . . . . . . . . . . . 1 Standards Compliance for SNMP Traps . . . . . . . . . . . . . . . . . . . .
PAGE 4
Contents ii June 2003 8000-A2-GB30-00
PAGE 5
About This Guide Document Purpose and Intended Audience This reference manual contains the network management specification for the Hotwire GranDSLAM 8620 and 8820 Release 3.0 and above. It is designed for network managers who use SNMP in the course of installing, configuring, monitoring, and troubleshooting GranDSLAM chassis and associated cards.
PAGE 6
About This Guide Product-Related Documents Complete documentation for this product is available online at www.paradyne.com. Select Support → Technical Manuals → Hotwire DSL Systems.
PAGE 7
Network Management Specification 1 1. GranDSLAM 3.0 Network Management Interface This document describes the SNMP support for the GranDSLAM 3.0 product. The product includes the following models: Table 1-1. Model Numbers for the GranDSLAM 3.0 Product Type Model Description Release SHDSL 8985 ATM Card, 24 SHDSL Ports R3.0 ReachDSL-V3 8955 ATM Card, 24 ReachDSL-V3 Ports R3.0 ADSL 8965 ATM Card, 24 ADSL Ports R3.0 SCP 8412-A1-000, SCP with OC3/STM1 MM ATM uplink R3.
PAGE 8
1. Network Management Specification Table 1-2.
PAGE 9
1. Network Management Specification Table 1-2. Supported RFCs and MIBs (3 of 5) RFC Name Description N/A IMA MIB The MIB module for managing ATM Forum Inverse Multiplexing for ATM (IMA) interfaces. AF-PHY-0086.001 (http://www.atmforum.com/atmforum/s pecs/approved.
PAGE 10
1. Network Management Specification Table 1-2.
PAGE 11
1. Network Management Specification Table 1-2. Supported RFCs and MIBs (5 of 5) RFC Name Description enterprise pdn_Config.mib devConfigTestTimer enterprise pdn_Security.mib [devSecurityMgrValidation], [devSecurityMgrMaxNumber], [devSecurityMgrCurrentNumber], [securityMgrTable] enterprise pdn_time.mib [devTimeAndDate], [devNTP] enterprise pdn_syslog.mib [pdnSyslog], [pdnSyslogEntry] enterprise pdn_dslam.mib [sysDevUserAccountEntry] enterprise pdn_spectrummgmt.
PAGE 12
1. Network Management Specification Table 1-3. Other Supported RFCs Used as Guidelines for Implementation RFC Name/Description 768 User Datagram Protocol 791 Internet Protocol 792, 950 Internet Control Message Protocol; Internet Standard Subnetting Procedure 793 Transmission Control Protocol 826 Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48.
PAGE 13
1. Network Management Specification 2. Standards Compliance for SNMP Traps This section describes the standards compliance and any special operational features/options for the SNMP Traps supported by the GranDSLAM 3.0 products. The following traps are supported. Table 1-4. Summary of Traps (1 of 7) Trap Description VarBind(s) Standard Traps LinkDown Signifies that the unit has recognized a failure in one of the communication interfaces.
PAGE 14
1. Network Management Specification Table 1-4. Summary of Traps (2 of 7) Trap Description VarBind(s) atmfM4IfLofAlarm LOF (Loss of Frame) condition has occurred. ifIndex, ifOperStatus, atmfM4TrapAlarmSeverity devLastTrapString atmfM4VclXConnCreated Indicates that the VCL cross-connection has just been created. When a cross-connection is created along with its VCL endpoints, this trap should be emitted to indicate the creation of the entire group of objects.
PAGE 15
1. Network Management Specification Table 1-4. Summary of Traps (3 of 7) Trap Description VarBind(s) hdsl2ShdslPerfSESThresh This notification indicates that the severely errored seconds threshold has been reached/exceeded for the HDSL2/SHDSL segment endpoint. hdsl2ShdslEndpointCurr15MinSES, This notification indicates that the CRC anomalies threshold has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
PAGE 16
1. Network Management Specification Table 1-4. Summary of Traps (4 of 7) Trap Description VarBind(s) hdsl2ShdslprotocolInitFailure This notification indicates that the bit setting forprotocolInitFailure in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed. hdsl2ShdslEndpointCurrStatus This notification indicates that the bit setting for noNeighborPresent in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed.
PAGE 17
1. Network Management Specification Table 1-4. Summary of Traps (5 of 7) Trap Description VarBind(s) devSonetStatusChange A devSonetStatusChange trap is sent when the value of an instance of sonetSectionCurrentStatus or sonetLineCurrentStatus or sonetPathCurrentStatus changes.
PAGE 18
1. Network Management Specification Table 1-4. Summary of Traps (6 of 7) Trap Description VarBind(s) adslAtucPerfLolsThreshTrap Loss of Link 15-minute interval threshold reached ifIndex adslAtucPerfCurr15MinLols adslAtucThresh15MinLols devLastTrapString adslAtucInitFailureTrap ATUC initialization failed.
PAGE 19
1. Network Management Specification Table 1-4. Summary of Traps (7 of 7) Trap Description VarBind(s) adslAturSesLThreshTrap Severly errored seconds 15 minutes threshold reached ifIndex adslAturPerfCurr15MinSesL devLastTrapString adslAturUasLThreshTrap Unavailable seconds 15 minutes threshold reached ifIndex adslAturPerfCurr15MinUasL devLastTrapString IMA Traps imaFailureAlarm The imaFailureAlarm provides a method for an agent implementing IMA to notify an NMS of an alarm condition.
PAGE 20
1. Network Management Specification 3. Standards Compliance to SNMP MIBs This section describes the standards compliance and any special operational features/options for the SNMP MIBs supported on the GranDSLAM 3.0 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 particular object does not exist in the MIB tree Mandatory groups will be supported as is.
PAGE 21
1. Network Management Specification Port Cards ACTIVE SCP card on slot 19 entPhysicalIndex=01190001 entPhysicalIndex=01010001 Slot 1 ETH rs-232 T1/E1 IMA Child-card ATM DSL Chan ADSL slot 19 entPhysicalIndex=01020001 Slot 2 AAL5 IMA ATM ATM DSL Chan ReachDSL SonetPath DS1 Sonet STANDBY SCP card slot 20 entPhysicalIndex=01200001 ETH entPhysicalIndex=01180001 Slot 18 T1/E1 IMA Child-card slot 20 ATM AAL5 SHDSL IMA ATM SonetPath DS1 Figure 1-1.
PAGE 22
1. Network Management Specification 3.1 Management Information Base (MIB)-II - RFC 1213. The objects defined by MIB-II are organized into 10 different groups. The GranDSLAM 3.0 will implement only those groups where the semantics of the group are applicable to the implementation of the stack (for example, if EGP is not implemented the EGP group will not be supported). The MIB-II object groups supported by the GranDSLAM 3.0 are as follows: System Group Supported.
PAGE 23
1. Network Management Specification 3.2.2 “sysObjectID” Object (system 2) This object provides the authoritative identification of the network management subsystem contained in the unit. This object will be set to display the following object identifier: sme-chassis-8820[Company Enterprise OID].1.14.9.14.5.1 sme-chassis-8620[Company Enterprise OID].1.14.9.14.5.2 3.2.
PAGE 24
1. Network Management Specification Therefore this object will be set to the value of 127. 4. Evolution of the Interfaces Group of MIB-II (RFC 2863) The interfaces group consists of an object indicating the number of interfaces supported by the unit and an interface table containing an entry for each interface in the GranDSLAM 3.0. Since RFC 2863 is an SNMPv2 MIB it will be converted to SNMPv1 for support by the GranDSLAM 3.0.
PAGE 25
1. Network Management Specification Table 1-6. GranDSLAM 3.
PAGE 26
1. Network Management Specification 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 committee to solve a general stack hierarchy and it is shown in Figure 1-2: R R C Figure 1-2. C S S L P P P ifIndex Scheme Where: - RR: Reserved for future use. - CC: Chassis number from 1..99. For the GranDSLAM 3.0, this value will always be 1, identifying the 8820 or the 8620 chassis.
PAGE 27
1. Network Management Specification Table 1-8. ifIndex Assignments Interface* Interface Name (ifName) ** Interface Type (IANAifType) ifInterface Index (ifIndex) Interface Descr (ifDescr) rs232 (33) ccss1801 “Console port in unit ’cc’, slot ‘ss” Console port CONx Ethernet Mgmt port ETHx ethernetCsmacd(6) ccss1802 “Ethernet Management port in unit ’cc’, slot ‘ss” T1 T1_x ds1 (18) ccss190x “T1 interface in unit ‘cc’, slot ‘ss‘ ” Where x=[1..
PAGE 28
1. Network Management Specification 4.1.3 “ifType” Object (ifEntry 3) This object identifies the type of the interface based on the physical/link protocol(s). The IfType values in Table 1-8, ifIndex Assignments are supported. 4.1.4 “ifMtu” Object (ifEntry 4) This object identifies the largest datagram, associated with a management link, which can be sent/received on the interface. ifMTU will have the following values:. Table 1-9.
PAGE 29
1. Network Management Specification 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: Table 1-10. ifSpeed Interface ifSpeed AAL5 0 ATMUP 155000000 DSL 16000000 DSLATM 16000000 DSLChan 16000000 E1 2048000 ETH 100000000 IMA [1544000..8*2048000] SONET 155000000 SONETPath 155000000 T1 1544000 4.1.
PAGE 30
1. Network Management Specification Table 1-11. ifAdminStatus Interface ifAdminStatus AAL5 Up(1) ATMUP Up(1) DSL Up(1), Down(2) DSLATM Up(1) DSLChan Up(1) E1 Up(1), Down(2) ETH1 Up(1), Down(2) IMA Up(1), Down(2) SONET Up(1), Down(2) SONETPath Up(1), Down(2) T1 Up(1), Down(2) 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: Table 1-12.
PAGE 31
1. Network Management Specification 4.1.9 “ifLastChange” Object (ifEntry 9) This object contains the value of “sysUpTime” at the time the interface entered its current operational state. 4.1.10 ATM and ATM Cell Management Input and Output counter explanations: • ifInOctets – The number of received octets over the interface, that is, the number of received, assigned cells, multiplied by 53.
PAGE 32
1. Network Management Specification 4.1.11.2 “ifInUcastPkts” Object (ifEntry 11) Table 1-14. ifInUncastPkts Interface ifInUcastPkts AAL5 PDUs inbound:The number of AAL5 CPCS PDUs passed to a higher layer ATMUP 0 DSL 0 DSLATM 0 DSLChan 0 E1 0 ETH1 0 IMA 0 SONET 0 SONETPath 0 T1 0 4.1.11.3 “ifInUncastPkts” Object (ifEntry 12) Table 1-15.
PAGE 33
1. Network Management Specification 4.1.11.4 “ifInDiscards” Object (ifEntry 13) Table 1-16. ifInDiscards Interface ifInDiscards AAL5 Number of AAL5 CPCS PDUs discarded ATMUP 0 DSL Number of Octets received for discard DSLATM 0 DSLChan 0 E1 0 ETH1 0 IMA 0 SONET 0 SONETPath 0 T1/E1 0 4.1.11.5 “ifInErrors” Object (ifEntry 14) Table 1-17. ifInErrors 8000-A2-GB30-00 Interface ifInErrors AAL5 Number of errored AAL5 CPCS PDUs received.
PAGE 34
1. Network Management Specification 4.1.11.6 “ifInUnknownProtos” Object (ifEntry 15) Table 1-18. ifInUnknownProtos Interface ifInUnknownProtos AAL5 0 ATMUP 0 DSL 0 DSLATM Number of cells dropped during header validation, and cells with unrecognized header patterns DSLChan 0 E1 0 ETH1 PDUs of incorrect type IMA 0 SONET 0 SONETPath 0 T1/E1 0 4.1.12 Output Counters (objects ifEntry 16 to ifEntry 20) 4.1.12.1 “ifOutOctets” Object (ifEntry 16) Table 1-19.
PAGE 35
1. Network Management Specification 4.1.12.2 “ifOutUcastPkts” Object (ifEntry 17) Table 1-20. ifOutUcastPkts Interface ifOutUcastPkts AAL5 PDUs outbound: The number of AAL5 CPCS PDUs received from a higher layer for transmission. ATMUP 0 DSL 0 DSLATM 0 DSLChan 0 E1 0 ETH1 0 IMA 0 SONET 0 SONETPath 0 T1/E1 0 4.1.12.3 “ifOutNUcasts” Object (ifEntry 18) Table 1-21.
PAGE 36
1. Network Management Specification 4.1.12.4 “ifOutDiscards” Object (ifEntry 19) Table 1-22. ifOutDiscards Interface ifOutDiscards AAL5 0 ATMUP 0 DSL 0 DSLATM 0 DSLChan 0 E1 0 ETH1 0 IMA 0 SONET 0 SONETPath 0 T1/E1 0 4.1.12.5 “ifOutErrors” Object (ifEntry 20) Table 1-23. ifOutErrors Interface ifOutErrors AAL5 0 ATMUP 0 DSL 0 DSLATM 0 DSLChan 0 E1 0 ETH1 0 IMA 0 SONET 0 SONETPath 0 T1/E1 0 4.1.
PAGE 37
1. Network Management Specification 4.1.14 “ifSpecific” (ifEntry 22) This object contains a reference to MIB definitions specific to the particular media being used. This object is not supported and will return a value of 0.0 (that is, no MIB definition specific to the particular media is available). 4.2 Extension to the Intf. Table (ifXTable) - (RFC 2863) The Extension to the interface table contains additional objects for the interface table.
PAGE 38
1. Network Management Specification 4.3 Interface Stack Group - (RFC 2863) The interface stack group consists of an object containing information on the relationships between the multiple sub-layers of network interfaces. In the GranDSLAM 3.0, the interface stack group will be used to show the relationship between the multiple logical and physical interfaces, if a physical interface exists. The ifStackTable entries for the product is illustrated below, please refer to Table 1-6, GranDSLAM 3.
PAGE 39
1. Network Management Specification 4.3.2 “ifStackLowerLayer” Object (ifStackEntry 2) This object provides the ifIndex corresponding to the lower sub-layer running on ‘below’ the interface specified in the corresponding ifStackHigherLayer. Table 1-27. ifStackLowerLayer GranDSLAM 3.0 Higher Interface Number GranDSLAM 3.
PAGE 40
1.
PAGE 41
1. Network Management Specification 5. Physical Layer 5.1 ADSL MIB (RFC 2662) Table 1-28.
PAGE 42
1. Network Management Specification 5.3 Paradyne ReachDSL MIB (pdn_reachDSL.mib) This Paradyne enterprise MIB provides objects for configuration of objects specific to ReachDSL devices as well as for Spectrum Management objects specific to ReachDSL products. The various objects supported are shown in the following table. Table 1-30.
PAGE 43
1. Network Management Specification The various objects supported are shown in the following table. Table 1-32. DS1-EXT MIB Table Comments pdnDs1ExtConfTable Supported objects: pdnDs1ExtConfLineLengthType pdnDs1ExtConfLineLength pdnDs1ExtConfLineBuildOut pdnDs1ExtConfConnector 5.5.1 pdnDs1ExtConfLineLengthType (RW): This entry specifies the type of loop length for the interface. The posibble values are shortHaul(1), longHaul(2). short-haul is intended for intra-building use.
PAGE 44
1. Network Management Specification 5.6 SONET-MIB (RFC 2558) Table 1-33.
PAGE 45
1. Network Management Specification 5.7 Paradyne SONET-EXT MIB (pdn_SonetExt.mib). Table 1-35. SONET-EXT MIB Table Comments devSonetConfigEntry_t Supported as is 5.7.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.7.2 devSonetStatusLastChange. This MIB object corresponds to the sysUpTime since this Sonet interface entered the current line status. 5.7.
PAGE 46
1. Network Management Specification 5.8 SHDSL MIB (RFC 3276) Table 1-36.
PAGE 47
1. Network Management Specification 6. Link Layer 6.1 ATM (AtoM) MIB (RFC 2515) The ATM MIB provides objects for management of the ATM Cell and AAL5 interfaces. Although primarily associated with mib-2 37, RFC 2515 provides 9 groups for support of ATM. The following table indicates the support for these groups. The related MIB objects are supported in the DSLATM, ATMUP and AAL5 interfaces as they apply per RFC 2515. Please refer to Table 1-6, GranDSLAM 3.
PAGE 48
1. Network Management Specification 6.1.1.2 “atmInterfaceMaxVccs” Object (atmInterfaceConfEntry 2) This object contains the maximum number of VCCs supported at this ATM interface. The only valid values for this object are: Table 1-40. atmInterfaceMaxVccs Interface atmInterfaceMaxVccs DSLATM 4 ATMUP 8192 AAL5 10 6.1.1.3 “atmInterfaceConfVpcs” Object (atmInterfaceConfEntry 3) This object contains the number of VPCs configured for use at this ATM interface. Table 1-41.
PAGE 49
1. Network Management Specification 6.1.1.6 “atmInterfaceMaxActiveVciBits” Object (atmInterfaceConfEntry 6) This object contains the maximum number of active VCI bits configured for use at this ATM interface. Table 1-44. atmInterfaceMaxActiveVciBits Interface atmInterfaceMaxActiveVciBits DSLATM 6 ATMUP 10 AAL5 6 6.1.1.7 “atmInterfaceIlmiVpi” Object (atmInterfaceConfEntry 7) 6.1.1.8 This object contains the VPI value of the VCC supporting the ILMI on the ATM Interface.
PAGE 50
1. Network Management Specification Write access to this object is not supported Table 1-47. atmInterfaceMyNeighborIpAddress Interface atmInterfaceMyNeighborIpAddress Access DSLATM 0.0.0.0 Read-Only ATMUP 0.0.0.0 Read-Only AAL5 0.0.0.0 Read-Only 6.1.1.
PAGE 51
1. Network Management Specification 6.1.1.12 “atmInterfaceCurrentMaxVciBits” Object (atmInterfaceConfEntry 14) The maximum number of VCI Bits that may currently be used at this ATM interface. Table 1-50. atmInterfaceCurrentMaxVciBits Interface atmInterfaceCurrentMaxVpiBits DSLATM 6 ATMUP 10 AAL5 6 6.1.1.13 “atmInterfaceSubscrAddress” Object (atmInterfaceConfEntry 15) The identifier assigned by a service provider to the network side of a public network UNI.
PAGE 52
1. Network Management Specification 6.
PAGE 53
1. Network Management Specification 6.2.1.1 “atmVclOperStatus” Object (atmVclEntry 4) This object indicates the current operational status of the 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 VCLs for a given interface will be created automatically once the box comes up initially. These VCLs will be given an OperStatus of unknown. 6.2.1.
PAGE 54
1. Network Management Specification 6.2.2 Virtual Channel Cross Connect Group (RFC 2515) This table contains configuration and state information of point-to-point, point-to-multipoint or multipoint-to-multipoint VC cross-connects for PVCs. This table has read-create access and is used to cross-connect the VCLs together in an ATM switch or network that belong to a VC connection. The atmVcCrossConnectIndex is used to associate the related VCLs that are cross-connected together.
PAGE 55
1. Network Management Specification • active • createAndGo • destroy 6.3 atmfM4MIB- SNMP M4 Network Element View MIB - [atmfM4MIB] The ATM Forum MIB - (atmfM4MIB.MIB). As defined in the ATM Forum SNMP M4 Network Element View MIB (AF-NM-0095.001) document. The table below shows the object of this MIB that are supported. For the GranDSLAM 3.0 product VP switching is not supported. Table 1-55.
PAGE 56
1. Network Management Specification 6.3.1.2 ATM Cell Layer Table (atmfM4ATMLayerEntry) These are the ATM Forum M4 interface Configuration table extensions for the ATM cell layer. The default configuration of an entry in this table is used whenever the entries for the physical path TP, etc., are created.
PAGE 57
1. Network Management Specification 6.4 Paradyne Extensions to the ATM Interface Config Table and ATM Forum M4. The following MIBs are intended to augment ATM Interface Config Table and ATM Forum M4 MIBs. pdn_ATMM4Ext.mib. Table 1-56. Paradyne Extensions to ATM MIBs (1 of 2) Table Object Type pdnATMIfConfExtEntry pdn_ATMM4Ext.
PAGE 58
1. Network Management Specification Table 1-56. Paradyne Extensions to ATM MIBs (2 of 2) Table Object Supported Type pdnATMVclCurrEntry Yes (pdn_ATMStats.mib) pdnATMVclCurrElapsedTime Gauge32 Read-Only pdnATMVclCurrTotalCellIns Gauge32 Read-Only pdnATMVclCurrTotalInDiscards Gauge32 n pdnATMVclCurrTotalCellOuts Gauge32 Read-Only pdnATMVclCurrTotalOutDiscards Gauge32 Read-Only pdnATMVclHistEntry pdnATMVclHistIndex INTEGER Read-Only (pdn_ATMStats.
PAGE 59
1. Network Management Specification get (atmfM4TestId, atmfM4TestStatus) } /* * Is not being used right now -- let’s compete * to see who gets it. */ lock_value = atmfM4TestId if ( set(atmfM4TestId = lock_value, atmfM4TestStatus = inUse, atmfM4TestOwner = ’my-IP-address’) == FAILURE) /* * Another manager got the atmfM4TestEntry -- go * try again */ goto try_again; /* * I have the lock */ set up any test parameters.
PAGE 60
1. Network Management Specification 6.6 IMA MIB (AF-PHY-0086.001) Table 1-58.
PAGE 61
1. Network Management Specification 7. Configuration Management 7.1 Entity MIB Version 2 - (RFC 2737) 7.1.1 MIB Structure. The Entity MIB (version 2) contains five groups of MIB objects: - entityPhysical group Describes the physical entities managed by a single agent. - entityLogical group Describes the logical entities managed by a single agent.
PAGE 62
1. Network Management Specification Table 1-59. entPhysicalEntry {entPhysicalTable 1} (2 of 2) Object OID Syntax Access Status Supported entPhysicalModelName {entPhysicalEntry 13} SnmpAdminString read-only current Yes entPhysicalAlias {entPhysicalEntry 14} SnmpAdminString read-write current Yes entPhysicalAssetID {entPhysicalEntry 15} SnmpAdminString read-write current Yes entPhysicalIsFRU {entPhysicalEntry 16} Truth Value read-only current Yes 7.1.2.1.
PAGE 63
1. Network Management Specification Valid Object Value(s): Table 1-61. entPhysicalDescr Entity Description Chassis sysDescr as described in the MIB-II’s System Group. Container "Paradyne DSLAM Slot x", Where x=1..
PAGE 64
1. Network Management Specification .3 sme-scp-8414-card (SCP w/OC3/STM1 .4 sme-scp-8416-card (SCP w/8 port T1 .5 sme-scp-8417-card (SCP w/8 port E1 .6 sme-scp-8418-card (SCP w/8 port E1 SM long ATM Uplink) IMA uplink) IMA uplink 75 ohm) IMA uplink 120 ohm) Company Enterprise.1.14.9.14.4 (sme-portcards) .1 sme-8965-card .2 sme-8955-card .3 sme-8985-card Company Enterprise.1.14.9.14.6 (sme-components) .1 sme-comp-fan .2 sme-comp-pld .3 sme-comp-sensor .
PAGE 65
1. Network Management Specification Table 1-63. entPhysicalVendorType (2 of 2) Entity entPhysicalVendorType T1/E1 port { Company Enterprise.1.14.9.14.3.5 } sme-t1e1-port OC3 port { Company Enterprise.1.14.9.14.3.6 } sme-oc3-port Console port { Company Enterprise.1.14.9.14.3.4 } sme-rs232-port Ethernet Mgmt port { Company Enterprise.1.14.9.14.3.4 } sme-eth-port Temp Sensor { Company Enterprise.1.14.9.14.6.3}sme-comp-sensor Fan { Company Enterprise.1.14.9.14.6.
PAGE 66
1. Network Management Specification 7.1.2.1.5 entPhysicalClass An indication of the general hardware type of the physical entity. Valid Object Value(s): The following table shows the different classes identified for the ATM stackable DSLAM’s entities. Table 1-65.
PAGE 67
1. Network Management Specification Table 1-66. entPhysicalParentRelPos (2 of 2) Entity entPhysicalParentRelPos T1/E1 port A value between [3..11] OC3 port 3 Console port 1 Ethernet Mgmt port 2 Temp Sensor A value between [1..3] Fan A value between [1..1] PowerSupply A value between [1..2] Management Plane PLD 1 7.1.2.1.7 entPhysicalName The textual name of the physical entity. Valid Object Value(s): Table 1-67.
PAGE 68
1. Network Management Specification The following table shows the entPhysicalHardwareRev defined for each entity. Table 1-68.
PAGE 69
1. Network Management Specification Table 1-69. entPhysicalFirmwareRev (2 of 2) Entity entPhysicalFirmwareRev Console port zero-length-string Ethernet Mgmt port zero-length-string Temp Sensor zero-length-string Fan zero-length-string PowerSupply zero-length-string Management Plane PLD A String with the currently running Software Revision Level. 7.1.2.1.11 entPhysicalSerialNum The vendor-specific serial number string for the physical entity.
PAGE 70
1. Network Management Specification The following table shows the entPhysicalMfgName designated for the entities. Table 1-71.
PAGE 71
1. Network Management Specification Table 1-72. entPhysicalModelName (2 of 2) Entity entPhysicalModelName Ethernet Mgmt port zero-length-string Temp Sensor zero-length-string Fan zero-length-string PowerSupply zero-length-string Management Plane PLD zero-length-string 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-volatilehandle’ for the physical entity.
PAGE 72
1. Network Management Specification 7.1.2.1.15 entPhysicalAssetID This object is a user-assigned asset tracking identifier for the physical entity as specified by a network manager, and provides non-volatile storage of this information. If no asset tracking information is associated with the physical component, then this object will contain a zero-length string. Valid Object Value(s): The following table shows the entPhysicalAssetID assigned by default to the entities.
PAGE 73
1. Network Management Specification Table 1-75. entPhysicalIsFRU (2 of 2) Entity entPhysicalIsFRU Splitter card TRUE DSL Port FALSE T1/E1 port FALSE OC3 port FALSE Console port FALSE Ethernet Mgmt port FALSE Temp Sensor FALSE Fan FALSE PowerSupply FALSE Management Plane PLD FALSE 7.1.2.2 entityLogical Group. The entLogicalTable { entityLogical 1} described below shows the attributes supported for each the physical entities. For the GranDSLAM 3.
PAGE 74
1. Network Management Specification 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 MCP 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 will be snmpUDPDomain. 7.1.2.2.6 entLogicalContextEngineID. The value of this object will be the null-string. 7.1.2.2.7 entLogicalContextName.
PAGE 75
1. Network Management Specification Table 1-79. entPhysicalChildIndex Entity entPhysicalIndex entPhysicalChildIndex Semantic Chassis 0001000000 0001ss0000 A chassis contains ’ss’ containers, ss=[1..20]. 0001ss010x A chassis contains a sensor ’x’, x=[1..3]. 0001ss011x A chassis contains a fan “x”, x=[1..1] 0001ss013x A chassis contains a powersupply “x”, x=[1..2] Container 0001ss0000 0001ss000y A container ’ss’ contains module ’y’, ss=[1..20], y=[1..
PAGE 76
1. Network Management Specification 7.2.2 mpeEntPhysicalExtOperStatus This is a read-only object that allows managers to determine the operational status of the entities in the managed device. The possibles values are ’up’, ’down’ and ’testing’. 7.3 Entity Sensor MIB (RFC 3433): This MIB has only one group (entitySensorValueGroup) which consists of a single (read-only) table that will be supported as indicated in the following table. There will be as many entries as sensors. For the GranDSLAM 3.
PAGE 77
1. Network Management Specification Table 1-82.
PAGE 78
1. Network Management Specification dot3MauType100BaseFXHD, dot3MauType100BaseFXFD, dot3MauType100BaseT2HD, dot3MauType100BaseT2FD, etc. 7.4.1.4 ifMauStatus (RO): The current state of the MAU. 7.4.1.5 ifMauDefaultType (RW): This object identifies the default administrative baseband MAU type, to be used in conjunction with the operational MAU type denoted by ifMauType. 7.4.1.6 ifMauAutoNegSupported (RO): This object indicates whether or not auto-negotiation is supported on this MAU. 7.4.1.
PAGE 79
1. Network Management Specification Table 1-84.
PAGE 80
1. Network Management Specification 7.6.1.2 pdnMgmtIpAddress (RW). The IP address assigned to this port. If the pdnMgmtIpConfigMode 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 the DHCP client (or 0.0.0.0, if none assigned). Changes to this object could disrupt data flow through the port. 7.6.1.3 pdnMgmtIpNetMask (RW). The IP subnet mask assigned to this port.
PAGE 81
1. Network Management Specification 7.6.2 pdnMgmtAtmInvArpTable. This table contains one row per Inverse ATM ARP entry in the system. This table maps the index to corresponding of the pdnMgmtIpPortTable in 3.30.1. 7.6.2.1 pdnMgmtAtmIfIndex (NA) The interface index associated with the ATM PVC. 7.6.2.2 pdnMgmtAtmVpi (NA) The VPI associated with the ATM PVC. 7.6.2.3 pdnMgmtAtmVci (NA) The VCI associated with the ATM PVC. 7.6.2.
PAGE 82
1. Network Management Specification 7.7.2 Supporting MIBs. 7.7.3 SNMP-MPD-MIB (RFC 3412) This MIB provides statistics for message processing. The following scalar MIB objects will be supported to provide statistics about invalid or unknown conditions in the message processing: 7.7.3.1 snmpUnknownSecurityModels 7.7.3.2 snmpInvalidMsgs 7.7.3.3 snmpUnknownPDUHandlers 7.7.
PAGE 83
1. Network Management Specification 7.7.4.5.3 snmpTargetParmsTable: It is used to configure target parameters (message processing level, security model, etc.) that will be used in the generation of SNMP notification messages. This table will be supported read-only with default entries as indicated in section 7.7.4.6.4 and 7.7.4.6.5 7.7.4.5.4 snmpUnavailableContexts and snmpUnknownContexts: Statistics. These tables will be stored in nonvolatile memory. 7.7.4.
PAGE 84
1. Network Management Specification 7.7.5 User-based Security Model (USM) RFC 3414 RFC 3414 discusses the “User-based security model” for SNMPv3. It defines the elements of procedure for providing SNMP message-level security. The mechanisms to be implemented related to this feature are Discovery and Timeliness, Authentication, Privacy and Key management. The product will support the HMAC-MD5-96 and the HMAC-SHA-96 protocols for authentication and the CBC-DES Symmetric Encryption Protocol for Privacy. 7.
PAGE 85
1. Network Management Specification 7.7.6.1.1 vacmContextTable. It defines the locally available contexts. This table is read-only and can not be configured by SNMP. 7.7.6.1.2 vacmSecurityToGroupTable. It maps a securityModel and securityName to a groupName. Supported read-only with default values. 7.7.6.1.3 vacmAccessTable. It maps a groupName, context and securityInformation into a MIB view. Supported read-only with default values. 7.7.6.1.4 vacmViewTreeFamilyTable.
PAGE 86
1. Network Management Specification 7.8 Link Fault Management. This sections describes the mibs associated with the Automatic Protection Switching (APS), Manual Dual Link Load Sharing (DLLS) and Redundancy Features. 7.8.1 Automatic Protection Switching (APS) draft-ietf-atommib-sonetaps-mib-xx.txt This MIB objects are used to control and manage SONET linear APS architectures. The generation of APS notifications is enabled by default (apsNotificationEnable).
PAGE 87
1. Network Management Specification 7.8.2 Link Load Sharing (LLS) - (PDN-LINK-LOAD-SHARING-MIB.mib) The object pdnLinkLoadSharingSelection is used to enable Load Sharing in the device. By default Load Sharing is disabled. Table 1-87. Link Load Sharing Table Comments pdnLLSConfigEntry Supported as is pdnLLSMapEntry Supported as is 7.8.2.1 pdnLLSConfigGroupName. This object contains a text describing a group configured for load sharing. 7.8.2.2 pdnLLSConfigSelection.
PAGE 88
1. Network Management Specification 7.8.4.1 pdnRedunCommand. This MIB object allows managers to command an action to an entity module (given by the entPhysicalIndex), configured for redundancy. The supported commands are switch(2) and forceswitch (3). The value noCmd (1) will be returned when no previous command had been issued. Users should specify the slot-based entPhysicalIndex (for example, 1190001) corresponding to the entity that will take the action. 7.8.4.2 pdnRedunAlarmStatus.
PAGE 89
1. Network Management Specification 8. Timing and Clocking 8.1 Paradyne mpe_Config MIB (mpe_Config.mib ) The tabular object mpeDevConfigClockSrcEntry defined in mpe_Config.mib provides the capability of choosing network timing reference source on the GranDSLAM. Table 1-90.
PAGE 90
1. Network Management Specification disable(1) - Tests will not be terminated based on a timer and enable(2) - Tests will be terminated after the duration specified by devConfigTestDuration. This object specifies whether tests are to be terminated after a defined duration. If the value is enable(2), the duration is defined by devConfigTestDuration. 8.2.2 devConfigTestDuration This object specifies the duration (in seconds) that a test will be allowed to run before it is automatically terminated.
PAGE 91
1. Network Management Specification 8.3.5 devNTPEnable (RW): .Indicates whether or not the 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/SNTP server. Default value is enabled(1). 8.3.6 devNTPOffsetFromUTC: .Offset (minutes) from the coordinated universal time (UTC), also known as Greenwich mean time (GMT), to local time represented as a signed integer.
PAGE 92
1. Network Management Specification 9. Access Control and Security. 9.1 Paradyne DSLAM System Mib [pdn_dslam.mib] (pdn-common 24) . Support for the pdn_dslam MIB is provided to enable an NMS access certain objects that are specific to this product. Table 1-93. pdn_dslam.
PAGE 93
1. Network Management Specification 9.2 Paradyne Security MIB (pdn_Security.mib): The pdn_security MIB is used for enabling applications control security aspects of the unit for the purpose of Telnet, FTP, and so on. The various objects supported are as follows: Table 1-94. pdn_Security.
PAGE 94
1. Network Management Specification 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 securityMgrFtpAccess. That is, changing the TelnetAccess will also change those two objects. 9.2.4.5 securityMgrFtpAccess (RW): This is used to specify the ftp access to the device. This object is tied with the securityMgrTelnetAccess and securityMgrSnmpAccess.
PAGE 95
1. Network Management Specification 9.3 Paradyne Control MIB (mpe_Control.mib) Table 1-95. mpe_Control.
PAGE 96
1. Network Management Specification Table 1-95. mpe_Control.mib (2 of 2) Table Object Type mpeDevFirmwareControlTable Supported Yes entPhysicalIndex Yes mpeDevFirmwareControlIndex(1) INTEGER Yes mpeDevFirmwareControlRelease(2) DisplayString Yes mpeDevFirmwareControlOperStatus(4) INTEGER Yes mpeDevFirmwareControlAdminStatus(5) INTEGER Yes 9.3.
PAGE 97
1. Network Management Specification 9.3.2 mpeDevFirmwareControlTable : This table contains a list of the 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 String and Operational Status of the release (valid or invalid) and activate a valid Firmware Release by changing the Administration Status to active.The active Firmware will always be the first entry in this table.
PAGE 98
1. Network Management Specification 10. Status and Alarms. 10.1 Paradyne Syslog MIB (pdn_syslog.mib): Table 1-96.
PAGE 99
1. Network Management Specification 10.1.5 pdnSyslogSeverityThreshold (RW): The valid values are emerg (0), alert (1), critical (2), error (3), warning (4), notice (5), info (6), debug (7). This value corresponds to a minimum severity level that a syslog messages can be set. All syslog message with an enum value greater than the threshold will not be sent.
PAGE 100
1. Network Management Specification 10.1.12 pdnSyslogRateLimiting (RW): Valid values are disable (1), enable (2). This allows one to enable or disable rate limitiming. When rate limiting is enabled, it prevents the exact same message from being resent within a fixed amount of time. 10.2 Paradyne Health and Status MIB (mpe_HealthAndStatus.mib) The Paradyne health & Status MIB is used to store the results of the Power On Self Test (POST). It is indexed by the entPhysicalIndex of the unit being selftested.
PAGE 101
1. Network Management Specification Table 1-98. devLastTrapString (2 of 4) Trap devLastTrapString DSX Traps dsx1LineStatusChange "The dsx1LineStatus has changed on a dsx1 interface." ATM-M4 Traps atmfM4IfAisAlarm "AIS alarm detected." atmfM4IfLcdAlarm "Loss of Cell delineation detected." atmfM4IfLosAlarm "Loss of Signal detected." atmfM4IfLofAlarm "Loss of Frame detected." atmfM4VclXConnCreated "VCL cross-connection has just been created.
PAGE 102
1. Network Management Specification Table 1-98. devLastTrapString (3 of 4) Trap devLastTrapString hdsl2ShdslnoNeighborPresent "No Neighbor Present status has changed for this Endpoint." hdsl2ShdslLocalPowerLoss " Impending unit failure due to loss of local power condition has been detected." SONET LINEAR APS MIB Traps: apsEventSwitchover "Switchover status has changed." apsEventModeMismatch "Mode status mismatch." apsEventChannelMismatch "Channel status mismatch.
PAGE 103
1. Network Management Specification Table 1-98. devLastTrapString (4 of 4) Trap devLastTrapString IMA Traps imaFailureAlarm 8000-A2-GB30-00 "Alarm condition on Ima interface.
PAGE 104
1.
PAGE 105
Index A Access Control, 86 ADSL extension MIB, 35 MIB, 35 traps, 11, 96 adslAtucInitFailureTrap, 12 adslAtucPerfESsThreshTrap, 11 adslAtucPerfLofsThreshTrap, 11 adslAtucPerfLolsThreshTrap, 12 adslAtucPerfLossThreshTrap, 11 adslAtucRateChangeTrap, 11 adslAtucSesLThreshTrap, 12 adslAtucUasLThreshTrap, 12 adslAturPerfESsThreshTrap, 12 adslAturPerfLofsThreshTrap, 12 adslAturPerfLossThreshTrap, 12 adslAturPerfLprsThreshTrap, 12 adslAturRateChangeTrap, 12 adslAturSesLThreshTrap, 13 adslAturUasLThreshTrap, 13 AF-
PAGE 106
Index Enterprise-Specific MIB, 72 traps, 10, 96 Entity MIB, 55 extension, 69 traps, 95 Entity Redundancy, 81 Entity Sensor MIB, 70 entityLogical Group, 67 entPhySensorEntry, 70 entPhysicalAlias, 65 entPhysicalAssetID, 66 entPhysicalChildIndex, 69 entPhysicalClass, 60 entPhysicalContainedIn, 59 entPhysicalContainsTable, 68 entPhysicalDescr, 57 entPhysicalEntry, 55 entPhysicalFirmwareRev, 62 entPhysicalHardwareRev, 61 entPhysicalIndex, 56 entPhysicalIsFRU, 66 entPhysicalMfgName, 63 entPhysicalModelName, 64 e
PAGE 107
Index MIB standards compliance, 14 supported, 1 MIB-II organization, 16 SNMP Group, 33 Transmission Group, 33 model numbers, 1 mpe_Control.mib, 89 mpe_HealthAndStatus.mib, 94 mpeCcn, 10 mpeDevConfigClockSrcEntry, 83 mpeDevControlTable, 89 mpeDevHealthAndStatusEntry, 94 mpeEntPhysicalExtEntry, 69 mpeSelfTestFailure, 10 P pdn_ATMM4Ext.mib, 51 pdn_Config.mib, 83 pdn_dslam.mib, 86 pdn_reachDSL.mib, 36 pdn_Security.mib, 87 pdn_spectrummgmt.mib, 40 pdn_syslog.mib, 92 pdn_time.
PAGE 108
Index sysDevUserAccountTable, 86 Syslog MIB, 92 sysObjectID, 17 sysServices, 17 System Group, 16 T TC Adapter Layer table, 49 TC Sublayer Group, 45 Timing, 83 Traffic Descriptor Types, 46 Transmission Group, 33 traps ADSL, 96 ATM-M4, 95 devLastTrapString, 94 DSX, 95 Enterprise-Specific, 96 Entity MIB, 95 IMA, 97 SHDSL, 95 SNMPv2, 77 SONET, 96 standards compliance, 7 summary of, 7 IN-4 U User-based Security Model, 78 V VC Cross-Connect Table, 50 VCL, 46 View-based Access Control (VACM), 78 Virtual Chann