Paradyne 8820 - Manuals - manualsarea.com

Page 2 - June; Notice; Visit the Paradyne World Wide Web site at; Document Feedback

A June 2003 8000-A2-GB30-00 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 ...

Page 3 - Contents; About This Guide; iii; Network Management Specification

8000-A2-GB30-00 June 2003 i Contents About This Guide Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . iii Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Product-Related Documents . . . . . . . . . . . . . . . . . ...

Page 4 - ii

Page 5 - Document Purpose and Intended Audience; Support; Section; Index

8000-A2-GB30-00 June 2003 iii 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, confi...

Page 6 - iv; Product-Related Documents; Complete documentation for this product is available online at; Document Number; GrandVIEW EMS User’s Guide

About This Guide iv June 2003 8000-A2-GB30-00 Product-Related Documents Complete documentation for this product is available online at www.paradyne.com . Select Support → Technical Manuals → Hotwire DSL Systems . To order a paper copy of a Paradyne document, or to speak with a sales representative, ...

Page 8 - Network Management Specification; RFC

1. Network Management Specification 2 June 2003 8000-A2-GB30-00 2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types [dsx1ConfigEntry_t],[dsx1CurrentEntry_t], [dsx1IntervalEntry_t], [dsx1TotalEntry_...

Page 12 - Other Supported RFCs Used as Guidelines for Implementation

1. Network Management Specification 6 June 2003 8000-A2-GB30-00 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 Transmiss...

Page 13 - Standards Compliance for SNMP Traps

1. Network Management Specification 8000-A2-GB30-00 June 2003 7 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...

Page 14 - Trap

1. Network Management Specification 8 June 2003 8000-A2-GB30-00 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 i...

Page 16 - SONET LINEAR APS MIB Traps:

1. Network Management Specification 10 June 2003 8000-A2-GB30-00 hdsl2ShdslprotocolInitFailure This notification indicates that the bit setting forprotocolInitFailure in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed. hdsl2ShdslEndpointCurrStatus devLastTrapString hdsl2Shdslno...

Page 19 - IMA Traps

1. Network Management Specification 8000-A2-GB30-00 June 2003 13 adslAturSesLThreshTrap Severly errored seconds 15 minutes threshold reached ifIndex adslAturPerfCurr15MinSesL devLastTrapString adslAturUasLThreshTrap Unavailable seconds 15 minutes threshold reached ifIndex adslAturPerfCurr15MinUasL d...

Page 20 - Standards Compliance to SNMP MIB; a) a whole table does not exist in the MIB tree or

1. Network Management Specification 14 June 2003 8000-A2-GB30-00 3. Standards Compliance to SNMP MIB s 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 sa...

Page 21 - GranDSLAM Interfaces; Port Cards

1. Network Management Specification 8000-A2-GB30-00 June 2003 15 Figure 1-1. GranDSLAM Interfaces ATM DSL ChanADSL Port Cards Slot 1 Slot 2 Slot 18 ATM DSL ChanReachDSL ATM SHDSL DS1 Sonet SonetPath ATM IMA AAL5 ETH rs-232 T1/E1 IMAChild-card DS1 Sonet SonetPath ATM IMA AAL5 ETH T1/E1 IMAChild-card ...

Page 22 - Chassis

1. Network Management Specification 16 June 2003 8000-A2-GB30-00 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 implem...

Page 23 - The following table shows the values supported :; sysServices; Physical

1. Network Management Specification 8000-A2-GB30-00 June 2003 17 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...

Page 24 - Therefore this object will be set to the value of 127.; ifIndex scheme

1. Network Management Specification 18 June 2003 8000-A2-GB30-00 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 tabl...

Page 26 - ifIndex Scheme; will have a special meaning on the GranDSLAM 3.0. Slot 00 will be used

1. Network Management Specification 20 June 2003 8000-A2-GB30-00 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 ...

Page 27 - Please refer to; ifIndex Assignments; Interface

1. Network Management Specification 8000-A2-GB30-00 June 2003 21 * Please refer to Table 1-6, GranDSLAM 3.0 Interface List , for the exact number of interfaces supported of each class in the current release. ** Console interface will not be displayed in the ifTable. Only in the entPhysicalTable. 4.1...

Page 28 - ifMtu; * Per RFC 2515, this object is set to the largest

1. Network Management Specification 22 June 2003 8000-A2-GB30-00 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 ...

Page 31 - Input Counters (objects ifEntry 10 to ifEntry 15)

1. Network Management Specification 8000-A2-GB30-00 June 2003 25 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: • ifInOcte...

Page 34 - Output Counters (objects ifEntry 16 to ifEntry 20)

1. Network Management Specification 28 June 2003 8000-A2-GB30-00 4.1.11.6 “ifInUnknownProtos” Object (ifEntry 15) 4.1.12 Output Counters (objects ifEntry 16 to ifEntry 20) 4.1.12.1 “ifOutOctets” Object (ifEntry 16) Table 1-18. ifInUnknownProtos Interface ifInUnknownProtos AAL5 0 ATMUP 0 DSL 0 DSLATM...

Page 37 - “ifLinkUpDownTrapEnable” Object (ifXEntry 14)

1. Network Management Specification 8000-A2-GB30-00 June 2003 31 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 p...

Page 38 - GranDSLAM 3.0 Interface List; “ifStackHigherLayer” Object (ifStackEntry 1)

1. Network Management Specification 32 June 2003 8000-A2-GB30-00 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 w...

Page 39 - “ifStackLowerLayer” Object (ifStackEntry 2); If the associated ATM link is part of an IMA group; is supported as a “read only” variable; The Transmission Group Objects is SUPPORTED.; Comments

1. Network Management Specification 8000-A2-GB30-00 June 2003 33 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. * If the associated ATM link is...

Page 41 - Physical Layer

1. Network Management Specification 8000-A2-GB30-00 June 2003 35 5. Physical Layer 5.1 ADSL MIB (RFC 2662) 5.2 ADSL-EXT MIB (draft-ietf-adslmib-adslext-xx.txt) Table 1-28. ADSL MIB Table Comments adslLineEntry Supported as is adslAtucPhysEntry Supported as is adslAturPhysEntry Supported as is adslAt...

Page 42 - Table

1. Network Management Specification 36 June 2003 8000-A2-GB30-00 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 ...

Page 43 - The various objects supported are shown in the following table.; The default value is; . This object only applies to DS1 interfaces.; pdnDs1ExtConfTable

1. Network Management Specification 8000-A2-GB30-00 June 2003 37 The various objects supported are shown in the following table. 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 in...

Page 44 - This scalar object will be supported read-only.

1. Network Management Specification 38 June 2003 8000-A2-GB30-00 5.6 SONET-MIB (RFC 2558) 5.6.1 sonetMediumEntry 5.6.2 sonetSESthresholdSet This scalar object will be supported read-only. 5.6.3 sonetPathCurrentWidth This scalar object will be supported read-only. Table 1-33. SONET-MIB Table Comments...

Page 45 - devSonetStatusLastChange.; devSonetConfigEntry_t

1. Network Management Specification 8000-A2-GB30-00 June 2003 39 5.7 Paradyne SONET-EXT MIB (pdn_SonetExt.mib). 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 de...

Page 46 - newSpectrumMgmtGeneralConfigEntry

1. Network Management Specification 40 June 2003 8000-A2-GB30-00 5.8 SHDSL MIB (RFC 3276) 5.9 Spectrum Management (pdn_spectrummgmt.mib) This MIB is a common MIB supported for both ReachDSL and SHDSL ports. 5.9.1 newSpectrumMgmtGeneralConfigEntry This table is indexed by the entPhysicalIndex and ifT...

Page 47 - for the exact number of ATM

1. Network Management Specification 8000-A2-GB30-00 June 2003 41 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 tabl...

Page 50 - Write access to this object is not supported

1. Network Management Specification 44 June 2003 8000-A2-GB30-00 Write access to this object is not supported 6.1.1.10 “atmInterfaceMyNeighborIfName” Object (atmInterfaceConfEntry 12) In Hybrid Management Model, the value of this object contains the textual name of the interface on the neighbor syst...

Page 52 - “atmServiceCategory” Object (atmTrafficDescrParamEntry 10); The only valid value for this object is :

1. Network Management Specification 46 June 2003 8000-A2-GB30-00 6.2 ATM Traffic Descriptor Group (RFC 2515) This table contains a set of self-consistent ATM traffic parameters including the ATM traffic service category, The ATM virtual link tables (that is, VPL and VCL tables), will use this ATM Tr...

Page 53 - “atmVclOperStatus” Object (atmVclEntry 4); atmVccAal5CpcsTransmitSduSize =; “atmVclAal5CpcsReceiveSduSize” Object (atmVclEntry 10); atmVccAal5CpcsReceiveSduSize =; “atmVclEncapsType” Object (atmVclEntry 11)

1. Network Management Specification 8000-A2-GB30-00 June 2003 47 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...

Page 54 - Virtual Channel Cross Connect Group (RFC 2515)

1. Network Management Specification 48 June 2003 8000-A2-GB30-00 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 acce...

Page 55 - active

1. Network Management Specification 8000-A2-GB30-00 June 2003 49 • 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...

Page 58 - /* Loop while a test is running or some other

1. Network Management Specification 52 June 2003 8000-A2-GB30-00 6.5 ATM Loopback pdnATMfM4VcLoopbackTestTable in pdn_atmM4Ext.mib is supported to provide detailed test results on ATM F5 loopback test. This tabular object augments atmfM4VcTestTable (see Section 3.15). In order to distinguish a singl...

Page 59 - set up any test parameters.

1. Network Management Specification 8000-A2-GB30-00 June 2003 53 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’...

Page 62 - The index for this entry.

1. Network Management Specification 56 June 2003 8000-A2-GB30-00 7.1.2.1.1 entPhysicalIndex The index for this entry. Valid Object Value(s): The value of this object is based on the ifIndex in the Interfaces Group. Refer to Evolution of the Interfaces Group of MIB-II (RFC 2863) on page 1-18 for furt...

Page 63 - entPhysicalVendorType

1. Network Management Specification 8000-A2-GB30-00 June 2003 57 Valid Object Value(s): a. Refers to the sysDescr in the MIB-II’s System Group for clarification onCompany 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 number ...

Page 64 - Entity

1. Network Management Specification 58 June 2003 8000-A2-GB30-00 .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 Enter...

Page 65 - entPhysicalContainedIn

1. Network Management Specification 8000-A2-GB30-00 June 2003 59 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 physical entity is not contained in any other physical entity. Note that the s...

Page 66 - An indication of the general hardware type of the physical entity.

1. Network Management Specification 60 June 2003 8000-A2-GB30-00 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. 7.1.2.1.6 entPhysic...

Page 67 - The textual name of the physical entity.

1. Network Management Specification 8000-A2-GB30-00 June 2003 61 7.1.2.1.7 entPhysicalName The textual name of the physical entity. Valid Object Value(s): 7.1.2.1.8 entPhysicalHardwareRev The vendor-specific hardware revision string for the physical entity. Valid Object Value(s): T1/E1 port A value ...

Page 70 - entPhysicalModelName

1. Network Management Specification 64 June 2003 8000-A2-GB30-00 The following table shows the entPhysicalMfgName 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...

Page 71 - entPhysicalAlias

1. Network Management Specification 8000-A2-GB30-00 June 2003 65 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. On the first instantiation of an physical entity, the val...

Page 74 - The value of this object will be the null-string.

1. Network Management Specification 68 June 2003 8000-A2-GB30-00 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 t...

Page 75 - This group will be supported as specified in RFC 2737.

1. Network Management Specification 8000-A2-GB30-00 June 2003 69 7.1.2.5 entityGeneral Group. This group will be supported as specified in RFC 2737. 7.1.2.6 entityNotifications Group An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an NM...

Page 78 - The current state of the MAU.; ipCidrRouteNumber

1. Network Management Specification 72 June 2003 8000-A2-GB30-00 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 administrati...

Page 80 - The IP subnet mask assigned to this port.

1. Network Management Specification 74 June 2003 8000-A2-GB30-00 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 ...

Page 82 - snmpUnknownSecurityModels; See RFC 3411 for details on how this is formatted.; supported; to configure

1. Network Management Specification 76 June 2003 8000-A2-GB30-00 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 proce...

Page 83 - snmpTargetParmsTable:; These tables will be stored in nonvolatile memory.; snmpNotifyFilterTable:; Filtering of traps will not be supported.

1. Network Management Specification 8000-A2-GB30-00 June 2003 77 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 d...

Page 84 - The following statistics MIB objects will be supported:; procedure is stardarized in RFC 3414.; same; value of the; localized key; to; will not be supported

1. Network Management Specification 78 June 2003 8000-A2-GB30-00 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 t...

Page 85 - vacmSecurityToGroupTable.

1. Network Management Specification 8000-A2-GB30-00 June 2003 79 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 re...

Page 86 - This object is supported

1. Network Management Specification 80 June 2003 8000-A2-GB30-00 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...

Page 87 - This feature can not be enabled if APS is enabled.

1. Network Management Specification 8000-A2-GB30-00 June 2003 81 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 . 7.8.2.1 pdnLLSConfigGroupName. This object cont...

Page 88 - pdnRedunNotificationEnable.

1. Network Management Specification 82 June 2003 8000-A2-GB30-00 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)...

Page 89 - The mpeDevCfgClkWhichSrc object takes the following two values:

1. Network Management Specification 8000-A2-GB30-00 June 2003 83 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. The mpeDe...

Page 90 - disable(1) - Tests will not be terminated based on a timer and; devConfigTestDuration; The following objects are supported for GranDSLAM 3.0.; Object

1. Network Management Specification 84 June 2003 8000-A2-GB30-00 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 duratio...

Page 92 - The various objects are described in the above table.

1. Network Management Specification 86 June 2003 8000-A2-GB30-00 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. The various objects ar...

Page 93 - The current number of managers in the devSecurityMgrTable..

1. Network Management Specification 8000-A2-GB30-00 June 2003 87 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: 9.2.1 de...

Page 94 - This is used to create and remove entries to this table.

1. Network Management Specification 88 June 2003 8000-A2-GB30-00 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 ob...

Page 96 - mpeDevFileXferConfigTable:

1. Network Management Specification 90 June 2003 8000-A2-GB30-00 9.3.1 mpeDevControlTable: This table is indexed on the entPhysicalIndex and contains mpeDevControlReset object which is used to reset the associated entity (for example, card). Writing the value reset (2) to this object initiates a Har...

Page 97 - mpeDevFirmwareControlTable :

1. Network Management Specification 8000-A2-GB30-00 June 2003 91 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 Relea...

Page 98 - This object has been deprecated.

1. Network Management Specification 92 June 2003 8000-A2-GB30-00 10. Status and Alarms. 10.1 Paradyne Syslog MIB (pdn_syslog.mib): The pdn_syslog MIB defines a collection of objects for managing syslog messages. The objects are used to configure both syslog functions and syslog daemons. This MIB als...

Page 99 - pdnEntitySyslogMessage; The text of the syslog message.

1. Network Management Specification 8000-A2-GB30-00 June 2003 93 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 ...

Page 100 - The format for the selfTest results is as follows:; administratively

1. Network Management Specification 94 June 2003 8000-A2-GB30-00 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 amou...

Page 101 - DSX Traps

1. Network Management Specification 8000-A2-GB30-00 June 2003 95 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 ...

Page 102 - entPhysicalIndex

1. Network Management Specification 96 June 2003 8000-A2-GB30-00 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 Tra...

Page 103 - imaFailureAlarm

1. Network Management Specification 8000-A2-GB30-00 June 2003 97 IMA Traps imaFailureAlarm "Alarm condition on Ima interface." Table 1-98. devLastTrapString (4 of 4) Trap devLastTrapString

Page 105 - Definitions for the IEEE 802.3 Medium Attachment Units,

8000-A2-GB30-00 June 2003 IN-1 Index A Access Control, 86ADSL extension MIB, 35MIB, 35traps, 11, 96 adslAtucInitFailureTrap, 12adslAtucPerfESsThreshTrap, 11adslAtucPerfLofsThreshTrap, 11adslAtucPerfLolsThreshTrap, 12adslAtucPerfLossThreshTrap, 11adslAtucRateChangeTrap, 11adslAtucSesLThreshTrap, 12ad...