Paradyne 8620, 8820 manual ATM Loopback Comments

Page 59

Table 1-57. Paradyne Extensions to ATM MIBs (2 of 2)

 

 

 

Sup-

Table

Object

Type

ported

 

 

 

 

pdnATMVclCurrEntry

 

 

Yes

(pdn_ATMStats.mib)

 

 

 

pdnATMVclCurrElapsedTime

Gauge32

Read-Only

 

 

 

 

 

pdnATMVclCurrTotalCellIns

Gauge32

Read-Only

 

 

 

 

 

pdnATMVclCurrTotalInDiscards

Gauge32

n

 

 

 

 

 

pdnATMVclCurrTotalCellOuts

Gauge32

Read-Only

 

 

 

 

 

pdnATMVclCurrTotalOutDiscards

Gauge32

Read-Only

 

 

 

 

pdnATMVclHistEntry

pdnATMVclHistIndex

INTEGER

Read-Only

(pdn_ATMStats.mib)

 

 

 

pdnATMVclHistElapsedTime

TimeInterval

Read-Only

 

 

 

 

 

pdnATMVclHistTotalCellIns

Gauge32

Read-Only

 

 

 

 

 

pdnATMVclHistTotalInDiscards

Gauge32

n

 

 

 

 

 

pdnATMVclHistTotalCellOuts

Gauge32

Read-Only

 

 

 

 

 

pdnATMVclHistTotalOutDiscards

Gauge32

Read-Only

 

 

 

 

6.5ATM 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).

Table 1-58. ATM Loopback

Table

Comments

 

 

pdnATMfM4VcLoopbackTestEntry

Supported as is

 

 

In order to distinguish a single-cell loopback test from a multi-cell loopback test, In addition to ATM Forum M4 Test Types atmfM4VcTestOAMLoopbackSeg and atmfM4VcTestOAMLoopbackE2E, which indicate a single-cell loopback test, two new test commands pdnATMfM4TestOAMLoopbackSegMultiCell and pdnATMfM4VcTestOAMloopbackE2EMultiCell are defined to stop but not dealloc the ATM F5 loopback test resource (such as result).

In order to initiate an ATM F5 Segment loopback test, an NMS must first obtain ‘ownership’ of the entry in the atmfM4VcTestTable for the VCC or VCL to be tested. This is accomplished with atmfM4VcTestId and atmfM4VcTestStatus object as follows:

try_again:

get (atmfM4VcTestId, atmfM4VcTestStatus) while (atmfM4TestStatus != notInUse)

/* Loop while a test is running or some other

*manager is configuring a test. */

short delay

8000-A2-GB30-10

November 2003

53

Image 59
Contents Hotwire 8620 Copyright 2003 Paradyne Corporation All rights reserved Contents Contents November Section Description About This GuideDocument Number Document Title Product-Related DocumentsName Description GranDSLAM 3.2 Network Management InterfaceSupported RFCs and MIBs 1 IMA MIB Supported RFCs and MIBs 2Supported RFCs and MIBs 3 PDN-ENTITY-REDUNDANCY-MIB Supported RFCs and MIBs 4PDN-DS1EXT-MIB Supported RFCs and MIBs 5Name/Description Other Supported RFCs Used as Guidelines for ImplementationATM-M4 Traps Standards Compliance for Snmp TrapsSummary of Traps 1 Description VarBinds Standard Traps DSX TrapsShdsl MIB Traps Summary of Traps 2 Description VarBindsEntity MIB Traps Summary of Traps 3 Description VarBinds Enterprise Specific Traps Summary of Traps 4 Description VarBindsSonet Linear APS MIB 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 SysDescr Object system Management Information Base MIB-II RFCSystem Group, MIB-II RFC SysUpTime Object system SysServices Object systemSysServices Layer L Functionality Value2L-1 Sum SysObjectID Object systemIfIndex scheme Evolution of the Interfaces Group of MIB-II RFCIfNumber Object interfaces IfIndex Object ifEntryGranDSLAM R3.2 Interface List Layer Supported Maximum IfName Interface indexes ifIndex IfDescr Object ifEntry IfIndex AssignmentsInterface IfMtu IfType Object ifEntryIfMtu Object ifEntry IfMtuInterface IfSpeed IfAdminStatus Object ifEntryIfSpeed Object ifEntry IfSpeedIfOperStatus IfAdminStatusInterface IfAdminStatus IfOperStatus Object ifEntryIfLastChange Object ifEntry IMA Atmup AAL5 ETH1 Sonet IfInDiscards Object ifEntry 13 -16. ifInDiscards Interface IfInErrors Object ifEntry 14 -17. ifInErrors InterfaceETH1 IMA IfOutNUcasts Object ifEntry 18 -21. ifOutNUcasts Interface IfOutQLen ifEntry IfOutErrors Object ifEntry Interface24. Extension to the Interface Table IfLinkUpDownTrapEnable Object ifXEntryIfSpecific ifEntry Extension to the Intf. Table ifXTable RFCIfStackHigherLayer Object ifStackEntry Interface Stack Group RFCSnmp Group, MIB-II RFC IfStackLowerLayer Object ifStackEntryIfStackStatus Object ifStackEntry Transmission Group, MIB-II RFC 1213 SupportedNovember 8000-A2-GB30-10 Physical Layer Adsl MIB RFC 2662 -28. Adsl MIB Comments 31. ReachDSL MIB Comments Paradyne ReachDSL MIB pdnreachDSL.mibPdnDs1ExtConfLineLengthType RW DS1 MIB RFC 2495 -32. DS1 MIB CommentsParadyne DS1-EXT MIB PDN-DS1EXT-MIB 33. DS1-EXT MIB CommentsPdnDs1ExtConfLineBuildOut RW PdnDs1ExtConfConnector RWSonetPathCurrentWidth SONET-MIB RFC 2558 -34. SONET-MIB CommentsSonetMediumEntry -35. sonetMediumEntry Comments SonetSESthresholdSetDevSonetStatusLastChange DevSonetStatusChangeTrapEnableBy default, this object is enabled DevSonetXmitClkSrc38. Spectrum Management Comments NewSpectrumMgmtGeneralConfigEntry37. Shdsl MIB Comments Spectrum Management pdnspectrummgmt.mibAtmInterfaceMaxVpcs Object atmInterfaceConfEntry ATM Interface Configuration Parameter Group RFCLink Layer ATM AtoM MIB RFC 39. ATM MIB CommentsAtmInterfaceConfVpcs Object atmInterfaceConfEntry AtmInterfaceMaxVccs Object atmInterfaceConfEntryAtmInterfaceMaxVccs Interface AtmInterfaceMaxVccsAtmInterfaceMaxActiveVciBits AtmInterfaceIlmiVpi AccessAtmInterfaceIlmiVci Access AtmInterfaceMaxActiveVciBits Object atmInterfaceConfEntryAtmInterfaceCurrentMaxVpiBits Object atmInterfaceConfEntry AtmInterfaceMyNeighborIpAddress AccessAtmInterfaceMyNeighborIfName Access AtmInterfaceMyNeighborIfName Object atmInterfaceConfEntryAtmInterfaceSubscrAddress AtmInterfaceTCAlarmState Object atmInterfaceTCEntryAtmInterfaceCurrentMaxVciBits Object atmInterfaceConfEntry AtmInterfaceSubscrAddress Object atmInterfaceConfEntry55. Traffic Descriptor Types AtmServiceCategory Object atmTrafficDescrParamEntryVirtual Channel Link VCL Configuration Group RFC ATM Traffic Descriptor Group RFCAtmVccAal5CpcsTransmitSduSize Object atmVclEntry AtmVclOperStatus Object atmVclEntryAtmVclLastChange Object atmVclEntry AtmVccAalType Object atmVclEntryAtmVcCrossConnectRowStatus Object atmVcCrossConnectEntry Virtual Channel Cross Connect Group RFCTC Adapter Layer Table atmfM4TcAdapterEntry AtmfM4TcAlarmSeverityIndexObject atmfM4TcAdapterEntryAtmfM4MIB- Snmp M4 Network Element View MIB atmfM4MIB 56. Object Supported in ATM Forum MIB TypeAtmfM4IfSubscriberAddress Object atmfM4ATMLayerEntry AtmfM4VcXConnRecover Object atmfM4VcXConnEntry1ATM Cell Layer Table atmfM4ATMLayerEntry AtmfM4IfType Object atmfM4ATMLayerEntry57. Paradyne Extensions to ATM MIBs 1 Sup Object Type Ported 58. ATM Loopback Comments ATM LoopbackGoto tryagain IMA MIB AF-PHY-0086.001 -59. IMA MIB Object 60. entPhysicalEntry entPhysicalTable 1 1 Sup Object Syntax Access Status PortedEntity MIB version 2 Objects supported EntityPhysical GroupEntPhysicalDescr 60. entPhysicalEntry entPhysicalTable 1 2 Sup ObjectEntPhysicalIndex 61. entPhysicalIndex Entity CommentsEntPhysicalVendorType 62. entPhysicalDescr Entity Description64. entPhysicalVendorType 1 Entity EntPhysicalVendorType 65. entPhysicalContainedIn Entity EntPhysicalContainIn 64. entPhysicalVendorType 2 Entity EntPhysicalVendorTypeEntPhysicalContainedIn EntPhysicalParentRelPos EntPhysicalClass66. entPhysicalClass Entity EntPhysicalClass EntPhysicalHardwareRev EntPhysicalName68. entPhysicalName Entity EntPhysicalName 70. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRev 69. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalSoftwareRev EntPhysicalFirmwareRevEntPhysicalMfgName 70. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum 71. entPhysicalSerialNum Entity EntPhysicalSerialNum73. entPhysicalModelName 1 Entity EntPhysicalModelName 72. entPhysicalMfgName Entity EntPhysicalMfgNameEntPhysicalModelName 74. entPhysicalAlias Entity EntPhysicalAlias 73. entPhysicalModelName 2 Entity EntPhysicalModelNameEntPhysicalAlias 76. entPhysicalIsFRU 1 Entity EntPhysicalAssetID75. entPhysicalAssetID Entity EntPhysicalAssetID EntPhysicalIsFRUEntLogicalIndex 76. entPhysicalIsFRU 2 Entity EntPhysicalIsFRUEntityLogical Group 77. entLogicalEntry entLogicalTable Sup ObjectEntLogicalContextName EntLogicalTAddressEntLogicalIPDomain EntLogicalContextEngineIDEntityNotifications Group MpeEntPhysicalExtAdminStatusEntPhysicalChildIndex Entity EntPhysicalIndex Semantic EntityGeneral Group82. Entity Sensor MIB Comments EntPhySensorValueUpdateRateMpeEntPhysicalExtOperStatus Entity Sensor MIB RFCIfMauType RO IfMauTable Supporte Object Type AccessIfMauIfIndex RO IfMauIndex ROIfMauTypeListBits RO IfMauDefaultType RWIfMauStatus RO IfMauAutoNegSupported ROPdnMgmtIpPortIndex NA 85. PDN-MGMT-IP-MIB Object Type SupportedPdnMgmtIpPortTable PdnMgmtBootVci RW PdnMgmtIpConfigMode RWPdnMgmtBootIfIndex RW PdnMgmtBootVpi RWPdnMgmtAtmVci NA PdnMgmtAtmInvArpTablePdnMgmtAtmIfIndex NA PdnMgmtAtmVpi NASnmpEngineTime SnmpEngineBootsSupporting MIBs SNMP-MPD-MIB RFC SnmpEngineIDSnmpUnavailableContexts and snmpUnknownContexts SNMPv1 traps Default valuesSNMPv2 traps Default values SnmpTargetParmsTableStatistics View-based Access Control VacmUser-based Security Model USM RFC Supporting MIBsVacmViewTreeFamilyTable VacmAccessTableVacmContextTable VacmSecurityToGroupTableApsConfigRowStatus Link Fault Management87. pdnLinkFaultMgmtApsSelection Comments ApsConfigModeLink Load Sharing LLS PDN-LINK-LOAD-SHARING-MIB.mib PdnLLSConfigGroupNamePdnLLSConfigSelection 89. pdnLinkFaultMgmtSwitchoverSelection CommentsPdnRedunEntityState PdnRedunCommandPdnRedunAlarmStatus PdnRedunNotificationEnableDevConfigTestTimeout Timing and Clocking Paradyne mpeConfig MIB mpeConfig.mib91. mpeDevConfigClockSrcEntry Object Type Access Supported DevDateAndTime RW DevConfigTestDuration93. pdntime.mib Object Type Access Supported Paradyne Time Mib pdntime.mibDevNTPOffsetFromUTC DevNTPEnable RWSysDevUserAccountTable SysDevUserAccountUserPassword RCSysDevUserAccountAccessPartition RC 94. pdndslam.mib Objects Supported TypeDevSecurityMgrValidation RW SecurityMgrSnmpAccess RWParadyne Security MIB pdnSecurity.mib 95. pdnSecurity.mib Object Type SupportedSecurityMgrRowStatus RW SecurityMgrTelnetAccessRWSecurityMgrFtpAccess RW SecurityMgrTrapAccess RWMpeDevFileXferFileType3 MpeDevControlTable MpeDevFileXferConfigTable96. mpeControl.mib 2 Object Type Supported MpeDevFirmwareControlTable PdnSyslogPort RW PdnSyslogStatus RWPdnSyslogIPAddr RW PdnSyslogLevelPdnEntitySyslogNumber NA PdnSyslogSeverityThreshold RWPdnSyslogRemoteDaemon RW PdnEntitySyslogTable NA98. Health and Status MIB Comments Traps PdnDevConfigTrapsEnable RW pdnTrapMgr.mibPdnSyslogRateLimiting RW Paradyne Health and Status MIB mpeHealthAndStatus.mib99. devLastTrapString 2 DevLastTrapString DSX Traps Adsl Specific Traps 99. devLastTrapString 3 DevLastTrapString99. devLastTrapString 4 DevLastTrapString IMA Traps Index IN-2 IN-3 IN-4
Related manuals
Manual 108 pages 7.87 Kb Manual 58 pages 27.69 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.