Está en la página 1de 32

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 prop
er models of equipment, plug the boards into the correspon
ding slots.
 Connect the equipment according to the networking diagra
m.
 Connect the serial port of the serial cable to the NMS PC, c
onnect the network port at the other end to the CON port (f
or 6100 and 6100, this port is the OUT port).

Serial cable CON or OUT port

PC ZXCTN
Power On/Off the Equipment
 Inspection before Power-ON
 verify that the rack and subracks are installed firmly,
 the boards are inserted correctly and in close contact wi
th the backplane,
 the cabling is in compliance with the requirement,
 the interfaces are connected firmly.
 Make sure that the external and on-equipment power su
pply are "OFF".
 Power-on Sequence
 First, turn on the power supply of the power cabinet;
 Then, turn on the power supply of the equipment cabine
t;
 Finally, turn on the power supply of the equipment.
 Summary: Power-on should be from the far to the near.
Power On/Off the Equipment
 Inspection after Power-ON
 Verify that the components are working normally

Power supply

FAN

SCCU Card

Broad Card
 Verify that the physical connection between the i
nterfaces is set up.
 Check whether the system version is correct.
If not, upgrade the system to correct version.
Power On/Off the Equipment
 Power-off Sequence
The power-off should be in the reverse sequence with that
of power-on.
 First, turn off the power supply of the equipment;

 Then , turn off the power supply of the equipment cabin


et;
 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 writi
ng into the board FLASH.
 First, turn off the on-equipment switch,

 Then turn off the -48V DC power supply of the equipme


nt room.
Sample Networking
Data Planning Priniciples
 MCC VLAN :
( 1 ) The MCC VLANID should be within the ra
nge of 3001 - 4093. The U31 NMSVLAN will aut
omatically shield these values to prevent the co
nflict between the management VLAN and the s
ervice VLAN.
( 2 ) The service VLAN ID should be within th
e range of 100 - 3000.
Data Planning Priniciples
 IP Address of NE
( 1 ) The IP address of the NE should be the same wi
th that of the loopback address
( 2 ) The IP address of the NE (the loopback address
) should be unique in the entire network (Here, the entir
e network refers to the network related to the service).
 IP Address of MCC Port
( 1 ) The IP addresses of the MCC ports of each link (or
the IP addresses of the service ports) must belong to th
e same network segment.
( 2 ) The IP of different links should belong to diffrent n
etwork segments
System File Preparation
 The software program, configure file and other dat
a file of ZXCTN Serial product 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)
 Flash/data/ other data
 Flash/db/ database for the agent
 Flash/dataset/ New version of Agent startup file
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.
 Select 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 equip
ment.

 Step4: Create new configuration script.


 After the equipment is restarted normally, input the commands of c
onfiguration script in the global mode (configuraiton mode). See the
next section for detailed configurations.

 Step5: Get back to the Privileged mode and use the "w
rite" command to save the configuration.
Initialization Procedure
 Step6: Verify the result.
 From the NMS PC, ping the IP address of each NE and the man
agement IP address of each optic port to check whether the MC
C channel is OK.
 Check the configuration information of each NE: ZXR10#show ru
n
 Check the interface information of each NE: ZXR10#show interfa
ce vlan ***
 Use the TELNET command to log in the IP address of the NE an
d 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. T
his command mode is the User Mode
 ZXR10>en ( Password : zxr10 )
 ZXR10#
 //After logging in the equipment, a command window with # is show
n. This commnad mode is the Privileged Mode.
 ZXR10#configure terminal //You can input "con t", and use the
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
 TELNET log-in can adopt 3 modes:
 the remote mode of using Qx&MCC chan
nel,
 the local mode of using LCT,

 the mode of using common serivce interfa


ces.
TELNET Log-in Configuration
 naming the site

hostname 6100-NE1
 Configure the username, password and priority for telnet to log-in t
he equipment:Generally, the who/who combination is used as the u
sername/password, and the ptn/ptn is not used. After the log-in, the
command mode is the Global mode.The "zte/ecc"combination is us
ed by the user with the highest priority. After the log-in, the comma
nd 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 t
o 16 users to log in a NE at the same time.

multi-user configure
Alarm Information Report Configuration
 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 segmen
t. 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 the
NMS via the TRAP in the SNMP protocol. The TRAP message contain
s the IP of the sending end. The NMS can get to know the correspondi
ng NE according to this IP.
 snmp-server trap-source 1.1.1.1
Alarm Information Report Configuration
 Turn on the switch for the alarm reporting of the N
MS.
 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
 Report Alarm Level
 ZXCTN equipment can report 8 levels of alarms. The bi
gger 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.
 Alarm level can be checked via the command "show log
ging cur"

logging trap-enable informational
 Configure the alarm report time as "Beijing Time"

clock timezone BEIJING 8
Loopback Address Configuraiton
 Loopback Address Configuration
 interface loopback1
 ip address 1.1.1.1 255.255.255.0
 exit
NMS Interface Configuration
 If the NMS interface is the Qx port:
 interface qx_4/1
 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 belon
g to the same network segment.
IP Address MCC Monitoring Configuration
 Configuring MCC Monitoring VLAN
 vlan 4090
 exit
 Configuring the IP address of the layer-3 interface
that corresponds to this VLAN
(i.e. the IP address of the NMS monitoring chann
el)
 interface vlan 4090
 ip address 190.168.0.2 255.255.255.0
 exit
Layer-3 Port Property Configuration (take NE
1 as example)
 Layer-3 port property configuration: used to config
ure the working modes of the MCC channel. Adopt
"trunk mode" can let the NMS communication pac
kets be forwarded freely among the MCC ports.
 interface xgei_11/1
 mcc-vlanid 4090 #Create the association between t
he service port and the MCC-VLAN.
 mcc-bandwidth 2 #Available configuraitons: MCC ch
annel 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
 Routing notification configuration:
 Ip route X.X.X.X 255.255.255.255 X.X.X.X
 Ip route X.X.X.X 255.255.255.255 X.X.X.X
 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

También podría gustarte