Paradyne 8620, 8820 manual entPhysicalEntry entPhysicalTable 1 2 Sup Object, EntPhysicalIndex

Page 63

Table 1-60. entPhysicalEntry {entPhysicalTable 1} (2 of 2)

 

 

 

 

 

Sup-

Object

OID

Syntax

Access

Status

ported

 

 

 

 

 

 

entPhysicalModelName

{entPhysicalEntry 13}

SnmpAdminString

read-only

current

Yes

 

 

 

 

 

 

entPhysicalAlias

{entPhysicalEntry 14}

SnmpAdminString

read-write

current

Yes

 

 

 

 

 

 

entPhysicalAssetID

{entPhysicalEntry 15}

SnmpAdminString

read-write

current

Yes

 

 

 

 

 

 

entPhysicalIsFRU

{entPhysicalEntry 16}

Truth Value

read-only

current

Yes

 

 

 

 

 

 

7.1.2.1.1entPhysicalIndex

The index for this entry.

Valid Object Value(s):

The value of this object is based on the ifIndex in the Interfaces Group. Refer to Evolution of the Interfaces Group of MIB-II (RFC 2863) on page 1-18for further details of these indexes. The following are the values for the entPhysicalIndex object based on that scheme.

Table 1-61. entPhysicalIndex

Entity

R

R

C

C

S

S

L

P

P

P

Comments

 

 

 

 

 

 

 

 

 

 

 

 

Chassis

0

0

0

1

0

0

0

0

0

0

Chassis

 

 

 

 

 

 

 

 

 

 

 

 

Container

0

0

0

1

Y

Y

0

0

0

0

Slot ’yy’, yy=[1..20]

 

 

 

 

 

 

 

 

 

 

 

 

Module

0

0

0

1

Y

Y

0

0

0

1

Module (SCPs and ATM portcards)

 

 

 

 

 

 

 

 

 

 

 

in slot ’yy’, yy=[1..20]

 

 

 

 

 

 

 

 

 

 

 

 

Splitter card

0

0

0

1

Y

Y

0

0

0

3

Splitter in slot ’yy’, yy=[1..20]

 

 

 

 

 

 

 

 

 

 

 

 

DSL Port

0

0

0

1

Y

Y

1

0

Z

Z

Dsl user ports, yy=[1..20], zz=[1..48]

 

 

 

 

 

 

 

 

 

 

 

 

t1e1 port

0

0

0

1

0

0

1

9

0

Z

T1/E1 ports, z=[1..8]

 

 

 

 

 

 

 

 

 

 

 

 

OC3 port

0

0

0

1

0

0

1

9

0

Z

OC3 ports, z=[1..2]

 

 

 

 

 

 

 

 

 

 

 

 

Console port

0

0

0

1

0

0

1

8

0

1

Console port

 

 

 

 

 

 

 

 

 

 

 

 

Ethernet Mgmt port

0

0

0

1

0

0

1

8

0

2

Ethernet port

 

 

 

 

 

 

 

 

 

 

 

 

Temp Sensor

0

0

0

1

0

0

0

1

0

Z

Temperature Sensor in chassis ‘z’,

 

 

 

 

 

 

 

 

 

 

 

z=[1..3]

 

 

 

 

 

 

 

 

 

 

 

 

Fan

0

0

0

1

0

0

0

1

1

Z

Fan ‘z’in Chassis, z=[1]

 

 

 

 

 

 

 

 

 

 

 

 

Management Plane PLD

0

0

0

1

Y

Y

0

1

2

1

Management Plane PLD in slot yy,

 

 

 

 

 

 

 

 

 

 

 

yy=[1..20]

 

 

 

 

 

 

 

 

 

 

 

 

Power Supply

0

0

0

1

0

0

0

1

3

Z

Power Supply ‘z’in Chassis, z=[1..2]

 

 

 

 

 

 

 

 

 

 

 

 

7.1.2.1.2entPhysicalDescr

A textual description of physical entity. This object should contain a string which identifies the manufacturer’s name for the physical entity, and should be set to a distint value for each version or model of the physical entity.

8000-A2-GB30-10

November 2003

57

Image 63
Contents Hotwire 8620 Copyright 2003 Paradyne Corporation All rights reserved Contents Contents November Section Description About This GuideDocument Number Document Title Product-Related DocumentsGranDSLAM 3.2 Network Management Interface Supported RFCs and MIBs 1Name Description 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 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 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 64. entPhysicalVendorType 2 Entity EntPhysicalVendorType EntPhysicalContainedIn65. entPhysicalContainedIn Entity EntPhysicalContainIn EntPhysicalClass 66. entPhysicalClass Entity EntPhysicalClassEntPhysicalParentRelPos EntPhysicalName 68. entPhysicalName Entity EntPhysicalNameEntPhysicalHardwareRev 70. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRev 69. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalSoftwareRev EntPhysicalFirmwareRevEntPhysicalMfgName 70. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum 71. entPhysicalSerialNum Entity EntPhysicalSerialNum72. entPhysicalMfgName Entity EntPhysicalMfgName EntPhysicalModelName73. entPhysicalModelName 1 Entity EntPhysicalModelName 73. entPhysicalModelName 2 Entity EntPhysicalModelName EntPhysicalAlias74. entPhysicalAlias Entity EntPhysicalAlias 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 RO85. PDN-MGMT-IP-MIB Object Type Supported PdnMgmtIpPortTablePdnMgmtIpPortIndex NA 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 PdnRedunNotificationEnableTiming and Clocking Paradyne mpeConfig MIB mpeConfig.mib 91. mpeDevConfigClockSrcEntry Object Type Access SupportedDevConfigTestTimeout 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 MpeDevFileXferConfigTable 96. mpeControl.mib 2 Object Type SupportedMpeDevControlTable 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.