Escolar Documentos
Profissional Documentos
Cultura Documentos
Log Service
Version 3.09.30
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
20100705
R1.1
20100830
R1.2
20100926
Contents
Preface.............................................................. I
Overview ...........................................................1
Log Types ...................................................................... 1
Log Collection Methods.................................................... 2
Log Collection Principles .................................................. 2
Log Format Description ................................................... 3
KPI Log ..................................................................... 3
Associated Log ........................................................... 3
System Log ............................................................... 4
MR Log ..................................................................... 4
IMSI Log ................................................................... 4
DSP Black Box ........................................................... 5
Number of Log Files ........................................................ 5
File Path .................................................................... 5
Modification Methods................................................... 5
Software Installation Flow................................................ 6
Figures ............................................................ 69
Tables ............................................................. 71
II
Glossary .......................................................... 73
III
IV
Preface
Purpose
Thank you very much for choosing the UMTS wireless access system of ZTE Corporation!
The UMTS wireless access system of ZTE is a 3G mobile communication system developed on a basis of the UMTS technology. It
features strong capability in CS and PS service processing and provides diversified services. Compared with GSM, UMTS delivers a
wider range of telecommunication services, including such multimedia services as voice, data, and image transmission, with higher
rate and resource utilization ratio.
ZXWR RNC, a new generation radio network controller in the ZTE
UMTS V3 family, delivers functions of system access control, security mode control, mobility management, and radio resource management and control, etc.
ZXWR RNC provides all the functions defined in the 3GPP
R99/R4/R5/R6/R7 protocol, and offers Iu, Iub, and Iur series
standard interfaces, which enable it to connect with CNs, RNCs,
and Node Bs from different manufacturers.
Developed on a basis of ZTE all IP unified hardware platform,
ZXWR RNC features a distributed design, separating control plane
and user plane as well as interface and application. It supports
ATM/IP dual protocol stack and can smoothly evolve to full IP
UTRAN.
What is in This
Manual
Summary
Chapter 1, Overview
II
Chapter
Summary
Chapter
Overview
Table of Contents
Log Types ..........................................................................
Log Collection Methods........................................................
Log Collection Principles ......................................................
Log Format Description .......................................................
Number of Log Files ............................................................
Software Installation Flow....................................................
1
2
2
3
5
6
Log Types
During the operation, ZXWR RNC generates a lot of running log
information. Collecting, recording sorting, totaling, and storing
these log information can effectively help the maintenance personnel to analyze the overall operation status of ZXWR RNC system.
At present, ZXWR RNC provides three types of log services: System log, KPI log, associated log, MR log, IMSI log, and DSP black
box.
System log
System log is used to record the operation information of the
subsystems and boards in ZXWR RNC system.
KPI log
KPI log is used to record the value of KPI in ZXWR RNC system,
for the convenience of observing and locating the problem related to the system performance.
Associated log
Associated log is used to record the detailed processing information about the signaling flow of ZXWR RNC system. For
example, the processing information of each calling flow in the
case of large traffic.
Supposing that the signaling flow processing fails, the maintenance personnel can find the related associated log information, viewing the processing records and locating the fault
cause.
MR log
MR log is used to record the measurement data related to
ZXWR RNC performance, including data of UE coverage, UE
position, cell common measurement.
IMSI log
IMSI log is related to the use of system signaling trace tool.
When users trace the signaling of a designated IMSI through
the signaling trace tool, the log management automatically
saves the related IMSI signaling data and forwards to the signaling trace software.
The log service software receives and stores the log information from the ZXWR RNC. When writing the logs, the log service
software stores the logs as different log files according to the
type, name rule, and save path.
Chapter 1 Overview
KPILOG-YYYYMMDDHH-
Associated Log
Associated log contains two types: Associated log index file and
associated log code stream file.
The format of the associated log index file name is ASSLOGYYYYMMDDHHMMSS***.log, and *** indicates MSEL.
The sample of the associated log index file name is as shown
in Figure 2.
FIGURE 2 SAMPLE OF ASSOCIATED LOG INDEX FILE NAME
System Log
The format of the system log file name is SYSLOG-VX.XX.XXXYYYYMMDDHHMMSS***.log, and VX.XX.XXX indicates the produce version number and *** indicates MSEL.
The sample of the system log file name is as shown in Figure 4.
FIGURE 4 SAMPLE OF SYSTEM LOG FILE NAME
MR Log
The format of the MR log file name is ZTE_ MRR_UMTS_RNCID_YYYY-MM-DD-HH-MM-SS.dat .tar.gz. ZTE_ MRR_UMTS indicates the file head, which is permanent, YYYY-MM-DD-HH-MM-SS
indicates the time, RNCID indicates the RNC ID, and dat.tar.gz
indicates the log file is the compressed data file.
The sample of MR log file name is as shown in Figure 5.
FIGURE 5 SAMPLE OF MR LOG FILE NAME
IMSI Log
The format of the IMSI log file name is OBJTYPE.OBJID.BOARDIP.YYYYMMDDHHMMSS.tlog. OBJTYPE indicates the
object type, OBJID indicates the ID that the selected object
type corresponds to, BOARDIP indicates the IP ID of the board,
YYYYMMDDHHMMSS indicates the times that the log generates,
and tlog indicates the suffix of the log.
The relationship between OBJTYPE and OBJID is as shown in Table
1.
TABLE 1 RELATIONSHIP BETWEEN OBJTYPE AND OBJID
OBJTYPE
OBJID
UE
CELL
CELLID
NODEB
NODEBID
Chapter 1 Overview
File Path
The configuration file is located under bin/conf/LogService.conf. When the parameters are modified, the related
configurations automatically take effect automatically five minutes
later without the need to restart the log service software.
Modification Methods
Open the LogServer.conf file to modify the related parameters.
# The line beginning with # is a not eline.
# This is a configuration file of RNC log server.
# BEGIN
# Disk drive, only supporting the root directory settings:
RNCLOG_DIR = C:
# System log file Qty. (101000), Size (1024-10240 Kbyt
e):
SYSLOG_FILE_NUM = 100
SYSLOG_FILE_SIZE = 3072
# KPI log file Qty. (10-1000), Size (2048-10240 Kbyte):
KPILOG_FILE_NUM = 100
KPILOG_FILE_SIZE = 3072
# Associated log file Qty.
Kbyte):
ASSLOG_FILE_NUM = 500
ASSLOG_FILE_SIZE = 10240
# Associated log index file Qty. (10-1000), Size (1-5120
Kbyte):
ASSINDXLOG_FILE_NUM =100
ASSINDXLOG_FILE_SIZE = 5120
# Associated log code stream file Qty. (10-1000), Size (102
4-20480 Kbyte):
ASSCODELOG_FILE_NUM = 50
ASSCODELOG_FILE_SIZE = 20480
# Associated log guarantees 1:1 or not (set as 1 to guaran
tee associated log code stream file to correspond to associ
ated log index file by 1:1. Otherwise, set as 0):
ONEINDEX_AND_ONECODE = 1
# IMSI file Qty. (10-500), Size (4096-5120 Kbyte):
IMSILOG_FILE_NUM = 500
IMSILOG_FILE_SIZE = 4096
# MR log file Qty. (100-1000), Size (1024-30720 Kbyte):
MRLOG_FILE_NUM = 500
MRLOG_FILE_SIZE = 20480
# RNCID in file to store MR log file:
RNCID = 0
# END
Chapter 1 Overview
Chapter
SBCX Board
Table of Contents
Function Description ........................................................... 9
Panel Description...............................................................10
Working Principles .............................................................14
Slot Requirements .............................................................16
Networking Mode...............................................................16
Function Description
In actual applications, the Log Service software is running on the
SBCX board of RNC. One of the SBCX board functions is to collect
RNC log information and generates the log file as required. Thus,
the maintenance personnel can view the log information and increase the speed and capacity to locate the fault.
Panel Description
Board Structure
FIGURE 9 SBCX PANEL
10
Indicators
The colors and functions of indicators on SBCX panel are as shown
in Table 1. The statuses of indicators indicate the running status
of the SBCX CPU, power supply and the hard disk.
TABLE 1 INDICATORS ON SBCX PANEL
S.N.
Name
Color
Description
ENUM
Yellow
RUN
Green
Flashing slowly
indicates that
the board
is running
normally.
ACT
Green
M/S indicator.
ON indicates
the board is
master and OFF
indicates the
board is slave.
11
S.N.
Name
Color
Description
ALM
Red
Board alarm
indicator. ON
indicates there
is alarm on the
board and OFF
indicates there
is no alarm on
the board.
HD
Green
Hard disk
indicator. ON
indicates that
the board can
not be plugged.
PWR
Green
Power supply
indicator. ON
indicates that
the board 5
V and 3.3 V
power inputs
are normal.
SAS1
Green
ALM1
Yellow
SAS2
Green
10
ALM2
Yellow
Buttons
The buttons on SBCX panel are as shown in Table 2.
12
Button
Function
Slot No.
EXCH
M/S switch
S1A3
RST
Board reset
S1A4
PWB
S1A2
ENUM1
ENUM2
Interfaces
TABLE 2 INTERFACES ON SBCX PANEL
Location
Interface
Direction
Description
Logic Network
Interface
SBCX
front
board
SAS
hard
disk interface
1
Bidirectional
Interface of SAS
hard disk 1 with
SAS subcard
None
SAS
hard
disk interface
2
Bidirectional
Interface of SAS
hard disk 2 with
SAS subcard
None
KB
Rx
Keyboard interface
None
MS
Rx
Mouse interface
None
VGA
Tx
Display interface
None
USB1
Bi-directional
USB interface
None
USB2
Bi-directional
USB interface
None
13
Location
Interface
Direction
Description
Logic Network
Interface
RSVB
rear
board
OMC1
Bi-directional
External Gigabit
Ethernet interface
eth3
OMC2
Bi-directional
External Gigabit
Ethernet interface
eth4
OMP1
Bi-directional
External 100M
Ethernet interface,
connecting OMM
NM internal
network
eth6
HEART1
Bi-directional
External 100M
Ethernet interface
eth1
HEART2
Bi-directional
External 100M
Ethernet interface
eth2
RS232
Bi-directional
Debugging serial
interface machine
eth5
USB1
Bi-directional
USB interface
None
USB2
Bi-directional
USB interface
None
100 M
control
plane/FE
Bi-directional
Connecting the
control plane port
of UIM board of
the switching
unit through the
backplane
eth0
Backplane
Working Principles
The principle diagram of the SBCX is as shown in Figure 11.
14
CPU
CPU includes dual-CPU, south/north bridge chip, memory, hard
disk, and two SAS subcards. Two SAS hard disks can be inserted through the subcard interface and configured as RAID1.
Meanwhile, it provides the external interfaces, including VGA
display interface, PS/2 mouse interface, keyboard interface,
four USB interfaces, control plane FE electrical interface, two
GE interfaces, and three FE interfaces.
15
Slot Requirements
Each SBCX board occupies two specific slots on the switching shelf,
control shelf, resource shelf, and BGSN, as shown in Table 3.
TABLE 3 SLOT REQUIREMENTS
Shelf
Available Slot
Support M/S
or Not
Remarks
BPSN switching
shelf
1/3
Yes
BPSN070200
(PCB version
4) and latter
versions
BCTC control
shelf
1/3/5/7/11
No
BCTC060201
(PCB version
3) and former
versions
1/3/5/7/11/13/
15
Slot 1/3/5/7
supports M/S,
while Slot
11/13/15 does
not support
M/S.
BCTC060201
(PCB version
3) and latter
versions
BUSN resource
shelf
1/3/5/7/11/13
No
None
BGSN
1/3/5/7
No
None
Networking Mode
FIGURE 12 NETWORKING OF SBCX
16
Chapter
Install Linux OS
Table of Contents
Preparations .....................................................................17
Steps for Linux OS Installation ............................................17
Check for Linux OS Installation............................................21
Preparations
Context
Steps
Set the BIOS of the SBCX board, to modify the booting order and
startup order when the system starts. Thus, the system can start
easily from USB hard disk and enter the installation interface of
the Linux OS.
1. Power on and start the SBCX board.
2. During the startup, press Delete to enter the BIOS setup interface of the board.
3. On BIOS SETUP UTILITY interface, select Boot tab.
4. On Boot tab, select
pops up.
Click
OF STEPS
The system startup order is set to start from the USB CD.
Context
17
Steps
Disk
SAS(sda)
Mounting
Point
System
Type
Size
/boot
ext3
swap
swap
ext3
/home
ext3
Remaining
8. Click Next and the system enters Boot Load Program Configuration interface.
Keep the default setting of
Select
tem.
Select
9. Click Next and the system enters Configure Prior Boot Load
Program Option interface.
Select
18
as
Installation Location
Note:
If the option is /dev/sdb Master Boot Record (MBR), change the
booting order. Select SATA harddisk menu and drag it to the
first. Confirm the modification and then continue with the
installation.
10. Click Next and the system enters Network Configuration,
where the hardware and configurations of the network devices
are set.
Check
eth3
Uncheck
Check
and click
Edit.
Manually.
Note:
IP address and network mask listed in this section is just
an example. Fill in IP address and netmask according to
the actual cases.
Check
Manual
in
Hostname.
No firewall.
Disable
SELinux.
English (USA).
15. Click Next and the system enters Time Zone Selection interface. Select the time zone according to the actual cases.
Uncheck
16. Click Next and the system enters Set Root Password interface. Enter the password twice and the setting takes effect
immediately.
17. Click Next and the system enters Package Group Selection
interface. Select Customize the software package to install.
The software packages to install (the software packages are
not required under level-2 directory are default) include:
19
X Window System
GNOME Desktop Environment
Editors
Server configuration tool
Windows File Server
FTP Server
Network Server
Extra Software Packages
vnc-server - VNC Server
dhcp - DHCP Server and Forward Agent
Remaining Network Server
Extra Software Packages
tftp-server - TFTP Server
telnet-server - Server Program Used for telnet Remote Login
Protocol
Development Tool
Previous Software Development
Management Tool
System Tool
Extra Software Packages
ethereal - Network Traffic Analyzer
nmap - Network Search Tool and Security Scanner
sysstat - sar and iostat System Monitor Command
18. Click Next and the system enters Ready to Install interface.
19. Click Next and the system enters Required Installation
Medium interface. Insert the installation CD.
20. Click Next and the system prompts to insert different CDs. Operate according to the wizard. the installation may take about
0.51 hour, which depends on how many software packages
are installed and how fast the machine is.
21. After the installation completes, remove the installation CD and
restart the machine.
22. Set the BIOS of the machine, cancelling to start from the driver.
23. Restart and the system enter Welcome interface.
24. Click Next and the system enters License Agreement interface. Check yes, I accept the license agreement.
25. Click Next and the system enters Date and Time interface.
Set the date and time for the server.
26. Click Next and the system enters Display interface. Keep the
default settings.
27. Click Next and the system enters Red Hat Network Login
interface. Check Please tell me why to register and provide one
Red Hat login accountant.
20
28. Click Next and the system enters Why to register interface.
Check I can not register now. Please remind me later.
29. Click Next and the system enters Initialization interface.
later, License interface pops up and select Accept.
30. Click Next and the system enters System User interface. Create the root user.
User name: root
Full name: root
Password: ******
Confirm the password: ******
31. Click Next and the system enters Audio Card interface. Keep
the default settings.
32. Click Next and the system enters Extra Disk interface. Keep
the default settings.
33. Click Next and the system enters End of Installation interface.
34. Click Next and the system enter the graphic login interface.
END
OF STEPS
21
22
Chapter
Configure System
Table of Contents
Configuration Guide ...........................................................23
Configure User ..................................................................24
Configure FTP Services.......................................................33
Configure Telnet Services ...................................................36
Configure VNC ..................................................................41
Configure Network Interface ...............................................49
Configuration Guide
After Linux OS installation completes, perform some configurations
for OS, to get prepared for the operation of log service software.
The configuration order is as shown in Figure 13.
FIGURE 13 OPERATION SYSTEM CONFIGURATION GUIDE
23
Configure User
This section introduces how to configure users required in the system operation, and how to add the user into the related user group.
Prerequisites
Steps
24
3. Create New User dialog box pops up, as shown in Figure 16.
Enter the information of zte user.
FIGURE 16 CREATE NEW USER DIALOG BOX
25
6. Select Groups tab. Tick FTP and telnet to add the zte user
into these two groups, as shown in Figure 19.
26
OF STEPS
A new zte user is added into both FTP and telnet user group.
To add RNCV3PM user for OMM NM software to obtain the performance data through FTP mode.
Note:
This operation is only used when an anonymous user can not obtain the performance data.
Prerequisites
Steps
27
3. Create New User dialog box pops up, as shown in Figure 22.
Enter the information of RNCV3PM user.
28
29
6. Select Groups tab. Tick FTP and root to add the RNCV3PM
user into these two groups, as shown in Figure 25.
30
OF STEPS
Result
A new RNCV3PM user is added into both FTP and root user group.
Postrequisite
Supposing that OMM NM software requires obtaining the performance data through the RNCV3PM user, configure the following
settings at the server end where OMM software is installed:
1. Open the file of womc-cm-rnc-FTPinfo.xml under the
directory
of
$Home\ZXWR-OMCRB\WOMC\ums-svr\zxwomc\RNS\RNC\zxwomc-common-rnc-api.par\conf.
2. Use the following commands to modify the values of User and
Password as RNCV3PM.
<BLADESVRFTP>
<User>RNCV3PM</User>
<Password>********<Password>
</BLADESVRFTP>
3. Restart OMM server to obtain the performance data through
the user name of RNCV3PM and the preset password.
31
Steps
32
OF STEPS
vsFTPd,
as
33
OF STEPS
If you can not start the FTP server with the above methods, try
entering the command at the terminal, as shown in Figure 30.
FIGURE 30 STARTING FTP SERVICES THROUGH COMMAND LINE
34
Steps
3. Access FTP system as root users, zte user, and RNCV3PM user
respectively, as shown in Figure 32.
FIGURE 32 TESTING FTP ACCESS
35
Note:
Usually, the default FTP port is 21. If the port has been modified, recover it with the following method:
Add
END
Result
OF STEPS
36
Status.
37
Status.
8. Click
END
OF STEPS
Result
After the above commands are executed, all Telnet services have
been started.
Postrequisite
To start Telnet service with the command line, perform the following operations:
1. Access Linux OS as root user.
2. Choose Applications > System tools > Terminal, as shown
in Figure 35.
FIGURE 35 SELECTING TERMINAL
38
= yes
and mod-
39
Steps
40
END
Result
OF STEPS
Configure VNC
VNC service configurations include starting VNC services and setting as activating when computer starts. After the settings, test
whether Telnet services can be accessed and used normally.
41
Status.
Stopped,
42
OF STEPS
43
VNCSERVERS=1:root.
Save
This command line is to add root user into VNC service user.
44
5. Use the following commands and enter the VNC access password for the current root user, as shown in Figure 47.
FIGURE 47 SETTING ROOT PASSWORD FOR VNC
6. Use the following command to open the file of $home/.vnc/xstartup under the main directory of the user.
[root@localhost]#vi $home/.vnc/xstartup
7. Add the following command lines into the file contents:
#!/bin/bash
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc
45
command
to
open
the
file
of
[root@localhost.vnc]#vi /etc/X11/xorg.conf
12. Find the section of Module in the file contents and add the
following command line into this section.
Load vnc
FIGURE 49 MODIFYING MODULE SECTION
46
13. Find the section of Screen in the file contents and add the following command line into this section.
Option "passwordFile" "/root/.vnc/passwd"
FIGURE 50 MODIFYING SCREEN SECTION
OF STEPS
Steps
47
48
END
Result
OF STEPS
49
Note:
Set one IP address in 128 network segment for the network interface, to Ping through the UIM board on the same shelf, thus
ensuring the normal communication with other RNC boards. Test
the six network interfaces one by one until make sure that this
network interface is the one that connects with the UIM board.
Make records of its ID.
Prerequisites
Steps
The UIM board and the OMP board are both running normally.
50
3. Select eht0 and click Edit to set its static IP address, as shown
in Figure 56.
Caution:
Do not check Automatically obtain IP address settings
with. Otherwise, Linux OS will fail to start.
51
52
END
OF STEPS
Prerequisites
Steps
The SBCX board has been correctly configured with the network interfaces.
$home
53
3. Open the file of bin/conf/Chinese/NetIf.conf under the directory of the Log Service software.
[root@localhost]vi
bin/conf/Chinese/NetIf.conf
4. Check the file according to the notes.Modify this file and set the
device name of the control plane network interface as eth0 and
the device name of OMC network interface as eth3.
#Description: Enable all network interfaces that have
been configured. The enabling order is Channel1...Chan
nelX, which is unrelated to the writing order.
[CommChannel]
Count=3
#Control plane path - UIMC interface (FE)
#No alteration
[Channel1]
ChannelName= CtrlPlane
NetIfName = eth0
IP =
NETMASK =
MacAddr =
ShareIP = 0
#Platform log UDP path - UIMC interface (FE)
#No alteration
[Channel2]
ChannelName= UdpLog
NetIfName = eth0:1
IP = 128.200.200.200
NETMASK = 255.0.0.0
MacAddr =
ShareIP = 1
#OMP-OMCR path - OMP1 interface (FE) on rear board
[Channel3]
ChannelName= OMCR
NetIfName = eth6
IP = 129.200.200.200
NETMASK = 255.0.0.0
MacAddr = 00:D0:D0:FA:1A:01
ShareIP = 1
#OMM M/S path - OMC1 interface (GE) on rear board
#The IP of the left board must be configured as 128.0.3
0.1 and of the right board must be 128.0.30.9, which is
decided by NM configurations.
54
OF STEPS
55
56
Chapter
Description
The Log Service software is running on the SBCX board, to collect
the log information and performance data.
Make sure that the Log Service software is installed correctly before running it.
Steps
The SBCX board has been correctly configured with the network interfaces.
system,
decompress
the
LogSer-
57
OF STEPS
After the restart, the Log Service software can run automatically.
Steps
The SBCX board has been correctly configured with the network interfaces.
Result
58
OF STEPS
If the results displayed contain the above three processes, the log
service software is installed correctly and is running normally.
Chapter
Steps
59
No rights,
OF STEPS
Steps
60
OF STEPS
Result
The Log Service software is not in the list of the processes that are
running currently.
Steps
The Log Service software package of the new version has been
obtained.
Result
OF STEPS
Prerequisites
Steps
61
62
OF STEPS
Log Service is running normally and at the same time, it can receive and keep the log information normally.
Chapter
Correlative Tools
Table of Contents
VNC.................................................................................63
Telnet ..............................................................................64
FTP..................................................................................66
VNC
VNC Description
When the SBCX board is running normally, the VNC SERVER that
Linux OS contains itself is in Running status. The user can install
and run the VNC CLIENT on any PC that connects with the SBCX
board, to access the SBCX board at the remote.
VNC Instructions
Short Description
Prerequisites
Steps
To install the VNC CLIENT on the user PC, connecting with the
VNC SERVER that runs on the SBCX board and accessing the SBCX
board at the remote.
63
4. Click Connect.
5. VNC Authentication dialog box pops up. Enter the password
for the remote access in Session password, as shown in Figure
60.
FIGURE 60 VNC AUTHENTICATION DIALOG BOX
6. Click OK.
END
Result
OF STEPS
The system returns to the remote desktop that the access succeeds. The user can implement all controls through the remote
desktop.
Telnet
TELNET Description
When the SBCX board is running normally, the Telnet service that
Linux OS contains itself is in Running status. The user can run the
Telnet on any PC that connects with the SBCX board, to access
the SBCX board at the remote, install, use and maintain the Log
Service software.
64
TELNET Instructions
Abstract
Note:
For the system security, the system only allows the common users
to access the Linux OS at the remote through the Telnet. If the
common user wants to execute the root rights, apply to the persons with the related rights for the account.
Prerequisites
Steps
3. After the connection succeeds, enter the user name and password.
65
END
Result
OF STEPS
FTP
FTP Description
When installing, maintaining and upgrading the Log Service software, it is necessary to upload the file to the SBCX board through
FTP.
With the FTP client tool software or the FTP client that the Windows
contains itself, the users can upload and download the files.
FTP Instructions
Prerequisites
Context
Note:
This section takes the software at the FTP client as the example to
introduces how to use the FTP.
66
Steps
1. On the user PC, open the software at the FTP client, as shown
in Figure 63.
FIGURE 63 OPENING FTP SOFTWARE AT CLIENT
END
OF STEPS
67
Result
68
Figures
69
70
Tables
71
72
Glossary
BCTC
- Backplane of ConTrol Center
BGSN
- Backplane of Giga universal Service Network
BIOS
- Basic Input/Output System
BPSN
- Backplane of Packet Switch Network
BUSN
- Backplane Of Universal Service Network
FTP
- File Transfer Protocol
GE
- Gigabit Ethernet
KPI
- Key Performance Indicators
OMC
- Operation & Maintenance Center
OMM
- Operation & Maintenance Module
RAID
- Redundant Array of Independent Disks
RSVB
- Rearcard of SerVe Board
SBCX
- X86 Single Board Computer
VGA
- Video Graphic Adapter
VNC
- Virtual Network Computing
73