Paradyne 8820 Supporting MIBs SNMP-MPD-MIB RFC, SnmpEngineID, SnmpEngineBoots, SnmpEngineTime

Page 82

1. Network Management Specification

7.7.2Supporting MIBs.

7.7.3SNMP-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.1snmpUnknownSecurityModels

7.7.3.2snmpInvalidMsgs

7.7.3.3snmpUnknownPDUHandlers

7.7.4SNMP Framework MIB (RFC 3411)

In addition to defining new textual conventions, this MIB defines the following scalar objects that will be supported in the SCP:

7.7.4.1snmpEngineID:

There will be a unique identifier for the SNMP engine running in the device. It will be set up by following one of the schemes proposed in the RFC 3411. That is, it will use the private enterprise number assigned to Paradyne (1795) by the Internet Assigned Numbers Authority and the MAC address of the card (SCP) running the agent to generate a unique identifier for the Engine.

For example the MAC address of my SCP card is ’00-E0-39-C1-CD-16’ will result in the following snmpEngineID:

80 00 07 03 03 00 E0 39 C1 CD 16

See RFC 3411 for details on how this is formatted.

7.7.4.2snmpEngineBoots:

Number of times this entity has been reboot. This number must be preserved upon reset of the entity.

7.7.4.3snmpEngineTime:

Actual sysUpTime since last reboot.

7.7.4.4snmpMaxMessageSize: Based on configuration of the Emanate/Lite agent.

7.7.4.5SNMP-TARGET-MIB (RFC 2573)

The SCP will use the SNMP-TARGET-MIB exclusively to configure trap managers. The following MIB objects contained in SNMP-TARGET-MIB will be supported to configure trap managers.

7.7.4.5.1snmpTargetSpinLock:

It is used to control multiple simultaneous access to the target table. Users must follow the procedure in RFC 2573 to add/modify entries in this table.

7.7.4.5.2snmpTargetAddrTable:

It is used to configure transport addresses to be used in the generation of SNMP notification messages.

76

June 2003

8000-A2-GB30-00

Image 82
Contents Hotwire 8620 Copyright 2003 Paradyne Corporation All rights reserved Contents Contents June About This Guide Section DescriptionProduct-Related Documents Document Number Document TitleSupported RFCs and MIBs 1 GranDSLAM 3.0 Network Management InterfaceName Description Supported RFCs and MIBs 2 Supported RFCs and MIBs 3 IMA MIBSupported RFCs and MIBs 4 PDN-ENTITY-REDUNDANCY-MIBSupported RFCs and MIBs 5 PDN-DS1EXT-MIBOther Supported RFCs Used as Guidelines for Implementation Name/DescriptionDSX Traps Standards Compliance for Snmp TrapsSummary of Traps 1 Description VarBinds Standard Traps ATM-M4 TrapsEntity MIB Traps Summary of Traps 2 Description VarBindsShdsl MIB Traps Summary of Traps 3 Description VarBinds Sonet Linear APS MIB Traps Summary of Traps 4 Description VarBindsEnterprise Specific Traps Adsl Specific Traps Summary of Traps 5 Description VarBindsSummary of Traps 6 Description VarBinds IMA Traps Summary of Traps 7 Description VarBindsStandards Compliance to Snmp MIBs GranDSLAM Interfaces System Group, MIB-II RFC Management Information Base MIB-II RFCSysDescr Object system SysObjectID Object system SysServices Object systemSysServices Layer L Functionality Value2L-1 Sum SysUpTime Object systemIfIndex Object ifEntry Evolution of the Interfaces Group of MIB-II RFCIfNumber Object interfaces IfIndex schemeGranDSLAM 3.0 Interface List Layer Supported Maximum IfName Interface indexes ifIndex IfIndex Assignments IfDescr Object ifEntryIfMtu IfType Object ifEntryIfMtu Object ifEntry Interface IfMtuIfSpeed IfAdminStatus Object ifEntryIfSpeed Object ifEntry Interface IfSpeedIfOperStatus Object ifEntry IfAdminStatusInterface IfAdminStatus IfOperStatusIfLastChange Object ifEntry IfInUcastPkts Object ifEntry 14. ifInUncastPkts Interface IfInUncastPkts Object ifEntry 15. ifInUncastPkts InterfaceIfInErrors Object ifEntry 17. ifInErrors Interface IfInDiscards Object ifEntry 16. ifInDiscards InterfaceETH1 IMA IfOutUcastPkts Object ifEntry 20. ifOutUcastPkts Interface IfOutNUcasts Object ifEntry InterfaceIfOutDiscards Object ifEntry 22. ifOutDiscards Interface IfOutErrors Object ifEntry InterfaceIfOutQLen ifEntry Extension to the Intf. Table ifXTable RFC IfLinkUpDownTrapEnable Object ifXEntryIfSpecific ifEntry 24. Extension to the Interface TableInterface Stack Group RFC IfStackHigherLayer Object ifStackEntryTransmission Group, MIB-II RFC 1213 Supported IfStackLowerLayer Object ifStackEntryIfStackStatus Object ifStackEntry Snmp Group, MIB-II RFCNetwork Management Specification Physical Layer Adsl MIB RFC 28. Adsl MIB Comments DS1 MIB RFC 31. DS1 MIB Comments Paradyne ReachDSL MIB pdnreachDSL.mib30. ReachDSL MIB Comments Paradyne DS1-EXT MIB PDN-DS1EXT-MIBPdnDs1ExtConfLineLengthType RW PdnDs1ExtConfConnector RW32. DS1-EXT MIB Comments PdnDs1ExtConfLineLength RWSonetSESthresholdSet SONET-MIB RFC 33. SONET-MIB CommentsSonetMediumEntry 34. sonetMediumEntry Comments SonetPathCurrentWidthDevSonetXmitClkSrc DevSonetStatusChangeTrapEnableBy default, this object is enabled DevSonetStatusLastChangeSpectrum Management pdnspectrummgmt.mib NewSpectrumMgmtGeneralConfigEntry36. Shdsl MIB Comments 37. Spectrum Management Comments38. ATM MIB Comments ATM Interface Configuration Parameter Group RFCLink Layer ATM AtoM MIB RFC AtmInterfaceMaxVpcs Object atmInterfaceConfEntryAtmInterfaceMaxVccs AtmInterfaceMaxVccs Object atmInterfaceConfEntry40. atmInterfaceMaxVccs AtmInterfaceConfVpcs Object atmInterfaceConfEntryAtmInterfaceMaxActiveVciBits Object atmInterfaceConfEntry AtmInterfaceIlmiVpi AccessAtmInterfaceIlmiVci Access AtmInterfaceMaxActiveVciBitsAtmInterfaceMyNeighborIfName Object atmInterfaceConfEntry AtmInterfaceMyNeighborIpAddress AccessAtmInterfaceMyNeighborIfName Access AtmInterfaceCurrentMaxVpiBits Object atmInterfaceConfEntryAtmInterfaceSubscrAddress Object atmInterfaceConfEntry AtmInterfaceTCAlarmState Object atmInterfaceTCEntryAtmInterfaceCurrentMaxVciBits Object atmInterfaceConfEntry AtmInterfaceSubscrAddressATM Traffic Descriptor Group RFC AtmServiceCategory Object atmTrafficDescrParamEntryVirtual Channel Link VCL Configuration Group RFC 54. Traffic Descriptor TypesAtmVccAalType Object atmVclEntry AtmVclOperStatus Object atmVclEntryAtmVclLastChange Object atmVclEntry AtmVccAal5CpcsTransmitSduSize Object atmVclEntryVirtual Channel Cross Connect Group RFC AtmVcCrossConnectRowStatus Object atmVcCrossConnectEntry55. Object Supported in ATM Forum MIB Type AtmfM4TcAlarmSeverityIndexObject atmfM4TcAdapterEntryAtmfM4MIB- Snmp M4 Network Element View MIB atmfM4MIB TC Adapter Layer Table atmfM4TcAdapterEntryAtmfM4IfType Object atmfM4ATMLayerEntry AtmfM4VcXConnRecover Object atmfM4VcXConnEntry1ATM Cell Layer Table atmfM4ATMLayerEntry AtmfM4IfSubscriberAddress Object atmfM4ATMLayerEntry56. Paradyne Extensions to ATM MIBs 1 Sup Object Type Ported ATM Loopback 57. ATM Loopback CommentsGoto tryagain IMA MIB AF-PHY-0086.001 58. IMA MIB Object EntityPhysical Group Syntax Access Status PortedEntity MIB version 2 Objects supported 59. entPhysicalEntry entPhysicalTable 1 1 Sup Object60. entPhysicalIndex Entity Comments 59. entPhysicalEntry entPhysicalTable 1 2 Sup ObjectEntPhysicalIndex EntPhysicalDescr61. entPhysicalDescr Entity Description EntPhysicalVendorType63. entPhysicalVendorType 1 Entity EntPhysicalVendorType EntPhysicalContainedIn 63. entPhysicalVendorType 2 Entity EntPhysicalVendorType64. entPhysicalContainedIn Entity EntPhysicalContainIn 65. entPhysicalClass Entity EntPhysicalClass EntPhysicalClassEntPhysicalParentRelPos 67. entPhysicalName Entity EntPhysicalName EntPhysicalNameEntPhysicalHardwareRev EntPhysicalFirmwareRev 68. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalSoftwareRev 69. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRev70. entPhysicalSerialNum Entity EntPhysicalSerialNum 69. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum EntPhysicalMfgNameEntPhysicalModelName 71. entPhysicalMfgName Entity EntPhysicalMfgName72. entPhysicalModelName 1 Entity EntPhysicalModelName EntPhysicalAlias 72. entPhysicalModelName 2 Entity EntPhysicalModelName73. entPhysicalAlias Entity EntPhysicalAlias EntPhysicalIsFRU EntPhysicalAssetID74. entPhysicalAssetID Entity EntPhysicalAssetID 75. entPhysicalIsFRU 1 Entity76. entLogicalEntry entLogicalTable Sup Object 75. entPhysicalIsFRU 2 Entity EntPhysicalIsFRUEntityLogical Group EntLogicalIndexEntLogicalContextEngineID EntLogicalTAddressEntLogicalIPDomain EntLogicalContextNameEntityGeneral Group MpeEntPhysicalExtAdminStatusEntPhysicalChildIndex Entity EntPhysicalIndex Semantic EntityNotifications GroupEntity Sensor MIB RFC EntPhySensorValueUpdateRateMpeEntPhysicalExtOperStatus 81. Entity Sensor MIB CommentsIfMauIndex RO IfMauTable Supporte Object Type AccessIfMauIfIndex RO IfMauType ROIfMauAutoNegSupported RO IfMauDefaultType RWIfMauStatus RO IfMauTypeListBits ROPdnMgmtIpPortTable 84. PDN-MGMT-IP-MIB Object Type SupportedPdnMgmtIpPortIndex NA PdnMgmtBootVpi RW PdnMgmtIpConfigMode RWPdnMgmtBootIfIndex RW PdnMgmtBootVci RWPdnMgmtAtmVpi NA PdnMgmtAtmInvArpTablePdnMgmtAtmIfIndex NA PdnMgmtAtmVci NASnmpEngineID SnmpEngineBootsSupporting MIBs SNMP-MPD-MIB RFC SnmpEngineTimeSnmpTargetParmsTable SNMPv1 traps Default valuesSNMPv2 traps Default values SnmpUnavailableContexts and snmpUnknownContextsSupporting MIBs View-based Access Control VacmUser-based Security Model USM RFC StatisticsVacmSecurityToGroupTable VacmAccessTableVacmContextTable VacmViewTreeFamilyTableApsConfigMode Link Fault Management86. pdnLinkFaultMgmtApsSelection Comments ApsConfigRowStatus88. pdnLinkFaultMgmtSwitchoverSelection Comments PdnLLSConfigGroupNamePdnLLSConfigSelection Link Load Sharing LLS PDN-LINK-LOAD-SHARING-MIB.mibPdnRedunNotificationEnable PdnRedunCommandPdnRedunAlarmStatus PdnRedunEntityState90. mpeDevConfigClockSrcEntry Object Type Access Supported Timing and Clocking Paradyne mpeConfig MIB mpeConfig.mibDevConfigTestTimeout Paradyne Time Mib pdntime.mib DevConfigTestDuration92. pdntime.mib Object Type Access Supported DevDateAndTime RWDevNTPEnable RW DevNTPOffsetFromUTC93. pdndslam.mib Objects Supported Type SysDevUserAccountUserPassword RCSysDevUserAccountAccessPartition RC SysDevUserAccountTable94. pdnSecurity.mib Object Type Supported SecurityMgrSnmpAccess RWParadyne Security MIB pdnSecurity.mib DevSecurityMgrValidation RWSecurityMgrTrapAccess RW SecurityMgrTelnetAccessRWSecurityMgrFtpAccess RW SecurityMgrRowStatus RWMpeDevFileXferFileType3 95. mpeControl.mib 2 Object Type Supported MpeDevFileXferConfigTableMpeDevControlTable MpeDevFirmwareControlTable PdnSyslogLevel PdnSyslogStatus RWPdnSyslogIPAddr RW PdnSyslogPort RWPdnEntitySyslogTable NA PdnSyslogSeverityThreshold RWPdnSyslogRemoteDaemon RW PdnEntitySyslogNumber NAParadyne Health and Status MIB mpeHealthAndStatus.mib Traps PdnDevConfigTrapsEnable RW pdnTrapMgr.mibPdnSyslogRateLimiting RW 97. Health and Status MIB Comments98. devLastTrapString 2 DevLastTrapString DSX Traps 98. devLastTrapString 3 DevLastTrapString Adsl Specific Traps98. devLastTrapString 4 DevLastTrapString IMA Traps Network Management Specification June Index IN-2 IN-3 IN-4
Related manuals
Manual 58 pages 27.69 Kb Manual 108 pages 33.36 Kb

8620, 8820 specifications

The Paradyne 8620 and Hotwire 8620 GranDSLAM are advanced DSLAM devices designed to provide high-speed broadband access over existing copper lines. This installation guide will outline the main features, technologies, and characteristics of these powerful units.

The Paradyne 8620 is engineered to support various DSL technologies, including ADSL, ADSL2+, and VDSL. This versatility allows operators to deploy services tailored to the needs of their customers, enabling data rates of up to 50 Mbps downstream, making it an ideal choice for meeting increasing bandwidth demands. The Hotwire 8620 GranDSLAM shares many similarities, focusing on providing enhanced service delivery for both residential and business users.

One of the key features of the GranDSLAM series is its modular architecture. Both models support up to 48 subscriber line interfaces in a single chassis, which provides significant scalability. Operators can seamlessly increase capacity by adding additional cards to accommodate growth. The devices are designed for easy deployment and management, equipped with an intuitive web-based interface that simplifies configuration and monitoring tasks.

Both units also feature advanced management capabilities, including support for SNMP and TR-069 protocols. This allows service providers to manage and provision devices remotely, significantly reducing operational costs and improving service reliability. The GranDSLAM models can also provide detailed diagnostic information, helping operators quickly identify and troubleshoot issues.

The Paradyne and Hotwire series ensure interoperability with various customer premises equipment, enabling service providers to offer bundled services such as voice, video, and data over the same connection. This capability is enhanced by the units’ ability to support VLANs and QoS features, ensuring that high-priority traffic receives the necessary bandwidth.

In addition to performance, the 8620 series is built with energy efficiency in mind. By utilizing power-saving features, these units help reduce overall operational costs while still providing reliable service.

Overall, the Paradyne 8620 and Hotwire 8620 GranDSLAM are robust solutions for service providers looking to deliver high-speed broadband services. Their modular design, advanced management capabilities, and support for multiple DSL technologies make them an excellent choice for today’s demanding telecommunications environment. With these advantages, operators can effectively meet customer needs while preparing for future growth and technology advancements.