Paradyne 8820, 8620 manual Interface indexes ifIndex

Page 26

1. Network Management Specification

4.1.1.1.1Interface indexes (ifIndex).

A unique value, greater than zero number will be assigned to each interface. The following ifIndex scheme was developed by a committee to solve a general stack hierarchy and it is shown in Figure 1-2:

R R C C S S L P

P P

Figure 1-2. ifIndex Scheme

Where:

-RR: Reserved for future use.

-CC: Chassis number from 1..99. For the GranDSLAM 3.0, this value will always be 1, identifying the 8820 or the 8620 chassis.

-SS: Slot number from 1..99. For the GranDSLAM 3.0, this value will range from 1 through 20.

-Slot 00 will have a special meaning on the GranDSLAM 3.0. Slot 00 will be used for the interfaces contained in the SCP cards.

-L: Layer number associated in the interface stack in Table 1-7, Interface Stack.

-PPP: Port/Interface number from 1..999.

The value 0 will be used as a special case in any of the above fields to denote N/A.

The following table shows the assigned ifIndexes to be used for the GranDSLAM 3.0 product. In the table, the DSL ports are enumerated from 1-48, with the Layer field set to 1. The product will support 2 DSL Channels (Interleave, Fast) per DSL ports, that make a total of 96 channels numbered from 1-96 with the Layer field set to 2. Similarly, their corresponding DSL ATM links will be numbered from 1-96, but with the Layer field set to 3. In the case of the WAN ports, the number starts at 901 for the first T1/E1or OC3 link and increments up to the max number of WAN ports supported. When some of these DS1 are aggregated to form an IMA Group, the first IMA group starts at 910, but with the Layer field set to 4. Similarly, the ATM links associated with the DS1 port will carry the same starting number as the physical interface but with the Layer Field set to 3, which corresponds to the ATM layer in Table 1-7, Interface Stack. Finally, other ports dedicated to management of the device such as Ethernet ports and async ports will have ifIndexes starting at 801 for the first port, and so on.

The suffix ‘cc’ indicates the chassis number where the interface is instantiated. The chassis number for the 8820 or the 8620 will be 1 for the GranDSLAM 3.0.

The suffix ‘ss’ indicates the slot number where the interface is instantiated. For the GranDSLAM 3.0, this number corresponds to the physical position where the associated module is located in the 8820 or 8620 chassis.

For the GranDSLAM 3.0, the value ss=’00’ have a special meaning. A logical slot number of 00 will be used for those interfaces contained and accessible in the SCP cards. Therefore, these interfaces will be independent and remain contant regardless of which SCP is in charge. However, the internal software may require that the corresponding slot based ifIndexes in the SCP be also supported.

20

June 2003

8000-A2-GB30-00

Image 26
Contents Hotwire 8620 Copyright 2003 Paradyne Corporation All rights reserved Contents Contents June About This Guide Section DescriptionProduct-Related Documents Document Number Document TitleName Description GranDSLAM 3.0 Network Management InterfaceSupported RFCs and MIBs 1 Supported RFCs and MIBs 2 Supported RFCs and MIBs 3 IMA MIBSupported RFCs and MIBs 4 PDN-ENTITY-REDUNDANCY-MIBSupported RFCs and MIBs 5 PDN-DS1EXT-MIBOther Supported RFCs Used as Guidelines for Implementation Name/DescriptionDSX Traps Standards Compliance for Snmp TrapsSummary of Traps 1 Description VarBinds Standard 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 Adsl Specific Traps Summary of Traps 5 Description VarBindsSummary of Traps 6 Description VarBinds IMA Traps Summary of Traps 7 Description VarBindsStandards Compliance to Snmp MIBs GranDSLAM Interfaces SysDescr Object system Management Information Base MIB-II RFCSystem Group, MIB-II RFC SysObjectID Object system SysServices Object systemSysServices Layer L Functionality Value2L-1 Sum SysUpTime Object systemIfIndex Object ifEntry Evolution of the Interfaces Group of MIB-II RFCIfNumber Object interfaces IfIndex schemeGranDSLAM 3.0 Interface List Layer Supported Maximum IfName Interface indexes ifIndex IfIndex Assignments IfDescr Object ifEntryIfMtu IfType Object ifEntryIfMtu Object ifEntry Interface IfMtuIfSpeed IfAdminStatus Object ifEntryIfSpeed Object ifEntry Interface IfSpeedIfOperStatus Object ifEntry IfAdminStatusInterface IfAdminStatus IfOperStatusIfLastChange Object ifEntry IfInUcastPkts Object ifEntry 14. ifInUncastPkts Interface IfInUncastPkts Object ifEntry 15. ifInUncastPkts InterfaceIfInErrors Object ifEntry 17. ifInErrors Interface IfInDiscards Object ifEntry 16. ifInDiscards InterfaceETH1 IMA IfOutUcastPkts Object ifEntry 20. ifOutUcastPkts Interface IfOutNUcasts Object ifEntry InterfaceIfOutQLen ifEntry IfOutErrors Object ifEntry InterfaceIfOutDiscards Object ifEntry 22. ifOutDiscards Interface Extension to the Intf. Table ifXTable RFC IfLinkUpDownTrapEnable Object ifXEntryIfSpecific ifEntry 24. Extension to the Interface TableInterface Stack Group RFC IfStackHigherLayer Object ifStackEntryTransmission Group, MIB-II RFC 1213 Supported IfStackLowerLayer Object ifStackEntryIfStackStatus Object ifStackEntry Snmp Group, MIB-II RFCNetwork Management Specification Physical Layer Adsl MIB RFC 28. Adsl MIB Comments DS1 MIB RFC 31. DS1 MIB Comments Paradyne ReachDSL MIB pdnreachDSL.mib30. ReachDSL MIB Comments Paradyne DS1-EXT MIB PDN-DS1EXT-MIBPdnDs1ExtConfLineLengthType RW PdnDs1ExtConfConnector RW32. DS1-EXT MIB Comments PdnDs1ExtConfLineLength RWSonetSESthresholdSet SONET-MIB RFC 33. SONET-MIB CommentsSonetMediumEntry 34. sonetMediumEntry Comments SonetPathCurrentWidthDevSonetXmitClkSrc DevSonetStatusChangeTrapEnableBy default, this object is enabled DevSonetStatusLastChangeSpectrum Management pdnspectrummgmt.mib NewSpectrumMgmtGeneralConfigEntry36. Shdsl MIB Comments 37. Spectrum Management Comments38. ATM MIB Comments ATM Interface Configuration Parameter Group RFCLink Layer ATM AtoM MIB RFC AtmInterfaceMaxVpcs Object atmInterfaceConfEntryAtmInterfaceMaxVccs AtmInterfaceMaxVccs Object atmInterfaceConfEntry40. atmInterfaceMaxVccs AtmInterfaceConfVpcs Object atmInterfaceConfEntryAtmInterfaceMaxActiveVciBits Object atmInterfaceConfEntry AtmInterfaceIlmiVpi AccessAtmInterfaceIlmiVci Access AtmInterfaceMaxActiveVciBitsAtmInterfaceMyNeighborIfName Object atmInterfaceConfEntry AtmInterfaceMyNeighborIpAddress AccessAtmInterfaceMyNeighborIfName Access AtmInterfaceCurrentMaxVpiBits Object atmInterfaceConfEntryAtmInterfaceSubscrAddress Object atmInterfaceConfEntry AtmInterfaceTCAlarmState Object atmInterfaceTCEntryAtmInterfaceCurrentMaxVciBits Object atmInterfaceConfEntry AtmInterfaceSubscrAddressATM Traffic Descriptor Group RFC AtmServiceCategory Object atmTrafficDescrParamEntryVirtual Channel Link VCL Configuration Group RFC 54. Traffic Descriptor TypesAtmVccAalType Object atmVclEntry AtmVclOperStatus Object atmVclEntryAtmVclLastChange Object atmVclEntry AtmVccAal5CpcsTransmitSduSize Object atmVclEntryVirtual Channel Cross Connect Group RFC AtmVcCrossConnectRowStatus Object atmVcCrossConnectEntry55. Object Supported in ATM Forum MIB Type AtmfM4TcAlarmSeverityIndexObject atmfM4TcAdapterEntryAtmfM4MIB- Snmp M4 Network Element View MIB atmfM4MIB TC Adapter Layer Table atmfM4TcAdapterEntryAtmfM4IfType Object atmfM4ATMLayerEntry AtmfM4VcXConnRecover Object atmfM4VcXConnEntry1ATM Cell Layer Table atmfM4ATMLayerEntry AtmfM4IfSubscriberAddress Object atmfM4ATMLayerEntry56. Paradyne Extensions to ATM MIBs 1 Sup Object Type Ported ATM Loopback 57. ATM Loopback CommentsGoto tryagain IMA MIB AF-PHY-0086.001 58. IMA MIB Object EntityPhysical Group Syntax Access Status PortedEntity MIB version 2 Objects supported 59. entPhysicalEntry entPhysicalTable 1 1 Sup Object60. entPhysicalIndex Entity Comments 59. entPhysicalEntry entPhysicalTable 1 2 Sup ObjectEntPhysicalIndex EntPhysicalDescr61. entPhysicalDescr Entity Description EntPhysicalVendorType63. entPhysicalVendorType 1 Entity EntPhysicalVendorType 64. entPhysicalContainedIn Entity EntPhysicalContainIn 63. entPhysicalVendorType 2 Entity EntPhysicalVendorTypeEntPhysicalContainedIn EntPhysicalParentRelPos EntPhysicalClass65. entPhysicalClass Entity EntPhysicalClass EntPhysicalHardwareRev EntPhysicalName67. entPhysicalName Entity EntPhysicalName EntPhysicalFirmwareRev 68. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalSoftwareRev 69. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRev70. entPhysicalSerialNum Entity EntPhysicalSerialNum 69. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum EntPhysicalMfgName72. entPhysicalModelName 1 Entity EntPhysicalModelName 71. entPhysicalMfgName Entity EntPhysicalMfgNameEntPhysicalModelName 73. entPhysicalAlias Entity EntPhysicalAlias 72. entPhysicalModelName 2 Entity EntPhysicalModelNameEntPhysicalAlias EntPhysicalIsFRU EntPhysicalAssetID74. entPhysicalAssetID Entity EntPhysicalAssetID 75. entPhysicalIsFRU 1 Entity76. entLogicalEntry entLogicalTable Sup Object 75. entPhysicalIsFRU 2 Entity EntPhysicalIsFRUEntityLogical Group EntLogicalIndexEntLogicalContextEngineID EntLogicalTAddressEntLogicalIPDomain EntLogicalContextNameEntityGeneral Group MpeEntPhysicalExtAdminStatusEntPhysicalChildIndex Entity EntPhysicalIndex Semantic EntityNotifications GroupEntity Sensor MIB RFC EntPhySensorValueUpdateRateMpeEntPhysicalExtOperStatus 81. Entity Sensor MIB CommentsIfMauIndex RO IfMauTable Supporte Object Type AccessIfMauIfIndex RO IfMauType ROIfMauAutoNegSupported RO IfMauDefaultType RWIfMauStatus RO IfMauTypeListBits ROPdnMgmtIpPortIndex NA 84. PDN-MGMT-IP-MIB Object Type SupportedPdnMgmtIpPortTable PdnMgmtBootVpi RW PdnMgmtIpConfigMode RWPdnMgmtBootIfIndex RW PdnMgmtBootVci RWPdnMgmtAtmVpi NA PdnMgmtAtmInvArpTablePdnMgmtAtmIfIndex NA PdnMgmtAtmVci NASnmpEngineID SnmpEngineBootsSupporting MIBs SNMP-MPD-MIB RFC SnmpEngineTimeSnmpTargetParmsTable SNMPv1 traps Default valuesSNMPv2 traps Default values SnmpUnavailableContexts and snmpUnknownContextsSupporting MIBs View-based Access Control VacmUser-based Security Model USM RFC StatisticsVacmSecurityToGroupTable VacmAccessTableVacmContextTable VacmViewTreeFamilyTableApsConfigMode Link Fault Management86. pdnLinkFaultMgmtApsSelection Comments ApsConfigRowStatus88. pdnLinkFaultMgmtSwitchoverSelection Comments PdnLLSConfigGroupNamePdnLLSConfigSelection Link Load Sharing LLS PDN-LINK-LOAD-SHARING-MIB.mibPdnRedunNotificationEnable PdnRedunCommandPdnRedunAlarmStatus PdnRedunEntityStateDevConfigTestTimeout Timing and Clocking Paradyne mpeConfig MIB mpeConfig.mib90. mpeDevConfigClockSrcEntry Object Type Access Supported Paradyne Time Mib pdntime.mib DevConfigTestDuration92. pdntime.mib Object Type Access Supported DevDateAndTime RWDevNTPEnable RW DevNTPOffsetFromUTC93. pdndslam.mib Objects Supported Type SysDevUserAccountUserPassword RCSysDevUserAccountAccessPartition RC SysDevUserAccountTable94. pdnSecurity.mib Object Type Supported SecurityMgrSnmpAccess RWParadyne Security MIB pdnSecurity.mib DevSecurityMgrValidation RWSecurityMgrTrapAccess RW SecurityMgrTelnetAccessRWSecurityMgrFtpAccess RW SecurityMgrRowStatus RWMpeDevFileXferFileType3 MpeDevControlTable MpeDevFileXferConfigTable95. mpeControl.mib 2 Object Type Supported MpeDevFirmwareControlTable PdnSyslogLevel PdnSyslogStatus RWPdnSyslogIPAddr RW PdnSyslogPort RWPdnEntitySyslogTable NA PdnSyslogSeverityThreshold RWPdnSyslogRemoteDaemon RW PdnEntitySyslogNumber NAParadyne Health and Status MIB mpeHealthAndStatus.mib Traps PdnDevConfigTrapsEnable RW pdnTrapMgr.mibPdnSyslogRateLimiting RW 97. Health and Status MIB Comments98. devLastTrapString 2 DevLastTrapString DSX Traps 98. devLastTrapString 3 DevLastTrapString Adsl Specific Traps98. 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.