Paradyne 8620 PdnMgmtAtmInvArpTable, PdnMgmtAtmIfIndex NA, PdnMgmtAtmVpi NA, PdnMgmtAtmVci NA

Page 81

1. Network Management Specification

7.6.2pdnMgmtAtmInvArpTable.

This table contains one row per Inverse ATM ARP entry in the system. This table maps the <ifIndex, vpi, vci> index to corresponding <ipPortIndex, remoteIp> of the pdnMgmtIpPortTable in 3.30.1.

7.6.2.1pdnMgmtAtmIfIndex (NA)

The interface index associated with the ATM PVC.

7.6.2.2pdnMgmtAtmVpi (NA)

The VPI associated with the ATM PVC.

7.6.2.3pdnMgmtAtmVci (NA)

The VCI associated with the ATM PVC.

7.6.2.4pdnMgmtIpPortIfIndex (RC)

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.

7.6.2.5pdnMgmtNextHopIp (RC)

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.

7.6.2.6pdnMgmtAtmInvArpRowStatus (RC)

This object is used to create/delete the ATM inverse ARP entry in this table.

pdnMgmtIpDefaultRouter (RW)

This object identifies the default IP router to use for IP packets with no other known route.

An IP address of 0.0.0.0 would disable and delete the default route from the system.

7.7SNMPv3.

7.7.1Framework and Applications.

Based on current requirements for the GranDSLAM 3.0 project, this is the level of support desired:

Command Generators: It is not required that our DSLAM products generate SNMP messages. However, it may not be possible to turn this feature off from the Emanate/Lite agent configuration.

Command Responders: This is the primary function of our DSLAM management entity. Thus, this will be implemented as indicated in RFC 2573.

Notification Originators: Initiating traps is a primary function of the SCP management entities. The INFORM operation (Confirmed notifications) is currently not required in our products and will not be implemented.

Notification Receivers: It is not required that our DSLAM products be able to receive and process notifications from other Entities, thus this application will not be implemented.

Proxy Forwarders: It is not required that our GranDSLAM 3.0 product act as a proxy since we will have only one SNMP engine running. The implementation of this application is optional as per the standard.

8000-A2-GB30-00

June 2003

75

Image 81
Contents Hotwire 8620 Copyright 2003 Paradyne Corporation All rights reserved Contents Contents June Section Description About This GuideDocument Number Document Title Product-Related DocumentsGranDSLAM 3.0 Network Management Interface Supported RFCs and MIBs 1Name Description Supported RFCs and MIBs 2 IMA MIB Supported RFCs and MIBs 3PDN-ENTITY-REDUNDANCY-MIB Supported RFCs and MIBs 4PDN-DS1EXT-MIB Supported RFCs and MIBs 5Name/Description Other Supported RFCs Used as Guidelines for ImplementationSummary of Traps 1 Description VarBinds Standard Traps Standards Compliance for Snmp TrapsDSX Traps ATM-M4 TrapsSummary of Traps 2 Description VarBinds Entity MIB TrapsShdsl MIB Traps Summary of Traps 3 Description VarBinds Summary of Traps 4 Description VarBinds Sonet Linear APS MIB TrapsEnterprise Specific Traps Summary of Traps 5 Description VarBinds Adsl Specific TrapsSummary of Traps 6 Description VarBinds Summary of Traps 7 Description VarBinds IMA TrapsStandards Compliance to Snmp MIBs GranDSLAM Interfaces Management Information Base MIB-II RFC System Group, MIB-II RFCSysDescr Object system SysServices Layer L Functionality Value2L-1 Sum SysServices Object systemSysObjectID Object system SysUpTime Object systemIfNumber Object interfaces Evolution of the Interfaces Group of MIB-II RFCIfIndex Object ifEntry IfIndex schemeGranDSLAM 3.0 Interface List Layer Supported Maximum IfName Interface indexes ifIndex IfDescr Object ifEntry IfIndex AssignmentsIfMtu Object ifEntry IfType Object ifEntryIfMtu Interface IfMtuIfSpeed Object ifEntry IfAdminStatus Object ifEntryIfSpeed Interface IfSpeedInterface IfAdminStatus IfAdminStatusIfOperStatus Object ifEntry IfOperStatusIfLastChange Object ifEntry IfInUncastPkts Object ifEntry 15. ifInUncastPkts Interface IfInUcastPkts Object ifEntry 14. ifInUncastPkts InterfaceIfInDiscards Object ifEntry 16. ifInDiscards Interface IfInErrors Object ifEntry 17. ifInErrors InterfaceETH1 IMA IfOutNUcasts Object ifEntry Interface IfOutUcastPkts Object ifEntry 20. ifOutUcastPkts InterfaceIfOutErrors Object ifEntry Interface IfOutDiscards Object ifEntry 22. ifOutDiscards InterfaceIfOutQLen ifEntry IfSpecific ifEntry IfLinkUpDownTrapEnable Object ifXEntryExtension to the Intf. Table ifXTable RFC 24. Extension to the Interface TableIfStackHigherLayer Object ifStackEntry Interface Stack Group RFCIfStackStatus Object ifStackEntry IfStackLowerLayer Object ifStackEntryTransmission Group, MIB-II RFC 1213 Supported Snmp Group, MIB-II RFCNetwork Management Specification Physical Layer Adsl MIB RFC 28. Adsl MIB Comments 30. ReachDSL MIB Comments Paradyne ReachDSL MIB pdnreachDSL.mibDS1 MIB RFC 31. DS1 MIB Comments Paradyne DS1-EXT MIB PDN-DS1EXT-MIB32. DS1-EXT MIB Comments PdnDs1ExtConfConnector RWPdnDs1ExtConfLineLengthType RW PdnDs1ExtConfLineLength RWSonetMediumEntry 34. sonetMediumEntry Comments SONET-MIB RFC 33. SONET-MIB CommentsSonetSESthresholdSet SonetPathCurrentWidthBy default, this object is enabled DevSonetStatusChangeTrapEnableDevSonetXmitClkSrc DevSonetStatusLastChange36. Shdsl MIB Comments NewSpectrumMgmtGeneralConfigEntrySpectrum Management pdnspectrummgmt.mib 37. Spectrum Management CommentsLink Layer ATM AtoM MIB RFC ATM Interface Configuration Parameter Group RFC38. ATM MIB Comments AtmInterfaceMaxVpcs Object atmInterfaceConfEntry40. atmInterfaceMaxVccs AtmInterfaceMaxVccs Object atmInterfaceConfEntryAtmInterfaceMaxVccs AtmInterfaceConfVpcs Object atmInterfaceConfEntryAtmInterfaceIlmiVci Access AtmInterfaceIlmiVpi AccessAtmInterfaceMaxActiveVciBits Object atmInterfaceConfEntry AtmInterfaceMaxActiveVciBitsAtmInterfaceMyNeighborIfName Access AtmInterfaceMyNeighborIpAddress AccessAtmInterfaceMyNeighborIfName Object atmInterfaceConfEntry AtmInterfaceCurrentMaxVpiBits Object atmInterfaceConfEntryAtmInterfaceCurrentMaxVciBits Object atmInterfaceConfEntry AtmInterfaceTCAlarmState Object atmInterfaceTCEntryAtmInterfaceSubscrAddress Object atmInterfaceConfEntry AtmInterfaceSubscrAddressVirtual Channel Link VCL Configuration Group RFC AtmServiceCategory Object atmTrafficDescrParamEntryATM Traffic Descriptor Group RFC 54. Traffic Descriptor TypesAtmVclLastChange Object atmVclEntry AtmVclOperStatus Object atmVclEntryAtmVccAalType Object atmVclEntry AtmVccAal5CpcsTransmitSduSize Object atmVclEntryAtmVcCrossConnectRowStatus Object atmVcCrossConnectEntry Virtual Channel Cross Connect Group RFCAtmfM4MIB- Snmp M4 Network Element View MIB atmfM4MIB AtmfM4TcAlarmSeverityIndexObject atmfM4TcAdapterEntry55. Object Supported in ATM Forum MIB Type TC Adapter Layer Table atmfM4TcAdapterEntryATM Cell Layer Table atmfM4ATMLayerEntry AtmfM4VcXConnRecover Object atmfM4VcXConnEntry1AtmfM4IfType Object atmfM4ATMLayerEntry AtmfM4IfSubscriberAddress Object atmfM4ATMLayerEntry56. Paradyne Extensions to ATM MIBs 1 Sup Object Type Ported 57. ATM Loopback Comments ATM LoopbackGoto tryagain IMA MIB AF-PHY-0086.001 58. IMA MIB Object Entity MIB version 2 Objects supported Syntax Access Status PortedEntityPhysical Group 59. entPhysicalEntry entPhysicalTable 1 1 Sup ObjectEntPhysicalIndex 59. entPhysicalEntry entPhysicalTable 1 2 Sup Object60. entPhysicalIndex Entity Comments EntPhysicalDescrEntPhysicalVendorType 61. entPhysicalDescr Entity Description63. entPhysicalVendorType 1 Entity EntPhysicalVendorType 63. entPhysicalVendorType 2 Entity EntPhysicalVendorType EntPhysicalContainedIn64. entPhysicalContainedIn Entity EntPhysicalContainIn EntPhysicalClass 65. entPhysicalClass Entity EntPhysicalClassEntPhysicalParentRelPos EntPhysicalName 67. entPhysicalName Entity EntPhysicalNameEntPhysicalHardwareRev EntPhysicalSoftwareRev 68. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalFirmwareRev 69. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum 69. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRev70. entPhysicalSerialNum Entity EntPhysicalSerialNum EntPhysicalMfgName71. entPhysicalMfgName Entity EntPhysicalMfgName EntPhysicalModelName72. entPhysicalModelName 1 Entity EntPhysicalModelName 72. entPhysicalModelName 2 Entity EntPhysicalModelName EntPhysicalAlias73. entPhysicalAlias Entity EntPhysicalAlias 74. entPhysicalAssetID Entity EntPhysicalAssetID EntPhysicalAssetIDEntPhysicalIsFRU 75. entPhysicalIsFRU 1 EntityEntityLogical Group 75. entPhysicalIsFRU 2 Entity EntPhysicalIsFRU76. entLogicalEntry entLogicalTable Sup Object EntLogicalIndexEntLogicalIPDomain EntLogicalTAddressEntLogicalContextEngineID EntLogicalContextNameEntPhysicalChildIndex Entity EntPhysicalIndex Semantic MpeEntPhysicalExtAdminStatusEntityGeneral Group EntityNotifications GroupMpeEntPhysicalExtOperStatus EntPhySensorValueUpdateRateEntity Sensor MIB RFC 81. Entity Sensor MIB CommentsIfMauIfIndex RO IfMauTable Supporte Object Type AccessIfMauIndex RO IfMauType ROIfMauStatus RO IfMauDefaultType RWIfMauAutoNegSupported RO IfMauTypeListBits RO84. PDN-MGMT-IP-MIB Object Type Supported PdnMgmtIpPortTablePdnMgmtIpPortIndex NA PdnMgmtBootIfIndex RW PdnMgmtIpConfigMode RWPdnMgmtBootVpi RW PdnMgmtBootVci RWPdnMgmtAtmIfIndex NA PdnMgmtAtmInvArpTablePdnMgmtAtmVpi NA PdnMgmtAtmVci NASupporting MIBs SNMP-MPD-MIB RFC SnmpEngineBootsSnmpEngineID SnmpEngineTimeSNMPv2 traps Default values SNMPv1 traps Default valuesSnmpTargetParmsTable SnmpUnavailableContexts and snmpUnknownContextsUser-based Security Model USM RFC View-based Access Control VacmSupporting MIBs StatisticsVacmContextTable VacmAccessTableVacmSecurityToGroupTable VacmViewTreeFamilyTable86. pdnLinkFaultMgmtApsSelection Comments Link Fault ManagementApsConfigMode ApsConfigRowStatusPdnLLSConfigSelection PdnLLSConfigGroupName88. pdnLinkFaultMgmtSwitchoverSelection Comments Link Load Sharing LLS PDN-LINK-LOAD-SHARING-MIB.mibPdnRedunAlarmStatus PdnRedunCommandPdnRedunNotificationEnable PdnRedunEntityStateTiming and Clocking Paradyne mpeConfig MIB mpeConfig.mib 90. mpeDevConfigClockSrcEntry Object Type Access SupportedDevConfigTestTimeout 92. pdntime.mib Object Type Access Supported DevConfigTestDurationParadyne Time Mib pdntime.mib DevDateAndTime RWDevNTPOffsetFromUTC DevNTPEnable RWSysDevUserAccountAccessPartition RC SysDevUserAccountUserPassword RC93. pdndslam.mib Objects Supported Type SysDevUserAccountTableParadyne Security MIB pdnSecurity.mib SecurityMgrSnmpAccess RW94. pdnSecurity.mib Object Type Supported DevSecurityMgrValidation RWSecurityMgrFtpAccess RW SecurityMgrTelnetAccessRWSecurityMgrTrapAccess RW SecurityMgrRowStatus RWMpeDevFileXferFileType3 MpeDevFileXferConfigTable 95. mpeControl.mib 2 Object Type SupportedMpeDevControlTable MpeDevFirmwareControlTable PdnSyslogIPAddr RW PdnSyslogStatus RWPdnSyslogLevel PdnSyslogPort RWPdnSyslogRemoteDaemon RW PdnSyslogSeverityThreshold RWPdnEntitySyslogTable NA PdnEntitySyslogNumber NAPdnSyslogRateLimiting RW Traps PdnDevConfigTrapsEnable RW pdnTrapMgr.mibParadyne Health and Status MIB mpeHealthAndStatus.mib 97. Health and Status MIB Comments98. devLastTrapString 2 DevLastTrapString DSX Traps Adsl Specific Traps 98. devLastTrapString 3 DevLastTrapString98. 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.