1.1 1.1.1 Feature Introduction

Definition

Equipment vendors are rolling out new multiple x units (MxUs) quickly to meet the requirements at diverse carrier markets. These MxUs have similar basic features but different chips, appearance, type names, and subtle features. In the old management style, MxUs are coupled with the U2000. To manage new types of MxUs, users need to use specific U2000 versions.

MxU decoupling enables users to manage new types of MxUs without upgrading the U2000 or installing patches.

Benefits

MxU decoupling enables users to install and manage new types of MxUs using the current U2000, which does not affect service provisioning.

Application Scenarios

During network expansion or MxU replacement, new types of MxUs are installed, but no new feature needs to be applied. The MxU decoupling feature prevents frequent U2000 upgrades when such MxUs are installed.

The new types of MxUs must be developed by Huawei.

GUIs

The U2000 supports automatic and manual MxU installation.

l   Automatic installation:

When adding MxUs, the U2000 obtains device type description files from the MxUs and installs the files automatically.

The U2000 V100R008C00 and later versions support automatic installation.

l   Manual installation:

On the U2000 server, start the /server/nemgr/nemgr_access/bin/pnpshell.bat or /server/nemgr/nemgr_access/bin/pnpshell.sh installation script.

Installation interface

In this interface, select the desired operation, for example, querying the device type list or installing a new device type.

Two installation modes, online and offline, are available. The online mode requires the U2000 to be online. The offline mode requires the database to be running properly. If you use the online installation mode, you do not need to restart the U2000 after installation is complete, whereas in the offline installation mode, restarting the U2000 is mandatory.

l  On a non-Windows OS, start the installation tool as the ossuser user.

l  For more details, see Installing a Decoupled MxU in the OG for ONU NE Management.

1.1.2 Function Description

MxU decoupling provides the following functions:

l   Installing new device types

l   Querying the list of managed device types

1.1.3 Key Indicators

Installing a new type of MxU: within 30s

1.1.4 Standards/Protocols

None

1.1.5 Availability

Licenses

No license is required for using the MxU decoupling feature.

NE Versions

The following table lists the MxU types and versions involved in the MxU decoupling feature.

Product Domain	Product Series	Device Type	Minimum Version
Access	MxU	N/A	V800R312C00

Hardware Requirements

None

Feature Dependencies

None

1.1.6 Technical Principles

Principles

MxUs are decoupled from the U2000 in the following ways:

l   Manually loading description files of new device types

l   Automatically obtaining description files of new device types from MxUs and loading the files to the running U2000

The details of these two ways are as follows:

l   Manual loading

−       A device type description file (XML file) is released together with a new type of MxU if the MxU supports the decoupling feature.

−       Obtain the file from the release package and load it to the U2000.

−       New resources, such as subracks, boards, and daughter boards, of a new type of MxU, also have description files. To manage these new resources, the U2000 obtains the resource description files from the MxU and loads the files automatically.

l   Automatic loading

−       When adding an access NE, the U2000 automatically performs the following operations:

1. Checks whether the NE can be managed.

2. Checks whether the NE is an MxU if the NE can be managed.

3. Checks whether the NE supports decoupling if the NE is an MxU.

4. Obtains and loads the device type description file if the MxU supports decoupling.

−       New resources, such as subracks, boards, and daughter boards, of a new type of MxU, also have description files. To manage these new resources, the U2000 obtains the resource description files from the MxU and loads the files automatically.

System Context

System Impact

The MxU decoupling feature does not affect the system.

Restrictions

l   MxU decoupling applies only to existing MxU features but does not apply to new MxU features.

l   MxU decoupling applies to some MxUs. (For details on whether an MxU supports decoupling, see the device feature document.)

l   The U2000 V100R008C00 and later versions support automatic installation of new device types.

1.1.7 Change History

First Version with the Feature

U2000 V100R006C02

Feature Updates

No.	Description	Purpose	Domain
1	The MxU decoupling feature is first implemented in the U2000 V100R006C02: l  New MxU types can be installed in offline mode. l  Installation of new MxU types takes effect only after the U2000 is restarted.	To manage new types of MxUs by loading the device type description files manually.	Access
2	The MxU decoupling feature is enhanced in the U2000 V100R008C00: l  New MxU types can be installed in online mode. l  Installation of new MxU types takes effect immediately without a U2000 restart.	l  To manage new types of MxUs by obtaining the device type description files from MxUs and loading them automatically. l  To install new MxU types without restarting the U2000.	Access

1.1.8 Acronyms and Abbreviations

Acronyms and Abbreviations	Full Name
OLT	optical line terminal
MxU	multiple x unit, such as MDU, MTU