Table 1-96. mpe_Control.mib (2 of 2)

Table

Object

Type

Supported

 

 

 

 

mpeDevFirmwareControlTable

 

 

Yes

 

 

 

 

 

entPhysicalIndex

 

Yes

 

 

 

 

 

mpeDevFirmwareControlIndex(1)

INTEGER

Yes

 

 

 

 

 

mpeDevFirmwareControlRelease(2)

DisplayString

Yes

 

 

 

 

 

mpeDevFirmwareControlOperStatus(4)

INTEGER

Yes

 

 

 

 

 

mpeDevFirmwareControlAdminStatus(5)

INTEGER

Yes

 

 

 

 

9.3.1mpeDevControlTable:

This table is indexed on the entPhysicalIndex and contains mpeDevControlReset object which is used to reset the associated entity (for example, card). Writing the value reset (2) to this object initiates a Hardware power-on reset of the entity. Writing the value resetToFactoryDefaults (3) causes the entity to re-configure itself with factory defaults. Writing the value of resetToNewActiveConfig (4) causes a new configuration to be applied without resetting the unit. The value read from this object is noOp(1).

9.3.1.1mpeDevFileXferConfigTable:

The Paradyne FileXfer Client Config Table is indexed by the entPhysicalIndex. Use of the File Tranfer MIB could be used with other MIBS in the following manner:

a)Use another MIB/means to verify available space /make room for a file to be transfered to this device

b)Use this MIB to download the file.

c)Use another MIB/means to select the file you want to make active if your selecting firmware for example.

d)Use another MIB/means to reset the device.

A management station wishing to initiate a file transfer needs to create an entry in this table. To do so, you must first identify the entPhysicalIndex of the device you intend to do the transfer with. You should then create the associated instance of the row status. It must also, either in the same or in successive PDUs, create an instance of mpeDevFileXferFileName, mpeDevFileXferFileType, mpeDevFileXferServerIpAddress, mpeDevFileXferOperation. It should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created, either by an explicit SNMP set request or by default, the row status should be set to active to initiate the request. Note that this entire procedure may be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted configuration objects. Once the MpeDevFileXferConfigEntry request has been created (that is, the mpeDevFileXferRowStatus has been made active), the entry cannot be modified - the only two operations possible after this are read and delete the row. Once the request completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries could be aged out, but an entry will never be deleted within 5 minutes of completing.

8000-A2-GB30-10

November 2003

91

Page 97
Image 97
Paradyne 8620, 8820 manual mpeControl.mib 2 Object Type Supported, MpeDevControlTable, MpeDevFileXferConfigTable

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.