Paradyne 8620, 8820 manual Goto tryagain

Page 59

1. Network Management Specification

get (atmfM4TestId, atmfM4TestStatus)

}

/*

*Is not being used right now -- let’s compete

*to see who gets it.

*/

lock_value = atmfM4TestId

if ( set(atmfM4TestId = lock_value, atmfM4TestStatus = inUse, atmfM4TestOwner = ’my-IP-address’) == FAILURE)

/*

*Another manager got the atmfM4TestEntry -- go

*try again

*/

goto try_again; /*

* I have the lock

*/

set up any test parameters.

/*

*This starts the test */

set(atmfM4TestType = test_to_run);

set(atmfM4TestCode = pdnATMfM4VcLoopbackTestTable);

when test is stopped by this NMS station, agent sets atmfM4TestResult agent also sets atmfM4TestStatus = ’notInUse’

retrieve any additional test results, and atmfM4TestId 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. If the loopback location code is absent from the pdnATMfM4VcTestOAMLoopbackSegMultiCell, the loopback is performed at the end of the segment or connection. The Ubiquity ATM unit supports next-hop segment ATM loopback, which means that the Ubiquity ATM unit ignores the loopback location code if the NMS application provides one.

Once a test is started, the SNMP agent will set the value of atmfM4VcTestCode to 1.3.6.1.4.1.1795.2.24.2.6.11.6.1.4 (pdnATMfM4VcLoopbackTestTable) indicating the test statistics are in pdnATMfM4VcLoopbackTestTable. The NMS can retrieve the test results by querying the objects in this table.

The NMS station, the owner of the ongoing OAM F5 loopback test, must explicitly stop this loopback test by setting atmfM4VcTestType to NoTest (0.0) when the NMS no longer needs this test The test result might be available depending upon whether there is enough room in the system.

At any time, an NMS station can set atmfM4VcTestType to “0.0” to abort the ongoing test owned by this NMS.

8000-A2-GB30-00

June 2003

53

Image 59
Contents Hotwire 8620 Copyright 2003 Paradyne Corporation All rights reserved Contents Contents June Section Description About This GuideDocument Number Document Title Product-Related DocumentsName Description GranDSLAM 3.0 Network Management InterfaceSupported RFCs and MIBs 1 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 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 3.0 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 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 InterfaceIfOutQLen ifEntry IfOutErrors Object ifEntry InterfaceIfOutDiscards Object ifEntry 22. ifOutDiscards Interface 24. 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 SupportedNetwork Management Specification Physical Layer Adsl MIB RFC 28. Adsl MIB Comments Paradyne DS1-EXT MIB PDN-DS1EXT-MIB Paradyne ReachDSL MIB pdnreachDSL.mib30. ReachDSL MIB Comments DS1 MIB RFC 31. DS1 MIB CommentsPdnDs1ExtConfLineLength RW PdnDs1ExtConfConnector RW32. DS1-EXT MIB Comments PdnDs1ExtConfLineLengthType RWSonetPathCurrentWidth SONET-MIB RFC 33. SONET-MIB CommentsSonetMediumEntry 34. sonetMediumEntry Comments SonetSESthresholdSetDevSonetStatusLastChange DevSonetStatusChangeTrapEnableBy default, this object is enabled DevSonetXmitClkSrc37. Spectrum Management Comments NewSpectrumMgmtGeneralConfigEntry36. Shdsl MIB Comments Spectrum Management pdnspectrummgmt.mibAtmInterfaceMaxVpcs Object atmInterfaceConfEntry ATM Interface Configuration Parameter Group RFCLink Layer ATM AtoM MIB RFC 38. ATM MIB CommentsAtmInterfaceConfVpcs Object atmInterfaceConfEntry AtmInterfaceMaxVccs Object atmInterfaceConfEntry40. atmInterfaceMaxVccs AtmInterfaceMaxVccsAtmInterfaceMaxActiveVciBits AtmInterfaceIlmiVpi AccessAtmInterfaceIlmiVci Access AtmInterfaceMaxActiveVciBits Object atmInterfaceConfEntryAtmInterfaceCurrentMaxVpiBits Object atmInterfaceConfEntry AtmInterfaceMyNeighborIpAddress AccessAtmInterfaceMyNeighborIfName Access AtmInterfaceMyNeighborIfName Object atmInterfaceConfEntryAtmInterfaceSubscrAddress AtmInterfaceTCAlarmState Object atmInterfaceTCEntryAtmInterfaceCurrentMaxVciBits Object atmInterfaceConfEntry AtmInterfaceSubscrAddress Object atmInterfaceConfEntry54. 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 55. Object Supported in ATM Forum MIB TypeAtmfM4IfSubscriberAddress Object atmfM4ATMLayerEntry AtmfM4VcXConnRecover Object atmfM4VcXConnEntry1ATM Cell Layer Table atmfM4ATMLayerEntry AtmfM4IfType 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 59. entPhysicalEntry entPhysicalTable 1 1 Sup Object Syntax Access Status PortedEntity MIB version 2 Objects supported EntityPhysical GroupEntPhysicalDescr 59. entPhysicalEntry entPhysicalTable 1 2 Sup ObjectEntPhysicalIndex 60. entPhysicalIndex Entity CommentsEntPhysicalVendorType 61. entPhysicalDescr Entity Description63. entPhysicalVendorType 1 Entity EntPhysicalVendorType 64. entPhysicalContainedIn Entity EntPhysicalContainIn 63. entPhysicalVendorType 2 Entity EntPhysicalVendorTypeEntPhysicalContainedIn EntPhysicalParentRelPos EntPhysicalClass65. entPhysicalClass Entity EntPhysicalClass EntPhysicalHardwareRev EntPhysicalName67. entPhysicalName Entity EntPhysicalName 69. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRev 68. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalSoftwareRev EntPhysicalFirmwareRevEntPhysicalMfgName 69. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum 70. entPhysicalSerialNum Entity EntPhysicalSerialNum72. entPhysicalModelName 1 Entity EntPhysicalModelName 71. entPhysicalMfgName Entity EntPhysicalMfgNameEntPhysicalModelName 73. entPhysicalAlias Entity EntPhysicalAlias 72. entPhysicalModelName 2 Entity EntPhysicalModelNameEntPhysicalAlias 75. entPhysicalIsFRU 1 Entity EntPhysicalAssetID74. entPhysicalAssetID Entity EntPhysicalAssetID EntPhysicalIsFRUEntLogicalIndex 75. entPhysicalIsFRU 2 Entity EntPhysicalIsFRUEntityLogical Group 76. entLogicalEntry entLogicalTable Sup ObjectEntLogicalContextName EntLogicalTAddressEntLogicalIPDomain EntLogicalContextEngineIDEntityNotifications Group MpeEntPhysicalExtAdminStatusEntPhysicalChildIndex Entity EntPhysicalIndex Semantic EntityGeneral Group81. 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 84. 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 Management86. pdnLinkFaultMgmtApsSelection Comments ApsConfigModeLink Load Sharing LLS PDN-LINK-LOAD-SHARING-MIB.mib PdnLLSConfigGroupNamePdnLLSConfigSelection 88. pdnLinkFaultMgmtSwitchoverSelection CommentsPdnRedunEntityState PdnRedunCommandPdnRedunAlarmStatus PdnRedunNotificationEnableDevConfigTestTimeout Timing and Clocking Paradyne mpeConfig MIB mpeConfig.mib90. mpeDevConfigClockSrcEntry Object Type Access Supported DevDateAndTime RW DevConfigTestDuration92. pdntime.mib Object Type Access Supported Paradyne Time Mib pdntime.mibDevNTPOffsetFromUTC DevNTPEnable RWSysDevUserAccountTable SysDevUserAccountUserPassword RCSysDevUserAccountAccessPartition RC 93. pdndslam.mib Objects Supported TypeDevSecurityMgrValidation RW SecurityMgrSnmpAccess RWParadyne Security MIB pdnSecurity.mib 94. pdnSecurity.mib Object Type SupportedSecurityMgrRowStatus RW SecurityMgrTelnetAccessRWSecurityMgrFtpAccess RW SecurityMgrTrapAccess RWMpeDevFileXferFileType3 MpeDevControlTable MpeDevFileXferConfigTable95. mpeControl.mib 2 Object Type Supported MpeDevFirmwareControlTable PdnSyslogPort RW PdnSyslogStatus RWPdnSyslogIPAddr RW PdnSyslogLevelPdnEntitySyslogNumber NA PdnSyslogSeverityThreshold RWPdnSyslogRemoteDaemon RW PdnEntitySyslogTable NA97. Health and Status MIB Comments Traps PdnDevConfigTrapsEnable RW pdnTrapMgr.mibPdnSyslogRateLimiting RW Paradyne Health and Status MIB mpeHealthAndStatus.mib98. 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.