ZXONE 8X00 SOSCB Board Common Command

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 47

Internal Use Only▲

ZXONE 8X00 SOSCB Board Common Command


Description V1.1
Zhang Qiao (ID: 00092118)

1 Common Commissioning
Commands Provided by the
Framework

1.1 Logging into the SOSCB

Log in to the SOSCB through telnet or serial interfaces.

Through telnet: run the telnet 192.168.1.12 9023 command (192.168.1.12


indicates the actual IP address of the SOSCB).
Login: zte
Password: zte

Then, you enter the admin shell. Run the cd 0 or sh 0 command to enter
the management process shell. Run the cd 1 or sh 1 command to enter the
app shell, as shown in the following figure.

Figure 1-1 admin shell

All Rights reserved, No Spreading abroad without Permission of ZTE 1


Internal Use Only▲

Figure 1-2 Management process shell

Figure 1-3 app shell

When the actual IP address of the SOSCB is unknown or the telnet


operation fails, you can try logging in to the SOSCB through serial
interfaces. The connection configuration for login through serial interfaces is
described in the following figure.

All Rights reserved, No Spreading abroad without Permission of ZTE 2


Internal Use Only▲

Figure 1-4 Configuring Parameters in Case of Logging in to the SOSCB


through Serial Interfaces

1.2 Checking All the JOB Information


[M2SOSCBD4APP1.bin]#Showalljob

Figure 1-5 All the JOB Information Registered

1.3 Checking All the Tasks


[M2SOSCBD4APP1.bin]#Showalltask

Figure 1-6 Private Tasks Enabled

All Rights reserved, No Spreading abroad without Permission of ZTE 3


Internal Use Only▲

1.4 Checking the Board Production Information


[M2SOSCBD4APP1.bin]#GetBoardInfor

Figure 1-7 Checking the Board Production Information

All Rights reserved, No Spreading abroad without Permission of ZTE 4


Internal Use Only▲

2 Private Commands under APP


SHELL

2.1 Checking the System Status


[M2SOSCBD4APP1.bin]# sysstate

The options for the running status of the system are: normal, alarm, not
configured, self-check failure and so on.

Figure 2-8 Running Status of the System

2.2 Checking the Version Information

There are two ways to check the version information:


[M2SOSCBD4APP1.bin]# modulever
[M2SOSCBD4APP1.bin] #version

Figure 2-9 Running the modulever Command to Query the Version Information
of the Module

All Rights reserved, No Spreading abroad without Permission of ZTE 5


Internal Use Only▲

Figure 2-10 Running the version Command to Query the Version Information
of Each Operating Component in the Board

2.3 Checking and Modifying the Production


Sequence Information

Run the following command to check the production sequence information:


[M2SOSCBD4APP1.bin]#GetBoardInfor

Figure 2-11 Checking the Board Production Sequence Information

Run the following commands to modify the production sequence


information:
[M2SOSCBD4APP1.bin] #Usr_SetBrdPhyInfo(0x101,2) /* Nx*/
[M2SOSCBD4APP1.bin] #Usr_SetBrdPhyInfo(0x102,2) /* Mx*/
[M2SOSCBD4APP1.bin]# Usr_SetBrdPhyInfo(0x103,0x0025) /* YYY*/
[M2SOSCBD4APP1.bin] #Usr_SetBrdSN_PN_PCBInfo
("SN1-111111111","PN2-222222222","PCB:10-07") /* PN/SN/PCB */

Check the production sequence information after the modification.

All Rights reserved, No Spreading abroad without Permission of ZTE 6


Internal Use Only▲

Figure 2-12 After Modifying the Production Sequence Information

2.4 Checking the LINK Status of the Port


[M2SOSCBD4APP1.bin]#links

Figure 2-13 Checking the link Status of 8 Ports

2.5 Checking and Setting the Communication


Configuration Information of 8 Ports
[M2SOSCBD4APP1.bin]#ipcfg

Description: The above command is executed to query the communication


configuration information of 8 ports and the NE IP address.

All Rights reserved, No Spreading abroad without Permission of ZTE 7


Internal Use Only▲

[M2SOSCBD4APP1.bin#]ipcfg [index ipaddr mask areaid type]

Description: The above command is executed to modify the IP address,


mask, area ID, and port type of the port.
[M2SOSCBD4APP1.bin]#ipcfg [index 0]

Description: The above command is executed to clear the configuration


information of one port.
[M2SOSCBD4APP1.bin]#ipcfg [ ipclr]

Description: The above command is executed to clear the configuration


information of all ports.

Note: when the NE can manage the SOSCB properly, the modifications by
the ipcfg command cannot take effect after the board is reset.

Figure 2-14 Communication Configuration Information and agent ip Information


of 8 Ports

Figure 2-15 Modifying the Configuration Information of Port 7

Check the configuration information after the modification.

Figure 2-16 Clearing the Configuration of Port 6

All Rights reserved, No Spreading abroad without Permission of ZTE 8


Internal Use Only▲

Check the configuration information after the modification.

Figure 2-17 Clearing the Configuration of 8 Ports

Check the configuration information after the modification.

All Rights reserved, No Spreading abroad without Permission of ZTE 9


Internal Use Only▲

2.6 Checking and Setting the Communication


Configuration Information of 48 Ports
[M2SOSCBD4APP1.bin]#esccfg

Description: The above command is executed to query the communication


configuration information of 48 ports.
[M2SOSCBD4APP1.bin]#esccfg [id ipaddr mask areaid type]

Note: Description: The above command is executed to modify the IP


address, mask, area ID, and port type of the port.
[M2SOSCBD4APP1.bin]#esccfg [id 0]

Description: The above command is executed to clear the configuration


information of one port.
[M2SOSCBD4APP1.bin]#esccfg [escclr]

Description: The above command is executed to clear the configuration


information of all ports.

Note: If IP address of electrical supervision port 1 or 4 is modified on the


EMS, the modification by the essccfg command will be covered. In other
cases, the modification still take effect after the board is reset.

Figure 2-18 Communication Configuration Information of 48 Ports

All Rights reserved, No Spreading abroad without Permission of ZTE 10


Internal Use Only▲

Figure 2-19 Modifying the Configuration Information of Port 56

Check the configuration information after the modification.

Figure 2-20 Clearing the Configuration of Port 53

All Rights reserved, No Spreading abroad without Permission of ZTE 11


Internal Use Only▲

Check the configuration information after the modification.

Figure 2-21 Clearing the Configuration of 48 Ports

All Rights reserved, No Spreading abroad without Permission of ZTE 12


Internal Use Only▲

Check the configuration information after the modification.

All Rights reserved, No Spreading abroad without Permission of ZTE 13


Internal Use Only▲

2.7 Reading and Writing the IIC

Iicrd: This command is executed to read the IIC device register.

Iicwr: This command is executed to write the IIC device register.

Figure 2-22 Checking the EEPROM Register

All Rights reserved, No Spreading abroad without Permission of ZTE 14


Internal Use Only▲

Figure 2-23 Checking the 1388 Register

Figure 2-24 Checking the SFP A0 Register

All Rights reserved, No Spreading abroad without Permission of ZTE 15


Internal Use Only▲

Figure 2-25 Checking the SFP A2 Register

2.8 Reading and Writing the Register

Memd: This command is executed to read the register.

Memw: This command is executed to write the register.

The address range supporting access is: 0x67000000 ~ 0x6e200000.

Figure 2-26 Reading and Writing the Register

All Rights reserved, No Spreading abroad without Permission of ZTE 16


Internal Use Only▲

2.9 Reading and Writing the PHY

PhyRead: This command is executed to read the DP, 5248 and 8305 PHY.

PhyWrite: This command is executed to write the DP, 5248 and 8305 PHY.

Figure 2-27 Reading the DP83640 register

Figure 2-28 Reading the 5248 Register

Figure 2-29 Reading the 8305 Register

All Rights reserved, No Spreading abroad without Permission of ZTE 17


Internal Use Only▲

2.10 Checking the Configuration Information of


the PPS+FE Port
[M2SOSCBD4APP1.bin]# PpsInfo

Figure 2-30 Configuration Information of the External Time Port

2.11 Checking the Configuration Information of


the PTP Port
[M2SOSCBD4APP1.bin]# PtpPort 0

Figure 2-31 Configuration Information of 5 PTP Ports

All Rights reserved, No Spreading abroad without Permission of ZTE 18


Internal Use Only▲

All Rights reserved, No Spreading abroad without Permission of ZTE 19


Internal Use Only▲

All Rights reserved, No Spreading abroad without Permission of ZTE 20


Internal Use Only▲

2.12 Checking the Send Packet Number and


Receive Packet Number on the PTP Port
[M2SOSCBD4APP1.bin]# PtpPktNum para1 para2

The Para1 parameter is the flag of send or receive packet. The value 0
indicates the send packet while the value 1 indicates the receive packet.

The Para2 parameter is the flag of port. The value from 1 to 4 indicates
optical ports from 1 to 4, and the value 5 indicates the FE electrical port.

All Rights reserved, No Spreading abroad without Permission of ZTE 21


Internal Use Only▲

2.13 Checking the IRQ2 Statistics

Figure 2-32 SMI Interrupts Counts

All Rights reserved, No Spreading abroad without Permission of ZTE 22


Internal Use Only▲

All Rights reserved, No Spreading abroad without Permission of ZTE 23


Internal Use Only▲

2.14 Checking the IRQ4 Statistics

Figure 2-33 PPS In/Out Interrupts Counts

2.15 Checking the ZDP Statistics

Figure 2-34 ZDP Statistics of 6 Ports

2.16 Checking the Multicast Route Information

Figure 2-35 Multicast Route Information

All Rights reserved, No Spreading abroad without Permission of ZTE 24


Internal Use Only▲

2.17 Checking the PPPOE Statistics

Figure 2-36 PPPOE Statistics of 6 Ports

All Rights reserved, No Spreading abroad without Permission of ZTE 25


Internal Use Only▲

2.18 Checking the PPP Statistics

Figure 2-37 PPP Statistics of 6 Ports

All Rights reserved, No Spreading abroad without Permission of ZTE 26


Internal Use Only▲

2.19 Checking the GNE Information

Figure 2-38 GNE Information and NAT Information

2.20 Enable the Packet Sending/Receiving


Switch on the S Port

During the fault location, you should check the packets on the S port
frequently. The common packet sending/receiving switch on the S Port is
provided here. The called S port packets indicate those responded by CPU
of the SOSCB. However, the packets received by CPU of the SOSCB
cannot be printed (you can check the packets sent and received by the
SOSCB through capturing the agent packets). To check the S port packets
of other service boards passing by the SOSCB, perform the mirroring
function. When this function is not needed, please disable it.

All Rights reserved, No Spreading abroad without Permission of ZTE 27


Internal Use Only▲

[M2SOSCBD4APP1.bin] Usr_SetPrintScmdtext(1) Enable

[M2SOSCBD4APP1.bin] Usr_SetPrintScmdtext(0) Disable

2.21 Checking the Queue Property

The communication between processes of the SOSCB is by means of


queue. You can run the mqgetattr command to check the queue property.

2.22 Querying the Board Type

2.23 Querying Important Data of the Board

You can also query the important data on the EMS, as shown in the
following figure. The result is consistent.

All Rights reserved, No Spreading abroad without Permission of ZTE 28


Internal Use Only▲

2.24 Querying Private Important Data of the


Board

All Rights reserved, No Spreading abroad without Permission of ZTE 29


Internal Use Only▲

2.25 Checking the Memory

All Rights reserved, No Spreading abroad without Permission of ZTE 30


Internal Use Only▲

2.26 Querying the Used Space of the FLASH

2.27 Querying the CPU Usage

All Rights reserved, No Spreading abroad without Permission of ZTE 31


Internal Use Only▲

2.28 Querying the Running Time of the Board

All Rights reserved, No Spreading abroad without Permission of ZTE 32


Internal Use Only▲

2.29 Querying the Performance Alarm Status

2.30 Querying the FPGA Loading Status

All Rights reserved, No Spreading abroad without Permission of ZTE 33


Internal Use Only▲

2.31 Querying the FPGA ID

2.32 Querying the SFP Online Status

2.33 Querying the LOS Status of the Optical


Port

2.34 Querying the Status of the Laser Switch

All Rights reserved, No Spreading abroad without Permission of ZTE 34


Internal Use Only▲

2.35 Querying the Test Tooling Result: (to be


Determined)

Currently, test tooling only supports testing the 21M clock loopback and
Ethernet communication. If the return result is 1, it indicates that the test is
passed; if the return result is 2, it indicates that the test is not passed. For
detailed information, refer to Description of Interfaces for the Test of
Dynamically Aging ZXONE 8300 SOSCB Board.
KSH>ShowFFF4State()

Figure 2-39 Querying the Test Tooling Result

3 Common Commands under


USHELL

3.1 Logging in to the Management Process


shell

Log in to port 9023 through telnet to enter the admin shell. Then run the cd
0 or sh 0 command to enter the management process shell.

All Rights reserved, No Spreading abroad without Permission of ZTE 35


Internal Use Only▲

Figure 3-40 plat shell

3.2 Querying the Version Information of the


Module

PrintModuleVersion(1): This command is executed to check the information


about a software module registered.

PrintVersion(): This command is executed to check the management


process and the version information of the bsp.

Figure 3-41 Version Information

All Rights reserved, No Spreading abroad without Permission of ZTE 36


Internal Use Only▲

4 Common Commands under SDK


SHELL

4.1 Entering the SDK SHELL

You can log in either through telnet or through serial interfaces.

Through telnet: run the telnet 192.168.1.12 10000 command (192.168.1.12


indicates the actual IP address of the SOSCB).

Figure 4-42 Entering the BBSH

Then type 1 to enter the SDK SHELL.

Figure 4-43 Entering the SDK SHELL

If you log in to the board through serial interfaces, you can press CTRL+N
to switch to the BBSH. Then type 1 to enter the SDK SHELL.

All Rights reserved, No Spreading abroad without Permission of ZTE 37


Internal Use Only▲

Figure 4-44 Entering the SDK SHELL through Serial Interfaces

4.2 Checking the Send Packet Count and


Receive Packet Count of 9 Ports
BCM.0>g grpkt
BCM.0>g gtpkt

All Rights reserved, No Spreading abroad without Permission of ZTE 38


Internal Use Only▲

Figure 4-45 Send Packet Count and Receive Packet Count of 9 Ports

4.3 Checking the Network Route of the Chip


BCM.0>l3 defip show

Figure 4-46 Network Route

4.4 Checking the Host Route of the Chip


BCM.0>l3 l3table show

All Rights reserved, No Spreading abroad without Permission of ZTE 39


Internal Use Only▲

Figure 4-47 Host Route

4.5 Checking the L3 Interface Information


BCM.0>l3 intf show

Figure 4-48 L3 INTF Information

4.6 Checking the Mapping between the Chip


Port and Protocol Stack Port
BCM.0>portinfo

All Rights reserved, No Spreading abroad without Permission of ZTE 40


Internal Use Only▲

Figure 4-49 Mapping between Ports

All Rights reserved, No Spreading abroad without Permission of ZTE 41


Internal Use Only▲

4.7 Checking the MAC Address Related to the


Port
BCM.0>l2 show

Figure 4-50 MAC Address Table

4.8 Checking the COS Configuration


Information
BCM.0>cos show

All Rights reserved, No Spreading abroad without Permission of ZTE 42


Internal Use Only▲

Figure 4-51 COS Configuration Information

4.9 Checking the Chip Multicast Information


BCM.0>ipmc table show

Figure 4-52 Multicast Route Information of the Chip

4.10 Checking the VLAN Configuration of the


Port on the Chip
BCM.0>pvlan

All Rights reserved, No Spreading abroad without Permission of ZTE 43


Internal Use Only▲

Figure 4-53 Default VLAN IDs of 9 Ports

4.11 Checking the VLAN Information of the Chip


BCM.0>vlan show

Figure 4-54 VLAN Configuration Information of the Chip

5 Common Commands under BBSH

5.1 Logging in to the BBSH

Login through telnet: run the telnet 192.168.1.12 9023 command


(192.168.1.12 indicates the actual IP address of the SOSCB).

All Rights reserved, No Spreading abroad without Permission of ZTE 44


Internal Use Only▲

Figure 5-55 Entering the BBSH

5.2 Querying the Route Information

Figure 5-56 Route Information of the Protocol Stack

All Rights reserved, No Spreading abroad without Permission of ZTE 45


Internal Use Only▲

5.3 Checking the Startup Information of the


Board Process

All Rights reserved, No Spreading abroad without Permission of ZTE 46


Internal Use Only▲

5.4 Comparison between Common Commands


on the SOSC and SOSCB
SOSC Command SOSCB Command Notes

Because the platform is


changed, the displayed
Under BBSH, type ifconfig.
If –a content of the SOSCB is
Under APP SHELL, type ifconfig.
different from that of the
SOSC.

The two commands are


Ipcfg Under APP SHELL, type ipcfg.
the same.

The two commands are


Route Under BBSH, type route.
the same.

Under APP SHELL, type The two commands are


Static_route
static_route. the same.

Combine the SOSC’s


command gnei and
GNE Command Under APP SHELL, type gnei.
command gnei nat.

Multicast Route The two commands are


Under APP SHELL, type mr.
Command the same.

All Rights reserved, No Spreading abroad without Permission of ZTE 47

You might also like