Showing posts with label NMS. Show all posts
Showing posts with label NMS. Show all posts

Tuesday, November 14, 2017

How to Install the Patch of iManager U2000 V100R002C01CP5002 fails?

Issue Description
Customer need to install the patch V100R002C01CP5002 to his U2000 single-server System which is already upgraded to V100R002C01SPC100 , Huawei Engineer follow the installation guide and check all Precautions and the Preparations but when the engineer reach the upgrade step described as below :
12. Run the following commands to install the MSuite patch:
#cd /opt/nmspatch/patch
#chmod 755 *.sh
#./pre_patch.sh
he got the below error message and could not continue the installation
Installing the MSuite patch. Please wait...
Traceback (most recent call last):
File "patch/pre_patch.py", line 446, in ?
_patchNMSApp(curPatchPath)
File "patch/pre_patch.py", line 233, in _patchNMSApp
_copyFile(vcfcfgPath + "/process/process_std", nmsappPath + "/flag/nonCritic
alProcessList")
File "patch/pre_patch.py", line 57, in _copyFile
shutil.copyfile(fromFile, toFile)
File "/opt/U2000/server/3rdTools/python/lib/python2.4/shutil.py", line 49, in
copyfile
fdst = open(dst, 'wb')
IOError: [Errno 2] No such file or directory: '/opt/NMSApp/flag/nonCriticalProce
ssList'
#
please check attached Fig-1.
Alarm Information
None.
Handling Process
WE have check each of previous reason to find the root cause as below
1. NMS process has been already ended as the below commands does not display ( imap_sysmonitor -cmd start )
# ps -ef | grep imap 
2. Sybase database has been already ended as the below commands display no result.
#su - sybase
$cd /opt/sybase/ASE*/install
$ ./showserver|grep DBSVR
3. Msuite process has been already ended as the below commands does not display ( /opt/HWNMSJRE/jre_sol/bin/java -server)
#ps -ef | grep java.
4. UEasy check have been made and it shows no item with [No Go].
we contact RND for support, the reply was to check that No such file or directory: '/opt/NMSApp/flag/nonCriticalProcessList'
when we check we find that '/opt/NMSApp' directory exists, but the flag directory is not exists under that directory as shown in Fig-2,3
The RND reply again to confirm if this is Single Server or HA system , we confirm that it is Single Server system.
Thus the RND find the solution and reply to delete that directory '/opt/NMSApp' . After we delete it, the problem solved and installation complete
as shown in Fig-4.
 
Root Cause
Cause -1- \ the NMS processes have not been ended.
Cause -2- \ the Sybase database is still running and should be ended.
Cause -3- \ the MSuite server process has not been ended.
Cause -4- \ May need to Run UEasy check and send the Output report to ask for support.
Suggestions
It was found that this server has been used for HA before, then it has been modified to be used as single server , this is explain why the folder /opt/NMSApp was exists.
Thus in any case you are going to install that patch on Single-Server system check that this folder is not exists.
More related: 

U2000V100R006C02SPC301 Installation Introduction_Part 1


Monday, November 6, 2017

How to Replace an Huawei ONU Rapidly?

How to Replace an Huawei ONU Rapidly?

To replace a faulty optical network unit (ONU) on a live network, you need to reload the configurations after the replacement or back up the data before loading the configurations. The operations are complicated and prone to errors. Using the network management system (NMS) to replace the ONU improves the efficiencies in device replacement and configuration loading, and at the same time reduces the error probabilities. There are five steps for replacing an ONU rapidly.
  1. Configure automatic backup policies and automatic upgrade policies. (This is the prerequisite of the replacement.)
    • After the automatic backup policy is configured, the device backs up data at the configured time. The latest backup database will be used during the replacement.
    • After the automatic upgrade policy is configured, the NMS will create an automatic ONU upgrade task to upgrade the ONU if the ONU version is different from the target version set in the automatic upgrade policy.
  2. Replace the ONU and power on the ONU to ensure that the optical link on the device is normal.
  3. Start the ONU replacement operation on the NMS.
  4. Bind the MAC address of the new ONU on the NMS.
  5. Check the configurations and verify the services after the replacement.
In step 1, you only need to configure the automatic backup policy and automatic upgrade policy once. To replace ONUs in future, you only need to rebind the ONU MAC addresses on the NMS.


Monday, September 18, 2017

FTTH Networking and Configuration Scenarios

Typical FTTH networking diagram 



Bridging ONT + HGW Network Scenario

The HGW integrating an IAD provides Internet, voice over Internet Protocol (VoIP), and Internet Protocol television (IPTV) services to users.

Services are implemented on the HGW, and the bridging ONT works with the OLT to provide Layer 2 channels.

Bridging+Voice ONT Network Scenario
The ONT integrating an integrated access device (IAD) provides Internet, VoIP, and IPTV services to users.
The bridging+voice ONT provides Layer 2 data and voice services. This scenario provides transparent transmission channels and requires simple service configuration, so this scenario applies to Layer 2 networking.
  • For data services, a PC directly performs dial-up. Then, the upper-layer broadband remote access server (BRAS) device authenticates and accesses the PC. The PC can also access the Internet using the Dynamic Host Configuration Protocol (DHCP) or static IP address.
  • The ONT with a built-in voice module encapsulates voice service packets, and the OLT transmits them to the upstream next generation network (NGN) or IP multimedia subsystem (IMS).

Gateway ONT Network Scenario
Huawei ONT integrating an IAD provides Internet, VoIP, and IPTV services to users.
The HGW ONT facilitates interconnection of home devices by providing Layer 3 services, such as Point-to-Point Protocol over Ethernet (PPPoE)/DHCP dial-up, network address translation (NAT), and Internet Group Management Protocol (IGMP) snooping. This scenario provides fine-grained management channels and service control, and applies to Layer 3 networking.

FTTH Deployment Schemes

FTTH service application includes the deployment process and service provisioning process. The FTTH deployment process includes OLT deployment (configuration) and configuration of basic data. No deployment, however, is required on the ONT and the ONT is plug and play once services are provisioned.
FTTH deployment schemes

Scheme
  • On the NMS: Profiles can be issued in batches.
  • Using commands on the OLT: Configuration scripts containing commands can be imported to the OLT.
  • Using the OSS: This method is recommended and it can implement automatic service provisioning, and eliminate problems caused by manual service provisioning, such as large workload, low efficiency, and difficult management.
  • Using OSS+ITMS: This method is recommended if the multiple private nodes are customized for carriers. Using a TR069 server, new gateways and value-added voice services can be simply added.
    • Layer 2 configuration data is issued on the NMS or OLT MA5603T or MA5600T.
    • Other configuration data such as voice, Layer 3, and Wi-Fi data is issued using the ITMS.
  • On the NMS: It applies to the scenario when no OSS is available and services need to be provisioned manually on the NMS.
  • On the ONT web page: When it is not feasible to provision services on the OSS or NMS, you can log in to the ONT web page and configure or modify parameters to provision services.
Parameter
  • DBA profile
  • Line profile
  • Service profile
  • IP traffic profile
  • Service level profile
  • Global OLT configurations (rather than FTTH user configurations) such as multicast VLAN, multicast mode, and policy of forwarding unknown packets
  • FTTH user service VLAN configurations including adding VLANs, setting the attributes of VLANs, and adding upstream ports for VLANs
ONT service provisioning parameters are classified into common parameters and customized parameters:
  • Customized parameters are usually issued by the upper-layer system during service provisioning.
  • Common parameters are usually configured at delivery or during data pre-configuration.