Paradyne 8620 MpeEntPhysicalExtOperStatus, Entity Sensor MIB RFC, Entity Sensor MIB Comments

Page 77

7.2.2mpeEntPhysicalExtOperStatus

This is a read-only object that allows managers to determine the operational status of the entities in the managed device. The possibles values are ’up’, ’down’ and ’testing’.

7.3Entity Sensor MIB (RFC 3433):

This MIB has only one group (entitySensorValueGroup) which consists of a single (read-only) table that will be supported as indicated in the following table. There will be as many entries as sensors. For the GranDSLAM R3.2 product, there will be three temperature sensors

Table 1-82. Entity Sensor MIB

Table

Comments

 

 

entPhySensorEntry

Only the objects listed below will be supported

 

 

7.3.1entPhySensorType.

The value for this object corresponds to the measurement data type. The value of this object will be celsius (8).

7.3.2entPhySensorValue.

The value corresponds the most recent measurement obtained by the agent for this sensor.

7.3.3entPhySensorOperStatus.

The operational status of the sensor. The following status will be reported: ok (1), unavailable (2), nonoperational (3).

7.3.4entPhySensorValueTimeStamp.

The value of this object corresponds to the sysUpTime at the time the status and/or value fo this sensor was last obtained by the agent.

7.3.5entPhySensorValueUpdateRate.

The value of this object is an indication of the frequency that the agent updates the associated entPhySensorValue object. The value to be returned will be zero. This value has a special meaning in the mib.

7.4Definitions for the IEEE 802.3 Medium Attachment Units (MAUs) (RFC 2668):

RFC 2668 is used for accessing information about of ethernet interface. The following objects are supported.

7.4.1ifMauTable:

Table of descriptive and status information about MAU(s) attached to an interface. The following objects in this table are supported.

8000-A2-GB30-10

November 2003

71

Image 77
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 ImplementationSummary of Traps 1 Description VarBinds Standard Traps Standards Compliance for Snmp TrapsDSX Traps ATM-M4 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 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 R3.2 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 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 InterfaceIfSpecific 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 RFCNovember 8000-A2-GB30-10 Physical Layer Adsl MIB RFC 2662 -28. Adsl MIB Comments 31. ReachDSL MIB Comments Paradyne ReachDSL MIB pdnreachDSL.mibParadyne DS1-EXT MIB PDN-DS1EXT-MIB DS1 MIB RFC 2495 -32. DS1 MIB Comments33. DS1-EXT MIB Comments PdnDs1ExtConfLineLengthType RWPdnDs1ExtConfLineBuildOut RW PdnDs1ExtConfConnector RWSonetMediumEntry -35. sonetMediumEntry Comments SONET-MIB RFC 2558 -34. SONET-MIB CommentsSonetSESthresholdSet SonetPathCurrentWidthBy default, this object is enabled DevSonetStatusChangeTrapEnableDevSonetXmitClkSrc DevSonetStatusLastChange37. Shdsl MIB Comments NewSpectrumMgmtGeneralConfigEntrySpectrum Management pdnspectrummgmt.mib 38. Spectrum Management CommentsLink Layer ATM AtoM MIB RFC ATM Interface Configuration Parameter Group RFC39. ATM MIB Comments AtmInterfaceMaxVpcs Object atmInterfaceConfEntryAtmInterfaceMaxVccs AtmInterfaceMaxVccs Object atmInterfaceConfEntryInterface AtmInterfaceMaxVccs 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 55. 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 atmfM4TcAdapterEntry56. Object Supported in ATM Forum MIB Type TC Adapter Layer Table atmfM4TcAdapterEntryATM Cell Layer Table atmfM4ATMLayerEntry AtmfM4VcXConnRecover Object atmfM4VcXConnEntry1AtmfM4IfType Object atmfM4ATMLayerEntry AtmfM4IfSubscriberAddress 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 Entity MIB version 2 Objects supported Syntax Access Status PortedEntityPhysical Group 60. entPhysicalEntry entPhysicalTable 1 1 Sup ObjectEntPhysicalIndex 60. entPhysicalEntry entPhysicalTable 1 2 Sup Object61. entPhysicalIndex Entity Comments EntPhysicalDescrEntPhysicalVendorType 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 EntPhysicalSoftwareRev 69. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalFirmwareRev 70. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum 70. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRev71. entPhysicalSerialNum Entity EntPhysicalSerialNum EntPhysicalMfgName73. entPhysicalModelName 1 Entity EntPhysicalModelName 72. entPhysicalMfgName Entity EntPhysicalMfgNameEntPhysicalModelName 74. entPhysicalAlias Entity EntPhysicalAlias 73. entPhysicalModelName 2 Entity EntPhysicalModelNameEntPhysicalAlias 75. entPhysicalAssetID Entity EntPhysicalAssetID EntPhysicalAssetIDEntPhysicalIsFRU 76. entPhysicalIsFRU 1 EntityEntityLogical Group 76. entPhysicalIsFRU 2 Entity EntPhysicalIsFRU77. entLogicalEntry entLogicalTable Sup Object EntLogicalIndexEntLogicalIPDomain EntLogicalTAddressEntLogicalContextEngineID EntLogicalContextNameEntPhysicalChildIndex Entity EntPhysicalIndex Semantic MpeEntPhysicalExtAdminStatusEntityGeneral Group EntityNotifications GroupMpeEntPhysicalExtOperStatus EntPhySensorValueUpdateRateEntity Sensor MIB RFC 82. Entity Sensor MIB CommentsIfMauIfIndex RO IfMauTable Supporte Object Type AccessIfMauIndex RO IfMauType ROIfMauStatus RO IfMauDefaultType RWIfMauAutoNegSupported RO IfMauTypeListBits ROPdnMgmtIpPortIndex NA 85. PDN-MGMT-IP-MIB Object Type SupportedPdnMgmtIpPortTable 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 VacmViewTreeFamilyTable87. pdnLinkFaultMgmtApsSelection Comments Link Fault ManagementApsConfigMode ApsConfigRowStatusPdnLLSConfigSelection PdnLLSConfigGroupName89. pdnLinkFaultMgmtSwitchoverSelection Comments Link Load Sharing LLS PDN-LINK-LOAD-SHARING-MIB.mibPdnRedunAlarmStatus PdnRedunCommandPdnRedunNotificationEnable PdnRedunEntityStateDevConfigTestTimeout Timing and Clocking Paradyne mpeConfig MIB mpeConfig.mib91. mpeDevConfigClockSrcEntry Object Type Access Supported 93. pdntime.mib Object Type Access Supported DevConfigTestDurationParadyne Time Mib pdntime.mib DevDateAndTime RWDevNTPOffsetFromUTC DevNTPEnable RWSysDevUserAccountAccessPartition RC SysDevUserAccountUserPassword RC94. pdndslam.mib Objects Supported Type SysDevUserAccountTableParadyne Security MIB pdnSecurity.mib SecurityMgrSnmpAccess RW95. pdnSecurity.mib Object Type Supported DevSecurityMgrValidation RWSecurityMgrFtpAccess RW SecurityMgrTelnetAccessRWSecurityMgrTrapAccess RW SecurityMgrRowStatus RWMpeDevFileXferFileType3 MpeDevControlTable MpeDevFileXferConfigTable96. mpeControl.mib 2 Object Type Supported 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 98. Health and Status MIB Comments99. 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.