ZXCTN Series Equipment Initialization

V1.0

Contents

Initialization Preparation Initialization Procedure Initialization Command Configuration Commonly Used Initialization Commands

Tools Preparation

ZXCTN Series Product PC Console lines （ +USB interface driver ） Cross cables Hyper Terminal

Environment Preparation

According to the networking and service need, select proper models of equipment, plug the boards into the corresponding slots.

Connect the equipment according to the networking diagram.

Connect the serial port of the serial cable to the NMS PC, connect the network port at the other end to the CON port (for 6100 and 6100, this port is the OUT port).

PC ZXCTN

Serial cable CON or OUT port

Power On/Off the Equipment Inspection before Power-ON

Before the equipment is powered on, verify that the rack and subracks are installed firmly, the boards are inserted correctly and in close contact with the backplane, the cabling is in compliance with the requirement, and the interfaces are connected firmly.

Make sure that the external and on-equipment power supply are "OFF". Power-on Sequence

Power-on Sequence: First, turn on the power supply of the power cabinet; Then, turn on the power supply of the equipment cabinet; Finally, turn on the power supply of the equipment.

Summary: Power-on should be from the far to the near. Inspection after Power-ON

Verify that the components, including the power supply and the fan, are working normally. Verify that the physical connection between the interfaces is set up. Check whether the system version is correct. If not, upgrade the system to correct version.

Power-off Sequence The power-off should be in the reverse sequence with that of power-on. First, turn off the po

wer supply of the equipment; Then , turn off the power supply of the equipment cabinet; Finally, turn off the power supply of the power cabinet.

Summary: Power-off should be from the near to the far. Notes for Power-off

Power-off is not allowed before the system completes writing into the board FLASH. DC: First, turn off the on-equipment switch, then turn off the -48V DC power supply of the eq

uipment room. AC: First, turn off the on-equipment switch, then turn off the external 220V AC power supply.

Sample Networking

NE1

NE2 NE4

NE3

xgei_12/1

Mcc Port:193.168.0.1

NE IP Address / Loopback Address：

3.3.3.3　 　

Mcc Vlan:4093

NE5NE6

Mcc Vlan:4092 Mcc Vlan:4091

Mcc Vlan:4090

Mcc Port:193.168.0.2

Mcc Port:192.168.0.1

Mcc Port:192.168.0.2 Mcc Port:191.168.0.1

Mcc Port:191.168.0.2

Mcc Port:190.168.0.1

Mcc Port:190.168.0.2

6300 6200 6100

xgei_11/1

xgei_12/1xgei_11/1

xgei_3/1

xgei_4/1

xgei_4/1

xgei_3/1

gei_7/1gei_7/2

Mcc Vlan:3002

gei_1/9

gei_1/10

gei_1/10

gei_1/9NE IP Address / Loopback Address：5.5.5.5

NE IP Address / Loopback Address： 6.6.6.6

NE IP Address / Loopback Address：1.1.1.1

NE IP Address / Loopback Address：2.2.2.2　 　

EMS Server IP:195.195.195.111

Qx Management port IP：195.195.195.11

Mcc Vlan:3001

Mcc Vlan:3003

Mcc Port:196.168.0.2Mcc Port:194.168.0.1

Mcc Port:194.168.0.2

Mcc Port:196.168.0.1

Mcc Port:195.168.0.1

Mcc Port:195.168.0.2

NOTE：Agreed Mask is 255.255.255.0

Data Planning Priniciples

MCC VLAN ：（ 1 ） MCC VLANID can be re-used in compliance with the followi

ng pinciples: the VLANIDs of the adjacent link segments must be different, and the VLANIDs of the non-adjacent link segments can be the same.

（ 2 ） The MCC VLANID should be within the range of 3001 - 4093. The T3 NMSVLAN will automatically shield these values to prevent the conflict between the management VLAN and the service VLAN. The service VLAN ID should be within the range of 2 - 3000, and it is suggested to start from 17.

MCC VLAN

10GE ring

It is suggested to configure one VLAN for each link, the starting VLANID is 4093, and the VLANIDs are in descending order.

GE ring It is suggested to configure one VLAN for each link, the starting VLANID is 3001, and the VLANIDs are in increasing order.

Data Planning Priniciples

IP Address of NE（ 1 ） The IP address of the NE should be the same w

ith that of the loopback address, and be different from that of the MCC port.

（ 2 ） The IP address of the NE (the loopback address) should be unique in the entire network (Here, the entire network refers to the network related to the service).

IP Address of MCC Port（ 1 ） The IP addresses of the two MCC ports of each li

nk (or the IP addresses of the service ports) must belong to the same network segment. The IPs of different links should belong to diffrent network segments

System File Preparation The software program, configure file and other data file of ZXCTN Serial pro

duct are all stored in the flash memory, the file directory are shown below ： Flash/img/ software and boot upgrade program Flash/cfg/ configure file, the file name is startrun.dat (.old) when it is loading

The original configure data and the new modified data are all saved in startrun.dat 。 When starting the equipment, the system will search for the "startrun.dat" to load the co

nfiguration. If the system cannot find the file, it will load the "startrun.old". If both of the two files are not found, the equipment will be started without configuration.

When initializing the equipment, the system needs to delete the "startrun.dat" and the "startrun.old" at first, then the system will conduct reload to start the equipment without configuration.Then the system will assign the initialization script and use the "write" command to create a new "startrun.dat".

So, it is suggested to change the filename of the original "startrun.dat" to "startrun1.dat" and change the filename of "startrun.old" to "startrun1.old" before configuring the script.

Since the system will re-configure the data, why should we keep the original files? The reason is that the 63 equipment will only acknowledge the "startrun.dat （ .old ） ", in order to prevent problem caused by errors in new configuration data, we need to save the original files for recovering the data if needed.

Flash/data/ other data Flash/dataset/ New version of Agent startup file

If the Agent is in a new version, there will be a "dataset" folder in the FLASH. If there is a "InitDataSrcFlag" file in the folder, the equipment will be started from the ros, i.e. the configurations are loaded from "flash /cfg/startrun.dat". If the file doesn't exist, the equipment will be started from the Agent.

Contents

Initialization Preparation Initialization Procedure Initialization Command Configuration Commonly Used Initialization Commands

Initialization Procedure

Step1: Connect the Equipment. Connect the serial cable to the debugging port of the e

quipment that needs initialization, and open the Hyper Terminal.

Create new equipment. Seleect the COM port. Connect the equipment.

Initialization Procedure

Step2: Clear the configuration data. Open the "cfg" folder. Type in "delete startrun.dat" and "delete startrun.old".

Initialization Procedure Step3: Use the "reload" command to restart the equipme

nt.

Step4: Create new configuration script. After the equipment is restarted normally, input the commands of

configuration script in the global mode (configuraiton mode). See the next section for detailed configurations.

Step5: Get back to the Privileged mode and use the "write" command to save the configuration.

Initialization Procedure Step6: Verify the result.

From the NMS PC, ping the IP address of each NE and the management IP address of each optic port to check whether the MCC channel is OK.

Check the configuration information of each NE: ZXR10#show run

Check the interface information of each NE: ZXR10#show interface vlan ***

Use the TELNET command to log in the IP address of the NE and test the user name and password.

Check the directory of the "startrun.dat": ZXR10#cd cfg ZXR10#dir

– Directory of flash:/– attribute size date time name

» 1 drwx 4096 JAN-07-2010 16:32:56 .» 2 drwx 4096 JAN-07-2010 16:32:56 ..» 3 -rwx 6891 JAN-07-2010 16:32:56 startrun.dat

Contents

Initialization Preparation Initialization Procedure Initialization Command Configuration Commonly Used Initialization Commands

Command Modes for Terminal Operation

ZXR10> //After the equipment is connected, a command window appears.

This command mode is the User Mode ZXR10>en （ Password : zxr10 ）

ZXR10# //After logging in the equipment, a command window with # is sh

own. This commnad mode is the Privileged Mode. ZXR10#configure terminal //You can input "con t", and use th

e Tab key to complete the command.

ZXR10(config)# //This command mode is the Global Mode (or Configuration Mod

e). The configuration script is written in under this mode.

TELNET Log-in Configuration (take NE1 as example) TELNET log-in can adopt 3 modes: the remote mode of using Qx+M

CC channel, the local mode of using LCT, and the mode of using common serivce interfaces.

naming the site hostname 6100-NE1

Configure the username, password and priority for telnet to log-in the equipment:Generally, the who/who combination is used as the username/password, and the ptn/ptn is not used. After the log-in, the command mode is the Global mode.The "zte/ecc"combination is used by the user with the highest priority. After the log-in, the command mode is the Privileged mode.

username who password who privilege 15 username zte password ecc privilege 15 username ptn password ptn privilege 1

Show the created user account and permission level show username

If the multi-user configuration is adopted, the system can allow up to 16 users to log in a NE at the same time.

multi-user configure

Alarm Information Report Configuration (take NE1 as example) Configure the database upload/download function

snmp-server view AllView internet included snmp-server community public view AllView ro snmp-server community private view AllView rw

Configure the NMS sever IP: 162 is the default port for sending TRAP.The NMS server may have multiple network adapters and multiple IPs. The server IP and the NE IP must belong to the same network segment. Or the server IP must be ping through via the router.

snmp-server host 195.195.195.111 trap version 2c public udp-port 162 Configure the NE IP: The equipment will report the PTN alarms to th

e NMS via the TRAP in the SNMP protocol. The TRAP message contains the IP of the sending end. The NMS can get to know the corresponding NE according to this IP.

snmp-server trap-source 1.1.1.1

Alarm Information Report Configuration (take NE1 as example) Turn on the switch for the alarm reporting of the

NMS. snmp-server enable trap SNMP snmp-server enable trap VPN snmp-server enable trap BGP snmp-server enable trap OSPF snmp-server enable trap RMON snmp-server enable trap STALARM

Turn on the switch for system logs. logging on

Alarm Information Report Configuration (take NE1 as example) Report Alarm Level: the equipment can report 8 l

evels of alarms. The bigger bumber, the lower level: 1 - 3 corresponds to the first 3 levels ("urgent", "major", "minor"); 4-8 corresponds to the "prompt" level; 7 corresponds to "informational" level, which means the level-8 alarm will not be reported to the NMS.The alarm level can be checked via the command "show logging cur" logging trap-enable informational

Configure the alarm report time as "Beijing Time" clock timezone BEIJING 8

Loopback Address Configuraiton (take NE1 as example) - Continued Loopback Address Configuration

interface loopback1 ip address 1.1.1.1 255.255.255.0 exit

NMS Interface Configuration(take NE1 as example) If the NMS interface is the Qx port:

interface qx_4/1 (The Qx ports of different versions of equipment have different logical seri

al numbers, which needs to be confirmed in advance) ip address 195.195.195.11 255.255.255.0 Exit

If the NMS interface is LCT （ Local Craft Terminal ） port: nvram mng-ip-address 195.195.195.11 255.255.255.0

If the NMS interface is common eletrical service port: (e.g.: the 8th port of the number 8 slot)

interface gei_8/8 switchport mode access switchport access vlan 4090 Exit

Note: The IP of the NMS interface and the LAN IP of the NMS must belong to the same network segment.

IP Address MCC Monitoring Configuration (take NE1 as example) Configuring MCC Monitoring VLAN

vlan 4090 exit vlan 4093 exit

Configuring the IP address of the layer-3 interface that corresponds to this VLAN

(i.e. the IP address of the NMS monitoring channel) interface vlan 4090 ip address 190.168.0.2 255.255.255.0 exit interface vlan 4093 ip address 193.168.0.1 255.255.255.0 exit

Layer-3 Port Property Configuration (take NE1 as example)

Layer-3 port property configuration: used to configure the working modes of the MCC channel. Adopt "trunk mode" can let the NMS communication packets be forwarded freely among the MCC ports.

interface xgei_12/1 mcc-vlanid 4093 #Create the association between the service port and the MCC-VLAN.

Currently, only the 6100 equipment needs this configuration. mcc-bandwidth 2 #Available configuraitons: MCC channel bandwidth, rage: 1~100, unit:

Mbit/s, the general value is 2. switchport mode trunk switchport trunk vlan 4093 switchport trunk native vlan 4093 exit

interface xgei_11/1 mcc-vlanid 4090 #Create the association between the service port and the MCC-VLAN.

Currently, only the 6100 equipment needs this configuration. mcc-bandwidth 2 #Available configuraitons: MCC channel bandwidth, rage: 1~100, unit:

Mbit/s, the general value is 2. switchport mode trunk switchport trunk vlan 4090 switchport trunk native vlan 4090 exit

Routing Notification Configuration(take NE1 as example) Routing notification configuration: used to config

ure all the IP addresses (including the IP addresses of the monitoring port and loopback1) and the routing notification for all the enabled link ports to let the different VLANS to communicate with each other. router ospf 1 network 1.1.1.1 0.0.0.0 area 0.0.0.0 network 190.168.0.0 0.0.0.255 area 0.0.0.0 network 193.168.0.0 0.0.0.255 area 0.0.0.0 exit

Enable the OAM function under the Global mode. no tmpls oam disable

Initialization

Contents

Initialization Preparation Initialization Procedure Initialization Command Configuration Commonly Used Initialization Commands

Commonly Used Commands show version show logging current-alarm show logging history-alarm show logging notify show clock clock set hh:mm:ss show interface brief show ip interface brief show interface gei_x/x show vlan show interface vlan xxxx show ip route show run show start running-config dir cfg show mac show lldp neighbor show arp show lacp sys-id show ip ospf