Paradyne 8820 VacmContextTable, VacmSecurityToGroupTable, VacmAccessTable, SNMPv3 Coexistence

Page 86

7.7.6.1.1vacmContextTable.

It defines the locally available contexts. This table is read-only and can not be configured by SNMP.

7.7.6.1.2vacmSecurityToGroupTable.

It maps a securityModel and securityName to a groupName. Supported read-only with default values.

7.7.6.1.3vacmAccessTable.

It maps a groupName, context and securityInformation into a MIB view. Supported read-only with default values.

7.7.6.1.4vacmViewTreeFamilyTable.

It defines whether an OBJECT IDENTIFIER can be accessed for a given MIB view or not. Supported read-only with default values.

7.7.7SNMPv3 Coexistence.

RFC 2576 discusses the “Coexistence between Version 1, Version 2 and Version 3 of the Internet-standard Network Management Framework”. This table will be used to configure community strings for v1/v2c clients. This table has no significance and thus, it is not used for SNMPv3 clients.

By default, the SCP agent will configure a default community string ’public’ with read/write access level; which uses the v1 modeling processing and dispatching [snmpV1 (1)] as well as the community-based security model.

7.7.7.1Supporting MIBs

7.7.7.1.1SNMP-COMMUNITY-MIB.

7.7.7.1.1.1snmpCommunityTable.

It provides a mapping of a community string to a securityName (for example, snmpV1 (1) or snmpV2 (2)), contextEngineID, and contextName.

If configured, this table also allows the source address to be validated which provides some level of security for SNMPv1 and SNMPv2c environments. This source address validation will not be supported.

Because the GranDSLAM R3.2 will be configured as an SNMPv1, and entry in this table will exist by default with a communityName of “public” and the source address validation will be turned off (snmpCommunityTransportTag = empty-string).

A TL1 command or Web interface option will be required to enable/disable different versions of SNMP or ’none’ (the options are: ’None’, ’v1/v2c’ ’v3 with encryption’. An enterprise MIB might be required to handle this option. These commands will internally translate into additionsdeletions to the respective tables (snmpCommunityTable for v1/v2c users, usmUserTable for v3 users).

1)When ’v1/v2c’ is selected, users in usmUserTable will be set to inactive.

2)When ’v3-encryption’ is selected, users in entCommunityTable will be set to inactive.

3)When ’none’ is selected, users in both usmUserTable and entCommunityTable will be set to inactive.

80

November 2003

8000-A2-GB30-10

Page 85 Page 87
Image 86
Page 85 Page 87
Contents Hotwire 8620 Copyright 2003 Paradyne Corporation All rights reserved Contents Contents November About This Guide Section DescriptionProduct-Related Documents Document Number Document TitleName Description GranDSLAM 3.2 Network Management InterfaceSupported RFCs and MIBs 1 Supported RFCs and MIBs 2 IMA MIBSupported RFCs and MIBs 3 Supported 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 R3.2 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 IMA Atmup AAL5 ETH1 Sonet IfInErrors Object ifEntry 14 -17. ifInErrors Interface IfInDiscards Object ifEntry 13 -16. ifInDiscards InterfaceETH1 IMA IfOutNUcasts Object ifEntry 18 -21. ifOutNUcasts Interface IfOutErrors Object ifEntry Interface IfOutQLen ifEntryExtension 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 RFCNovember 8000-A2-GB30-10 Physical Layer Adsl MIB RFC 2662 -28. Adsl MIB Comments Paradyne ReachDSL MIB pdnreachDSL.mib 31. ReachDSL MIB Comments33. DS1-EXT MIB Comments DS1 MIB RFC 2495 -32. DS1 MIB CommentsParadyne DS1-EXT MIB PDN-DS1EXT-MIB PdnDs1ExtConfLineLengthType RWPdnDs1ExtConfConnector RW PdnDs1ExtConfLineBuildOut RWSonetSESthresholdSet SONET-MIB RFC 2558 -34. SONET-MIB CommentsSonetMediumEntry -35. sonetMediumEntry Comments SonetPathCurrentWidthDevSonetXmitClkSrc DevSonetStatusChangeTrapEnableBy default, this object is enabled DevSonetStatusLastChangeSpectrum Management pdnspectrummgmt.mib NewSpectrumMgmtGeneralConfigEntry37. Shdsl MIB Comments 38. Spectrum Management Comments39. ATM MIB Comments ATM Interface Configuration Parameter Group RFCLink Layer ATM AtoM MIB RFC AtmInterfaceMaxVpcs Object atmInterfaceConfEntryInterface AtmInterfaceMaxVccs AtmInterfaceMaxVccs Object atmInterfaceConfEntryAtmInterfaceMaxVccs 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 55. Traffic Descriptor TypesAtmVccAalType Object atmVclEntry AtmVclOperStatus Object atmVclEntryAtmVclLastChange Object atmVclEntry AtmVccAal5CpcsTransmitSduSize Object atmVclEntryVirtual Channel Cross Connect Group RFC AtmVcCrossConnectRowStatus Object atmVcCrossConnectEntry56. 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 atmfM4ATMLayerEntry57. Paradyne Extensions to ATM MIBs 1 Sup Object Type Ported ATM Loopback 58. ATM Loopback CommentsGoto tryagain IMA MIB AF-PHY-0086.001 -59. IMA MIB Object EntityPhysical Group Syntax Access Status PortedEntity MIB version 2 Objects supported 60. entPhysicalEntry entPhysicalTable 1 1 Sup Object61. entPhysicalIndex Entity Comments 60. entPhysicalEntry entPhysicalTable 1 2 Sup ObjectEntPhysicalIndex EntPhysicalDescr62. entPhysicalDescr Entity Description EntPhysicalVendorType64. entPhysicalVendorType 1 Entity EntPhysicalVendorType 65. entPhysicalContainedIn Entity EntPhysicalContainIn 64. entPhysicalVendorType 2 Entity EntPhysicalVendorTypeEntPhysicalContainedIn EntPhysicalParentRelPos EntPhysicalClass66. entPhysicalClass Entity EntPhysicalClass EntPhysicalHardwareRev EntPhysicalName68. entPhysicalName Entity EntPhysicalName EntPhysicalFirmwareRev 69. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalSoftwareRev 70. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRev71. entPhysicalSerialNum Entity EntPhysicalSerialNum 70. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum EntPhysicalMfgName73. entPhysicalModelName 1 Entity EntPhysicalModelName 72. entPhysicalMfgName Entity EntPhysicalMfgNameEntPhysicalModelName 74. entPhysicalAlias Entity EntPhysicalAlias 73. entPhysicalModelName 2 Entity EntPhysicalModelNameEntPhysicalAlias EntPhysicalIsFRU EntPhysicalAssetID75. entPhysicalAssetID Entity EntPhysicalAssetID 76. entPhysicalIsFRU 1 Entity77. entLogicalEntry entLogicalTable Sup Object 76. entPhysicalIsFRU 2 Entity EntPhysicalIsFRUEntityLogical Group EntLogicalIndexEntLogicalContextEngineID EntLogicalTAddressEntLogicalIPDomain EntLogicalContextNameEntityGeneral Group MpeEntPhysicalExtAdminStatusEntPhysicalChildIndex Entity EntPhysicalIndex Semantic EntityNotifications GroupEntity Sensor MIB RFC EntPhySensorValueUpdateRateMpeEntPhysicalExtOperStatus 82. Entity Sensor MIB CommentsIfMauIndex RO IfMauTable Supporte Object Type AccessIfMauIfIndex RO IfMauType ROIfMauAutoNegSupported RO IfMauDefaultType RWIfMauStatus RO IfMauTypeListBits ROPdnMgmtIpPortIndex NA 85. 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 Management87. pdnLinkFaultMgmtApsSelection Comments ApsConfigRowStatus89. pdnLinkFaultMgmtSwitchoverSelection Comments PdnLLSConfigGroupNamePdnLLSConfigSelection Link Load Sharing LLS PDN-LINK-LOAD-SHARING-MIB.mibPdnRedunNotificationEnable PdnRedunCommandPdnRedunAlarmStatus PdnRedunEntityStateDevConfigTestTimeout Timing and Clocking Paradyne mpeConfig MIB mpeConfig.mib91. mpeDevConfigClockSrcEntry Object Type Access Supported Paradyne Time Mib pdntime.mib DevConfigTestDuration93. pdntime.mib Object Type Access Supported DevDateAndTime RWDevNTPEnable RW DevNTPOffsetFromUTC94. pdndslam.mib Objects Supported Type SysDevUserAccountUserPassword RCSysDevUserAccountAccessPartition RC SysDevUserAccountTable95. pdnSecurity.mib Object Type Supported SecurityMgrSnmpAccess RWParadyne Security MIB pdnSecurity.mib DevSecurityMgrValidation RWSecurityMgrTrapAccess RW SecurityMgrTelnetAccessRWSecurityMgrFtpAccess RW SecurityMgrRowStatus RWMpeDevFileXferFileType3 MpeDevControlTable MpeDevFileXferConfigTable96. 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 98. Health and Status MIB Comments99. devLastTrapString 2 DevLastTrapString DSX Traps 99. devLastTrapString 3 DevLastTrapString Adsl Specific Traps99. 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.
Top Page Image Contents