Showing posts with label Huawei U2000. Show all posts
Showing posts with label Huawei U2000. Show all posts

Tuesday, March 13, 2018

How to Setting License on Huawei NMS?

This chapter describes how to perform license setting on the NMS. For example: The smart line card/The TP-Assist function/The OptiX OSN 8800 T32 standard Subrack Speedup.

Prerequisite

  • You must be an NM user with "NM operator" authority or higher.
  • The license file has been installed.
  • The NE has been created on the NMS.

Tools, Equipment, and Materials

U2000

Legend Information

Figure 1 shows legend information about U2000 operations.
Figure 1 Legend Information 

2000Batch Configuration

  1. Visit the following navigation path.
  1. Select the desired license.
  2. On the NE license Authorization window, select the desired NE and set the license.

    NOTE:
    1. To set the license to support TP-Assist, on the right side of the window, change the NE license status from off to on and click Apply on the lower right corner of the window.
    2. To set the license to support a smart line card, in the column of OptiX OTN Platform,Hybrid Service Line Card SDH Encapsulation Ability fee or OptiX OTN Platform,Hybrid Service Line Card Packet Encapsulation Ability fee, enter the number of virtual ports, and click Apply.
    3. To set the license to support OptiX OSN 8800T32 standard Subrack Speedup, in the column of OptiX OSN 8800T32 standard Subrack Speedup enter the number of borads, and click Apply

Single NE Configuration

You can also navigate to the NE Explorer to set the license for a single NE.
  1. IN the NE Explorer, set the license.

     NOTE:
    1. To set the license to support TP-Assist, on the right side of the window, change the NE license status from off to on and click Apply on the lower right corner of the window.
    2. To set the license to support a smart line card, in the column of OptiX OTN Platform,Hybrid Service Line Card SDH Encapsulation Ability fee or OptiX OTN Platform,Hybrid Service Line Card Packet Encapsulation Ability fee, enter the number of virtual ports, and click Apply.
    3. To set the license to support OptiX OSN 8800T32 standard Subrack Speedup, in the column of OptiX OSN 8800T32 standard Subrack Speedup enter the number of borads, and click Apply

Wednesday, March 22, 2017

How to Search Out the Resource License Fast in a PO?

Q:
Both the resource license for the U2000 software and the NE licenses for hardware devices are contained in a purchase order (PO). The numerous NE licenses in the PO make it difficult to search out the resource license fast.
Alarm Information
None
Handling Process
    A:
In the advanced search window of the FNO system, you can enter multiple search criteria, such as the PO, product name, product version and site information. In this manner, the required license can be located accurately.
Note:
NE licenses are licenses for network hardware devices. Currently, hardware devices can control functions by using NE licenses without executing license policies. Therefore, hardware devices need not use 
license files. The resource license is a license for the U2000 software used to manage specific NE or port resources on the U2000. Usually, the devices at a site share a PO. If capacity expansion is performed at the site, the NE licenses and the resource license that is used to manage those devices will be combined in one PO. As a result, a PO in the FNO system contains numerous NE licenses and one resource license for managing those devices.
Step 1  At the FNO website, click the button highlighted by the red oval as shown in Figure 1-1(check the attachment Figure 1-1 Manage entitlements).
Step 2  In the dialog box that is displayed, enter multiple search criteria as shown in Figure 1-2(check the attachment Figure 1-2 advanced search).
Root Cause
None
Suggestions
None 

More related:

Huawei MA5683T

Huawei MA5680T




Tuesday, March 21, 2017

How to Locate fault during Huawei OptiX OSN2500?

Handling of Abnormalities of Fiber, Cable, and Connector

This section describes how to handle a fiber failure, cable failure, and a connector failure based
on the common causes of the fiber failure, cable failure, and connector failure.

Common Causes

  1. Cables are broken or wrongly spliced.
  2. Attenuation of cable and flange is very high.
  3. The cable connector is loose.
  4. Power cables are wrongly connected.
  5. The interface board is wrongly connected.

Procedure
    Step 1 On the U2000, check whether alarms, such as R_LOS, R_LOF, T_ALOS, P_LOS or
      IN_PWR_ABN, are triggered when the fiber, cable, or connector is abnormal. When these
        alarms exist, refer to Huawei OptiX OSN 2500 Intelligent Optical Transmission System Alarms
          Reference to handle these alarms.
            Step 2 Check whether optical fibers and power cables are broken.
              Step 3 Check whether optical fibers are wrongly spliced.
                Step 4 Check whether connectors are loose.
                  Step 5 Check whether the bending radius of the optical fiber is not less than 60 mm.

                  Checking Configuration Data

                  During the fault location and rectification, the configuration data should be checked.
                  Check whether the data is correctly configured. Especially, check the configuration data when
                  the services are interrupted during the equipment installation, commissioning and upgrade.
                  The query items include data configuration of the network, NE and U2000.

                  Checking Misoperation
                  Human misoperation may result in service interruption.

                  Misoperation
                  Human misoperation refers to the following operations on the available services.
                  Configure hardware or software loopback.
                  Configure services as unloaded.

                  Procedure
                  Step 1 Check whether the loopback is configured on the tributary or line. If the loopback is configured,
                  the LOOP_ALM alarm, indicating the loopback, can be queried on the U2000. In this case,
                  release the software or hardware loopback on the U2000 or equipment.
                  Step 2 Check whether "service unloaded" is configured on the U2000. If "service unloaded" is
                  configured, the alarm indicating that the path is unloaded, such as LP_UNEQ, can be queried
                  on the U2000. In this case, modify "service unloaded" to "service loaded".

                  Checking Consistency of Board Models
                  After the replacement, models of the new board and original board should be consistent.
                  Procedure
                  Step 1 Check whether the model of the replaced or added board during the upgrade or expansion is
                  consistent with that of the original board. Especially, in the case of the cross-connect and timing
                  boards with the active and standby relation, the active and standby boards should of the same
                  model. If the board models are inconsistent, the WRG_BD_TYPE alarm, indicating that the
                  board type of the inserted board is incorrect, can be queried on the U2000.
                  Step 2 According to the actual situation, check whether the setting of the DIP switch and jumper is correct.

                  Handling Hardware Faults of Equipment
                  If the fault is a hardware fault, replace the faulty board with a new one.
                  Common alarms indicating hardware faults are listed as follows:
                  HARD_BAD
                  COMMUN_FAIL
                  HSC_UNAVAIL
                  BD_STATUS
                  BUS_ERR
                  CHIP_FAIL
                  PLL_FAIL
                  TR_LOC
                  T_LOSEX
                  For handling of the preceding alarms, refer to the Alarms and Performance Events Reference.
                  Locate the faulty station by analyzing the alarms, indicators or using the loopback. Then, replace
                  the faulty board to rectify the fault.


                  Monday, March 20, 2017

                  Ethernet configuration missing in NMS but normal when testing

                  Issue Description
                  Ethernet configuration missing in NMS, already configured at both site. However, when do testing end to end, no faulty alarm at test gear. The services still exist, if not, test gear will show faulty alarm. 
                  Alarm Information
                  No Alarm.
                  Handling Process
                  1, Current version U2000 V1R3C00SPC100 is upgrading to V1R5C00SPC600 as recommended by R&D.
                  2, After NMS restart, all Ethernet configurations appear normally.
                  Root Cause
                  1, Configuration not seen at NMS, but when test it normal, mean at NE side services were normal.
                  2, Services only cannot see at NMS side, mean problem probably related to NMS.
                  3, NE can login and communicate normally, means NMS and NE can communicate normally.

                  4, Collect data and send to R&D.
                  5, Feedback from R&D, probably the current NMS version have some bug which cannot support some features of NE or the version of NE and NMS may not compatible. R&D recommended version V1R5C00SPC600 to upgrade.

                  Suggestions
                  1, for new version of NE, always uses the latest NMS version to avoid some operations and monitoring failure.
                  2, V1R5C00SPC600 version is the latest recommended by R&D to use.

                  More related articles:

                  MA5600T Series LACP Configuration

                  MA5600T Series Equipment Downgrade Guidebook

                  How to configure DHCP on OLT