Paradyne 8620 VacmContextTable, VacmSecurityToGroupTable, VacmAccessTable, SNMPv3 Coexistence

Page 85

1. Network Management Specification

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 3.0 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.

8000-A2-GB30-00

June 2003

79

Image 85
Contents Hotwire 8620 Copyright 2003 Paradyne Corporation All rights reserved Contents Contents June Section Description About This GuideDocument Number Document Title Product-Related DocumentsSupported RFCs and MIBs 1 GranDSLAM 3.0 Network Management InterfaceName Description 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 ImplementationSummary of Traps 1 Description VarBinds Standard Traps Standards Compliance for Snmp TrapsDSX Traps ATM-M4 TrapsEntity MIB Traps Summary of Traps 2 Description VarBindsShdsl MIB Traps Summary of Traps 3 Description VarBinds Sonet Linear APS MIB Traps Summary of Traps 4 Description VarBindsEnterprise 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 System Group, MIB-II RFC Management Information Base MIB-II RFCSysDescr Object system 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 3.0 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 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 InterfaceIfOutDiscards Object ifEntry 22. ifOutDiscards Interface IfOutErrors Object ifEntry InterfaceIfOutQLen ifEntry IfSpecific 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 RFCNetwork Management Specification Physical Layer Adsl MIB RFC 28. Adsl MIB Comments 30. ReachDSL MIB Comments Paradyne ReachDSL MIB pdnreachDSL.mibDS1 MIB RFC 31. DS1 MIB Comments Paradyne DS1-EXT MIB PDN-DS1EXT-MIB32. DS1-EXT MIB Comments PdnDs1ExtConfConnector RWPdnDs1ExtConfLineLengthType RW PdnDs1ExtConfLineLength RWSonetMediumEntry 34. sonetMediumEntry Comments SONET-MIB RFC 33. SONET-MIB CommentsSonetSESthresholdSet SonetPathCurrentWidthBy default, this object is enabled DevSonetStatusChangeTrapEnableDevSonetXmitClkSrc DevSonetStatusLastChange36. Shdsl MIB Comments NewSpectrumMgmtGeneralConfigEntrySpectrum Management pdnspectrummgmt.mib 37. Spectrum Management CommentsLink Layer ATM AtoM MIB RFC ATM Interface Configuration Parameter Group RFC38. ATM MIB Comments AtmInterfaceMaxVpcs Object atmInterfaceConfEntry40. atmInterfaceMaxVccs AtmInterfaceMaxVccs Object atmInterfaceConfEntryAtmInterfaceMaxVccs 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 54. 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 atmfM4TcAdapterEntry55. Object Supported in ATM Forum MIB Type TC Adapter Layer Table atmfM4TcAdapterEntryATM Cell Layer Table atmfM4ATMLayerEntry AtmfM4VcXConnRecover Object atmfM4VcXConnEntry1AtmfM4IfType Object atmfM4ATMLayerEntry AtmfM4IfSubscriberAddress 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 Entity MIB version 2 Objects supported Syntax Access Status PortedEntityPhysical Group 59. entPhysicalEntry entPhysicalTable 1 1 Sup ObjectEntPhysicalIndex 59. entPhysicalEntry entPhysicalTable 1 2 Sup Object60. entPhysicalIndex Entity Comments EntPhysicalDescrEntPhysicalVendorType 61. entPhysicalDescr Entity Description63. entPhysicalVendorType 1 Entity EntPhysicalVendorType EntPhysicalContainedIn 63. entPhysicalVendorType 2 Entity EntPhysicalVendorType64. entPhysicalContainedIn Entity EntPhysicalContainIn 65. entPhysicalClass Entity EntPhysicalClass EntPhysicalClassEntPhysicalParentRelPos 67. entPhysicalName Entity EntPhysicalName EntPhysicalNameEntPhysicalHardwareRev EntPhysicalSoftwareRev 68. entPhysicalHardwareRev Entity EntPhysicalHardwareRevEntPhysicalFirmwareRev 69. entPhysicalFirmwareRev 1 Entity EntPhysicalFirmwareRevEntPhysicalSerialNum 69. entPhysicalFirmwareRev 2 Entity EntPhysicalFirmwareRev70. entPhysicalSerialNum Entity EntPhysicalSerialNum EntPhysicalMfgNameEntPhysicalModelName 71. entPhysicalMfgName Entity EntPhysicalMfgName72. entPhysicalModelName 1 Entity EntPhysicalModelName EntPhysicalAlias 72. entPhysicalModelName 2 Entity EntPhysicalModelName73. entPhysicalAlias Entity EntPhysicalAlias 74. entPhysicalAssetID Entity EntPhysicalAssetID EntPhysicalAssetIDEntPhysicalIsFRU 75. entPhysicalIsFRU 1 EntityEntityLogical Group 75. entPhysicalIsFRU 2 Entity EntPhysicalIsFRU76. entLogicalEntry entLogicalTable Sup Object EntLogicalIndexEntLogicalIPDomain EntLogicalTAddressEntLogicalContextEngineID EntLogicalContextNameEntPhysicalChildIndex Entity EntPhysicalIndex Semantic MpeEntPhysicalExtAdminStatusEntityGeneral Group EntityNotifications GroupMpeEntPhysicalExtOperStatus EntPhySensorValueUpdateRateEntity Sensor MIB RFC 81. Entity Sensor MIB CommentsIfMauIfIndex RO IfMauTable Supporte Object Type AccessIfMauIndex RO IfMauType ROIfMauStatus RO IfMauDefaultType RWIfMauAutoNegSupported RO IfMauTypeListBits ROPdnMgmtIpPortTable 84. PDN-MGMT-IP-MIB Object Type SupportedPdnMgmtIpPortIndex NA 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 VacmViewTreeFamilyTable86. pdnLinkFaultMgmtApsSelection Comments Link Fault ManagementApsConfigMode ApsConfigRowStatusPdnLLSConfigSelection PdnLLSConfigGroupName88. pdnLinkFaultMgmtSwitchoverSelection Comments Link Load Sharing LLS PDN-LINK-LOAD-SHARING-MIB.mibPdnRedunAlarmStatus PdnRedunCommandPdnRedunNotificationEnable PdnRedunEntityState90. mpeDevConfigClockSrcEntry Object Type Access Supported Timing and Clocking Paradyne mpeConfig MIB mpeConfig.mibDevConfigTestTimeout 92. pdntime.mib Object Type Access Supported DevConfigTestDurationParadyne Time Mib pdntime.mib DevDateAndTime RWDevNTPOffsetFromUTC DevNTPEnable RWSysDevUserAccountAccessPartition RC SysDevUserAccountUserPassword RC93. pdndslam.mib Objects Supported Type SysDevUserAccountTableParadyne Security MIB pdnSecurity.mib SecurityMgrSnmpAccess RW94. pdnSecurity.mib Object Type Supported DevSecurityMgrValidation RWSecurityMgrFtpAccess RW SecurityMgrTelnetAccessRWSecurityMgrTrapAccess RW SecurityMgrRowStatus RWMpeDevFileXferFileType3 95. mpeControl.mib 2 Object Type Supported MpeDevFileXferConfigTableMpeDevControlTable 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 97. Health and Status MIB Comments98. 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.