Dear friend！

I have collected some simple and commonly used commands, I hope it is useful to you.

cfg-get-phybd

#Querying Physical Boards

cfg-get-board

#Query logical boards.

alm-get-curdata-ext:2,0,0:

#Query alarms on the board in slot 2 of subrack 0.

cfg-get-vrcb

#To query the software version of the system control board

ver

#Querying the Basic Version of the System Control Board

cfg-reset-board:8,hard

#Perform a cold reset on the board in slot 8.

cfg-del-board:4

#Delete the logical board in slot 4.

cfg-get-wavelen:2,1,1

#To query the wavelength of channel 1 at port 1 on the board in slot 2, run the following command:

cfg-get-cfgwavelen:2,1,1:

#Query the wavelength configured for channel 1 of port 1 on the board in slot 2.

cfg-set-wavelen:2,1,1,cband,2:

#Configure channel 1 of port 1 in slot 2 and set the wavelength number to 2.

cfg-init-all

#Clear all configurations (initialize the NE)

cfg-get-bdinfo:2

#To query the configuration of slot 2, run the following command:

:sm-add-user:"liqiang","Changeme_123","super",enable;

#Creating a User Name and Password

cfg-get-bdinfo:2

###Query the configuration of the board in slot 2.

Item=34060568 indicates the wavelength-tunable optical module.

cfg-get-dxc-ex: 0,0

#To query the cross-connection configurations of all ports in all slots

Thank you！
Hi guys.

I want to share some functions in Navigator.

Navigator

The Navigator is a tool for configuration of transmission devices.

The Navigator is a tool for configuration and commissioning by command line interface for technical personal.

After you choose Connect, the dialog box shown in the following figure is displayed.

You can click Search to search for the IP addresses of gateway NEs. All the IP addresses that meet your search cri

After connection succesfull press Login in main menu.

Put correct Username and Password and then login. The dialog box shown in the following figure is displayed.

Force Login: indicates whether to log in to the NE forcibly.

Navigator have some function for users (for example Calculator)

The calculator need for convert exID-ID to the HEX (see in the following figure is displayed )

Another function of Navigator, also can use script to collect data from several NE (should have connection betwe
Use command “run” and then select file like *.txt

Select next step ( for example All)

In file script can have several commands (independence of command you can take some results, very fast.)

//#9-1000: is exID-ID

// For login to NE choose correct User and Password data :login:"User","Password"

File have several command and two NE ( it could be more then two NE, it in depends of topology and communic

Before using script, connect to local NE, or GNE.

First, choose NE, #9-1000:

Second, use command to connect NE :login:"User","Password"

After that you can take any results of NE (independence of command )

Third, use command to disconnect NE :logout; (after that can connect to the next NE)

#9-1000:
:login:"User","Password"

:cm-get-ip

:cm-get-submask

:cm-get-gateway

:cfg-get-nestate

:cfg-get-board;

:cfg-get-outpower:0,0,0;

:cfg-get-inpower:0,0,0;

:alm-get-curdata-ext:0,0,0;

:alm-get-hisdata-ext:0,0,0

:logout;

#9-1001:

:login:"User","Password"

:cm-get-ip

:cm-get-submask

:cm-get-gateway

:cfg-get-nestate

:cfg-get-board;

:cfg-get-outpower:0,0,0;

:cfg-get-inpower:0,0,0;

:alm-get-curdata-ext:0,0,0;

:alm-get-hisdata-ext:0,0,0
:logout;

The results can take from output log file in folder \Navigator \bin\log

script.rar(0.23KB)
erface for technical personal.

resses that meet your search criteria are listed in NE IP Address. You can click the drop-down list to display all the gateway NE IP addresses

following figure is displayed.

(should have connection between NE)

ake some results, very fast.)

ends of topology and communication between NE ( put command in script file in depends on NE type)
all the gateway NE IP addresses, or click Connect to set up a communication connection to the IP address displayed in the NE IP Address t
displayed in the NE IP Address text box.
Hi

How to change the password of the root user for E6616 through Navigator. When we received the E6616 and log

Further can any body share the link to get the command manual for the E6616. thanks
n we received the E6616 and login through Navigator then it does not allow any command and ask to change the password and did not fin
ge the password and did not find even the password change command not work. How to deal with it if we do not have any WEBLCT and N
do not have any WEBLCT and NCE for it and want to use Navigator only.
Select next step ( for example All)

In file script can have several commands (independence of command you can take some results, very fast.)

//#9-1000: is exID-ID

// For login to NE choose correct User and Password data :login:"User","Password"

File have several command and two NE ( it could be more then two NE, it in depends of topology and communic

Before using script, connect to local NE, or GNE.

First, choose NE, #9-1000:

Second, use command to connect NE :login:"User","Password"

After that you can take any results of NE (independence of command )

Third, use command to disconnect NE :logout; (after that can connect to the next NE)

#9-1000:

:login:"User","Password"

:cm-get-ip

:cm-get-submask

:cm-get-gateway
:cfg-get-nestate

:cfg-get-board;

:cfg-get-outpower:0,0,0;

:cfg-get-inpower:0,0,0;

:alm-get-curdata-ext:0,0,0;

:alm-get-hisdata-ext:0,0,0

:logout;

#9-1001:

:login:"User","Password"

:cm-get-ip

:cm-get-submask

:cm-get-gateway

:cfg-get-nestate

:cfg-get-board;

:cfg-get-outpower:0,0,0;

:cfg-get-inpower:0,0,0;

:alm-get-curdata-ext:0,0,0;

:alm-get-hisdata-ext:0,0,0

:logout;
ake some results, very fast.)

ends of topology and communication between NE ( put command in script file in depends on NE type)
Issue Description (Description du problème)
When the engineer tried to upload the NE, he received below error & it couldn't be uploaded.
Lorsque l'ingénieur a essayé de télécharger le NE, il a reçu une erreur ci-dessous et il n'a pas pu ê

Finally the engineer could only initialize the NE & configure it manually.
Enfin, l'ingénieur ne pouvait qu'initialiser le NE et le configurer manuellement.
Alarm Information
No alarm was reported.
Aucune alarme n’a été signalée.
Handling Process
Processus de manipulation
By checking the error message, it was found that the device was not in the running state which is
En vérifiant le message d'erreur, il a été découvert que le périphérique n'était pas dans l'état de fonctionnem
Run the command :cfg-get-nestate on the device using the navigator, the normal output should be
Exécutez la commande :cfg-get-nestate sur l'appareil à l'aide du navigateur, la sortie normale devrait être NE
Run the command :cfg-verify on the device to put it in the running state, then run the command
Exécutez la commande :cfg-verify sur le appareil pour le mettre à l'état d'exécution , puis exécuter la comma
* Pay attention: This's only applied for new installed devices. If there's any service configured on th
* Faites attention : Ceci s'applique uniquement aux nouveaux appareils installés. Si un service est configuré sur

Root Cause (Cause première)

The device was in install state, so it couldn't be uploaded.
L'appareil était en état d'installation, il n'a donc pas pu être téléchargé.

Solution
Change the NE state to running state & try again.
Changez l’état NE en l’état de fonctionnement et essayez à nouveau.

Suggestions
When a new device is installed, confirm the NE state first before configuration.
Lorsqu'un nouveau périphérique est installé, confirmez d'abord l'état NE avant la configuration.
couldn't be uploaded.
dessous et il n'a pas pu être téléchargé.

the running state which is normal for new devices hich come in install state. Devices in install state can't be uploaded to
s dans l'état de fonctionnement qui est normal pour les nouveaux périphériques qui arrivent à l'état d'installation. Les appareils en éta
normal output should be NE-STATE: running, but in this case the output will be NE-STATE: install.
rtie normale devrait être NE-STATE en en cours d'exécution, mais dans ce cas la sortie sera NE-STATE : installer.
, then run the command again :cfg-get-nestate to confirm that the output is changed to NE-STATE: running, and then try
on , puis exécuter la commande à nouveau : cfg-get-nestate pour confirmer que la sortie est modifiée vers NE-STATE : en cours d'exéc
y service configured on the device, running :cfg-verify will cause all services to be down.
un service est configuré sur l'appareil , l'exécution de :cfg-verify entraînera l'arrêt de tous les services .
 ate can't be uploaded to NMS.
allation. Les appareils en état d'installation ne peuvent être téléchargés vers NMS.

TE: running, and then try again to upload.

NE-STATE : en cours d'exécution et puis essayez à nouveau de télécharger.
Issue Description
OSN 1500B
5.36.13.47
Ecxl 3.16
Customer reported that HARD_BAD on GSCC is not clearing even after replacement of GSCC.

OSN1500B
5.36.13.47
Ecxl 3.16
Le client a signalé que HARD_BAD sur GSCC ne s'efface pas même après le remplacement de GSCC.

Alarm Information
The list of alarms present at node were:
TA_LOS & DN_E1AIS on 13 PQ1
R_LOS on ssq1sl1(No fiber connected)
COMMUN_FAIL on 9-EOW
HARD_BAD on 83-GSCC

La liste des alarmes présentes au nœud était :

TA_LOS et DN_E1AIS le 13 PQ1
R_LOS sur ssq1sl1 (Aucune fibre connectée)
COMMUN_FAIL sur 9-EOW
HARD_BAD sur 83-GSCC

Handling Process
The EOW card was given soft and hard reset but the board communication did not resume. In my case the EOW
La carte EOW a fait une réinitialisation logicielle et dure mais la communication avec le conseil n'a pas repris. Dans mon cas,

Root Cause
By following the GOLDEN RULE of HARD_BAD alarm parameters “When the later four parameters are 0xff, then
Upon investigation it was found that the site has an issue that its order wire is not working as well. The alarm tha
The para1 & para2 are meaning less and the remaining parameter shows that there is some Intra-Board Etherne
Now regarding EOW card problem, the possible causes are
1. The board is reset.
2. Board interface to backplane is faulty.
3. The backplane interface to board is faulty.
4. The board may have some other software or hardware discrepancies.
En suivant la RÈGLE D'OR des paramètres d'alarme HARD_BAD « Lorsque les quatre derniers paramètres sont 0xff, alors le
Après enquête , il a découvert que le site a un problème : son fil de commande ne fonctionne pas également. L'alarme qui est a
Les para1 et para2 signifient moins et le paramètre restant montre qu il y a une défaillance de communication Ethernet intra-c
Maintenant en ce qui concerne le problème de carte EOW, les causes possibles sont
1. La carte est réinitialisée.
2. L'interface de la carte avec le fond de panier est défectueuse.
3. L'interface du fond de panier avec la carte est défectueuse.
4. La carte peut présenter d'autres anomalies logicielles ou matérielles.

Suggestions
Null
ent of GSCC.

acement de GSCC.

ot resume. In my case the EOW card interface was faulty and by replacing the EOW board, the COMMUN_FAIL alarm on EOW and hard_ba
onseil n'a pas repris. Dans mon cas, l'interface de la carte EOW était défectueuse et en remplaçant la carte EOW, l'alarme COMMUN_FAIL sur EOW et l'

four parameters are 0xff, then the first parameter shows the slot which is having some problem.” The alarm parameters were (0x09 0xff 0
t working as well. The alarm that appeared on 9-EOW order wire is COMMUN_FAIL with parameters 0x01 0x00 0x03 0xff 0xff.
ere is some Intra-Board Ethernet Communication failure. EOW is an order wire processing board, which is used to provide the order wire p

rniers paramètres sont 0xff, alors le premier paramètre montre l'emplacement qui a un problème ." Les paramètres d'alarme étaient (0x09 0xff 0xff 0xff 0x
ne pas également. L'alarme qui est apparue sur le fil de commande 9-EOW est COMMUN_FAIL avec les paramètres 0x01 0x00 0x03 0xff 0xff.
de communication Ethernet intra-carte . EOW est une carte de traitement des fils de commandes , qui est utilisée pour fournir le téléphone filaire de comm
FAIL alarm on EOW and hard_bad alarm on GSCC were cleared.
me COMMUN_FAIL sur EOW et l'alarme hard_bad sur GSCC ont été effacées.

rm parameters were (0x09 0xff 0xff 0xff 0xff).And thus it was found that there is some problem with 9-EOW and not GSCC.
0x00 0x03 0xff 0xff.
used to provide the order wire phone or transparent transmission interface for the system.

arme étaient (0x09 0xff 0xff 0xff 0xff). Et ain il a découvert qu'il y avait un problème avec 9-EOW et pas GSCC.
x01 0x00 0x03 0xff 0xff.
fournir le téléphone filaire de commandes ou une interface de transmission transparente pour le système.
W and not GSCC.
Huawei New Optix OSN-3500 Configuration
Hello everyone!

I would like to talk about how to configure the new Optix OSN-3500 with a screenshot of each step by iManager

Local Craft Terminal

1- From NE information List press Create.

2- Select the object type of Huawei device series (OSN-3500), then you should set ID, Extended ID, IP which we w
3- After Login by Navigator you can see ID, Extended ID and to get IP use cm-get-ip.
4- Now we can set ID, Extended ID, IP.

5- After successfully adding the node, right click on the node and then select Configuration.
6- Select initialize and configure NE Data then confirm on waring dialog.
7- Now we can see the OSN default boards to add a physical board, click on the query physical boards informatio

8- Now we can see all physical boards.

9- click on finish.
10- for more configuration you can access OSN node NE Explorer.

thanks
uration

nshot of each step by iManager U2000

t ID, Extended ID, IP which we will get by Navigator in next step.

uery physical boards information.
Issue Description
The OSN 1500 starts to has POWER_ABNORMAL alarm in both PIU boards.

Alarm Information
After get the datacollector of the equioment we found that the alarm has the following parameters:

1 POWER_ABNORMAL MJ start 2012-05-03 16:14:14 None 0x01 0x00 0x01

0x00 0xff

11 POWER_ABNORMAL MJ start 2012-05-03 16:14:14 None 0x11 0x00 0x01 0x00 0xff

Handling Process
After analyze the information collected with R&D, we found that the root cause of the alarms may be is the AUX

1. The external power supply may has the under-voltage problem or fluctuates sharply. So need to measure and
If the standard voltage of the input power supply is -48 V, and the measured value should be in the range of -4
If the standard voltage of the input power supply is -60 V, and the measured value should be in the range of -5

2. If confirm the external power supply is normal and stable, check whether there is any pin bent in slot for AUX b

3. If AUX board and its slot are normal, check GSCC boards:
(1). plug-out the standby GSCC, 82-GSCC(4-CXL1);[PAY ATTENTION: plug-out this board could cause service affe

(2). If alarm exist, re-insert 82-GSCC and switch GSCC, then plug-out current standby GSCC, 83-GSCC(5-CXL1); [PA

4. If alarm still exist after plug-out both two GSCCs, check PIU boards: plug-out one PIU, check whether correspon

After review the possible causes, we found that the root cause of the alarm was the AUX board, after replace the

Root Cause
The customer needs to know the root cause ot this alarm ands also knows if the PIU baords are OK, also the cust

Suggestions
owing parameters:

x01 0x00 0xff

of the alarms may be is the AUX board, GSCC board or PIU board. With following steps we can determinate which board is the root cause:

harply. So need to measure and confirm the external power supply for this OSN1500 is normal and stable.
ue should be in the range of -41 V to -60 V;
ue should be in the range of -51 V to -72 V;

e is any pin bent in slot for AUX board; if no, replace AUX;

board could cause service affection] check whether POWER_ABNORMAL alarm disappear;

dby GSCC, 83-GSCC(5-CXL1); [PAY ATTENTION: plug-out this board could cause service affection] check whether POWER_ABNORMAL ala

ne PIU, check whether corresponding POWER_ABNORMAL alarm disappear, if yes, replace the PIU; and then plug-out another PIU with sam

he AUX board, after replace the board the issue was solve.

PIU baords are OK, also the customer informs that the same issue appears in another OSN 1500.
e which board is the root cause:

hether POWER_ABNORMAL alarm disappear;

en plug-out another PIU with same way;

Dear friend！

Please first enter the ECC link management page of the upper-end NE.

As shown below:

Check whether the NE is displayed. If the information can be queried, create a non-gateway NE on the NMS. The

Thank you!
n-gateway NE on the NMS. The gateway NE of the upstream NE functions as the forwarding NE of control information.
information.
We have a big Huawei MSTP network that works mainly in OSN 7500. we still use the U2000 management progra

I was making the swap for E1&E3 services using the (Service Configuration) when I the NE gave me a reply:

The NE has the cross-connect board (UXCSA)

I went to check the Cross-Connect Board low order cross-connect usage from the path

Inventory > SDH_Report > Lower Order Cross-Connections Statistic Report

There I could find the capacity & the usage of the board and I found that we used all available 128 VC4 used for l

I discovered that we have a shortage in the low order cross-connection traffic means the traffic in VC12 & VC3 or

And because I had a traffic swap, I needed a temporary solution.

1. The temporary solution

I looked for the VC12 & VC3 services (passthrough) going from a Line board to another line board in a group of VC

I deleted these services and recreate passthrough service in VC4 level (that will cause cut for deleted services for

I could reduce the number of used low order cross-connect with 14 * VC4 and then, I went to check the Cross-Co

Inventory > SDH_Report > Lower Order Cross-Connections Statistic Report and it was as in the following picture :

Then I could make the service swap.

2. The permeant solution was by replacing the Cross-connect board with other which has bigger capacity.

Available boards and their capabilities.

The old board was UXCSA, So we change the board with the type IXCSA to have 4 times the capacity of the UXCS

When changing the board with the higher capacity board, you need only to replace the standby board than wait
the U2000 management program.

I the NE gave me a reply:

 all available 128 VC4 used for low order services, as in the following picture:

ans the traffic in VC12 & VC3 order, While we still have a big capacity for High order cross-connection.

other line board in a group of VC12 or VC3, I found many services going in consequence as in the following picture.

ause cut for deleted services for seconds ) then the service will be as in the following picture

en, I went to check the Cross-Connect Board low order cross-connect usage from the path

was as in the following picture :

hich has bigger capacity.

times the capacity of the UXCSA in the low order services cross-connect.

ce the standby board than wait until it works normally then replace the main.
COMMUN_FAIL and BD_STATUS alarmsreported onmain and extended subarcks due to a locked AUX board

7月 25, 2018 vipvincent

Issue Description

over an Huawei OSN 3500 that have extended subrack, Alarms of BD_STATUS appear over the boards(PQ1, XCE

Main subrack:

Extended subrack:
Alarm Information

BD_STATUS(Extended subrack)
PQ1s
XCEs
PIUs
FANs

COMMUN_FAIL(Main subrack)
SXCSBs
SL64s
EFS0s
EGS4s
SLQ16s

the AUX board in both subracks did not have alarms.

Handling Process
in general for a problem with the AUX board in NEs with extended subrack, the handling procedure is:

1. Prepare two spare parts of AUX board;

2. Run the command cfg-get-oamport:ALL， to confirm EXT port is enable;
3. Check whether the cable interconnected with AUX board, EXT port of the main subrack and the extended su
4. Hard reset AUX board in the extended subrack;
5. Hard reset AUX board in the main subrack;
6. Replace AUX board in the extended subrack;
7. Replace AUX board in the main subrack;

in our case i run the command and confirm that the EXT port was enable, the cable was OK and connected corr

Root Cause

in cases like this, the most probable cause of this problem is the AUX board. it was necesary to check if was the A
the AUX board is take as the main point of failure in this case because it realizes communication between boards

The parameters of the COMMUN_FAIL alarms are 0x01 0x00 0x03 0xff 0xff 0xff 0xff.
According to the analysis of the alarm parameter, the COMMUN_FAIL alarm is reported becauseinter-board Ethe

Suggestions

in problems like this. it is necessary to check the AUX boards of the subracks.
due to a locked AUX board

ppear over the boards(PQ1, XCE, PIU and FAN) of the extended subrack, and COMMUN_FAIL(SXCSB, SL64,EFS0,EGS4,SLQ16) over the main
andling procedure is:

in subrack and the extended subrack, is connected correctly and well;

ble was OK and connected correctly and well; with the Hard reset over the AUX board in the extended subrack the problem persisted.

s necesary to check if was the AUX of the main or the Extended Subrack.
ommunication between boards in the subrack.

ported becauseinter-board Ethernet communication is abnormal.

EFS0,EGS4,SLQ16) over the main Subarack, like shows the next pictures:
subrack the problem persisted. but when we did a Hard reset over the AUX board in the main subrack, all the alarms dissapear. this boa
l the alarms dissapear. this board was locked.
Huawei New Optix OSN-3500 Configuration

1. From NE information List press Create.

2. Select the object type of Huawei device series (OSN-3500), then you should set ID, Extended ID, IP which we
3. After Login by Navigator you can see ID, Extended ID and to get IP use cm-get-ip.
et ID, Extended ID, IP which we will get by Navigator in next step.
 Convert a non-Gateway SDH node to

Friends and forum members, I want to share with you how to convert a non-Gateway network e

If we start from a subnet in the process of expansion, the increase in the network elements mea

The administrator in the management system must perform the following operations.
1-Right click on the node you want to convert in GW / NE Explorer
2-Access
Communicat
ion /
Communicat
ion
Parameters

In general,
the nodes
come with
an address
of 129.9.0.0
with mask
255.255.0.0,
in the
previous
figure the
new IP
address,
subnet mask
and default
Gateway are
displayed. It
is necessary
that the
addressing
established
in the node
reaches the
managemen
t layer
(network
servers).
After
changing
the IP of the
node we
proceed to
check the
connectivity
of the node
to the
network
servers, for
this we get
on top of
the node
and ping the
servers.
In the
highlighted
bar under IP
Address the
IP address
of the server
is put and it
is checked
that there is
connectivity
, in case of
connectivity
the
conditions
are created
to convert
the node
into GW,
therefore
the
configuratio
ns in the
DCN are
made
successfully
and we can
only modify
the
configuratio
n in the
managemen
t plane so
that the
node is
finally seen
as a
gateway.

Conversion of the node to GW.

From the U2000 client you can access the Administration tab and then access DCN Managemen

After the next view we access the NE view to find the element that we are going to convert into
After filtering the network element that we are going to convert the GW, we right click on the ro
Once the Change to GNE option is selected, we can see the same configuration that had been m

Once the changes are applied, the following is displayed, you can accept the message that is dis
Finally, the successful operation message is displayed on the U2000 client.

Then we access Administration / DCN Management / NE and finally GNE and filter the network e
After giving Ok in the U2000 client, the following image will be displayed. Resulting in that the m

Note:
OSN
500/1500/2
500/3500/7
500. It is not
advisable to
do it on the
Optix
M100 /
M500 nodes
as well as
the Optix
155 / 622H,
in this case
it is
recommend
ed to use
the tools
provided by
Huawei as is
the case
with the
Optix
Navigator
and make
the changes
at the
command
syntax level,
if not
available. of
the
mentioned
tool make
use of a
client server
version
provided by
SDH node to a Gateway from the Management system

rt a non-Gateway network element into a Gateway. The non-Gateway node is managed in-band or by the data communication channe

n the network elements means that the NE-GWs will have to process requests from the non-GW network elements through the D1-D3

owing operations.
en access DCN Management.

we are going to convert into GW.

GW, we right click on the row where the NE appears and we give the option Change to GNE.
nfiguration that had been made in the node beforehand to convert it into a GW in terms of IP addressing, the connection mode we se

cept the message that is displayed below because in advance you guaranteed communication of the node with the management layer
GNE and filter the network element converted to GNE.
ayed. Resulting in that the migration was successful. In addition, in the main view of the U2000 client, we can see the GW identificatio
system

data communication channels DCC (Data Communication Channel) of the SDH frame, instead the new Gateway (GW) network elemen

elements through the D1-D3 bytes of the SDH frame, causing delay or slow communication to and from the management system, so it
the connection mode we set the Common value, this brings with it the port number it changes to the value 1400 once the message sh

with the management layer and in extreme cases you can reverse the process.
can see the GW identification of the network element (G in the upper part).
eway (GW) network element will communicate out-of-band ESC (Communication Channel Electrical) this time through the implicit eth

e management system, so it is necessary to add network elements such as GW to improve the communication of the network element
e 1400 once the message shown below is accepted.
me through the implicit ethernet port of the management purpose node connected to the DCN (data communication network) netwo

tion of the network elements in the management system.

munication network) network architecture to reach the management layer or network servers.
 How to Change the NE ID on U2000
Hello, everyone.

Today, I'd like to share with you how to change the NE ID.

The ECC protocol uses the NE ID as the unique identifier of an NE. Hence, you need to assign a unique N

1.In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function Tree.

2.Click Modify NE ID. The Modify NE ID dialog box is displayed.

3.Set New ID and New Extended ID. Click OK.

4.Click OK in the warning dialog box.

Changing an NE ID may cause NE communication interruption and NE restart.

After an NE ID is changed, equipment configurations such as protection and fiber connection may be un
ou need to assign a unique NE ID to each NE when planning a network. Any conflict of NE IDs will cause an ECC route conflict a

e from the Function Tree.

d fiber connection may be unavailable. Therefore, it is recommended that you change NE IDs before the equipment is configur
cause an ECC route conflict and the failure on the NMS to manage certain NEs. During commissioning or capacity expansion, y
ore the equipment is configured.
ning or capacity expansion, you can adjust the existing network plan or change NE IDs on the NMS if required.
 How to add a network element in the i
and
members
of the
forum, I
want to
share with
you how
to add a
network
element
using the
iManagem
ent DC
V200R011
C00T tool
for
upgrade
purposes,
it is true
that
Huawei
does not
recommen
d it,
instead
Huawei
suggests
using
other tools
such as
U2000
The first
thing that
they must
guarantee
for its
correct
operation
is that
there are
no spaces
in the files
that make
up the
IManagem
ent DC
V200R011
C00T,
otherwise
they will
not work.
you must
make sure
that the
files that
make up
the
IManagem
ent DC
V200R011
C00T are
in the
same
directory.
Once the
executabl
e
dc_Stand
Alone has
been
executed,
the
following
window
will be
displayed,
where you
must
check the
basic
settings
System->
ftp

The figure above shows the main view of iManagement DC V200R011C00T

The figure above shows the ftp configuration option where we can observe the IP address where th
The top
figure shows
the
directory
where the
iManageme
nt DC
V200R011C
00T files
should be
housed, it is
recommend
ed that the
software to
update the
nodes be in
the
directory
shown as an
example C: /
upgrade.
Once this is
seen, we go
to the main
window and
by right
clicking on
the main
view, we
create the
network
element
that will be
updated. In
the next
view, the
above is
displayed.
In the top
view it is
explained
how a
network
element is
created.

Extended
ID-> 9
(Usually)

NE ID->
Node ID
(Unique in
the
network)

Gateway
Type-> IP
Gateway
(Set IP
Gateway)

NE IP / LAN / Gateway IP-> If the node is not a Gateway, put the IP address of the Gate
Connection Mode-> Security Mode, it is set to Common mode and automatically the p

User Name-> We insert user and password of the node to update.

Once the aforementioned operations have been carried out, the node will be ready to

So far a guide for the management of the iManagement DC V200R011C00T tool focuse
lement in the iManagement DC V200R011C00T platform for up
observe the IP address where the iManagement DC V200R011C00T is running.
y, put the IP address of the Gateway to which it belongs, you on top of the node from a U2000 client can give the node that is going to upg
n mode and automatically the port changes to 1400.

e to update.

d out, the node will be ready to update and will be displayed in the main window.

nt DC V200R011C00T tool focused on the process of lifting the network elements for the upgrade process. Any questions in this regard can
platform for upgrade purposes.
ive the node that is going to upgrade right click on the NE and inside Attribute shows us the IP address of the Gateway to which it belongs
Any questions in this regard can contact me I will always be attentive to any questions from you.
he Gateway to which it belongs (We take as an example a DWDM node, if it is an SDH node, right click on the node and Properties).
he node and Properties).
 How to set the DCC byte on WDM

Hello everyone!

This time, I will share with you

how to set the DCC byte on
WDM NE.

Overview

A DCC is used to transmit OAM

information between NEs. The
DCC defined for Huawei NG
WDM products uses the D1 to
D12 overhead bytes in a Huawei
proprietary frame structure to
transmit OAM information.
Configuration Procedure

1. Open the NE Explorer and

select the NE, then click
Communication, and DCC
Management, in the right DCC
management tab, you can set
the DCC channel like below from
Enable to Disable. Attention:
Setting a DCC channel to enable
or disable also applies to all other
DCC channels on the same port.
To disable only a single channel,
use the Delete button instead.
2. You can delete the signal DCC
channel at a port by select the
DCC channel and Click the Delete
button like below:

And you can add it back by

Create Button:
Please note that the above
operation applies to the
OSN3800/OSN6800/OSN8800.
That's all, I welcome everyone to
leave a message and exchange in
the comment area!

Thank you！
C byte on WDM NE
 Binding an SDH Trail to a Port in SDH (OSN75

In my previous articles Configuring SDH Trail VC3 SNCP Service for 1+1 Protection (Manual Creation) and Config

To complete a service, the SDH trail created between service boards of two nodes we need to bind the SDH trail

1-Ethernet Line Service

2-Ethernet LAN Service

The difference between the Ethernet Line service and Ethernet LAN service in simple words is that in a Line serv

This article only covers Ethernet Line Service configuration.

Before we start configuration, we need to understand that to bind a service to a port three things are required.

1-Port on which the service needs to be dropped.

2-The configured SDH trail.

3-A VCTRUNK

1-Checking a Port for Service termination:

To check the port status click on the service board on which the SDH trail is terminated > Ethernet Configuration
 Figure 1: NE Explorer Window of the Node

Following window will open as can be seen in Figure 2.

Figure 2: NE Interface Managem

In Figure 2 Click on the External port radio button. The following window will open showing all the ports and the
 Figure 3: Ports Status window

in Figure 3 we can see that all the ports are disabled therefore we can select any port for the service drop. Here l

2-The configured SDH trail

The SDH trails are configured depending on the bandwidth requirement. One important thing to note here is the

Here we assume that the service level is VC3 and the terminating timeslot details are VC4-1-VC3-1 (which means

3-Choosing a VCTrunk
To check the total no of VC trunks available in a card just double-click on the card and it will show the total no of

Figure 4: Showing VCTRUNKs of the board

From the above figure, we can see that there is a total of 24 VCTRUNK from VCTRUNK1 to VCTRUNK24. The grey

An important thing to note is that you cannot randomly bind any VCTRUNK with any timeslot and it varies with th

Here for the board N5EFS0 following are the limitations.

*It supports only VC-3 and VC-12 levels of timeslot binding between the SDH trail and port so if you have config
*Trunks cannot be randomly bounded to any VC-4/VC-3 or VC-12 timeslot. VCTRUNK1 to VCTRUNK12 can be us
*The VC-12 level of service it can be only configured in VC4-4 and VC4-8 timeslots rest VC4s can only be utilized
Note: There are 8 VC4s in the N5EFS0 board.

Since we have configured the SDH trail on VC4-1-VC3-1 on the board we can use VCTRUNK1 to VCTRUNK12 let’s

After all the important parameters are decided let’s bind the SDH trail to the port. Follow the same procedure sh

Figure 5: Showing Ethernet Line Interface Window

Click on the New button available at the bottom right of the window in Figure 5. Following window
 Figure 6: Ethernet Line Service Creation window

In Figure 6 click on the Source Port and select PORT1 from the list, in Sink Port select VCTRUNK1 and enter VLAN
 Figure 7: Bound Path Configuration

In Figure 7 change the Level to VC3-xv, Service Direction should be Bidirectional then in Available Resources clic

Figure 8: Bound Path Configuration with timeslot details

Once the required timeslot has been selected click on Apply then click on OK it will take you to Figure 6 with bou
 Figure 9: Ethernet Line Service Creation window with details

Since all the details have been entered just click on Apply then OK. The SDH trail has been bounded to PORT-1 w

Figure 10: Showing the Configured Port wit

Since we have bounded the Port with the service at one end of the service the same operation needs to be carrie

Reference,
HedEx
in SDH (OSN7500) Nodes

n (Manual Creation) and Configuring an SDH Trail (VC12 Service) Over an MSP Ring, I have explained different ways via which an SDH tra

s we need to bind the SDH trail to a port and pass through a VLAN so that the data can flow between the nodes. There are two ways by wh

mple words is that in a Line service, an SDH trail can be bound to a single port and single trunk while in Ethernet Line Service the same SDH

port three things are required.

ation:
nated > Ethernet Configuration > Ethernet Interface Management to select a port on which we can terminate the service as seen in Figur
plorer Window of the Node

gure 2: NE Interface Management window

en showing all the ports and their Enabled/Disabled status, as seen in Figure 3.
gure 3: Ports Status window

port for the service drop. Here let’s take 19-ETF8 Port-1 (ETF8 is the sub-board of N5EFS0).

portant thing to note here is the VC4/VC3 or VC-12 timeslot details of the card on which the SDH trail is ending on the board.

are VC4-1-VC3-1 (which means the first VC-3 of the VC4-1 timeslot).
 and it will show the total no of VCTRUNKS available on the board as can be seen in Figure 4.

RUNK1 to VCTRUNK24. The grey color highlight means that they are not occupied and can be used.

any timeslot and it varies with the service boards as well.

ail and port so if you have configured a VC-4 level service you can’t bind it to the port instead create a 3*VC-3 level service.
RUNK1 to VCTRUNK12 can be used for VC4-1 to VC4-4 timeslots while VCTRUNK13 to VCTRUNK24 can be used for VC4-5 to VC4-8 timeslo
ots rest VC4s can only be utilized for VC-3 services.
 VCTRUNK1 to VCTRUNK12 let’s select VCTRUNK1.

. Follow the same procedure shared in Figures 1 and 2 then click on Ethernet Service > Ethernet Line Service available at the bottom left

hernet Line Interface Window

w in Figure 5. Following window will pop up as can be seen in Figure 6.

elect VCTRUNK1 and enter VLAN 123 then click on the Configuration button available at the bottom of the window to select the required V
then in Available Resources click on VC4-1, and in Available timeslots select VC3-1 then click on the>> button as shown in Figure 8.

timeslot details

ill take you to Figure 6 with bound path details visible as shown in Figure 9.
has been bounded to PORT-1 with VLAN-123 as can be seen in Figure 10.

howing the Configured Port with timeslot details

me operation needs to be carried on the other end of the SDH service trail (2nd SDH Node) to complete the circuit and allow the VLAN to
erent ways via which an SDH trail can be created.

odes. There are two ways by which we can bind the service to the port and assign VLAN to it. These methods are

ernet Line Service the same SDH trail can be bounded to multiple ports, or multiple trunks depending upon the requirement. So, if there is

nate the service as seen in Figure 1.

ding on the board.
C-3 level service.
used for VC4-5 to VC4-8 timeslots.
ice available at the bottom left of the window. The following window will open as shown in Figure 5.
window to select the required VC3 details i.e., VC4-1-VC3-1. The following window will pop up as can be seen in Figure 7.
tton as shown in Figure 8.
e circuit and allow the VLAN to pass through.
n the requirement. So, if there is a service that needs to be passed or dropped to multiple ports or trunks then it is configured in Ethernet L
een in Figure 7.
hen it is configured in Ethernet LAN service while if the service needs to be dropped on a single port, we configure it on Ethernet Line serv
onfigure it on Ethernet Line service.
Configuring SDH Trail VC3 SNCP Service for 1+
Created: 2023-11-28 13:37:20Latest reply: 2024-01-14 08:42:09
9954 40 0
0
View the author0#

The purpose of this article is to provide users with an understanding of configuring VC3 SNCP servic

After reading this article readers will be able to understand the following.

1. What is SNCP service?

2. When to configure an SNCP service?
3. How to Configure an SNCP VC3 Service

The article covers the example of VC3 service but the same can be applied for configuration of VC4

Sub-Network Connection Protection (SNCP):

SNCP or sub-network connection protection is a type of protection scheme implemented for provid

In this type of protection scheme working and protection time slots are configured on different fibe

SNCP services are usually configured in access SDH rings having two directions. In this way, one dire
 Figure1: Access Ring for SNCP Creation betwe

Pasted below is the complete step-by-step process for 1*VC3 SNCP service creation between Node

Step 1: Checking Available timeslots on the Service Board:

The very first thing to do is identify the service board on which the service will be terminating. As st

Node A Slot-17-N3EFS4
Node D slot 4-N3EFS4.

As boards are identified it’s time to check the available VC3 slots on the boards. For checking availa
Click on Create in Figure 2 then another window will pop up as shown in Figure 3.

Figure 3: Time slot selection window

Here select the Level to VC3, Direction to Bidirectional. After this click on the … three dots at the end of the sourc

Figure 4: Showing time slots of slot Node A-17-N3EFS4

Here we can see that in VC4-1, 1st VC3 is already utilized so we will use 2nd VC3 of the VC4-1 for our service con

Note: It is always a good practice to use the already utilized higher-order time slots for the same order of cross-c

Since we have selected the time slot click on cancel as the service will be configured at the end. The same proced
 Following the same procedure as shared above in Figure 2-4 VC4-1 2nd VC3 is selected. Table-1 pasted below sho

Time Slot
Node Name Slot Detail (VC3)
Slot-17-
Node A N3EFS4 VC4-1 VC3-2
Slot-3-
Node D N3EFS4 VC4-1 VC3-2

Table 1: Representing SNCP drop boards time slots

Step 2: Checking Line boards for all pass-through and SNCP nodes:

The 2nd step is to check and list down all the line boards of Node A, B, C, and D which are part of the access ring

For example, referencing Figure 1 we need to check the line boards of Node A which are connecting with Node B

To check the board details, click on the fiber between both the nodes then click on properties. A window will pop
 Figure 5: Showing line boards of link Node A---Node B

Similarly record all the links for the entire access ring from Node A to Node E. Tabel 2 represents all the line boar

East West
Direction Direction
Node ID Slot Detail Slot Detail

Node A 7-N4SL64-1 12-N4SL64-1

Node B 7-N4SL64-1 12-N4SL64-1

Node C 7-N4SL64-1 12-N4SL64-1

Node D 7-N4SL64-1 12-N4SL64-1

Node E 7-N4SL64-1 12-N4SL64-1

Node F 7-N4SL64-1 12-N4SL64-1

Table 2: Representing Time slots of line boards

Note: Here the connectivity between nodes is linked to Node A-12-N4SL61-1(west)-----Node B-7-N4SL64-1(west)

Step 3: Checking VC3 time slots for all pass-through and SNCP nodes:

The third step is to check and record the time slots for all the line boards represented in Table 2.

Note: It’s a good practice to configure the same time slots in both directions for all the nodes for example if we c
 Now follow the same procedure shared in step 1 from Figure 2 to Figure 4 for time slot selection and record them

Table 3 represents the line boards for all the nodes along with the time slots for service configuration.

East West
Direction Time Slot Direction Time Slot
Node ID Slot Detail (VC3) Slot Detail (VC3)

Node A 7-N4SL64-1 VC4-9 VC3-2 12-N4SL64-1 VC4-9 VC3-2

Node B 7-N4SL64-1 VC4-9 VC3-2 12-N4SL64-1 VC4-9 VC3-2

Node C 7-N4SL64-1 VC4-9 VC3-2 12-N4SL64-1 VC4-9 VC3-2

Node D 7-N4SL64-1 VC4-9 VC3-2 12-N4SL64-1 VC4-9 VC3-2

Node E 7-N4SL64-1 VC4-9 VC3-2 12-N4SL64-1 VC4-9 VC3-2

Node F 7-N4SL64-1 VC4-9 VC3-2 12-N4SL64-1 VC4-9 VC3-2

Table 3: Time slots and Line boards of all nodes

Step 4: SNCP and pass through service configuration:

Step 4 comprises two types of service configuration one is pass and the second is SNCP service creation.

Pass-through service needs to be configured on all the nodes from where service is only passing but not dropping

For creating pass through cross connection follow step 1 from Figure 2 to Figure 4 to fill the source and sink time
Figure 6: Pass through cross connection for Node B

Similarly, pass-through cross-connections need to be made on Nodes C, E, and F.

After pass-through cross-connections are made it's time to create SNCP cross-connections on Node A and Node D

For SNCP service creation on Node A follow step 1 until you reach Figure 2. In Figure 2 click on Create SNCP Serv
 Figure 7: SNCP Service Creation window

Here in Figure 7 check the following attributes:

Service Type should be SNCP

Level VC3
Direction Bidirectional
Revertive Mode can be either Revertive or Non-Revertive (we are setting it to non-revertive)
WTR time (only set if the mode is revertive)

Then in the Working Service window at the top select the service board and time slot which in the case of Node

On the bottom of the Working Service window is the working direction line board. If you want Node A---Node D

After the service board along with the working and protection line boards are selected click on Apply and then cl

Similarly configure SNCP service on Node D.

Step 5: Running SDH Trail for Service Visibility:

After the cross-connection is completed it's time for creating an SDH trail for service visibility. For running the SD
 Figure 8: NCE-T Window

The following window will open as shown in figure 9. Click on Search for SDH Trail.

Figure 9: SDH Trail Window

After clicking on Search for SDH trail NCE-T will try to find all the undiscovered trails on the NMS. Click on Next u
 Figure 10: SDH Search Trail Window

After the SDH trail search is completed the service configuration is completed and the trail will be visible. The tra

Reference,

HedEx
Figure 11: Checking Configured SDH Trail
P Service for 1+1 Protection (Manual Creation)Highlighted

of configuring VC3 SNCP service for working and backup protection paths.

pplied for configuration of VC4 or VC12 services as well.

scheme implemented for providing services a dual path (working and protection) ensuring service protection.

are configured on different fiber paths. In case any interruption is observed on the working path the service will switch to protection.

directions. In this way, one direction works as an active and the other works as protection.
s Ring for SNCP Creation between Node A and D

service creation between Node A Slot-17-N3EFS4 and Node D Slot 3-N3EFS4.

ervice will be terminating. As stated above following are the service boards of Node A and Node D on which the service needs to be dropp

the boards. For checking available VC3 slots Node A Slot-17-N3EFS4 click on NE > NE Explorer then Configuration > SDH/PDH Service Ma
Figure 2: SDH/PDH Service Management Window
hree dots at the end of the source slot. Another window will pop up showing time slots available on all the cards of the node. From the ava

s of slot Node A-17-N3EFS4

of the VC4-1 for our service configuration.

ts for the same order of cross-connection as we did above.

red at the end. The same procedure is to be followed for Node D slot 4-N3EFS4 VC3 time slot selection.
 ected. Table-1 pasted below shows the time slots along with card details for both Node A and Node D where SNCP is to be configured.

which are part of the access ring on which we need to configure service.

hich are connecting with Node B and Node F similarly at Node B we need to check the line boards that are connecting with Node A and No

n properties. A window will pop up showing the board details as shown in Figure 5 for Node A—Node B.
bel 2 represents all the line boards categorized in east and west direction.

t)-----Node B-7-N4SL64-1(west) and so on. The east direction of 1st node links with the west direction of 2nd node.

nted in Table 2.

ll the nodes for example if we choose Node A 7-N4SL64-1 VC4-5—VC3(2) then for the rest of the boards if the same time slot is available t
e slot selection and record them.

ervice configuration.

SNCP service creation.

is only passing but not dropping these nodes are B, C, E, and F.

4 to fill the source and sink time slot according to Table 3 then click on Apply then click on OK. An example is pasted below in Figure 6 for
nnections on Node A and Node D.

ure 2 click on Create SNCP Service following window will pop up as shown in Figure 7.
on-revertive)

slot which in the case of Node A is 17-N3EFS4 and the time slot is VC4-1 VC3-2.

d. If you want Node A---Node D service via Node E and F to be working direction then choose the line board of Node A which is facing Nod

ected click on Apply and then click on OK.

ice visibility. For running the SDH Trail, at the top of the NCE-T NMS click on Service then on the View tab click on SDH Trail as shown in F
SDH Trail Window

ails on the NMS. Click on Next until the search is completed. You may need to click Next multiple times until the procedure is completed.
d the trail will be visible. The trail can be checked via right-clicking on either service boards like Node A Slot-17-N3EFS4 or Node D Slot 4-N
king Configured SDH Trail
Highlighted

e will switch to protection.

ch the service needs to be dropped.

uration > SDH/PDH Service Management. The following window will open as shown in Figure 2.
cards of the node. From the available boards click on Slot 17-N3EFS4. Then all the available VC4s of the board and VC3 time slots will be vi
re SNCP is to be configured.

connecting with Node A and Node C. In this way, we need to check the line boards of all the nodes.
the same time slot is available then choose that one as it would make it easy to configure and would help in troubleshooting as well.
is pasted below in Figure 6 for Node B.
d of Node A which is facing Node F similarly under the Protection Service window choose the line board of Node A which is facing Node B

click on SDH Trail as shown in Figure 8.

til the procedure is completed.
t-17-N3EFS4 or Node D Slot 4-N3EFS4 and choosing Browse SDH Trails as shown in Figure 11.
ard and VC3 time slots will be visible as shown in Figure 4.
in troubleshooting as well.
f Node A which is facing Node B as the Node A---Node D service via Node B and Node C will be the protection service direction.
on service direction.
 Configuring an SDH Trail (VC12 Se
This article aims to provide readers with an understanding and command over configuring an SDH trail service. T

After reading this article users will be able to understand

1. What is MSP protection

2. Configuring an SDH trail

Before starting the configuration of the SDH trail let’s first understand what is an MSP protection briefly.

MSP (Multiplex Section Protection):

MSP is a type of protection scheme implemented on a ring level. In this type of protection scheme services are co

For example, if an MSP Ring is configured on STM-64 boards. Then only VC4-1---VC4-32 will be utilized for the co
 Figure 1: MSP Ring showing working and protection time slots

Consider Figure 1 for the configuration of VC12 service between Node A to Node C. From Figure 1 we can see tha

1-Identify Line boards for Nodes A, B, and Node C:

The very first step is to identify the line cards that are connecting the node on which the MSP ring is configured a

To check the line card details just right-click on the fiber > Properties. Then check the line boards. Pasted below i
 Figure 2: Showing line boards

Similarly, check the line boards for link Node B----Node C. Pasted below is the table for both links.

1st Node 2nd Node

Node Name Line board Node Name Line board

Node A 7-N4SL64-1 Node B 12-N4SL64-1

Node B 7-N4SL64-1 Node C 13-N4SL64-1

Table 1: Connecting line boards for Links

2-Identify Service Drop boards at Nodes A and Node C:

After the identification of line boards, 2nd step is to identify the service drop boards i.e., the boards on which the
 Time Slot
Node Name Line board (VC12 Level)
Node A 2-N2PQ1 45
5-N1SLT1- 1
Node C Port-1

Table 2: Showing drop boards and time slots

3-Identifying time slots (VC12 level) on line boards at Node A, B, and Node C:

After the identification of line boards, service drop boards along with time slots at service drop boards it is time t

Line boards are the two ends of the fiber link. If a time slot is empty at one end it should also be vacant at the oth

To check the time slot at Node A -7-N4SL64-1 click on Node A > NE Explorer. The following window will open as
 Figure 3: NE Explorer Window of Node A

Configuring an SDH Trail (VC12 Service) Over an MS

Figure 4: Service Configuration Window Node A

Now click on the Create button available at the bottom of the window. The following window will pop up as show
 Figure 5: Create SDH/PDH Service Window

Here change the Level to VC12 as we want to create a VC12 service for VC3 and VC4 services the levels need to b

When you click on the board 7-N4SL64, then select Port 1. All the VC4 time slots will be available. Try to select th

Here in Figure 6, we can see that the 2nd VC12 of the 1st VC4 (out of 64 VC4) is empty so we will choose this for
 Figure 6: Time slot window of Node A
Now close the window as we will be configuring the cross-connections at the end after all the time slots are final

Here we have seen that Node-A-7-N4SL64-1- VC4-1 (VC12-2) is empty similarly Node B-12-N4SL64-1-- VC4-1 (VC

Follow the same procedure from Figure 3 to Figure 6 for identification of time slots for link Node B-7-N4SL64-1--

Table 3 shows the time slots for both links i.e., Node A -7-N4SL64-1-----------Node B-12-N4SL64-1 and 1 Node B -7

1st Node 2nd Node

Time Slot Time Slot

Node Name Line board (VC12 Level) Node Name Line board (VC12 Level)
VC4-1--- VC4-1---
Node A 7-N4SL64-1 VC12 -2 Node B 12-N4SL64-1 VC12 -2
 VC4-1--- VC4-1---
Node B 7-N4SL64-1 VC12 -53 Node C 13-N4SL64-1 VC12 -53

Table 3: Available VC12 time slots for configuration

4-Service Configuration:

Since we
have
selected all
the time
slots for
configuratio
n. It's time
to configure
services.
Table 4
shows all
the
configuratio
ns (cross-
connection)
that we
need to
make at
Node A,
Node B, and
Node C.

Cross Source Time Sink Time

Connection Source slot (VC12 Slot (VC12
Node Board Level) Sink Board Level)
VC4-1---
Node A 2-N2PQ1 VC12-45 7-N4SL64-1 VC12 -2
VC4-1--- VC4-1---
Node B 12-N4SL64-1 VC12 -2 7-N4SL64-1 VC12 -53
 VC4-1---
Node C 13-N4SL64-1 VC12 -53 5-N1SLT1-1 VC12-1

Table 4: Cross Connection Time Slots on all nodes

Sink and source boards are replaceable which means the boards shown in Table 4 in Source can be utilized in the

Now configure cross connections w.r.t to the above table 4. For making cross connections follow the steps share
 Figure 7: Cross Connection at Node A

Similarly, configure cross-connections at Node B and Node C. When all the cross-connections are configured it's ti

For running the SDH Trail, at the top of the NCE-T NMS click on Service then on the View tab click on SDH Trail a

Figure 8: NCE-T Window

The following window will open as shown in figure 9. Click on Search for SDH Trail.
 Figure 9: SDH Trail Window

After clicking on Search for SDH trail NCE-T will try to find all the undiscovered trails on the NMS. Click on Next u
 Figure 10: SDH Search Trail Window

After the SDH trail search is completed the service configuration is completed and the trail will be visible. The tra

Figure 11: Checking Configured SDH Trail

Reference,

HedEx
H Trail (VC12 Service) Over an MSP Ring
nfiguring an SDH trail service. This article covers an example of VC12 service configured over MSP but V3 and VC4 services are also configu

MSP protection briefly.

rotection scheme services are configured on ½ of the available resources while the rest of the ½ resources are reserved for protection.

VC4-32 will be utilized for the configuration of services. Rest VC4-33----VC4-64 will be utilized by the protection scheme itself in case of sign
C. From Figure 1 we can see that there are two paths available for service configuration either Node A to Node C via Node B or Node A to

ich the MSP ring is configured already.

k the line boards. Pasted below is a picture of line boards connecting Node A---Node B.
le for both links.

rds i.e., the boards on which the service will be terminating. Usually, these are the ports that are connected with the client end devices. Fo
t service drop boards it is time to identify the time slots at line boards for the links shown in Table 1.

should also be vacant at the other end. Consider Table 1 Node A - 7-N4SL64-1-----------Node B-12-N4SL64-1 is a fiber link so if a time slot a

following window will open as shown in Figure 3.

xplorer Window of Node A

ce) Over an MSP Ring

Window Node A

wing window will pop up as shown in Figure 5.

VC4 services the levels need to be accordingly. Direction should be Bidirectional. In the source slot click on the … dots another window wil

will be available. Try to select that VC-4 time slot on which VC12 is already configured if possible so a new VC4 with no VC12 configured tim

mpty so we will choose this for configuration. The reason for choosing the first VC4 is that the 1st VC12 of this VC4 is already utilized as its
 slot window of Node A
after all the time slots are finalized.

Node B-12-N4SL64-1-- VC4-1 (VC12-2) should be empty as these are the two-line boars of the same fiber link. It can be verified by followin

ts for link Node B-7-N4SL64-1----Node C-13-N4SL64-1.

B-12-N4SL64-1 and 1 Node B -7-N4SL64-1-----------Node C-13-N4SL64-1.

4 in Source can be utilized in the sink and similarly boards written on the sink can be utilized on Source it won’t make any difference w.r.t c

nections follow the steps shared from Figure 3 to Figure 6 for choosing time slots for both source and sink boards. Once the time slots are
connections are configured it's time to run the SDH Trail.

he View tab click on SDH Trail as shown in Figure 8.

ails on the NMS. Click on Next until the search is completed. You may need to click Next multiple times until the procedure is completed.
 Search Trail Window

d the trail will be visible. The trail can be checked via right clicking on Node A-2-N2PQ1-45 and choosing Browse Relevant Trail as shown i
nd VC4 services are also configured the same way.

are reserved for protection.

tion scheme itself in case of signal failure to ensure customer services are not affected.
Node C via Node B or Node A to Node C via Node D. We can choose any path we want. Let’s configure via node B. Follow the following pro
d with the client end devices. For this example, let’s follow the table pasted below for service drop at Node A and Node C.
1 is a fiber link so if a time slot at a specific VC4 is empty at Node A -7-N4SL64-1 then the same time slot should be available at Node B-12-
the … dots another window will open showing the boards of the NE on which VC12 can be configured. In those boards go to 7-N4SL64-1 a

VC4 with no VC12 configured time slot is not disturbed as it may be later utilized on the VC4 level.

this VC4 is already utilized as its grey out as can be seen in figure 6. It means the 1st VC4 is reserved for VC12 services.
nk. It can be verified by following the procedure shown from Figure 3 to Figure 6.
on’t make any difference w.r.t configuration.

boards. Once the time slots are selected click on Apply and then OK as shown in Figure 7 for Node A.
til the procedure is completed.
owse Relevant Trail as shown in Figure 11.
ode B. Follow the following procedure for smooth configuration of the VC12 service.
e A and Node C.
ould be available at Node B-12-N4SL64-1.
hose boards go to 7-N4SL64-1 as this port is connected with Node B as can be seen in Table 1.

12 services.
A new Huawei OSN 3500 SDH equipment just created, generated after the upload operation the NE

The troubleshooting developed was:

1. Run in Navigator the commands (:ver, :hbu-get-backup-info, :cfg-get-nestate, :alm-get –curdata

2. Try to create the NE with only one SCC board.
3. Downgrade the NE to a pure SDH version.

There was two troubles, first the NE had two SCC boards that didn’t synchronize because each one

The solution was remove one SCC board, and after that the configured the ID belong to the board th
Finally when the NE get the target version V100R010C03SPH211, all the boards belong to the equip

The key to create on the NM a new NE without problems is; to demand a good commissioning on si
fter the upload operation the NE error: Invalid parameters error code: 38722; and some boards didn’t appear or turned grey (picture).

g-get-nestate, :alm-get –curdata)

synchronize because each one had a different ID, and the second issue was a mistake made by the person that upgrade the element on si

ed the ID belong to the board that was outside of the equipment in the board that kept inside. The next step was insert again the SCC boa
the boards belong to the equipment appeared in the layout, and began to work properly.

and a good commissioning on site with a complete report when buy Huawei OSN 3500.
ar or turned grey (picture).

that upgrade the element on site; he put on the equipment the version V2R11C00SPH303 which is a version for Huawei MSTP equipment

ep was insert again the SCC board and wait until those boards turned synchronized. Once the Navigator command :hbu-get-backup-info, s
on for Huawei MSTP equipments, and the customer network only managed SDH elements.

ommand :hbu-get-backup-info, showed the result: “Backup-Info : 0x00000003”; I proceed to ask the partner on site to downgrade the NE f
er on site to downgrade the NE from the firmware V2R11C00SPH303 to V100R010C03SPH211.
Comment gérer l'alarme COMMUN_FAIL
publié il y a: 2021-09-23 11:12:12
1950 0 0
0
Lire cet auteur0#
Bonjour à
tous!

Dans cet
article, je
partagerai
mon
expérience
dans la
gestion de
l'alarme
COMMUN
_FAIL sur
les
équipeme
nts SDH.

1.
Qu'est-
ce que
l'alarme
COMM
UN_FAI
L
avec
l'alarme
COMMUN
_FAIL. Parf
ois,
l'alarme
COMMUN
_FAIL est
générée
indépenda
mment. Pa
rfois, une
seule carte
signale
l'alarme. P
arfois,
plusieurs
cartes
signalent
l'alarme
en même
temps. L'al
arme
COMMUN
_FAIL
indique
que la
communic
ation
entre les
Paramètre
s
d'alarme :

Le
paramètre
1 indique
le numéro
de port,
qui a une
valeur fixe
de 0x01.

Le
paramètre
2 a une
valeur fixe
de 0x00.

Le
paramètre
3 a les
significatio
ns
suivantes :

0x01
indique
que le
chemin
RS485 1
signale
cette
alarme.
0x02
indique
que le
chemin
RS485 2
signale
cette
alarme.

0x03
indique le
premier
canal de
communic
ation
Ethernet
inter-
cartes.

0x04
indique le
deuxième
canal de
communic
ation
Ethernet
inter-
cartes.

Symptôme
s de
panne
courants
2.
Principe
s de
commu
nication
Etherne
t
interne
Sur la
base de la
descriptio
n de
l'alarme
dans la
document
ation du
produit,
vous
pouvez
connaître
la
significatio
n et les
causes
possibles
de
l'alarme.

Pour
mieux
comprend
re l'alarme
COMMUN
_FAIL, il
faut
également
maîtriser
le principe
de
communic
ation
interne de
l'appareil.
Comme le
montre la
figure, il
existe
deux
canaux de
communic
ation
internes :
485 (divisé
en deux
canaux A
et B) et
ETH.
Si la valeur
du
paramètre
3 de
l'alarme
commun_f
ail est
0x01 ou
0x02, la
route A et
la route B
communiq
uent entre
elles via
485.

Si la
communic
ation
Ethernet
interne est
anormale,
la valeur
du
paramètre
3 de
l'alarme
commun_f
ail est
0x03.
passer par
AUX. (SAP
sur OptiX
OSN 2500
et EOW
sur OptiX
OSN 7500)
Si la carte
AUX est
défectueu
se, toutes
les cartes
ou un
grand
nombre
de cartes
signalent
l'alarme
commun_f
ail. La
communic
ation 485,
cependant
, ne passe
pas par la
carte
AUX. Il
échange
principale

3.
Localisa
tion de
l'alarme
COMM
UN_FAI
L
3.1
Vérifiez
d'abord
le
troisième
paramètr
e
d'alarme.

Vérifiez si
le
paramètre
d'alarme 3
est 0x01,
0x02 ou
0x03. La
méthode
de
localisatio
n de
l'exception
de
communic
ation
RS485 est
différente
de celle de
localisatio
n de
l'exception
de
communic
ation
Ethernet.
nt
configuré,
étant
donné que
le circuit
de
command
e du bus
485 se
trouve sur
la carte
d'intercon
nexion,
trop de
cartes
sont
configurée
s. En
conséque
nce, la
tension
d'entraîne
ment du
bus est
insuffisant
e et le
niveau est
anormale
ment
qui
affectent
l'Optix
OSN 7500
sont des
cartes
EOW. Les
cartes
AUX sont
les claviers
qui
affectent
l'optix
OSN 3500.
Les
claviers
qui
affectent
l'optix
OSN 2500
sont des
cartes
SAP. Ce
type de
carte
dispose
du
module de
communic

3.2
Confirme
z l'état du
rapport
d'alarme.
persiste
pendant
une
longue
période
ou par
intermitte
nce
(comme
l'alarme
existe
pendant
une
seconde,
disparaît
pendant la
seconde
suivante,
puis
réapparaît
pendant la
seconde
suivante.
Continuez
comme
ça) et si
elle est
signalée
avec le

3.2.1
Rapports
d'alarme
répétés
et
intermitt
ents
réinitialisat
ion pour
analyse. Si
l'alarme
Bd_status
est
signalée
fréquemm
ent et de
manière
transitoire,
vérifiez si
l'alarme
Bd_status
est
réinitialisé
e à
plusieurs
reprises. E
n
particulier,
si une
boucle se
produit
sur une
carte
Ethernet
ou si un
grand

3.2.2 Une
seule
carte
signale
les
alarmes
pendant
une
longue
période
une
longue
période,
veillez à ce
que les
alarmes
soient
signalées
par blocs
multiples
ou
uniques. L
a moitié
des
alarmes
signalées
par une
seule carte
sont des
problèmes
individuels
. Générale
ment, le
matériel
de la carte
est
anormal
ou le
logement
du fond

3.2.3
Plusieurs
cartes
signalent
des
alarmes
pendant
une
longue
période
Si
plusieurs
cartes
signalent
des
alarmes en
même
temps, il
est
probable
que les
cartes
AUX et
GSCC
fonctionne
nt
anormale
ment. Dan
s ce cas,
retirez et
insérez les
cartes
(éteignez
et
redémarre
z les
cartes) ou
remplacez
les cartes.

3.3 Des
conflits
d'adress
es IP
existent
sur le
réseau
DCN
Lorsqu'un
conflit
d'adresse
IP se
produit, la
carte NE
signale
l'alarme
COMMUN
_FAIL.
bac,
chaque
carte qui
utilise la
communic
ation
Ethernet
doit avoir
sa propre
adresse
IP. Pour
éviter les
conflits
d'adresse
IP, chaque
carte
détermine
son
adresse IP
en
fonction
de son
emplacem
ent
correspon
dant lors
de la mise
sous
tension. L'
adresse IP
3.4 Non-
concorda
nce de la
version
du
logiciel

NE, vous
devez
débloquer
certaines
alarmes
matérielles
(en
particulier
les
alarmes
Hard_err
et
Hard_bad).
Si
certaines
cartes
signalent
des
alarmes
anormales
telles que
commun_f
ail, vous
pouvez
effectuer
un
rollback
manuel
pour
restaurer
Pour plus
de détails
sur la
façon de
gérer
l'alarme
COMMUN
_FAIL d'un
NE WDM,
consultez
le lien
suivant :

https://support.huawei.com/hedex/hdx.do?docid=EDOC1100197069&id=FEK0520J_03_10078&lan

Si vous n'avez pas la permission d'ouvrir le lien, veuillez cliquer sur Comment mettre à niveau notre

Merci!
MUN_FAIL
La carte GSCC signale des alarmes dues à une
publié il y a: 2020-09-07 14:18:46
2170 0 0
0
Lire cet auteur0#
Salut!

Cette fois,
je vais
partager
avec vous
un cas sur
les
alarmes
de
rapports
de la carte
GSCC en
raison
d'une
incohéren
ce de
version.

Descripti
on du
problèm
e
L'alarme
NESOFT_
MM est
signalée
après le
remplace
ment de la
carte
GSCC de
l'OptiX
OSN 3500.

Informati
ons
d'alarme

Veuillez
consulter
la figure
ci-
dessous:

Processu
s de
traiteme
nt
1. D'après
le
paramètre
d'alarme,
nous
savons
que les
versions
de fichier
du SCC
opération
nel et
celles du
SCC de
protection
sont
incohérent
es.

2.
Exécutez
la
command
e pour
vérifier la
version du
logiciel de
la carte
SCC, peut
également
vérifier la
version
sur le
NMS.
: sftm-
get-
testver:
bid

3. On
constate
que les
versions
de base
des cartes
des
emplacem
ents 17 et
18 ne sont
pas
cohérente
s.

4. Chargez
le BIOS de
la carte
dans
l'emplace
ment 17
vers la
version
08.09.14
via la mise
à niveau
du logiciel
au niveau
de la
carte.
Cause
première

Les
versions
BIOS du
SCC
opération
nel et
celles du
SCC de
protection
ne sont
pas
cohérente
s.

Solution

Mettez à
niveau la
version du
BIOS de la
carte de
secours,
effacez
l'alarme.
C'est tout,
bienvenue
à tous
pour
laisser un
message
et
échanger
dans la
zone de
commenta
ire!

Je vous
remercie!
mes dues à une incohérence de version
Issue Description
The version of the OptiX OSN 6800 is 5.51.04.13.
The network comprises two OTM stations that are configured with bi-directional services.
The relevant boards are NS2, FIU, SC1 in station A and those in station B.
The following alarms are reported:
The SC1 in station A reports the OSC-RDI alarm.
In station B, the NS2 reports the OCH_SSF-O alarm, the FIU reports the OTS_LOS-O alarm, and the SC1 reports the R-L

Alarm Information
OCH_SSF-O, OTS_LOS-O, R-LOS, OSC-RDI

Handling Process
1. It is easily confirmed that the key alarm is the R-LOS alarm reported by the SC1 in station B. The OCH_SSF-O
2. The FIU board in station B detects the OTS_LOS-O alarm. The cause for the R-LOS alarm reported by the SC
3. The OTS_LOS-O alarm indicates loss of the monitoring signal (overhead) in the OTS layer. The optical port of
4. It is confirmed that the physical fiber connection from the FIU to the SC1 in station B is incorrect. All the alarms

Root Cause
1. The boards are faulty.
2. The fiber connections are incorrect.

Suggestions
1. The service alarm indicator (SRV) gives green light when the NS2 reports the OCH_SSF-O alarm or when the
2. The two alarms are related to the logical fiber connection from the FIU to the SC1. Neither alarm is reported if n
3. To handle the unfamiliar alarms, refer to the Alarms and Performance Events in the relevant product manual.
m, and the SC1 reports the R-LOS alarm.

1 in station B. The OCH_SSF-O alarm reported by the NS2 in station B and the OSC-RDI alarm reported by the SC1 in station A are caused by the R-L
-LOS alarm reported by the SC1 board in station B is mistaken for the OTS_LOS-O alarm detected by the FIU. The following conclusion then is drawn:
e OTS layer. The optical port of the OSC board connecting to the TM port of the FIU board reports the OTS_LOS-O alarm because the R-LOS alarm is
on B is incorrect. All the alarms are cleared after the fiber connection is corrected.

CH_SSF-O alarm or when the FIU board reports the OTS_LOS-O alarm. This means that the alarm is not generated at the board side.
C1. Neither alarm is reported if no logical fiber is created from the FIU to the SC1.
the relevant product manual.
station A are caused by the R-LOS alarm.
owing conclusion then is drawn: Station A is faulty, or at least the fiber connection from the FIU board to the SC1 in station B is correct. Actually, the rel
m because the R-LOS alarm is detected.

the board side.

on B is correct. Actually, the relationship between the two alarms is misunderstood. The correct relationship is as follows: The FIU reports the OTS_LO
s: The FIU reports the OTS_LOS-O alarm because the SC1 reports the R-LOS alarm.