BMS R11 TL1 create ONT with error in SQL

Issue Description

When the customer tries to create an Huawei ONT trough TL1 in BMS R11, there is an SQL error:
ADD-ONT::DEV=PRT45-1_OLT-HW_1,FN=0,SN=1,PN=0,ONTID=1:44422::NAME=devil,ALIAS=djdj,CAPABPROF=ONT_PROFILE_HW_HG850,SERIALNUM=2011-2E0A4C41,AUTH=SN,ALMPROF=alarm-profile_1;
0 2008-04-11 14:12:00
M  SN COMPLD
EN=1610614891   ENDESC=Failed to execute SQL
Eventhough, the ONT is created:
OLTHW-TestPLant1(config-if-gpon-0/1)#display ont info 0 1
—————————————————————————-
F/S/P           : 0/1/0
ONT-ID          : 1
Control flag    : active
Run state       : up
Config state    : normal
Match state     : match
DBA type        : SR
Loop mode       : disable
ONT RTD(us)     : –
Transparent     : disable
Ont Profile ID  : 6
Authentic type  : SN-auth
SN              : 323031312E0A4C41(2011-2E0A4C41)
Description     : ONT_NO_DESCRIPTION
Alarm profile-ID: 1
—————————————————————————-
———————————————-
T-CONT-ID     DBA-profile     Alloc-ID
———————————————-
0               1            1
– ———————————————-
This problems seems to happen in the case we had previously an ONT with the same ONT_ID in the same port.
If we create the ONT with a ONT_ID that was never used, the problem does not happen.
It seems that when we delete the ONT in the BMS, some information is not deleted in one of the tables.
Alarm Information

Null

Handling Process

CLI deleting leads to inconsistence between the device and BMS, syn can solve the problem.

Root Cause

Null

Suggestions

Null

Advertisements

Alternative way to enable U2000 admin user

Issue Description

Admin user account is disabled. Now customer can not have all rights on other users, and can not return admin account to be enabled

Alarm Information

According to documentation:

The users in the SMManagers group cannot activate the admin user.
If you need to activate the admin user, run the following command on the U2000 server:
In Solaris or SUSE Linux, run the following command:

#cd installation path
#. ./svc_profile.sh
#. ./bin/svc_enableUser user name

In Windows, run the following command:
>cd /d %IMAP_ROOT%
>svc_enableUser user name
Handling Process

On a U2000 test installation I was able to see which tables in database are used to store informations about users.

Tried to disable a test account and observed that information is updated in imapsmdb.tbl_SMUser.

The column in database which confirms if a user is disabled is: imap_accountvalidity (0 if account is  disabled, 1 if account is enabled).

Below actions were performed on live server:

1. Login with nmsuser credentials
2. cd /opt/sybase/OCS-15_0/bin
3. ./isql -SDBSVR -Usa -P<password>
4. > use imapsmdb
5. > go
6. > update tbl_SMUser SET imap_accountvalidity=1 WHERE username=’admin’
7. > go
8. > quit

Login to U2000 server with admin user and enable account from U2000/User management menu

Root Cause

When I’ve tried to run procedure specified in documentation, solaris reported that some libraries are missing.
In these conditions I was forced to look for alternative solutions.

Suggestions

I strongly recommend to enable user as from documentation.

In case of users which don’t have strong command line knowledge, please use a Database browser.

U2000 database structure might be different on different releases.
Above procedure was tested on U2000 V1R2C1SPC003.

For more Huawei solution please contact:

Telephone: 852-30623083
Email: Sales@Thunder-link.com
Supports@Thunder-link.com
Website: http://www.thunder-link.com

ALL network devices cannot be sync because of wrong configuration of xFTP watcher NAT

Issue Description

Customer cannot synchronize any device at the network, when he add new device, device panel cannot be viewed.
N2000 V200R012C05SPC030 Windows 2003 platform

Alarm Information

Null.

Handling Process

  1. FTP was not enabled on the server, so I enabled it by installing FTP server program on the Server then added it to xFTP watcher, however, problem not solved.
    2. check SNMP configuration on device, I noticed that traps are sent to IP 172.16.16.1, while server IP is 10.10.10.1
    3. customer informed us that there is firewall between NEs and N2000, IP range of NEs and firewall interface facing them is 172.16.x.x, while network 10.10.10.x is between Firewall and N2000.
    4. When making backup configuration of NE to N2000 through FTP on IP 172.16.16.1, backup succeed.
    5. When making backup configuration of NE to N2000 through FTP on IP 10.10.10.1, backup failed.
    6. I concluded that FTP is masked for IP 10.10.10.1
    7. If xftp watcher NAT is not configured, N2000 server will send IP 10.10.10.1 to NE to use for synchronization, so sync will fail.
    8. xFTP NAT is designed for such case, we configured $N2000\server\conf\xftp_mapping.cfg using below line, problem solved
    172.16.0.0/16  172.16.16.1

Root Cause

Causes for such problem can be:
1. FTP is not configured correctly on the server.
2. xFTP watcher is not configured.
3. SNMP communities on device are not consistent between NE and BMS.
4. Firewall blocks FTP packets between BMS and NEs.

Suggestions

Checking Topolgy is very important, don’t assume anything whiel troubleshooting.

For more Huawei solution please contact:

Telephone: 852-30623083
Email: Sales@Thunder-link.com
Supports@Thunder-link.com
Website: http://www.thunder-link.com

Can the Huawei S2700/S3700/S5700/S6700 Switches Use AC and DC Power Supply Simultaneously?

In versions prior to V100R006C01, the S2700, S3700, and S5700 cannot use AC and DC power supply simultaneously.

In V100R006C01 and later versions, the S3700-26C-HI, S5700-28C-HI, and S5700-28C-HI-24S can use AC and DC power supply simultaneously. S6700 cannot use AC and DC power supply simultaneously.

In V200R001C00 and later versions, the S5710-28C-EI and S5710-52C-EI can use AC and DC power supply simultaneously.

In versions prior to V200R005C00, the S6700-EI cannot use AC and DC power supply simultaneously.

In V200R005C00, the S5700-EI (non-PoE), S5700-SI (non-PoE), and S6700-EI can use AC and DC power supply simultaneously.

In V200R006C00 and later versions, the S5720-HI (non-PoE) can use AC and DC power supply simultaneously.

The S5720-C-EI (non-PoE) and S5720-PC-EI (non-PoE) can use AC and DC power supply simultaneously.

The S5720-SI (non-PoE), S6720-EI, and S6720S-EI can use AC and DC power supply simultaneously.

GPON ONU Profile Match state is Mismatch

An ONU connected to a GPON port of an Huawei OLT can go online successfully, but the queried Match state of the ONU is displayed as mismatch by running the display ont info command on the OLT.

Context

The ONU matching status indicates whether the actual ONU capability is the same as the service profile bound to the ONU. The status includes: initial, mismatch, and match. To some extent, the matching status is determined by the ONU running status and configuration status.

  • The matching status of the ONU can be queried only when the ONU running status is online. The matching status is match when the actual hardware capability of ONU is the same as the ONU service profile bound with the ONU. Otherwise, the status is mismatch.
  • In other configuration states, the matching status is initial.
  • The ONU matching status does not affect the normal forwarding of the service flow, and only indicates whether the actual ONU capability is the same as the service profile bound to the ONU.
In practice, ONUs in the offline state are bulk pre-configured on the OLT to facilitate service provisioning. An ONU service profile and an ONU line profile are specified during such configurations. The ONU profiles together can be regarded as a virtual ONU. Subsequent services are configured based on this virtual ONU. Inconsistency between the capability set configured in the ONU profiles and the actual ONU capabilities involves the following two situations:

  • The configured capability set outmatches the actual ONU capabilities. If the ONU is bound to such ONU profiles, ONU configurations will fail to match when the ONU goes online.
  • The configured capability set undermatches the actual ONU capabilities. In this case, the ONU capabilities that are not covered by the ONU profiles will fail to be configured or applied.

Location Method

When the queried Match state of the ONU is displayed as mismatch, locate the fault according to the following procedure:

  1. Check whether the capability set configured in the ONU service profile matches the actual ONU capabilities.
  2. Procedure

    1. Run the display ont capability command to query the actual ONU capabilities. According to the data plan, modify the current ONU profiles, or bind matching ONU profiles to the ONU.
      • If this problem occurs on all the ONUs of the same type, the configurations of the ONU profiles may be incorrect.
        • If the OLT works in the distributed mode, the profiles that are bound to the ONU cannot be modified or deleted. In this case, bind matching ONU profiles to the ONU.
        • If the OLT works in the profile mode:
          1. Run the display ont-srvprofile command to query the information about the ONU service profile and run the display ont-lineprofile command to query the information about the ONU line profile.
          2. Modify the ONU profiles by referring to Configuring a GPON ONT Profile in the Commissioning and Configuration Guide.
      • If this problem occurs on only one ONU, it is suggested to bind matching ONU profiles to the ONU.
        • If the OLT works in the distributed mode:
          1. Run the display ont-profile command to query the current ONU profiles that are configured on the OLT.
          2. If the OLT does not have matching ONU profiles, run the ont-profile add command to add matching ONU profiles.
          3. Run the ont modify command to bind the ONU profiles to the ONU.
        • If the OLT works in the profile mode:
          1. Run the display ont-srvprofile command to query the information about the ONU service profile and run the display ont-lineprofile command to query the information about the ONU line profile.
          2. If the OLT does not have matching ONU profiles, add matching ONU profiles by referring to Configuring a GPON ONT Profile in the Commissioning and Configuration Guide.
          3. In the GPON mode of the OLT, run the ont modify command to bind the ONU profiles to the ONU.
    2. Check whether Match state of the ONU is displayed as match.
      • If Match state of the ONU is displayed as match, go to 4.
      • If Match state of the ONU is displayed as mismatch, proceed to 3.
    3. Connect Huawei for technical support.
    4. The fault is rectified.

There is many error message on optical modules saying that the power is too low in Huawei S6700 Switch

Issue Description

There is many error message on optical modules saying that the power is too low in Huawei S6700 Switch
QQ图片20171226164905

Alarm Information

May 23 2014 15:36:09+01:00 FEDERATEUR-RG %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[25]:Optical module in interface XGigabitEthernet0/0/7 exception, Rx power is too low.
May 23 2014 15:34:48+01:00 FEDERATEUR-RG %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[26]:Optical module in interface XGigabitEthernet0/0/9 exception, Rx power is too low.
May 23 2014 15:34:44+01:00 FEDERATEUR-RG %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[27]:Optical module in interface XGigabitEthernet1/0/10 exception, Rx power is too low.
May 23 2014 15:34:44+01:00 FEDERATEUR-RG %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[28]:Optical module in interface XGigabitEthernet1/0/5 exception, Rx power is too low.
May 23 2014 15:26:02+01:00 FEDERATEUR-RG %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[29]:Optical module in interface XGigabitEthernet0/0/22 exception, Rx power is too low.
May 23 2014 15:26:02+01:00 FEDERATEUR-RG %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[30]:Optical module in interface XGigabitEthernet0/0/20 exception, Rx power is too low.
May 23 2014 15:26:02+01:00 FEDERATEUR-RG %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[31]:Optical module in interface XGigabitEthernet0/0/19 exception, Rx power is too low.
May 23 2014 15:26:02+01:00 FEDERATEUR-RG %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[32]:Optical module in interface XGigabitEthernet0/0/8 exception, Rx power is too low.

Handling Process

Test the fiber cable if it’s normal or if the Fiber is too winding.
You can change another normal Fiber to these interfaces who have the error message.

The physical fiber cable has problem

I think it is better if you replace it by another good one and test again

Root Cause

only some interfaces have this error message:

In slot 1: XGigabitEthernet1/0/10 and XGigabitEthernet1/0/5
   In slot 0: XGigabitEthernet0/0/7, XGigabitEthernet0/0/8, XGigabitEthernet0/0/9, XGigabitEthernet0/0/19, XGigabitEthernet0/0/20, XGigabitEthernet0/0/22.

The receive power is out of the allowed range

For example:
XGigabitEthernet1/0/5 transceiver information:
**************************************************
Common information:
Transceiver Type               :1000_BASE_SX_SFP
Connector Type                 :LC
Wavelength(nm)                 :850
Transfer Distance(m)           :275(OM1),550(OM2),1000(OM3)
Digital Diagnostic Monitoring  :YES
Vendor Name                    :HUAWEI
Vendor Part Number             :02315204
Ordering Name                  :
————————————————————-
Manufacture information:
Manu. Serial Number            :PQH0QRV
Manufacturing Date             :2013-10-23
Vendor Name                    :HUAWEI
————————————————————-
Diagnostic information:
Temperature(°C)              :21.29
Temp High Threshold(°C)      :95.00
Temp Low  Threshold(°C)      :-25.00
Voltage(V)                    :3.29
Volt High Threshold(V)        :3.90
Volt Low  Threshold(V)        :2.70
Bias Current(mA)              :6.11
Bias High Threshold(mA)       :32.40
Bias Low  Threshold(mA)       :1.55
RX Power(dBM)                 :-17.28    — Too low
RX Power High Threshold(dBM)  :0.00
 RX Power Low  Threshold(dBM)  :-16.98
TX Power(dBM)                 :-4.91
TX Power High Threshold(dBM)  :0.00
TX Power Low  Threshold(dBM)  :-12.50

Suggestions

No