ZXONE 9700 Initial
Configuration
Contents
NE Initialization
Easy Provisioning
OTN 9700 EGNE(/GNE) Configuration Guide
NE Initialization
NE initialization is to
implement the NE
management procedure
through configuring the
SNP, SOSC, or SOSCB
boards. The SNP board is
the core board of the NE
monitoring system,
providing NE management,
protection control, data
forwarding, and channel
maintenance.
SOSCB
© ZTE Corporation. All rights reserved
NE Initialization Procedure
© ZTE Corporation. All rights reserved
IP Address
ZTE OTN devices (9700, x20 & 8000 Series ) include two IP address
(Internal & External IP address). The followings are internal IP address
defined way.
X20 & 8000 series: Subrack No. Slot No.
192 168 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Intra-board IP address: 192.168.X.4*Y
Where X indicates sub-rack number (Sub-rack number is defined by
backplane DIP switch), X=1-127,
Y is the slot number. Y < = 63.
if Y = > 63. X= Sub-rack number +128, Y=(slot number -64)*4.
9700 series:
192.X.Y.0 255.255.0.0, X= Sub-rack number 、Y= slot number
© ZTE Corporation. All rights reserved
Querying the Temporary External IP Address of
the M2SNP Board
The IP address used for communication between NEs is called an
external address. A temporary external IP address has been
allocated for the SNP board before equipment delivery. The
temporary external IP must be replaced by the planned external
IP address on site. The external temporary address of the M2SNP
board is used as the IP address of the new NE.
Prerequisite
The IP address of the EMS server and the temporary external IP address of
the SNP board belong to the same network segment.
The EIC board is the external interface board of a shelf. Only after the EMS
server is connected to the NX41 or DX41 shelf through the ETH1 or ETH2 port
of the EIC board, can the EMS query the temporary external IP address of the
SNP board.
© ZTE Corporation. All rights reserved
Querying the Temporary External IP Address
1. Press the TST button of the EIC board for 5 seconds. When the NOM indicator
of the EIC board quickly flashes, release the TST button.
Note:
If the NOM and ALM indicators of the M2SNP board flash at the same time, and
the internal IP address 192.168.1.4 of the M2SNP board can be pinged
successfully, VLANs are converged successfully.
2. On the EMS server, select Start > Run. A dialog box is displayed. Enter cmd and
press Enter. The DOS command window is displayed.
3. In the DOS command window, enter the telnet 192.168.1.4 9023 command,
Press Enter, and you can log in to the M2SNP board.
4. On the login window, enter user name ZTE and password ZTE. Press Enter.
© ZTE Corporation. All rights reserved
Querying the Temporary External IP Address
5. After you log in to the board successfully, enter the :ifconfig
command. Press Enter. The external IP address of the M2SNP
board 192.100.10.1 is displayed under eth0:1.
© ZTE Corporation. All rights reserved
Creating an NE (9700)
After the temporary external IP address is queried, you need to
create an NE on the EMS and set up management relationship
between the EMS and the NE.
Prerequisite
The IP address of the EMS server and the temporary external IP address of
the SNP board belong to the same network segment.
Steps
1. In the Topology Management window, right-click the blank area, and
select Create Object > Add BN-xTN NE from the shortcut menu. The Add BN-
xTN NE window is displayed.
2. In the Add BN-xTN NE window, select a device type from the object type
tree in the left pane.
© ZTE Corporation. All rights reserved
Creating an NE (9700)
© ZTE Corporation. All rights reserved
Creating an NE (9700)
Parameter
Description for
Creating a BN-
xTN NE (OTN)
© ZTE Corporation. All rights reserved
Creating an NE (9700)
Steps
3. Click the Rack/Shelf Configuration button on the bottom-right corner. The
Rack/Shelf Configuration dialog box is displayed.
Note:
The shelf type selected on the EMS must be the same with the shelf installed
in the cabinet.
4. From the left NE list select the main shelf.
© ZTE Corporation. All rights reserved
Creating an NE (9700)
Main Shelf Configuration
Parameter Descriptions
for Main Shelf
Configuration
There is an 8-digit DIP switch (marked as SI)
on the shelf backplane. It is used to set the
shelf ID.
© ZTE Corporation. All rights reserved
Creating an NE (9700)
Shelf ID Setting Descriptions
1. The first bit of the DIP is reserved.
2. up: A DIP switch is moved to the upper side. It represents
binary digit 0.
3. down: A DIP switch is moved to the lower side. It represents
binary digit 1.
© ZTE Corporation. All rights reserved
Creating an NE (9700)
5. Right-click Main Rack[R0] and select Add Slave Shelf from the
shortcut menu. 6. Click OK. 7. Click Apply.
© ZTE Corporation. All rights reserved
Configuring Monitoring Boards
To monitor an NE that has been created, you must configure the
SNP board and monitoring boards, such as the SOSC or SOSCB
board.
Prerequisite: The NE status is Offline.
Steps:
1. In the Topology Management window, double-click an NE. The Rack Chart
window is displayed.
2. Click the button. The Board Selection tab is displayed in the right side
of the Rack Chart window.
© ZTE Corporation. All rights reserved
Configuring Monitoring Boards
3. On the Board Selection tab, select SNP. Select the Pre-setting check box on
the bottom-left corner. Click slot 1 in the Rack Chart to insert the SNP board.
The Board Property dialog box is displayed.
Board Property Setting
APS of the SNP
board must be set
to Exist. If not, the
APS controller
cannot be selected
when the
protection group is
configured.
© ZTE Corporation. All rights reserved
(Optional) Query the Agent software version on
the Board Basic Property tab
Querying the Board Agent Software Version
© ZTE Corporation. All rights reserved
Configuring Monitoring Boards
4. In the Topology Management window, right-click the NE. Select NE
Property from the shortcut menu. The NE Property dialog box is displayed.
Modify the software version. For the correspondence between the NE
software version and the Agent version of the selected SNP board.
Correspondence Between NE Software Version and Agent Version
© ZTE Corporation. All rights reserved
Configuring Monitoring Boards
5. Right-click the NE and select Online/Offline from the shortcut menu, and
set it to Online. Click OK.
6. In the NE Property dialog box, set IP Address to the planned IP address.
7. Click Apply to reset the SNP board.
8. In the Topology Management window, double-click the NE. The Rack Chart
window is displayed. Select the SOSC or SOSCB board from the Board
Selection tab, and click slot 3 in the Rack Chart to insert the SOSC or SOSCB
board.
Note:
The active SOSC or SOSCB board is configured in slot 3, and the standby
SOSC or SOSCB board is configured in slot 5.
© ZTE Corporation. All rights reserved
Configuring Monitoring Boards
9. Select the SOSC or SOSCB board from the Customized Resource tree.
Select Communication Maintenance > Board IP Configuration from the Board
Operation navigation tree.
10. In the Board IP Configuration window, set IP, Mask, and Area ID of
Electrical Port 3 in accordance with the planning.
© ZTE Corporation. All rights reserved
Creating an NE (9700)
Note:
To configure the NE as the access NE, the IP address of electrical port 3 of the SOSC or
SOSCB board must be configured. If the NE is connected to the EMS server through a
network cable, the IP address of electrical port 3 and that of the of the EMS PC must
belong to the same network segment. If the NE is connected to the EMS PC through
the DCN, the IP address of electrical port 3 must be set in accordance with the
planning.
The SOSC or SOSCB board is automatically reset after the configuration is sent. It
requires some time.
11. Press the TST button of the EIC board for 5 seconds. When the NOM indicator of
the EIC board slowly flashes, release the TST button. The EMS can manage Nes
properly.
Note:
If the NOM and ALM indicators of the SNP board flash at the same time, or the internal
IP address 192.168.1.4 of the SNP board cannot be pinged through, the VLAN converge
is cancelled.
© ZTE Corporation. All rights reserved
Clearing Databases
After the external IP address of an NE is modified, you need to
clear the NCP database before the EMS starts to manage the NE
again to prevent that the left settings affect NE after the SPN
board is inserted into the NE.
Prerequisite : The NE status is online.
© ZTE Corporation. All rights reserved
Downloading the Database
To ensure that the NE database and the EMS database are the
same, you need to download the EMS database to the NE
database to synchronize the data.
Prerequisite : The NE status is Online.
© ZTE Corporation. All rights reserved
Automatic Discovery of Boards
The EMS supports the automatic discovery function of boards. It
can automatically install the boards that have been physically
installed on the equipment to an NE that is created on the EMS.
Prerequisite : The NE status is Online.
© ZTE Corporation. All rights reserved
Contents
NE Initialization
Easy Provisioning
OTN 9700 EGNE(/GNE) Configuration Guide
Easy Provisioning (9700)
If a remote NE cannot be managed, you can use the easy provisioning
function to manage the remote NE through the physical links between
NEs. By using the easy provisioning function, you can query and set the
port IP address and NE IP address of the remote NE, query the board
information, set and query static routes, and reset the monitoring board
of the remote NE.
© ZTE Corporation. All rights reserved
Easy Provisioning Steps
Steps
1. In the Topology Management window, right-click the NE. Select NE
Management from the shortcut menu. The NE Management window is
displayed.
2. Select the SOSCB board from the Customized Resource navigation tree.
Select Communication Maintenance > DCN Neighbor Configuration from the
Board Operation navigation tree.
3. Click the Query button on the bottom-right corner of the Local Port
Information tab. The local ports with actual connections are displayed.
© ZTE Corporation. All rights reserved
Easy Provisioning Steps
Steps
4. Select Optical Port 3. Select the query button under Neighbor Port
Information to query the port information of the peer end.
© ZTE Corporation. All rights reserved
Easy Provisioning Steps
Steps
5. Click the Query button on the bottom-right corner of the Neigh NE IP
Address tab to query the IP address of the peer NE
© ZTE Corporation. All rights reserved
Easy Provisioning Steps
6. After the IP address of the adjacent NE is queried, create the adjacent NE
and set the IP address to the planning IP address in the Topology view.
Create the adjacent NE, and modify the IP address to the planned IP address.
7. Click the Query button on the bottom-right corner of the Neighbor NE
Board tab to query the board information of the peer NE.
© ZTE Corporation. All rights reserved
Easy Provisioning Steps
8. Select the SOSCB board on the Neighbor NE Board tab. Click the Query
button on the bottom-right corner of the Board IP Address Config tab. All the
ports of the SOSCB board of the peer NE are displayed.
© ZTE Corporation. All rights reserved
Easy Provisioning Steps
9. Add static routes on the Static Router Config tab, and click Apply. After the
operation is successful, the EMS indicates that you to reset the board.
Note:
When the gateway NE is configured, you should use the static route configuration
function.
10. Click the Board Reset tab and select the reset mode.
© ZTE Corporation. All rights reserved
Contents
NE Initialization
Easy Provisioning
OTN 9700 EGNE(/GNE) Configuration Guide
Terms
Term Description
Gateway
Directly connected to the DCN or the EMS. The GNE forwards
Network
communication data between the NE and EMS.
Element (GNE)
Not directly connected to the EMS or connected to the EMS through
Network
the DCN. At least one GNE is required to forward communication
Element (NE)
data when the NE communicates with the EMS.
One NE can be configured with multiple GNEs, and one of the GNEs
Active GNE can be set to the active GNE. The active GNE is preferred for
communications.
One NE can be configured with multiple GNEs, and the GNEs except
for the active GNE are standby GNEs. When the communication of the
Standby GNE active GNE is interrupted, one standby GNE is automatically switched
to continue communication (the active/standby GNE switching is
triggered by the EMS).
© ZTE Corporation. All rights reserved
GNE\ EGNE Processing Capacity
Each GNE manages up to 60 physical NEs according to the GNE
NAT forwarding capacity, and the quantity of configured GNEs
varies with network size.
Each EGNE manages up to 60 physical NEs according to the
number of EGNE TCP/IP connections (a connection is required
between each NE and the EGNE), and the quantity of configured
EGNEs varies with network size.
© ZTE Corporation. All rights reserved
GNE\EGNE-Supported Equipment and Versions
Board Type Description
In M1SNP+SOSCB/SOSC mode:
1. The GNE function is enabled on the SOSCB board. The
route is from SOSCB electrical interface 3 through the DCN to
the EMS. The static route of the equipment is set on the
SOSCB board.
SOSCB GNE 2. Equipment supporting the GNE/EGNE function: ZXWM
M920, ZXMP 820, ZXMP M720, and ZXONE 8000 series.
3. The D1209 system version and later support the GNE/EGNE
function. The M1NCP version matches the SCSC\SOSB
version.
In M2SNP+SPWA/EIC mode:
1. The GNE and EGNE functions are enabled on the M2SNP
board. The route is from the M2SNP access IP through the
DCN to the EMS. The static route of the equipment is set
on the M2SNP. The EGNE function is recommended in a
GNE new network.
M2SNP
EGNE 2. Equipment supporting the GNE/EGNE function: ZXWM
M920, ZXMP 820, ZXMP M720, ZXONE 8000 series and
ZXONE 9700.
3. The D1306 system version and later support the
GNE/EGNE function. The M2SNP version matches the
SPWA/EIC version.
© ZTE Corporation. All rights reserved
Minimum Version Requirement
D1209 System Version Descriptions
Minimum Version Requirement
U31 NetNumen U31 R22V12.11.20 P01
M1SNP AGENT_M720_TST_4.21.001
M720_SOSC_TST_3.23.016
SOSC\SOSCB
8500V1.00_MST_SOSCB_V3.21.018
D1306 System Version Descriptions
Minimum Version Requirement
U31 NetNumen U31 R22V12.13.10 P02
M1SNP AGENT_M8x00_TST_4.30.011
M2SNP AGENT_M8X00_SVT_6.00.120
M720_SOSC_TST_3.23.021
SOSC\SOSCB
8500V1.00_MST_SOSCB_V3.21.034
SPWA M720_SPWA_TST_3.30.018
EIC M820V2.52_MST_M1EIC_V1.01.008
© ZTE Corporation. All rights reserved
EGNE Configuration (With the DCN)
Network Topology
© ZTE Corporation. All rights reserved
L-EMS Configuration
In the network with the DCN, the EGNE is first configured on the
L-EMS, and the R-EMS manages the EGNE by synchronizing the
configuration data. A static route is required for the L-EMS
configuration.
Local EMS Access Debugging
1.To ensure that the L-EMS can manage Nea, add an IP address on the L-EMS.
© ZTE Corporation. All rights reserved
L-EMS Configuration
2. Create an NE, and modify the version properties of the NE.
Create an NE on the EMS. The hardware version is 2.52 and the
software version is 6.00 in NE Property. For the EGNE, the
software version must be set to 6.00. If the device type is x20, the
hardware version of the M2SNP is 10.02 and the software version
is 6.xx on the Board Basic Property tab.
If the device type is 8x00, the hardware version of the M2SNP is
M2N2 and the software version is 6.xx on the Board Basic
Property tab.
© ZTE Corporation. All rights reserved
L-EMS Configuration
© ZTE Corporation. All rights reserved
L-EMS Configuration
3.Set the EGNE management port on the SEIA/EIC board.
Set the EGNE Management Port on the SEIA\EIC Board
(1) Right-click the SEIA or EIC board, and select NE Management
> WDM Service Configuration > Ethernet Port Property.
(2) In the displayed Ethernet Port Property window, select the
port that is connected to the EMS, set Use Mode to EGNE
Management Port, and select the Enable check box for port
status.
© ZTE Corporation. All rights reserved
L-EMS Configuration
Setting the EGNE Management Port (SEIA1)
© ZTE Corporation. All rights reserved
L-EMS Configuration
3.Set the EGNE management port on the SEIA/EIC board.
Setting the EGNE Management Port (EIC)
© ZTE Corporation. All rights reserved
L-EMS Configuration
4.Modify the NE property for the EGNE, and enter the access IP
address (for example, 172.60.10.1/24, the IP address of the
corresponding port of the M2SNP board).
Note: The EGNE
is enabled only
through the
EMS, and the
command line
cannot be used.
© ZTE Corporation. All rights reserved
L-EMS Configuration
5. (Optional) Delete the static routes from the SOSC/SOSB board. If no
static routes have been configured, skip the step.
(1) Delete the static routes from the SOSC/SOSB board on the L-EMS.
After the EGNE is enabled, the static route that is used to communicate
with the DCN must be configured on the M2SNP board. Path to delete
the static route:
NE Management > SOSC\SOSCB Board > Communication Maintenance
> Static Route Configuration
View the static routes on the PC using route print, and delete the
specified static routes using route delete.
(2) Delete the IP address and mask of electrical interface 3 from the
SOSC/SOSB board. If the IP address and mask do not conflict with other
IP addresses and masks, they can be reserved.
© ZTE Corporation. All rights reserved
L-EMS Configuration
© ZTE Corporation. All rights reserved
L-EMS Configuration
6. After the static route is configured on the PC where the R-EMS
is installed, to ensure intercommunication between the R-EMS
and access IP address, add a static route on the M2NCP board of
NEa. The ping command can be executed if the command is
available in the DCN. Path to add a static route after selecting
NEa:
NE Management > SNP > Communication Maintenance > Static
Route Configuration
© ZTE Corporation. All rights reserved
L-EMS Configuration
© ZTE Corporation. All rights reserved
L-EMS Configuration
A static route can be added on the M2SNP board by the command line, but the configuration
data is only saved on the board. If the libary is downloaded before the EMS uploads the
configuration data, the configuration of the static route is lost.
Telnet to port 9023 of the M2SNP board, and enter the username zte and passward zte.
Under [admin]#, execute sh2 and open the [SNP_AGENT] prompt.
To add a static route: route add -net destination IP netmask destination mask gateway IP.
To delete a static route:
route delete -net
destination
IP netmask destination
mask.
© ZTE Corporation. All rights reserved
L-EMS Configuration
The colon must be added before a command.
7. Update the MAC address on the PC where the EMS is located.
Enter the arp –d command on the command line of the PC to delete old MAC
information and re-learn a new MAC address from the EGNE.
© ZTE Corporation. All rights reserved
L-EMS Configuration
Add a static route from NEa to the access IP address on the L-
EMS PC to ensure that the L-EMS can monitor the EGNE after
being enabled.
route add 172.60.10.0 mask 255.255.255.0 14.14.14.111 –p
© ZTE Corporation. All rights reserved
R-EMS Configuration
After the physical link between NEa and RT3 is connected, and
the route between the R-EMS and NEa operates normally,
perform the following steps on the R-EMS.
1. Create an NE on the R-EMS, and set attributes including version, M2SNP
IP address, M2SNP access IP address, and EGNE. NEa can be created in offline
status.
2. After the R-EMS manages the NE, upload the database on the M2NCP.
3. View the static route configuration on the M2SNP, and click the Apply
button to ensure that the R-EMS database is synchronized with the device.
4. View the management port on the SEIA/EIC board, and click the Apply
button to ensure that the R-EMS database is synchronized with the device.
© ZTE Corporation. All rights reserved
