1. Manuals
  2. Brands
  3. Paradyne Manuals
  4. Network Accessory
  5. Hotwire 8620
  6. Reference manual

Paradyne 8620 Reference Manual

Broadband access concentrator snmp reference
Hide thumbs Also See for 8620:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Installation Manual
8620 and 8820
Broadband Access Concentrator
SNMP Reference
Document No. 8000-A2-GB30-30
June 2004

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 8620 and is the answer not in the manual?

Questions and answers

Related Manuals for Paradyne 8620

Summary of Contents for Paradyne 8620

  • Page 1 8620 and 8820 Broadband Access Concentrator SNMP Reference Document No. 8000-A2-GB30-30 June 2004...
  • Page 2 Copyright © 2004 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.

  • Page 3: Table Of Contents

    Contents About This Guide Document Purpose and Intended Audience ....Document Summary ........Product-Related Documents .
  • Page 4 Contents June 2004 8000-A2-GB30-30...

  • Page 5: Document Purpose And Intended Audience

    Document Purpose and Intended Audience This reference manual contains the network management specification for the 8620 and 8820 Broadband Access Concentrators (BACs) managed by SCP cards running Release 3.2 (ATM uplink) and Release 4.0 (IP uplink) and above. It is designed for network managers who use SNMP in the course of installing, configuring, monitoring, and troubleshooting BACs and associated cards.

  • Page 6: Product-Related Documents

    GrandVIEW EMS User’s Guide Shelf Concentration and Processing (SCP) Card with ATM Uplink User’s Guide Shelf Concentration and Processing (SCP) Card with IP Uplink User’s Guide 8620 Broadband Access Concentrator Installation Guide 8820 Broadband Access Concentrator Installation Guide June 2004 8000-A2-GB30-30...

  • Page 7: Network Management Specification

    Network Management Specification SCP Card 3.2 (ATM) and 4.0 (IP) Network Management Interface This document describes the SNMP support for the 8620 and 8820 Broadband Access Concentrator (BAC) product. The product includes the following models: Table 1-1. Model Numbers for the BAC Product...
  • Page 8 1. Network Management Specification Table 1-2. Supported RFCs and MIBs (1 of 8) Name IANAifType-MIB SNMPv2-SMI SNMPv2-TC ADSL-TC-MIB Definitions of Supplemental Managed Objects for ATM Interface. draft-ietf-atommib-atm2-xx.txt IMA MIB AF-PHY-0086.001 (http://www.atmforum.com/atmforum/spec s/approved.html) SNMP M4 Network Element View MIB atmfM4MIB AF-NM-0095.001 (http://www.atmforum.com/atmforum/spec s/approved.html) draft-ietf-snmpv3-coex-v2-02.txt...
  • Page 9 Table 1-2. Supported RFCs and MIBs (2 of 8) Name 1493 Defnitions of Managed Objects for Bridges dot1dBaseBridgeAddress 1907 SNMPv2-MIB 2096 IP Forwarding Table 2493 PerfHist-TC 2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types 2496 Definitions of Managed Objects for the DS3/E3 Interface Type...
  • Page 10 1. Network Management Specification Table 1-2. Supported RFCs and MIBs (3 of 8) Name 2558 Definitions of Managed Objects for the SONET/SDH Interface Type 2662 Definitions of Managed Objects for the ADSL Lines 2665 Definitions that describes generic objects for Ethernet-like network interfaces 2668 Definitions of Managed objects for IEEE 802.3 Medium Attachment Units(MAU).
  • Page 11 Table 1-2. Supported RFCs and MIBs (4 of 8) Name 2674p Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions 2737 Entity MIB (Version 2) 2863 Evolution of MIB-II Interfaces 2864 Inverted Stack Extension MIB 2933 Internet Group Management Protocol 3276...
  • Page 12 1. Network Management Specification Table 1-2. Supported RFCs and MIBs (5 of 8) Name 3414_std62_a User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) 3414_std62_b User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) 3415_std62 View-based Access Control Model...
  • Page 13 Table 1-2. Supported RFCs and MIBs (6 of 8) Name enterprise mpe_Control.mib enterprise mpe_HealthAndStatus.mib enterprise pdn_ATMExt.mib pdn_ATMM4Ext.mib pdn_ATMStats.mib enterprise PDN-MGMT-IP-MIB.mib enterprise pdn_Config.mib enterprise pdn_Security.mib enterprise pdn_time.mib enterprise pdn_dslam.mib enterprise pdn_spectrummgmt.mib enterprise pdn_reachDSL.mib enterprise PDN-DS1EXT-MIB 8000-A2-GB30-30 1. Network Management Specification Description Paradyne Enterprise Device Control MIB includes the Paradyne File Transfer Group.
  • Page 14 1. Network Management Specification Table 1-2. Supported RFCs and MIBs (7 of 8) Name enterprise mpe_dslam enterprise pdn_Ds3Ext.mib PDN-MPD-EXT-MIB.mib enterprise PDN-SFP-MIB.mib enterprise enterprise pdn_ether.mib pdn_TrapMgr.mib enterprise PDN-ENTITY-SENSOR-EXT-MIB enterprise PDN-ATM-BRIDGE-IWF-MIB enterprise enterprise PDN-DOT1QEXT-MIB.mib enterprise PDN-IGMP-STD-EXT-MIB.mib enterprise PDN-IP-MULTICAST-MIB.mib PDN-UPLINK-TAGGING-MIB.mib enterprise enterprise PDN-VLAN-MIB.mib Description mpeEntExtAlarms_t mpeEntPhysicalEntEntry_t...
  • Page 15 Table 1-2. Supported RFCs and MIBs (8 of 8) Name enterprise pdn_IfExtConfig.mib Table 1-3. Other Supported RFCs Used as Guidelines for Implementation Name/Description User Datagram Protocol Internet Protocol 792, 950 Internet Control Message Protocol; Internet Standard Subnetting Procedure Transmission Control Protocol Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48.bit Ethernet address for transmission on Ethernet hardware Telnet Protocol Specification...

  • Page 16: Standards Compliance For Snmp Traps

    1. Network Management Specification Standards Compliance for SNMP Traps This section describes the standards compliance and any special operational features/options for the SNMP Traps supported by the BAC products. The following traps are supported. Table 1-4. Summary of Traps (1 of 7) Trap LinkDown LinkUp...
  • Page 17 Table 1-4. Summary of Traps (2 of 7) Trap atmfM4VclXConnCreated atmfM4VclXConnDeleted atmfM4VclXConnChanged atmfM4VplXConnCreated atmfM4VplXConnDeleted atmfM4VplXConnChanged atmfM4HwFanFailAlarm atmfM4AtmCellIfCreated atmfM4AtmCellIfDeleted entConfigChange mpeEntPhysicalExtEntityCreated 8000-A2-GB30-30 Description 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 18 1. Network Management Specification Table 1-4. Summary of Traps (3 of 7) Trap mpeEntPhysicalExtEntityDeleted mpeEntPhysicalExtEntityChanged hdsl2ShdslLoopAttenCrossing hdsl2ShdslSNRMarginCrossing hdsl2ShdslPerfESThresh hdsl2ShdslPerfSESThresh hdsl2ShdslPerfCRCanomaliesThresh hdsl2ShdslPerfLOSWSThresh hdsl2ShdslPerfUASThresh hdsl2ShdslSpanInvalidNumRepeaters hdsl2ShdslLoopbackFailure Description This trap signifies that an instance of this entity has been deleted from the entPhysicalTable. This trap signifies that an instance of this entity has been changed from the entPhysicalTable.
  • Page 19 Table 1-4. Summary of Traps (4 of 7) Trap hdsl2ShdslpowerBackoff hdsl2ShdsldeviceFault hdsl2ShdsldcContinuityFault hdsl2ShdslconfigInitFailure hdsl2ShdslprotocolInitFailure hdsl2ShdslnoNeighborPresent hdsl2ShdslLocalPowerLoss mpeSelfTestFailure mpeCcn devSonetStatusChange pdnRedunEventNoActiveModule pdnRedunEventHwIncompatible 8000-A2-GB30-30 Description This notification indicates that the bit setting for powerBackoff in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed. This notification indicates that the bit setting for deviceFault in the hdsl2ShdslEndpointCurrStatus object for...
  • Page 20 1. Network Management Specification Table 1-4. Summary of Traps (5 of 7) Trap pdnRedunEventStandbyAlarmOrReset pdnRedunEventFwIncompatible pdnRedunEventCfgIncompatible pdnRedunEventLinkDefect pdnRedunEventHwDefect pdnRedunEventHwMissingHwFailure sfpEventFaulty sfpEventOperational sfpEventInserted sfpEventRemoved adslAtucPerfLofsThreshTrap adslAtucPerfLossThreshTrap adslAtucPerfESsThreshTrap Description This notification will be issued when one of the modules configured for redundancy is either in the Standby/Alarm or Reset Test state.
  • Page 21 Table 1-4. Summary of Traps (6 of 7) Trap adslAtucRateChangeTrap adslAtucPerfLolsThreshTrap adslAtucInitFailureTrap adslAturPerfLofsThreshTrap adslAturPerfLossThreshTrap adslAturPerfLprsThreshTrap adslAturPerfESsThreshTrap adslAturRateChangeTrap adslAtucSesLThreshTrap adslAtucUasLThreshTrap adslAturSesLThreshTrap adslAturUasLThreshTrap 8000-A2-GB30-30 Description The ATUCs transmit rate has changed (RADSL mode only) Loss of Link 15-minute interval threshold reached ATUC initialization failed. See adslAtucCurrStatus for potential reasons Loss of Framing 15-minute interval threshold reached...
  • Page 22 1. Network Management Specification Table 1-4. Summary of Traps (7 of 7) Trap imaFailureAlarm Description IMA Traps The imaFailureAlarm provides a method for an agent implementing IMA to notify an NMS of an alarm condition. June 2004 VarBind(s) ifIndex, imaAlarmStatus, imaAlarmType, devLastTrapString 8000-A2-GB30-30...

  • Page 23: Standards Compliance To Snmp Mibs

    Standards Compliance to SNMP MIB This section describes the standards compliance and any special operational features/options for the SNMP MIBs supported on the BAC product. • The term Not Supported 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.
  • Page 24 1. Network Management Specification Port Cards entPhysicalIndex=1010001 Slot 1 8965/8955 DSL Chan ADSL/Reach entPhysicalIndex=1020001 Slot 2 8995 T1/E1 entPhysicalIndex=1180001 Slot 18 8985 SHDSL/SHDSL2 Figure 1-1. ACTIVE SCP card on slot 19 entPhysicalIndex=1190001 slot 19 STANDBY SCP card slot 20 entPhysicalIndex=1200001 slot 20 T1/E1 BAC Interfaces with Active SCP in slot 19 and StandBy SCP in slot 20.
  • Page 25 ADSL InterChannel (IANAifType=124), IMA Interface (IANAifType = 107) SONET Interface (IANAifType = 39) SONETPATH (IANAifType = 50) ATMLogical (IANAifType = 80) Bridge Interface (IANAifType = 135) NOT_SUPPORTED. NOT_SUPPORTED. NOT_SUPPORTED. NOT_SUPPORTED. NOT_SUPPORTED SUPPORTED SUPPORTED. This value will be 8820 or 8620. June 2004...
  • Page 26 “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 sme-chassis-8820-ip[Company Enterprise OID].1.14.9.14.5.3 sme-chassis-8620-ip[Company Enterprise OID].1.14.9.14.5.4 3.2.3 “sysUpTime”...

  • Page 27: Evolution Of The Interfaces Group Of Mib-Ii (Rfc 2863)

    The following table shows the values supported : Table 1-5. Layer (L) Therefore this object will be set to the value of 127. 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 BAC.
  • Page 28 1. Network Management Specification Table 1-6. Interface Console port Ethernet Mgmt Port IP Mgmt Ports GigaEthernet Ethernet 10/100BT SONET SONETPATH ATM SubInterface ATM Link ATM AAL5 DSL port DSL channels DSL ATM Links ATM SubInterface Links Bridge Interface The console will not be listed in the interface group, but it will be in the entPhysicalTable of the entityMIB.
  • Page 29 Table 1-7. Descr Layer 6 Layer 5 Layer 4 Layer 3 Layer 2 Layer 1 Table 1-8. Descr Layer 4 Layer 3 Layer 2 Layer 1 Table 1-9. Descr Layer 6 Layer 5 Layer 4 Layer 3 Layer 2 Layer 1 4.1.1.1.1 A unique value, greater than zero number will be assigned to each interface.
  • Page 30 The suffix ‘cc’ indicates the chassis number where the interface is instantiated. The chassis number for the 8820 or the 8620 will be 1 for the BAC. The suffix ‘ss’ indicates the slot number where the interface is instantiated. For the BAC, this number corresponds to the physical position where the associated module is located in the 8820 or 8620 chassis.
  • Page 31 Table 1-11. ifIndex Assignments Interface Name Interface (ifName) Console port CONx Ethernet Mgmt port ETHx IP Ports T1_x T1_x E1_x T3_x SONET_x GigaEthernet ETHGIGE_x 100BT Ethernet ETH100BT_x SONETPATH SONETPATH_x ATM Link ATMUP_x IMA_x AAL5 AAL5_x DSL port DSL_xx SHDSL port SHDSL_xx 8000-A2-GB30-30 ifInterface...
  • Page 32 1. Network Management Specification Table 1-11. ifIndex Assignments Interface Name Interface (ifName) DSL Channels DSLChan_xx ATMx ATM SubInterfaces ATMSUBINTF_x atmLogical (80) Bridge Interface BRIDGE_x * Applies only when the T1/E1 interfaces are used as user ports rather than uplinks (model 8995) Please refer to of each class in the current release.
  • Page 33 Table 1-12. ifMtu Interface DSLChan SONET SONETPath GIGE 10/100BT BRIDGE * Per RFC 2515, this object is set to the largest PDU size for the AAL5 CPCS layer that can be processed by the AAL5 Entity. 8000-A2-GB30-30 1. Network Management Specification ifMtu June 2004...
  • Page 34 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-13. ifSpeed Interface AAL5 ATMUP DSLATM DSLChan SONET SONETPath...
  • Page 35 Table 1-14. ifAdminStatus Interface AAL5 ATMUP DSLATM DSLChan T1/E1 ETH1 SONET SONETPath GIGE 10/100BT BRIDGE 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-15.
  • Page 36 1. Network Management Specification Table 1-15. ifOperStatus (2 of 2) Interface ifOperStatus Up(1), Down(2), Testing(3), Unknown(4), notPresent(6), lowerLayerDown(7) GIGE Up(1), Down(2), Testing(3), Unknown(4), notPresent(6), lowerLayerDown(7) 10/100BT Up(1), Down(2), Testing(3), Unknown(4), notPresent(6), lowerLayerDown(7) BRIDGE Up(1), Down(2), Testing(3), Unknown(4), notPresent(6), lowerLayerDown(7) 4.1.9 “ifLastChange”...
  • Page 37 Table 1-16. ifInOctets (2 of 2) Interface BRIDGE 4.1.11.2 Table 1-17. ifInUncastPkts Interface AAL5 ATMUP DSLATM DSLChan T1/E1 ETH1 SONET SONETPath 4.1.11.3 Table 1-18. ifInUncastPkts (1 of 2) Interface DSLChan DSLATM T1/E1 ETH1 ATMUP AAL5 ETH1 SONET SONETPath 8000-A2-GB30-30 ifInOctets “ifInUcastPkts”...
  • Page 38 1. Network Management Specification Table 1-18. ifInUncastPkts (2 of 2) Interface GIGE 10/100BT BRIDGE 4.1.11.4 Table 1-19. ifInDiscards Interface AAL5 ATMUP DSLATM DSLChan ETH1 SONET SONETPath T1/E1 GIGE 10/100BT BRIDGE 4.1.11.5 Table 1-20. ifInErrors (1 of 2) Interface AAL5 ATMUP DSLATM DSLChan ifInUncastPkts...
  • Page 39 Table 1-20. ifInErrors (2 of 2) Interface T1/E1 ETH1 SONET SONETPath GIGE 10/100BT BRIDGE 4.1.11.6 Table 1-21. ifInUnknownProtos Interface AAL5 ATMUP DSLATM DSLChan T1/E1 ETH1 SONET SONETPath GIGE 10/100BT BRIDGE 8000-A2-GB30-30 ifInErrors “ifInUnknownProtos” Object (ifEntry 15) ifInUnknownProtos Number of cells dropped during header validation, and cells with unrecognized header patterns PDUs of incorrect type June 2004...
  • Page 40 1. Network Management Specification 4.1.12 Output Counters (objects ifEntry 16 to ifEntry 20) 4.1.12.1 Table 1-22. ifOutOctets Interface AAL5 ATMUP DSLATM DSLChan T1/E1 ETH1 SONET SONETPath GIGE 10/100BT BRIDGE 4.1.12.2 Table 1-23. ifOutUcastPkts (1 of 2) Interface AAL5 ATMUP DSLATM DSLChan T1/E1 ETH1...
  • Page 41 Table 1-23. ifOutUcastPkts (2 of 2) Interface 10/100BT BRIDGE 4.1.12.3 Table 1-24. ifOutNUcasts Interface AAL5 ATMUP DSLATM DSLChan T1/E1 ETH1 SONET SONETPath 4.1.12.4 Table 1-25. ifOutDiscards (1 of 2) Interface AAL5 ATMUP DSLATM DSLChan T1/E1 ETH1 SONET SONETPath 8000-A2-GB30-30 ifOutUcastPkts “ifOutNUcasts”...
  • Page 42 1. Network Management Specification Table 1-25. ifOutDiscards (2 of 2) Interface GIGE 10/100BT BRIDGE 4.1.12.5 Table 1-26. ifOutErrors Interface AAL5 ATMUP DSLATM DSLChan T1/E1 ETH1 SONET SONETPath GIGE 10/100BT BRIDGE 4.1.13 “ifOutQLen” (ifEntry 21) This object contains the length of the output packet queue. It will contain a value assigned by the unit which is used for each interface.This object is not supported and will return a huge invalid number.
  • Page 43 Extension to the Intf. Table (ifXTable) - (RFC 2233) The Extension to the interface table contains additional objects for the interface table. Only the following objects in the Extension to the Interface Table will be supported in the BAC: Table 1-27. Extension to the Interface Table Interface AAL5 ATMUP...
  • Page 44 1. Network Management Specification 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 BAC, the interface stack group will be used to show the relationship between the multiple logical and physical interfaces, if a physical interface exists.
  • Page 45 Table 1-29. ifStackHigherLayer (2 of 2) ccss190x ccss390x ccss490x ccss5901 *** If the associated ATM link is part of an IMA group 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.
  • Page 46 1. Network Management Specification • snmpInReadOnlys (snmp 11) • snmpInGenErrs (snmp 12) • snmpOutGetRequests (snmp 25) • snmpOutGetNexts (snmp 26) • snmpOutSetRequests (snmp 27) The following objects are supported: • snmpInPkts (snmp 1) • snmpOutPkts (snmp 2) • snmpInBadVersions (snmp 3) •...

  • Page 47: Physical Layer

    Physical Layer ADSL MIB (RFC 2662) Table 1-31. ADSL MIB Table adslLineEntry adslAtucPhysEntry adslAturPhysEntry adslAtucChanEntry adslAturChanEntry adslAtucPerfDataEntry adslAturPerfDataEntry adslAtucIntervalEntry adslAtucIntervalEntry adslChanIntervalEntry adslChanIntervalEntry adslLineConfProfileEntry adslLineAlarmConfProfileEntry ADSL-EXT MIB (draft-ietf-adslmib-adslext-xx.txt) Table 1-32. ADSL-EXT MIB Table adslLineExtEntry adslAtucPerfDataExtEntry adslAturPerfDataExtEntry adslConfProfileExtEntry adslAlarmConfProfileExtEntry 8000-A2-GB30-30 1. Network Management Specification Comments Supported as is Supported as is...
  • Page 48 1. Network Management Specification 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-33.
  • Page 49 The various objects supported are shown in the following table. Table 1-35. DS1-EXT MIB Table pdnDs1ExtConfEntry 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. long-haul is intended for inter-building use.
  • Page 50 1. Network Management Specification SONET-MIB (RFC 2558) Table 1-36. SONET-MIB Table sonetMediumEntry sonetSectionCurrentEntry sonetSectionIntervalEntry sonetLineCurrentEntry sonetLineIntervalEntry sonetFarEndLineCurrentEntry sonetFarEndLineIntervalEntry sonetPathCurrentEntry sonetPathIntervalEntry sonetFarEndPathCurrentEntry sonetFarEndPathIntervalEntry 5.6.1 sonetMediumEntry Table 1-37. sonetMediumEntry Table sonetMediumType sonetMediumTimeElapsed sonetMediumValidIntervals sonetMediumLineCoding sonetMediumLineType sonetMediumCircuitIdentifier sonetMediumInvalidIntervals sonetMediumLoopbackConfig 5.6.2 sonetSESthresholdSet This scalar object will be supported read-only. 5.6.3 sonetPathCurrentWidth This scalar object will be supported read-only.
  • Page 51 Paradyne SONET-EXT MIB (pdn_SonetExt.mib). Table 1-38. SONET-EXT MIB Table devSonetConfigEntry_t 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.
  • Page 52 1. Network Management Specification SHDSL MIB (RFC 3276) Table 1-39. SHDSL MIB Table hdsl2ShdslSpanConfEntry hdsl2ShdslSpanStatusEntry hdsl2ShdslInventoryEntry hdsl2ShdslEndpointConfEntry hdsl2ShdslEndpointCurrEntry hdsl2Shdsl15MinIntervalEntry hdsl2Shdsl1DayIntervalEntry hdsl2ShdslEndpointMaintEntry hdsl2ShdslUnitMainEntry hdsl2ShdslSpanConfProfileEntry hdsl2ShdslEndpointAlarmConfProfileEntry Spectrum Management (pdn_spectrummgmt.mib) This MIB is supported only for the SHDSL ports. ReachDSL ports use pdn_ReachDSL.mib for spectrum management.
  • Page 53 5.10 DS3/E3 MIB (RFC 2496) Table 1-41. DS3/E3 MIB Table dsx3ConfigEntry dsx3LoopbackConfig dsx3Channelization dsx3Ds1ForRemoteLoop dsx3TransmitClockSource dsx3CurrentEntry dsx3IntervalEntry dsx3TotalEntry dsx3FarEndConfigEntry dsx3FarEndCurrentEntry dsx3FarEndIntervalEntry dsx3FarEndTotalEntry dsx3FracEntry 5.10.1 dsx3LoopbackConfig This variable represents the desired loopback configuration of the DS3/E3 interface. Only the following loopbacks are supported for the ds3 interfaces. 5.10.2 dsx3Channelization This variable indicates whether this ds3/e3 is channelized or unchannelized.
  • Page 54 1. Network Management Specification 5.11 Paradyne DS3 Extensions (pdn_Ds3Ext.mib) Table 1-42. pdn_Ds3Ext.MIB Table devDs3ConfigEntry devDs3ConfigTimingMarkerCode 5.11.1 devDs3ConfigTimingMarkerCode This variable indicates whether this ds3/e3 is channelized or unchannelized. This object is supported read-only and the value noTraceable(2) will be returned. 5.12 Ethernet-Like Statistics MIB (RFC2665.mib) Table 1-43.
  • Page 55 Table 1-45. 802.3 MAU mib Table dot3RpMauBasisGroup dot3ifMauBasicGroup ifMauEntry_t ifJackEntry_t dot3BroadMauBasicGroup dot3MauType dot3ifMauAutoNegGroup dot3ifMauAutoNegEntry_t 5.14.1 ifMauTable: Table of descriptive and status information about MAU(s) attached to an interface. The following objects in this table are supported. Table 1-46. ifMauTable Table Object ifMauTable ifMauIfIndex...
  • Page 56 1. Network Management Specification 5.14.1.2 This variable uniquely identifies the MAU described by this entry from among other MAUs connected to the same interface (ifMauIfIndex). 5.14.1.3 This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA.

  • Page 57: Link Layer

    Link Layer 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.
  • Page 58 1. Network Management Specification 6.1.1.2 This object contains the maximum number of VCCs supported at this ATM interface. The only valid values for this object are: Table 1-49. atmInterfaceMaxVccs Interface DSLATM ATMUP AAL5 6.1.1.3 This object contains the number of VPCs configured for use at this ATM interface. Table 1-50.
  • Page 59 6.1.1.6 This object contains the maximum number of active VCI bits configured for use at this ATM interface. Table 1-53. atmInterfaceMaxActiveVciBits Interface DSLATM ATMUP AAL5 6.1.1.7 6.1.1.8 Table 1-54. atmInterfaceIlmiVpi Interface DSLATM ATMUP AAL5 This object contains the VCI value of the VCC supporting the ILMI on the ATM Interface. . Table 1-55.
  • Page 60 1. Network Management Specification Write access to this object is not supported Table 1-56. atmInterfaceMyNeighborIpAddress Interface DSLATM ATMUP AAL5 6.1.1.10 In Hybrid Management Model, the value of this object contains the textual name of the interface on the neighbor system on the far end of this interface, and to which this interface connects.
  • Page 61 6.1.1.12 The maximum number of VCI Bits that may currently be used at this ATM interface. Table 1-59. atmInterfaceCurrentMaxVciBits Interface DSLATM ATMUP AAL5 6.1.1.13 The identifier assigned by a service provider to the network side of a public network UNI. If this interface has no assigned service provider address, or for other interfaces this is an octet string of zero length.
  • Page 62 1. Network Management Specification 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 Traffic Descriptor table to assign traffic parameters and service category to the receive and transmit directions of the ATM virtual links (that is, VPLs and VCLs), The ATM VPL or VCL table will indicate a row, in the atmTrafficDescrParamTable using its atmTrafficDescrParamIndex value.
  • Page 63 6.2.1.1 This object indicates the current operational status of the VCL. Possible values are: unknown (3) The state of the VCL can’t be determined. 6.2.1.2 This object contains the value of the MIB II’s sysUpTime object at the time the VCL entered its current operational state.
  • Page 64 1. Network Management Specification 6.2.3 “atmVcCrossConnectL2HOperStatus” Object (atmVcCrossConnectEntry 9) The value of this object identifies the current operational status of the VC cross-connect in one direction; (that is, from the low to high direction). The up and down states indicate that this ATM VC cross-connect from low to high direction is operational or not operational respectively.
  • Page 65 Similarly, ATM SubInterfaces can be deleted by removing entries from the atmVplTable. Table 1-64. Atm SubInterfaces Table atmVplLogicalPortDef atmVplLogicalPortIndex ‘0’ for regular VPL entries. 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.
  • Page 66 1. Network Management Specification Table 1-65. AtmfM4 MIB (2 of 2) atmfM4TcProtoHistEntry atmfM4VpUpcNpcCurrEntry atmfM4VpUpcNpcHistEntry atmfM4VcUpcNpcCurrEntry atmfM4VcUpcNpcHistEntry atmfM4TestTypes atmfM4VpTestTable atmfM4VcTestTable atmfM4EquipTable atmfM4EquipHolderTable atmfM4PlugInUnitTable atmfM4HwRunningSwTable atmfM4HwInstalledSwTable atmfM4AlarmSevDefault atmfM4AlarmSevProfileIndexNext atmfM4ALarmSevProfileTable atmfM4AlarmSevTable atmfM4ForwardAllTraps atmfM4TrapForwardingTable atmfM4TrapLogTable atmfM4LoggedTrapTable atmfM4LoggedAlarmTable atmfM4TrapAlarmSeverity atmfM4TrapAlarmBackedUp atmfM4TrapAlarmBUObject atmfM4TrapAlarmSpecificProb atmfM4TrapAlarmRepairAct 6.3.1 TC Adapter Layer Table (atmfM4TcAdapterEntry) Columns conceptually added to the interface table entry for an ATM interface to model the TC Adapter.
  • Page 67 6.3.1.1 Specifies the index of the entry in the communications alarm severity profile table that should be used. The only valid value of this object is 0. 6.3.1.2 These are the ATM Forum M4 interface Configuration table extensions for the ATM cell layer.
  • Page 68 1. Network Management Specification Paradyne Extensions to the ATM Interface Config Table (pdn_atmExt.mib). The following MIBs are intended to augment ATM Interface Config Table ( atmInterfaceConfTable). Table 1-66. Paradyne Extensions to the ATM MIB Table pdnAtmIfConfExtEntry pdnAtmTrafficDescrParamExtTable Paradyne Extensions to the ATM Forum M4 mibs (pdn_AtmM4Ext.mib) Table 1-67.
  • Page 69 if (atmfM4TestId == lock_value+1) results are valid Once ownership is obtained, an NMS could initiate a test by setting atmfM4VcTestType to pdnATMfM4VcTestOAMLoopbackSegMultiCell to which a loopback location code that uniquely identifies an intermediate point responsible for looping back the cell is appended for ATM OAM F5 Segment loopback test, or pdnATMfM4VcTestOAMLoopbackE2EMultiCell for ATM OAM F5 End to End loopback test.
  • Page 70 1. Network Management Specification Paradyne Enterprise ATM Statistics (pdn_AtmStats.mib) Table 1-68. Paradyne ATM Stats MIB Table pdnAtmVplStat pdnAtmVclStat IMA MIB (AF-PHY-0086.001) The following mib objects will be supported if the IMA interface is available in the device. Otherwise the whole IMA mib will not supported. Table 1-69.
  • Page 71 Bridge MIB (RFC1493.mib Table 1-70. Bridge Mibs. Table dot1dBase dot1dBaseBridgeAddress dot1dBaseNumPorts dot1dBaseType dot1dBasePortTable dot1dStp group dot1dSr group dot1dTp group dot1dTpLearnedEntryDiscards dot1dTpAgingTime dot1dTpFdbTable dot1dTpPortTable dot1dTpHCPortTable dot1dTpPortOverflowTable dot1dStatic group dot1dStaticTable 6.8.1 dot1dBaseType Indicates the type of bridging this bridge can perform. The only type of bridging supported in the BAC is transparent-only(2).
  • Page 72 1. Network Management Specification P-Bridge MIB (RFC2674p.mib) Table 1-71. P-Bridge MIB Object dot1dExtBase dot1dDeviceCapabilities dot1dTrafficClassesEnabled dot1dGmrpStatus dot1dPortCapabilitiesTable dot1dPriority dot1dPortPriorityTable dot1dUserPriorityRegenTable dot1dTrafficClassTable dot1dPortOutboundAccessPriorityTable dot1dGarp group dot1dPortGarpTable dot1dGmrp group dot1dPortGmrp group 6.10 Q-Bridge MIB (RFC2674q.mib) Table 1-72. Q-Bridge MIB (1 of 2) Object dot1qVlanVersionNumber dot1qMaxVlanId...
  • Page 73 Table 1-72. Q-Bridge MIB (2 of 2) Object dot1qStaticMulticastEntry dot1qVlan group dot1qVlanNumDeletes dot1qVlanCurrentEntry dot1qVlanStaticEntry dot1qNextFreeLocalVlanIndex dot1qPortVlanEntry dot1qPortVlanStatisticsEntry dot1qPortVlanHCStatisticsEntry dot1qLearningConstrainsEntry dot1qConstraintSetEnty dot1qConstraintTypeDefault 6.11 Paradyne ATM-Bridge Interworking Function (IWF) - PDN-ATM-BRIDGE-IWF-MIB.mib This mib contains objects that are used for monitoring and controlling the ATM/BRIDGE Interworking function.

  • Page 74: Network Layer

    1. Network Management Specification Network Layer IP Forwarding Table (RFC 2096) Table 1-75. IP Forwarding mibs Objects ipCidrRouteNumber ipCidrRouteEntry Internet Group Management Protocol (IGMP) (RFC 2933) Table 1-76. igmpStdMIB Object igmpInterfaceEntry igmpInterfaceQuerierUptime igmpInterfaceQuerierExperyTime igmpCacheEntry Paradyne Extension to IGMP mib (PDN-IGMP-STD-EXT-MIB.mib) This mis is a complement to the standard RFC2933 (IGMP) mib.

  • Page 75: Configuration Management

    Paradyne Enterprise IP Multicast mib (PDN-IP-MULTICAST-MIB.mib) Table 1-78. Paradyne IP Multicast mib Object pdnUltIndex pdnGenUltBaseVlanTag Paradyne Extension VLAN mib (PDN-VLAN-MIB.mib) Table 1-79. Paradyne Enterprise VLAN mib. Object pdnVlanReservedBlockStart pdnVlanInbandMgmtVlanId pdnVlanInbandMgmtVlanId2 Paradyne Enterprise configuration of interface role (pdn_IfExtConfig.mib) This mib allows configuration of the role for some interfaces of interest. The roles in this context can be either uplink or other (e.g, subtending).
  • Page 76 1. Network Management Specification Describes the physical entities managed by a single agent: entityLogical group Describes the logical entities managed by a single agent. entityMapping group Describes the associations between the physical entities, logical entities, interfaces, and non-interface ports managed by a single agent. entityGeneral group Describes general system attributes shared by potentially all types of entities managed by a single agent.
  • Page 77 Table 1-82. entPhysicalEntry {entPhysicalTable 1} (2 of 2) Object entPhysicalAlias {entPhysicalEntry 14} entPhysicalAssetID {entPhysicalEntry 15} entPhysicalIsFRU {entPhysicalEntry 16} 8.1.2.1.1 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 of the Interfaces Group of MIB-II (RFC 2863) indexes.
  • Page 78 1. Network Management Specification Table 1-83. entPhysicalIndex (2 of 2) Entity Management Plane PLD Uplink PLD Power Supply * The IP SCP card supports up to 24 containers or slots. Slot 22 is reserved for the wintegra ipnp card, slots 21, 23 and 24 will always be empty.
  • Page 79 T1/E1PLD Version xx.yy.zz T3/E3PLD Version xx.yy.zz entPhysicalVendorType Company Enterprise.1.14.9.14.5 (sme-chassis) .1 sme-chassis-8820 .2 sme-chassis-8620 Company Enterprise.1.14.9.14.7 (sme-container) Company Enterprise.1.14.9.14.1 (sme-scp-cards) .1 sme-scp-8412-card (SCP w/OC3/STM1 MM ATM Uplink) .2 sme-scp-8413-card (SCP w/OC3/STM1 SM int ATM Uplink) .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)
  • Page 80 .1 sme-comp-fan .2 sme-comp-pld .3 sme-comp-sensor .4 sme-comp-powersupply entPhysicalVendorType { Company Enterprise.1.14.9.14.5.1} sme-chassis-8820 { Company Enterprise.1.14.9.14.5.2} sme-chassis-8620 { Company Enterprise.1.14.9.14.7} sme-container { Company Enterprise.1.14.9.14.1.1} sme-scp-8412-card { Company Enterprise.1.14.9.14.1.2} sme-scp-8413-card { Company Enterprise.1.14.9.14.1.3} sme-scp-8414-card { Company Enterprise.1.14.9.14.1.4} sme-scp-8416-card { Company Enterprise.1.14.9.14.1.5} sme-scp-8417-card { Company Enterprise.1.14.9.14.1.6} sme-scp-8418-card...
  • Page 81 Table 1-86. entPhysicalVendorType (2 of 2) Entity DSL Port T1/E1 port OC3 port DS3 port GigE port 10/100BT port Console port Ethernet Mgmt port Temp Sensor Power Supply Management Plane PLD Uplink PLD 8.1.2.1.4 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.
  • Page 82 1. Network Management Specification Table 1-87. entPhysicalContainedIn (2 of 2) Entity OC3 port DS3 port GigE/100BT port Console port Ethernet Mgmt port Temp Sensor PowerSupply Management Plane PLD Uplink PLD 8.1.2.1.5 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.
  • Page 83 Table 1-88. entPhysicalClass (2 of 2) Entity Management Plane PLD Uplink PLD 8.1.2.1.6 An indication of the relative position of this “child” component among all its “sibling” components. Sibling components are defined as entPhysicalEntries --entries in the entPhysicalTable-- which share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects..
  • Page 84 1. Network Management Specification Valid Object Value(s): Table 1-90. entPhysicalName Entity Chassis Container Module Uplink Module Splitter card DSL Port T1/E1 port OC3 port DS3 port GigE/100BT port Console port Ethernet Mgmt port Temp Sensor PowerSupply Management Plane PLD Uplink PLD 8.1.2.1.8 The vendor-specific hardware revision string for the physical entity.
  • Page 85 Table 1-91. entPhysicalHardwareRev (2 of 2) Entity Splitter card DSL Port T1/E1 port OC3 port DS3 port GigE/100BT port Console port Ethernet Mgmt port Temp Sensor PowerSupply Management Plane PLD Uplink PLD 8.1.2.1.9 The vendor-specific software revision string for the physical entity. If no specific firmware programs are associated with the physical component, or this information is unknown to the agent, then this object will contain a zero-length string.
  • Page 86 1. Network Management Specification Table 1-92. entPhysicalFirmwareRev (2 of 2) Entity GigE/100BT port Console port Ethernet Mgmt port Temp Sensor PowerSupply Management Plane PLD Uplink PLD 8.1.2.1.11 The vendor-specific serial number string for the physical entity. Valid Object Value(s): The following table shows the entPhysicalSerialNum identified for the entities supported. Table 1-93.
  • Page 87 8.1.2.1.12 The name of the manufacturer of this physical component. The preferred value is the manufacturer name string actually printed on the component itself (if present).Note that comparisons between instances of the entPhysicalModelName, entPhysicalFirmwareRev, entPhysicalSoftwareRev, and the entPhysicalSerialNum objects, are only meaningful amongst entPhysicalEntries with the same value of entPhysicalMfgName.
  • Page 88 1. Network Management Specification The following table shows the entPhysicalModelName designated for the entities.. Table 1-95. entPhysicalModelName Entity Chassis Container Module Uplink Module Splitter card DSL Port T1/E1 port OC3 port DS3 port GigE/100BT port Console port Ethernet Mgmt port Temp Sensor PowerSupply Management Plane PLD...
  • Page 89 Table 1-96. entPhysicalAlias (2 of 2) Entity Container Module Uplink Module Splitter card DSL Port T1/E1 port OC3 port DS3 port GigE/100BT port Console port Ethernet Mgmt port Temp Sensor PowerSupply Management Plane PLD Uplink PLD 8.1.2.1.15 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.
  • Page 90 1. Network Management Specification Table 1-97. entPhysicalAssetID (2 of 2) Entity OC3 port DS3 port GigE/100BT port Console port Ethernet Mgmt port Temp Sensor PowerSupply Management Plane PLD Uplink PLD 8.1.2.1.16 This object indicates whether or not this physical entity is considered a 'field replaceable unit' by the vendor.
  • Page 91 Table 1-98. entPhysicalIsFRU (2 of 2) Entity PowerSupply Management Plane PLD Uplink PLD 8.1.2.2 The entLogicalTable { entityLogical 1} described below shows the attributes supported for each the physical entities. For the BAC product, there will be 1 row associated to the MCP if it is physically coexisting in the same chassis with the SCP card.
  • Page 92 1. Network Management Specification 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. 8.1.2.2.6 The value of this object will be the null-string. 8.1.2.2.7 The value of this object will be the null-string.
  • Page 93 The following table shows the entPhysicalChildIndex values for the different entities.ss=[1..20]. Table 1-102. entPhysicalChildIndex Entity entPhysicalIndex Chassis 0001000000 Container 0001ss0000 Module 0001ss0001 8.1.2.5 This group will be supported as specified in RFC 2737. 8.1.2.6 An entConfigChange notification is generated when the value of entLastChangeTime changes.
  • Page 94 1. Network Management Specification 8.2.1 mpeEntPhysicalExtUpTime The time since this entity was last re-initialized. 8.2.2 mpeEntPhysicalExtLocation Currently this object is supported read-only. Instead the agent supports the entPhysicalAlias that is stored in non-volatile storage. See section 8.1.2.1.14 for details on entPhysicalAlias.
  • Page 95 SNMPv3. 8.4.1 Framework and Applications. Based on current requirements for the BAC project, this is the level of support desired: Command Generators: It is not required that the DSLAM products generate SNMP messages. Command Responders: This is the primary function of our DSLAM management entity. Thus, this will be implemented as indicated in RFC 3413_std62.
  • Page 96 1. Network Management Specification Table 1-105. SNMP Framework mib objects (2 of 2) Object snmpMaxMessageSize 8.4.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: Table 1-106.
  • Page 97 8.4.3.2 This MIB allows the SNMP managers to configure notification recipients. The MIB is composed of the following tables: Table 1-109. SNMP-NOTIFICATION-MIB mib objects Object snmpNotifyTable snmpNotifyFilterTable snmpNotifyFilterProfileTable 8.4.3.2.1 The SNMP agent will be able to generate unconfirmed (TRAPS) using the SNMPv1 or SNMPv2 message format.
  • Page 98 1. Network Management Specification When creating new trap managers, the agent will set the following default values: TDomain=UDP (only UDP is supported) retryCount=3 timeout=100 8.4.4 User-based Security Model (USM) RFC 3414_std62 RFC 3414_std62 discusses the “User-based security model” for SNMPv3. It defines the elements of procedure for providing SNMP message-level security.
  • Page 99 As indicated before this table will have a default user whose name and password are the same as the default userID and password of the entire device. This initial password is run through an algorithm based on the HMAC-MD5-96 (default algorithm for authentication) and converted in what is called a localized key.
  • Page 100 1. Network Management Specification Table 1-114. SNMP-VACM-MIB mib objects (2 of 2) Object vacmAccessTable vacmViewTreeFamilyTable 8.4.5.0.1 The following default values are set up on the initial configuration. These entries can not be modified or deleted. Table 1-115. SNMP-VACM-MIB mib objects vacmSecurityModel vacmSecurityName vacmGroupName 1 (snmpV1) 1 (snmpV1)
  • Page 101 Table 1-116. Default entries in vacmViewTreeFamilyTable FamilyViewName “view_all” “view_read_only “view_read_only” Table 1-117. Default entries for the read-only vacmViewAccess SNMPv1 noAuthNoPriv SNMPv2 noAuthNoPriv SNMPv3 noAuthNoPriv 8000-A2-GB30-30 1. Network Management Specification FamilySubtree FamilyMask .1.3.6.1 “” .1.3.6.1 “” .1.3.6.1.6.3.18.1.1.1 “” vacmGroupName “Group-ro” vacmAccessContextPrefix ““...
  • Page 102 1. Network Management Specification Table 1-118. Default entries for the read-write vacmViewAccess SNMPv1 noAuthNoPriv SNMPv2 noAuthNoPriv SNMPv3 noAuthNoPriv SNMPv3 AuthPriv vacmGroupName “Group-rw” vacmAccessContextPrefix ““ vacmAccessSecurityModel 1 (snmpV1) vacmAccessSecurityLevel 1 (noAuthNoPriv) vacmAccessContextMatch prefix vacmAccessReadViewName “view_all” vacmAccessWriteViewName “view_all” vacmAccessNotifyViewName “view_all” vacmGroupName “Group-rw” vacmAccessContextPrefix ““...
  • Page 103 8.4.6 SNMPv3 Coexistence. This draft discusses the “Coexistence between Version 1, Version 2 and Version 3 of the Internet-standard Network Management Framework”. Among other things, this mib defines the snmpComunityTable. This table will be supported to configure community strings for SNMP managers capable of processing SNMPv1/v2c messages.
  • Page 104 1. Network Management Specification 8.4.7.1 This object is used to configure the level of SNMP access that the agent supports. The following values are supported for this object: SNMP config value (BITS) none (0) snmpv1NoAuthNoPriv (1) snmpv2cNoAuthNoPriv (2) snmpv3NoAuthNoPriv (3) snmpv3AuthNoPriv (4) snmpv3AuthNoPriv (5) Paradyne PDN-MGMT-IP-MIB.
  • Page 105 Table 1-122. PDN-MGMT-IP-MIB (2 of 2) Table pdnMgmtAtmInvArpEntry 8.5.1 pdnMgmtIpPortTable This is the IP Port Table. There is one entry per IP port/interface in the system.This table contains the configuration details of each Ip port. This table is indexed on the interface index of the IP port.
  • Page 106 1. Network Management Specification This object is supported only on IP ports that are configured to run over ethernet type of media. This object would be set to 0.0.0.0 for other types of interfaces and is not valid. 8.5.1.5 The physical address associated with the media. For IP Ports with Ethernet type of media, the MAX-ACCESS for this object is restricted to read-only.
  • Page 107 8.5.2.4 The Interface Index of the IP port to which this inverse ARP entry is associated with. Refer to the pdnMgmtIpPortTable for configuration of IP Ports. 8.5.2.5 The IP address of the unit at the other end of this ATM PVC. This represents the IP Gateway equivalent for IP traffic on this specific ATM PVC.
  • Page 108 1. Network Management Specification 8.6.1.3 This object is used to configure failure thresholds before switching over.. Table 1-125. Link Failure Config Table Object pdnLinkFailureLOSPeriodBeforeSwitching pdnLinkFailureLOFPeriodBeforeSwitching pdnLinkFailureAISPeriodBeforeSwitching pdnLinkFailureSdPeriodBeforeSwitching pdnLinkFailureSfPeriodBeforeSwitching pdnLinkFailureSdPeriodBeforeSwitching pdnLinkFailureSfPeriodBeforeSwitching 8.6.2 Entity redundancy - (PDN-ENTITY-REDUNDANCY-MIB.mib) This mib is used to configure redundancy features such as Y-cable selection, Trap generation, etc.
  • Page 109 8.6.2.5 8.6.2.5.1 This MIB object allows users to command an entity module, configured for redundancy to perform an action. The possible actions are: A read to this object return the last command issued or noCmd if none has been issue since reset.

  • Page 110: Timing And Clocking

    1. Network Management Specification Timing and Clocking Paradyne enterprise clock source MIB (pdn_Config.mib ) The devConfigClockSrcTable provides the capability of choosing a primary and a secondary clock source Table 1-127. devConfigClockSrcEntry Table devConfigClockSrcEntry 9.1.1 devCfgClkWhichSrc The devCfgClkWhichSrc object the following two values: •...
  • Page 111 9.1.5 devCurrentClockSrcSelection This is a read-only object that displays the clock source selected by the device. This object will return a value that corresponds to one of the valid clock sources (primary, secondary, tertiaty) 9.1.6 devConfigClockSrcAutoSwitch This object controls whether or not the device is allowed to switch back to a failed clock source if the device detects that the clock source has recovered.
  • Page 112 1. Network Management Specification Paradyne Time Mib (pdn_time.mib) The following objects are supported for BAC. Table 1-129. pdn_time.mib Object devDateAndTime devNTPServerIP devNTPMode devNTPSynchronised devNTPEnable devNTPOffsetFromUTC 9.3.1 devDateAndTime (RW): This objects displays the date and time on the entity. It allows an NMS to set the date and time in the appropriate timezone.

  • Page 113: Access Control And Security

    10. Access Control and Security. 10.1 Paradyne DSLAM System Mib [pdn_dslam.mib] . Support for the pdn_dslam MIB is provided to enable an NMS access certain objects that are specific to this product. . Table 1-130. pdn_dslam.mib (Objects Supported) Table sysDevUserAccountTable 10.1.1 sysDevUserAccountTable: This table contains the user accounts.The various supported objects are :...
  • Page 114 1. Network Management Specification 10.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-131. pdn_Security.mib Table devSecurityMgrValidation devSecurityMgrMaxNumber...
  • Page 115 10.2.4.3 This is used to specify the snmp access to the device. This object is tied with the securityMgrTelnetAccess and securityMgrFtpAccess. That is, changing the SnmpAccess will also change those two objects. This object is not supported. 10.2.4.4 This is used to specify the telnet access to the device. This object is tied with the securityMgrSnmpAccess and securityMgrFtpAccess.
  • Page 116 1. Network Management Specification 10.3 Paradyne Control MIB (mpe_Control.mib) Table 1-132. mpe_Control.mib (1 of 2) Table mpeDevControlTable mpeDevFileXferConfigTable mpeDevControlSelfTestTable mpeDevControlTestTable Object mpeDevControlReset(1) entPhysicalIndex entPhysicalIndex mpeDevFileXferFileName mpeDevFileXferCopyProtocol mpeDevFileXferFileType mpeDevFileXferServerIpAddress mpeDevFileXferUserName mpeDevFileXferUserPassword mpeDevFileXferOperation mpeDevFileXferPktsSent mpeDevFileXferPktsRecv mpeDevFileXferOctetsSent mpeDevFileXferOctetsRecv mpeDevFileXferOwnerString mpeDevFileXferStatus mpeDevFileXferErrorStatus mpeDevFileXferSendEvent mpeDevFileXferRowStatus mpeDevFileXferXferTime mpeDevFileXferFileFormat entPhysicalIndex...
  • Page 117 Table 1-132. mpe_Control.mib (2 of 2) Table mpeDevFirmwareControlTable 10.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 Hardware power-on reset of the entity. Writing the value resetToFactoryDefaults (3) causes the entity to re-configure itself with factory defaults.
  • Page 118 1. Network Management Specification 10.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 119: Status And Alarms

    11. Status and Alarms. 11.1 Paradyne Syslog MIB (pdn_syslog.mib): Table 1-133. Syslog MIB Table pdnEntitySyslogEntry pdnSyslogStatus pdnSyslogIPAddr pdnSyslogLevel pdnSyslogPort pdnSyslogSeverityThreshold pdnSyslogRemoteDaemon pdnSyslogNumOfMsgInTable pdnSyslogMaxTableSize pdnSyslogClearTable pdnSyslogMsgToConsole pdnSyslogRateLimiting 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 also allows one to retrieve syslog message from a device.
  • Page 120 1. Network Management Specification 11.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 121 11.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. 11.2 Paradyne Health and Status MIB (mpe_HealthAndStatus.mib) The Paradyne health &...
  • Page 122 1. Network Management Specification 11.4 Traps. 11.4.1 pdnDevConfigTrapsEnable (RW) (pdnTrapMgr.mib): This enterprise object allows NMS to turn on/off the generation of notifications in the device. The possible values are: • enabled (1) - default • disabled(2) 11.4.2 devLastTrapString (pdn_HealthAndStatus.mib) This is the value of the last trap string variable appended to every supported trap. Table 1-136.
  • Page 123 Table 1-136. devLastTrapString (2 of 3) Trap mpeEntPhysicalExtEntityChanged hdsl2ShdslLoopAttenCrossing hdsl2ShdslSNRMarginCrossing hdsl2ShdslPerfESThresh hdsl2ShdslPerfSESThresh hdsl2ShdslPerfCRCanomaliesThresh hdsl2ShdslPerfLOSWSThresh hdsl2ShdslPerfUASThresh hdsl2ShdslSpanInvalidNumRepeaters hdsl2ShdslLoopbackFailure hdsl2ShdslpowerBackoff hdsl2ShdsldeviceFault hhdsl2ShdsldcContinuityFault hdsl2ShdslconfigInitFailure hdsl2ShdslprotocolInitFailure hdsl2ShdslnoNeighborPresent hdsl2ShdslLocalPowerLoss mpeSelfTestFailure mpeCcn devSonetStatusChange pdnRedunEventNoActiveModule pdnRedunEventHwIncompatible pdnRedunEventStandbyAlarmOrReset pdnRedunEventFwIncompatible pdnRedunEventCfgIncompatible pdnRedunEventLinkDefect 8000-A2-GB30-30 devLastTrapString "Entity has been changed." SHDSL MIB Traps: "...
  • Page 124 1. Network Management Specification Table 1-136. devLastTrapString (3 of 3) Trap pdnRedunEventHwMissingHwFailure sfpEventFaulty sfpEventOperational sfpEventInserted sfpEventRemoved adslAtucPerfLofsThreshTrap adslAtucPerfLossThreshTrap adslAtucPerfESsThreshTrap adslAtucRateChangeTrap adslAtucPerfLolsThreshTrap adslAtucInitFailureTrap adslAturPerfLofsThreshTrap adslAturPerfLossThreshTrap adslAturPerfLprsThreshTrap adslAturPerfESsThreshTrap adslAturRateChangeTrap adslAtucSesLThreshTrap adslAtucUasLThreshTrap adslAturSesLThreshTrap adslAturUasLThreshTrap imaFailureAlarm devLastTrapString "An expected hw is missing on this redundant unit." "sfp is faulty"...
  • Page 125 Index Access Control, 1107 ADSL extension MIB, 141 MIB, 141 traps, 114, 1118 adslAtucInitFailureTrap, 115 adslAtucPerfESsThreshTrap, 114 adslAtucPerfLofsThreshTrap, 114 adslAtucPerfLolsThreshTrap, 115 adslAtucPerfLossThreshTrap, 114 adslAtucRateChangeTrap, 115 adslAtucSesLThreshTrap, 115 adslAtucUasLThreshTrap, 115 adslAturPerfESsThreshTrap, 115 adslAturPerfLofsThreshTrap, 115 adslAturPerfLossThreshTrap, 115 adslAturPerfLprsThreshTrap, 115 adslAturRateChangeTrap, 115 adslAturSesLThreshTrap, 115 adslAturUasLThreshTrap, 115 AF-PHY-0086.001, 164–165, 167 Alarms, 1113...
  • Page 126 Index entPhySensorEntry, 188 entPhysicalAlias, 182 entPhysicalAssetID, 183 entPhysicalChildIndex, 187 entPhysicalClass, 176 entPhysicalContainedIn, 175 entPhysicalContainsTable, 186 entPhysicalDescr, 172 entPhysicalEntry, 170 entPhysicalFirmwareRev, 179 entPhysicalHardwareRev, 178 entPhysicalIndex, 171 entPhysicalIsFRU, 184 entPhysicalMfgName, 181 entPhysicalModelName, 181 entPhysicalName, 177 entPhysicalParentRelPos, 177 entPhysicalSerialNum, 180 entPhysicalSoftwareRev, 179 entPhysicalVendorType, 174 extension to ADSL MIB, 141 to ATM MIB, 162...
  • Page 127 mpeDevControlTable, 1110 mpeDevHealthAndStatusEntry, 1115 mpeEntPhysicalExtEntry, 187 mpeSelfTestFailure, 113 pdn_Config.mib, 1105 pdn_dslam.mib, 1107 pdn_reachDSL.mib, 142 pdn_Security.mib, 1108 pdn_spectrummgmt.mib, 146 pdn_syslog.mib, 1113 pdn_time.mib, 1106 pdnATMIfConfExtEntry, 162 pdnDs1ExtConfTable, 143 PDN-ENTITY-REDUNDANCY-MIB.mib, 1102 pdnEntitySyslogEntry, 1113 PDN-LINK-LOAD-SHARING-MIB.mib, 1101, 1104 pdnMgmtAtmInvArpEntry, 199 PDN-MGMT-IP-MIB, 198 pdnMgmtIpPortTable, 198 pdnRedunEventCfgIncompatible, 114 pdnRedunEventFwIncompatible, 114 pdnRedunEventHwIncompatible, 113 pdnRedunEventNoActiveModule, 113...
  • Page 128 Index traps ADSL, 1118 ATM-M4, 1116 devLastTrapString, 1116 DSX, 1116 Enterprise-Specific, 1117 Entity MIB, 1116 IMA, 1118 SHDSL, 1117 standards compliance, 110 summary of, 110 IN-4 User-based Security Model, 192 VC Cross-Connect Table, 161 VCL, 156 View-based Access Control (VACM), 193, 197 Virtual Channel Link Configuration Group, 156 WarmStart, 110 June 2004...

This manual is also suitable for:

8820

Table of Contents