Xcc m User Guide 2
-
Upload
emmanuel-n-onuzurike -
Category
Documents
-
view
155 -
download
15
description
Transcript of Xcc m User Guide 2
xCCM Quick Start and debug Guide
Document number: UMT/BTS/DJD/022331 Document issue: 01.06 / EN Document status: Preliminary Date: 01/Feb/2008
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
Copyright 2007 Alcatel-Lucent, All Rights Reserved
Printed in France
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is “write protected”; it may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have received this document in error, please notify the sender and destroy it immediately.
without notice. Networks assumes no responsibility for errors that might appear in t.All other brand and product
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 2/46
PUBLICATION HISTORY
29/Mar/2007
Issue 01.01 / EN, Draft
Creation, Y. Kamezac
3/Jul/2007
Issue 01.02 / EN, Draft
Modification, Y. Kamezac
- New BCI architecture
29/Jul/2007
Issue 01.032 / EN, Draft
Modification, V.Navia
- Update Erreur ! Source du renvoi introuvable. :
- Update Erreur ! Source du renvoi introuvable. :
- Update Erreur ! Source du renvoi introuvable. :
- Update Erreur ! Source du renvoi introuvable. : Add IIS contacts
18/sep/2007
Issue 01.04 / EN, Draft
Modification, E. Rossi
- 0D network configuration changes
22/Jan/2008
Issue 01.05 / EN, Draft
Modification, C Fleurot
- New BCI architecture
- Suppression of 1W xCCM module part
01/Feb/2008
Issue 01.0 / EN, Preliminary
Modification, C Fleurot
- Modification after review
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 3/46
CONTENTS
1. INTRODUCTION............................................................................................................................5
1.1. OBJECT....................................................................................................................................5
1.2. SCOPE OF THIS DOCUMENT .......................................................................................................5
1.3. AUDIENCE FOR THIS DOCUMENT ................................................................................................5
2. RELATED DOCUMENTS .................................. ............................................................................5
2.1. APPLICABLE DOCUMENTS ..........................................................................................................5
2.2. REFERENCE DOCUMENTS..........................................................................................................5
3. XCCM OVERVIEW ........................................................................................................................6
3.1. HARDWARE ..............................................................................................................................6
3.1.1 Overview .........................................................................................................................6 3.1.2 Main differences with previous CCM version..................................................................8
3.2. SOFTWARE...............................................................................................................................9
3.2.1 Overview .........................................................................................................................9 3.2.2 Linux OS........................................................................................................................10 3.2.3 File System....................................................................................................................11 3.2.4 Start up..........................................................................................................................11 3.2.5 BCI ................................................................................................................................12 3.2.6 xCCM IP addresses ......................................................................................................12 3.2.7 xCCM roadmap .............................................................................................................13
4. HOW TO.......................................................................................................................................13
4.1. DEBUG CABLE.........................................................................................................................13
4.1.1 Cable schema ...............................................................................................................13 4.2. CONNECT TO THE XCCM ........................................................................................................13
4.3. TRANSFER FILES FROM / TO THE XCCM ...................................................................................16
4.4. RUN RTC TOOLS UNDER BCI ..................................................................................................17
4.5. DISABLE / ENABLE THE LOADER................................................................................................17
4.6. INSTALL A NEW XCCM SOFTWARE...........................................................................................18
4.7. EDIT THE DLU........................................................................................................................20
4.8. CHECK THE DLU ....................................................................................................................20
4.9. DISPLAY THE DLU ..................................................................................................................21
4.10. SWITCH FROM ONE DLU TO ANOTHER......................................................................................21
4.11. GET THE BTS CONFIGURATION SUMMARY ...............................................................................21
4.12. GET THE XCCM SOFTWARE MARKING ......................................................................................22
4.13. CHECK THE XCCM HWREF ...................................................................................................22
4.14. GET / SET THE IP ADDRESS (TEMPORARY) ...............................................................................22
4.15. SET THE IP ADDRESS (PERMANENTLY) .....................................................................................23
4.15.1 Modifying the IP address...............................................................................................23 4.15.2 Modifying the subnet mask ...........................................................................................24
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 4/46
4.15.3 Modifying the IP address and subnet mask using u-boot .............................................24 4.16. ADD AN IP ROUTE ...................................................................................................................24
4.17. CAPTURE TCP/IP TRAFFIC......................................................................................................24
4.18. RESET THE BOARD..................................................................................................................25
4.19. MODIFY ENVIRONMENT VARIABLES...........................................................................................25
4.20. SEND BCI COMMAND AUTOMATICALLY AT XCCM STARTUP .......................................................25
4.21. CREATE AN ALIAS....................................................................................................................26
4.22. MODIFY BOOTARGS (IN U-BOOT) .............................................................................................26
4.23. SWAP ACTIVE/PASSIVE PARTITIONS..........................................................................................27
4.23.1 Swap active / passive partitions using BCI menu .........................................................27 4.23.2 Swap active / passive partitions using u-boot ...............................................................27
4.24. COPY U-BOOT VAR INTO PASSIVE PARTITION............................................................................27
4.25. SEE PCONS TRACES (KERNEL TRACES) IN A TELNET TERMINAL ................................................28
4.26. MOUNT A NFS PARTITION .......................................................................................................28
4.27. GET A CORE FILE AFTER AN APPLICATION CRASH ......................................................................28
4.28. GET LEC SNAPSHOTS.............................................................................................................29
4.29. GET THE IMT..........................................................................................................................30
4.30. CHECK THE ALARMS................................................................................................................30
4.30.1 Check the active alarm..................................................................................................30 4.30.2 Check the alarm still present in circular buffer ..............................................................30
4.31. CHECK ATM...........................................................................................................................30
4.32. CONNECT TO A SLAVE FROM THE XCCM ..................................................................................31
4.33. ENABLE / DISABLE SOME TRACES .............................................................................................31
4.33.1 Configuration traces ......................................................................................................31 4.33.2 Traces redirection on the console.................................................................................32
4.34. LOAD A BOOTIMAGE VIA TFTP / BOOTP.................................................................................33
4.35. START THE TIL .......................................................................................................................35
5. U-BOOT ENVIRONMENT VARIABLES....................... ...............................................................37
6. ABBREVIATIONS AND DEFINITIONS...................... .................................................................39
6.1. ABBREVIATIONS ......................................................................................................................39
6.2. DEFINITIONS...........................................................................................................................44
7. ANNEX: SAMPLE OF PLTF.BCI FILE ..................... ..................................................................45
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 5/46
1. INTRODUCTION
1.1. OBJECT
This document is a quick start guide for the xCCM.
This digital module within the iBTS is in charge of OAM management, part of call processing and internal/external data flow switching/combining.
The xCCM is an enhanced version of the current iCCM2.
The module hardware has been completely redrawn and the board is now based on a Linux OS.
1.2. SCOPE OF THIS DOCUMENT
This document will describe the specific action and debug way in ordre to startup, debug and take traces in UA5.2 nodeb software version.
1.3. AUDIENCE FOR THIS DOCUMENT
This document is dedicated to each team working with xCCM module.
2. RELATED DOCUMENTS
2.1. APPLICABLE DOCUMENTS
[A1] PPP/DDD/CCC/NNNN Title
2.2. REFERENCE DOCUMENTS
[R1] UMT/BTS/DD/016513 xCCM General Specification
[R2] UMT/BTS/DD/017769 xCCM Design Specification
[R3] UMT/BTS/DD/016040 xCCM iBTS General Software Architecture
[R4] BaseOS Command Interpreter
[R5] UMT/BTS/APP/024285 XCCM Plateform Man Machine Interface
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 6/46
3. XCCM OVERVIEW
3.1. HARDWARE
3.1.1 OVERVIEW
The next generation CCM board on the UMTS Nortel BTS is based on a versatile backhaul access. It has to support all new customer interfaces like Ethernet, STM1, E3/DS3 and any other future protocol. The xCCM is the key element of the hybrid Iub.
The xCCM project is based on a motherboard which covers OAM management, part of call processing and internal/external data flow switching/combining (baseband switching). The network interface (Iub) with the RNC is managed using an additional PTMC mezzanine card called MDA (Media Dependant Adaptor) adapted to the physical link with the RNC required by customers.
To lower the overall cost of supporting all available kind of network interfaces, a specific MDA is developed for a specific physical interface.
The Board is split in functional following a model similar to the OBSAI standard.
- Transport backhaul (MDA)
- Control (PQ3)
- Base-Band samples (BBLINK+HSSL+CPRI)
The main parts of the xCCM are:
- NPU (Network Processor Unit): Wintegra winpath
• Allows all transport functions on the MDA
• Low cost with good performance
• well developed and tested protocol library
• Low power consumption
• Migration to Winpath2 (04Q05) integrates external PCI and DDR controller on the chip
- Control processor : PQ3
� Higher data bandwidth and CPU power (about 50% more) than iCCM2 to support new Linux requirements and future enhancements
� Integrated and versatile component planed to be used on xCEM
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 7/46
� Evolution to next generation HIP8 for DDR2 support and cost reduction with clear roadmap
- MDA: PTMC (PIGMG 2.15)
� Consistent with the requirements in terms of features and size
� Widely used around telecom world
� Some board OTS already exist almost identical to our needs
Figure 1: xCCM Hardware Layout
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 8/46
Figure 2: xCCM Block Diagram
Figure 3: xCCM Front Panel
The xCCM is fully compliant with the existing iBTS and slave modules. However, a xCCM cannot work in duplex mode with any kind of previous CCM.
3.1.2 MAIN DIFFERENCES WITH PREVIOUS CCM VERSION
The main differences with the previous board generation concern:
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 9/46
• The transport functions are performed on a mezzanine board. The functions covered on this board are managed from the PQ-III main processor.
• The control functions are performed on the PQ-III processor (it was an IBM 750Fx Processor on the iCCM2 board). The OS running on this processor is LINUX (it was VxWorks on the previous board’s versions).
• It supports the migration of the access network from ATM to IP technology. This migration implies changes at the Iub interface between the RNC and the Node-B.
• Backhaul interfaces are: 100BT or 100Fx Ethernet with redundancy, STM1 with redundancy and APS, 8 T1/E1 links with IMA.
• From a processing point of view, xCCM can handle up to 100Mbits per second data flow in ATM or Ethernet backplane mode.
• Radio samples from the CPRI interface can be accessed from the front panel to be routed to a remote radio equipement.
3.2. SOFTWARE
3.2.1 OVERVIEW
The xCCM is based on a Linux OS.
ST
M-1
/ D
S3
/ E1
TDM
PH
Ys
GE
/ E
thP
HY
s
LEGEND:
- xCCM – 3G Specific
- modified/
- Wintegra unchanged
NPU
IEEE 802.1Q
DiffservFW NAT
ATM IMA
CES TS
Local ATM/IPTerm.
AAL
IP ATM
IW - Linux unchanged
IPv4 IPsec
QoS
ShapingCES
BSP
NCGL WRS
PNE-LE NP
Linux 2.6.10
WintegraMemory Driver
Wintegra WWDILinux API Wrapper
clas
s-ba
sed
sche
d
OO
M r
epla
cem
ent
proc
cha
nge
notif
proc
ess
acco
untin
g
othe
r ex
tens
ions
pers
iste
nt m
emor
y
mul
ticas
t UN
IX s
ock
…
Loader
xCCM
IP-ATMconnMgr
NBAP router
ASU IP/ATM
Callp
SMSG
3G Application
CallP
Drivers UMTS time, eeprom,
OAMPerf MConf M
Fault M
Linux
Error
CollectorDrivers xCCM, Led, Mim, Imt
HA Manager
Interface
ST
M-1
/ D
S3
/ E1
TDM
PH
Ys
GE
/ E
thP
HY
s
LEGEND:
- xCCM – 3G Specific
- modified/
- Wintegra unchanged
NPU
IEEE 802.1Q
DiffservFW NAT
ATM IMA
CES TS
Local ATM/IPTerm.
AAL
IP ATM
IW - Linux unchanged
IPv4 IPsec
QoS
ShapingCES
BSP
NCGL WRS
PNE-LE NP
Linux 2.6.10
WintegraMemory Driver
Wintegra WWDILinux API Wrapper
clas
s-ba
sed
sche
d
OO
M r
epla
cem
ent
proc
cha
nge
notif
proc
ess
acco
untin
g
othe
r ex
tens
ions
pers
iste
nt m
emor
y
mul
ticas
t UN
IX s
ock
…
Loader
xCCM
IP-ATMconnMgr
NBAP router
ASU IP/ATM
CallpCallp
SMSG
3G Application
CallP
Drivers UMTS time, eeprom,
OAMPerf MConf M
Fault M
Linux
Error
CollectorDrivers xCCM, Led, Mim, Imt
HA Manager
HA Manager
Interface
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 10/46
Figure 4: xCCM Software Architecture
The xCCM software components are grouped in two categories:
Legacy components :
Inherited from the iCCM2 implementation (CallP, OAM, Loader) most of them are grouped for simplicity reason into a single linux manageable entity (i.e. process) the so-called 3G-Application, so that they constitute a single failure domain. Some legacy components closely related to hardware management may be plugged within the Linux kernel as kernel modules and/or drivers for efficiency reason, so that they share the linux kernel failure domain.
Linux Platform components:
These components not inherited from the iCCM2 implementation are related to new features as networking or related to the management of the linux platform.
3.2.2 LINUX OS
The Linux operating system is becoming more and more popular in the telecom world
as well as in many other domains. Developed by a large community, it integrates very
quickly all the emergency standards as the communication protocols, security features
and new hardware architectures.
The advantages of the Linux operating system are big:
- it is robust compared with the traditional real time kernels used by Nortel
- it is distributed according to the GPL licensing scheme. No royalties need to be
paid for using it (under the condition that some rules are respected).
- A lot of services, modules, tools are accessible in open source.
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 11/46
3.2.3 FILE SYSTEM
Figure 5: xCCM File System
The xCCM file system (JFFS2) is made of Linux specific components (/bin, /dev, /etc …) and of the Alcatel 3G application part.
This 3G application part is located in 2 folders: /active & /passive . These 2 folders are symbolic links to /ffs0 & /ffs1.
The 3G application starts on /active . /passive is used for software upgrade.
/active contains the bootImage , some FPGA and 5 directories :
/bin -> start_appli, launcher, embryo, bci …
/etc -> profile (file where is described the alias)
/home -> httpd
/lib -> *.so (# UC), module/*.ko (drivers)
3.2.4 START UP
Power ON
↓
Start U-Boot (Boot Loader: Initialize PQ3, RAM …)
Start the BIST (Load FPGAs)
↓
Load /ffs[i]/bootImage (Linux + Root FS) with /proc/cmdline arguments (bootargs)
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 12/46
↓
Run /etc/inittab (Script)
↓
Run /etc/init.d/rcS (Script; configure network interfaces, create /active symbolic link on /ffs[i], start the http server …)
Run /active/bin/start_appli (Script; load the kernel modules (/active/lib/modules/*.ko))
↓
Launch /active/bin/embryo with the /active/lib/libs_appli list (Load /active/lib/*.so dynamic libraries, initialize the LEC, start BCI)
3.2.5 BCI
Most of the RTC tools inherited from VxWorks environment are available under the Base Command Interpreter (BCI) emulator (See [R4] for more information).
To start BCI, open a Telnet session on the xCCM on the 7006 port, or type ‘bci’ under Linux prompt of the xCCM (Login: nodeb , password nodeblnx ). xCCM-nodeb-nodeb> bci
3.2.6 XCCM IP ADDRESSES
The first phase of the xCCM project implements only IPv4.
The xCCM has five IP addresses and belongs to three routable IP networks
(CIDR masks):
• OAM IP Address on the backhaul interface (ple0 interface; ie: 10.250.xxx.xxx),
• UTRAN IP Address on the backhaul interface,
• Internal IP address for communications with slave boards inside the iBTS (atm0 interface using back panel; ie: 192.168.xxx.xxx),
• Site LAN IP address on the debug interface,
• Debug IP address on the debug interface (eth1 interface; ie: 47.237.xxx.xxx).
ifconfig command in the console connected to the sCCM (Linux prompt) give the state of each interface.bci xCCM-nodeb-nodeb> ifconfig
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 13/46
3.2.7 XCCM ROADMAP
Step 1: UA5.1: iCCM like
Step 2: UA6.0: UTRAN IP, Hybrid IUB …
4. HOW TO
4.1. DEBUG CABLE
In order to connect have simultaneously both connection to the xCCM (Ethernet and physical connection), we may need Y cable:
BTS debug port -------------------> RJ 45 LAN |-----------> SubD9
4.1.1 CABLE SCHEMA
4.2. CONNECT TO THE XCCM
You can connect to the board via the Debug port of the front panel (Login: nodeb / Password: nodeblnx :
• By opening a Telnet session with the xCCM IP address (Debug address),
4
5 6
P2
PC serial port
P3
2
5
3
6
1
4
peer p23a TXD
RXD
Peer 23b masse
N.C
CONN. RJ 45 MALE
Debug xCCM board
CONN. 9 pts sub D female
7
8
1
3
2
P1 Network connection
CONN. RJ 45 MALE
N.C
7
5
8
6
1
4 3
2 peer p12a
ETH TX (P)
ETH TX (N)
Peer 12b N.
ETH RX (P)
ETH RX (N)
Peer 12c (masse)
N.
N.
7
8
N.C
N.
9 N.
N.
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 14/46
• OR by opening a Pcons session (RS232) with the following settings:
Figure 6: Pcons settings (Windows Hyperterminal)
Notice that with a PCONS you can take control of the xCCM when U-Boot starts (Press the escape key during the RAM test) whereas with telnet you have to wait the end of the bootImage initialization.
Here is the list of available commands in U-Boot:
xCCM=> h
? - alias for 'help'
as - assemble memory
autoscr - run script from memory
base - print or set address offset
bdinfo - print Board Info structure
bist - load and run binary bist file from a file system image
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
bootp - boot image via network using BootP/TFTP p rotocol
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 15/46
break - set or clear a breakpoint
chpart - change active partition
chuboot - Change u-boot next reset.
cmp - memory compare
coninfo - print console devices and information
continue- continue from a breakpoint
cp - memory copy
crc32 - checksum calculation
dcbf - flush data cache block start address 'add r'
dcbi - invalidate data cache block start address 'addr'
ds - disassemble memory
echo - echo args to console
eeprom - EEPROM sub-system
erase - erase FLASH memory
exit - exit script
flinfo - print FLASH memory information
fsinfo - print information about filesystems
fsload - load binary file from a filesystem image
go - start application at address 'addr'
help - print online help
icbi - invalidate instruction cache block start address 'addr'
icrc32 - checksum calculation
iloop - infinite loop on address range
imd - i2c memory display
iminfo - print header information for application image
imls - list all images found in flash
imm - i2c memory modify (auto-incrementing)
imw - memory write (fill)
inm - memory modify (constant address)
iprobe - probe to discover valid I2C chip addresse s
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loop - infinite loop on address range
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 16/46
ls - list files in a directory (default /)
lsuboot - Print u-boot Id.
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing)
mtdparts- define flash/nand partitions
mtest - simple RAM test
mw - memory write (fill)
next - single step execution, stepping over subr outines.
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP pr otocol
rdump - Show registers.
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sleep - delay execution for some time
step - single step execution.
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protoco l
version - print monitor version
where - Print the running stack.
4.3. TRANSFER FILES FROM / TO THE XCCM
You can transfer files from / to the temporary directory (/tmp) of the xCCM board by opening a FTP client (Login: nodeb / Pass word: nodeblnx on the xCCM IP address (Debug address).
The transfer must be done in bin mode.
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 17/46
After transfer is done file can be moved from the temporary directory to other directory by login using root user: su root
Pass word : nodeb3G
4.4. RUN RTC TOOLS UNDER BCI
Open a Telnet/Pcons session on the xCCM and type:
xCCM-nodeb-/> telnet localhost 7006
or use the bci alias:
xCCM-nodeb-/> bci
(Login: nodeb / Pass word: nodeblnx
Notice that BCI is available only if the application is started (via the start_appli script).
Use ls to get the commands list and cd to browse the sub dir.
Useful commands:
sessions : give the session/user list
clone sessionid : create a clone of the session sessionid
alias : create an alias of a command
shortcut : link a F* keyboard key to a command
history : give the commands history
exit : exit BCI
You can also start BCI directly by opening a Telnet session on the xCCM / 7006 port.
4.5. DISABLE / ENABLE THE LOADER
The Loader is enabled by default.
To disable it, start BCI and type:
> pltf/mim/mfwrite PNP 3
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 18/46
Then, reset the board.
To re-enable the loader type:
> pltf/mim/mfwrite PNP 0
Then, reset the board once again.
4.6. INSTALL A NEW XCCM SOFTWARE
Open a Telnet session on the xCCM (root login ).
First of all, disable the loader. Then verify that the application is not running (set APPLI_START=NO in /data/env_appli).
Then verify that the application is not running;
xCCM-root-/> ps
“embryo ” process should not be active.(Following line is not displayed)
330 root 31032 S /active/bin/embryo -v -w -f /tmp/libs_appli –
Check the active partition (type ll to get the target of /active symbolic link).
Delete the content of this directory.
xCCM-root-/> cd /active
xCCM-root-/> rm –R *
Check the active partition (type ll to get the target of /active symbolic link).
If /ffs1 is the active partition, delete the content of this directory. Then type:
xCCM-root-/> package-prepare.sh /ffs1
Else, type:
xCCM-root-/> package-prepare.sh /ffs0
The package-prepare.sh script creates the /ffs1/config directory.
Open a FTP session on the xCCM and transfer package files (*.deb) to the /tmp directory (binary).
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 19/46
Return to the Telnet terminal and type:
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/lnx.xccm.deb
This command unpacks the Linux image in /ffs1/lib/bootImage.
Unpack the other .deb files in /ffs1 with the previous command:
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/uboot.xccm.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/pltf.xccm.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/bist.xccm.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/extendfs.xccm.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/gpsam.xccm.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/toolfs.xccm.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/callpccm.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/oamappli.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/stub.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/til.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/dwl.xccm.deb
xCCM-root-/>dpkg --admindir=/upgrade/config/db/ -i /tmp/uxccmmrk.deb
Make a copy of firmware/xccCommandFile in the /active directory.
xCCM-root-/>cp /active/firmware/xccmCommandFile /ac tive/
The /active directory should look like this:
Figure 7: Active partition content
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 20/46
Reboot the board when all of the previous steps have been done.
xCCM-root-/>reboot
Notice that xCCM will be start without the application. To start the application, return to the Telnet terminal and remove type:
xCCM-root-/>cd /active
xCCM-root-/>./start_appli.no
4.7. EDIT THE DLU
When the OMC-B is not available, it can be useful to modify the DLU manually with the help of a tool called translator. Translator tool is available for each software version: this tool is nodeb software version dependency
./translator converts the binary DLU to text (and vice versa).
Retrieve the DLU (ex: DLU_00000002.TXT) from /data via FTP
Under Unix (i.e.: in your home directory) type:
./translator -in DLU_00000002.TXT -out DLU_00000002 .TEXT
Edit the .text to implement your changes.
Then translate from text to binary:
translator -in DLU_00000002.TEXT -out DLU_00000002. TXT
Put the new DLU in /data via FTP and delete the files: EOAM_CONF_M.TXT & EOAM_CONF_B.TXT (backup of the previous DLU).
Reset the board when all is done.
4.8. CHECK THE DLU
The DLU consistency can be verify on the board.
Start BCI and type:
> emo/alarm/ChkConfigFile
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 21/46
If the DLU parameters are OK, the tool should reply:
Result: All parameters are valid
Otherwise, errors are displayed.
4.9. DISPLAY THE DLU
Start BCI and type:
> emo/data/CFileDump
4.10. SWITCH FROM ONE DLU TO ANOTHER
The DLU is stored in /data.
To specify a DLU (example: DLU_00000002.TXT) to the system, a field must be changed in the MIM.
Start BCI and type:
> cd pltf
/pltf> cd mim
/pltf/mim> mfwrite ACREF 2
/pltf/mim> mfwrite UPGREQ 1
ACREF means MIM_FIELD_ACTIV_CONFREF (type mflist to get the MIM field list) and ‘2’ is for DLU_00000002.TXT. UPGREQ is a flag to activate the DLU switching.
Reset the board after the change.
/pltf/os/reset
4.11. GET THE BTS CONFIGURATION SUMMARY
Start BCI and type:
> emo/Bts
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 22/46
4.12. GET THE XCCM SOFTWARE MARKING
Start BCI and type:
> pltf/pkg/fmdir active
4.13. CHECK THE XCCM HWREF
Start BCI and type:
> pltf/mim/mfread HREF
You should see:
- HREF : 0x 580
If it is not the case, type:
> pltf/mim/mfwrite HREF 0580
4.14. GET / SET THE IP ADDRESS (TEMPORARY)
To get the IP address of the board, open a Telnet/Pcons session on the xCCM and type:
xCCM-nodeb-/> ifconfig
You should get:
eth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:47.237.82.189 Bcast:47.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:337398 errors:0 dropped:0 over runs:0 frame:0
TX packets:59491 errors:0 dropped:0 overr uns:0 carrier:59491
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 23/46
collisions:0 txqueuelen:1000
RX bytes:22105233 (21.0 MiB) TX bytes:43 50246 (4.1 MiB)
Base address:0x8500
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns: 0 frame:0
TX packets:0 errors:0 dropped:0 overruns: 0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
The interface name of the Debug port is eth2 and the associated IP address is 47.237.82.189
ifconfig is a Linux exe file located in /bin.
To set the IP address of the board, you must first be logged as root (su root).
From the previous example, type:
xCCM-root-/> ifconfig eth2 inet 47.237.82.188 netma sk 255.0.0.0
The new IP address (47.237.82.188) is set immediately (there’s no need to reset the board). This is a temporary address that will be lost after the next reset .
4.15. SET THE IP ADDRESS (PERMANENTLY)
Way to modify the IP address or subnet mask of the BTS is given by the BCI menu:
4.15.1 MODIFYING THE IP ADDRESS
Under the BCI prompt ‘>’ type cd pltf/mim in order to go the MIM sub-menu
Command mrdump will give the state of the actual xCCM Ethernet address. This address is given for both software area called b0 and b1 in this part. To change the IP address both area (b0 and b1= must be configured with the address. Command to change IP address are: /pltf/mim> mrwrite –b0 ipaddr www.xxx.yyy.zzz
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 24/46
/pltf/mim> mrwrite –b1 ipaddr www.xxx.yyy.zzz
where www.xxx.yyy.zzz is the expected IP address.
4.15.2 MODIFYING THE SUBNET MASK
Way to proceed is the same than way to change IP address (subnet mask must be write in both b0 and b1 area), but syntax is: /pltf/mim> mrwrite –b0 netmask 255.255.xxx.yyy /pltf/mim> mrwrite –b1 netmask 255.255.xxx.yyy wher 255.255.xxx.yyy is the expected subnet mask.
4.15.3 MODIFYING THE IP ADDRESS AND SUBNET MASK USING U-BOOT
To set a permanent IP address to the board, a U-Boot environment variable must be changed.
Open a Pcons session on the xCCM and reset the board.
Press escape key when the RAM test starts.
xCCM=> setenv ipaddr 47.237.82.188
xCCM=> setenv gatewayip 47.237.82.1
xCCM=> setenv netmask 255.0.0.0
In this example, U-Boot will pass the bootargs string to the Linux image. Then, Linux will start ethernet
interface eth with the 47.237.82.188 IP address, the 47.237.82.1 gateway address and the 255.0.0.0 subnet mask.
4.16. ADD AN IP ROUTE
Open a Telnet/Pcons session on the xCCM and type:
xCCM-nodeb-/> route add -host 47.162.10.64 gw 10.2. 15.6
In this example 47.162.10.64 is the destination host (i.e.: OMCB) and 10.2.15.6 is its gateway (ie: xCCM).
Type ‘route’ to get the route list.
4.17. CAPTURE TCP/IP TRAFFIC
Open a Telnet/Pcons session on the xCCM and type:
xCCM-nodeb-/> tcpdump –i eth2 –w /data/capture.pcap
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 25/46
In this exemple, the network traffic on the eth2 interface (debug port) is dumped in the /data/capture.pcap file.
This file can be further analyzed with Ethereal/Wireshark.
4.18. RESET THE BOARD
BCI menu is available to reset the xCCM board at prompt ‘>’ of BCI menu type command: > pltf/os/reset
4.19. MODIFY ENVIRONMENT VARIABLES
The default xCCM environment variables can be modified via the /data/env_appli file.
Here is the list of variables (default values underlined):
APPLI_START=YES /NO to start (or not) start_appli automatically APPLI_REBOOT=ON /OFF to enable/disable the reboot after a crash APPLI_MESSAGE=term to specify the default terminal APPLI_WRAP= … to start the application via a wrapper : gdb, gdbserver, strace … APPLI_WRAP_ARGS= … to pass args to the wrapper APPLI_NFS_HOST=host_ip:/dir to mount a NFS host APPLI_LEC_DEBUG=OFF /ON to enable/disable the LEC debug mode APPLI_LEC_TRAP_HOOK=GDBSERVER/WAIT/CORE to activate the LEC trap hook.
4.20. SEND BCI COMMAND AUTOMATICALLY AT XCCM STARTU P
Thanks to the /data/pltf.bci file, some BCI commands can be automatically executed at xCCM startup.
pltf.bci file content example:
# This is a comment...
tra effect i 513 # Ignore TRAP 513
tra effect i 514 # Ignore TRAP 513
flr output 0 3
flr output 2 3
flr output 4 3
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 26/46
flr output 5 3
flr output 6 3
trc sf 3 ioep
trc sf 4 ioep
trc sf 5 ioep
trc sf 11 ioep
trc sf 12 ioep
trc sf 13 ioep
trc sf 14 ioep
trc sf 15 ioep
4.21. CREATE AN ALIAS
Open a Telnet/Pcons session on the xCCM and type:
xCCM-nodeb-/> alias bci='telnet localhost 7006'
In this example, the bci command will act as “telnet localhost 7006”.
4.22. MODIFY BOOTARGS (IN U-BOOT)
Open a Pcons session on the xCCM and reset the board.
Press the escape key when the RAM test starts.
Example: modification of the IP address of eth2:
xCCM=> setenv ramboot root=/dev/ram rw
ip=136.147.47.237:::255.255.240.0::eth2:on console= ttyCPM0,38400
xCCM=> setenv bootargs $ramboot $mtdparts board=xCC M mem=$mem $reserved
bootid=$bootid
xCCM=> saveenv
xCCM=> run bootcmd (or xCCM=>reset )
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 27/46
Once the Linux image is launched, the bootargs can be found in the /proc/cmdline file.
4.23. SWAP ACTIVE/PASSIVE PARTITIONS
4.23.1 SWAP ACTIVE / PASSIVE PARTITIONS USING BCI MENU
In the BCI menu prompt ‘>’ type command > pltf/fsmg/activate
then reboot the BTS using the command > pltf/os/reset.
To unsure that the active was changed use command xCCM-nodeb-nodeb> cd /active
4.23.2 SWAP ACTIVE / PASSIVE PARTITIONS USING U-BOOT
Open a Pcons session on the xCCM and reset the board.
Press the escape key when the RAM test starts and type:
xCCM=> chuboot
You should see:
Current U-BOOT id is : 0
Next reset U-BOOT id will be : 1
Then reset the board.
4.24. COPY U-BOOT VAR INTO PASSIVE PARTITION
Open a Pcons session on the xCCM and reset the board.
Press the escape key when the RAM test starts.
If /ffs0 is the active partition type:
xCCM=> eeprom read 0x100000 0 800
xCCM=> eeprom write 0x100000 800 800
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 28/46
If /ffs1 is the active partition type:
xCCM=> eeprom read 0x100000 800 800
xCCM=> eeprom write 0x100000 0 800
4.25. SEE PCONS TRACES (KERNEL TRACES) IN A TELNET TERMINAL
Open a Telnet session on the xCCM and type:
xCCM-nodeb-/> tail –f /var/log/messages
4.26. MOUNT A NFS PARTITION
Open a Telnet/Pcons session on the xCCM (root login ) and type:
xCCM-root-/> mount 47.237.82.227:/iss /mnt
In this example, the remote /iss directory from 47.237.82.227 NFS server is mounted in the local /mnt folder.
xCCM-root-/> mount -t nfs -o rw 47.162.15.228:/home /rsiumts/iss /mnt
To unmount the NFS point, type:
xCCM-root-/> umount /mnt
4.27. GET A CORE FILE AFTER AN APPLICATION CRASH
The Linux OS creates a core file in case of application crash. This file is useful for developers to investigate the root cause of an error. The core is a large file (~ 400 MB) and cannot be created locally because of the xCCM flash memory size limitation. A NFS mounting point with enough space can solve the problem.
Open a Telnet session on the xCCM and type:
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 29/46
xCCM-root-/> mount 47.237.82.227:/iss /mnt
xCCM-root-/> cd /mnt
xCCM-root-/mnt> /active/bin/start_appli
We start the start_appli script from /mnt which is on the NFS server. In case of crash, the core file will be created on this server.
4.28. GET LEC SNAPSHOTS
The LEC (Linux Error Collector) provides useful services:
• Fatal error and reboot,
• Memory supervision,
• CPU load supervision,
• User data collection for debug,
• Session user data archiving,
• User data decoding,
• Traceback decoding tool.
The LEC snapshot is a “photo” of the data, states, frames stacks,…of an application or a part of it. This is a DEBUG tool, and NOT a trace tool.
When the board restarts, the lecmon process collects all data from the application (rmfs in persistent memory mounted to /rmem) and saves it in the flash in /store/1.
Six data sessions can be saved: /store/1 (the latest) … /store/6 (the oldest).
One of the useful LEC file is ….RESTART_CAUSE
xCCM-nodeb-/>cd /store
xCCM-nodeb-/>cd 1
xCCM-nodeb-/>ls
337.16842752.LEC_RESTART_CAUSE_V1.173.1970-01-01_00 h08m12.ppc.dump
To open this LEC file, type:
xCCM-nodeb-/>lectool –f 337.16842752.LEC_RESTART_CA USE_V1.173.1970-01-
01_00h08m12.ppc.dump
LEC snapshot consists in several .dump files. It can be useful to ‘tar’ these files in a single .tgz archive to retrieve it by FTP.
Open a Telnet session on the xCCM and type:
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 30/46
xCCM-nodeb-/> tar czpf /tmp/lec_snap.tgz /store/1/* .dump LEC traces are dumped in the IMT during the IMT generation.
4.29. GET THE IMT
This is a shell script which perform a snapshot on the live application,
Decode the snapshot and display the FLR/OPTF of the current application,
Decode the snapshot and display the FLR/OPTF of the 6 previous sessions,
Call the IMT on the current application,
Do the same into the remote xCCM,
Call the IMT on all *CEM slaves,
Save the IMT result to a gzipped text file.
Open a Telnet/Pcons session on the xCCM and type:
xCCM-nodeb-/> imt
A .gz archive will be created in /tmp.
4.30. CHECK THE ALARMS
4.30.1 CHECK THE ACTIVE ALARM
Start BCI and type:
> emo/ala/GlobalAlarms ALL
4.30.2 CHECK THE ALARM STILL PRESENT IN CIRCULAR BUFFER
It exist a way to display alarm history (Warning, Raised and Cleared) for all the alarm. This way to check alarm history is limited to alarm still present in circular buffer. Under BCI ‘>’ prompt type following command:
> pltf/flr/display 2 x
Where x correspond to the x last alarms (however it is Raised, Warning or Cleared).
4.31. CHECK ATM
Start BCI and type:
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 31/46
> cd conn
/conn> ProfilPath ALL
/conn> External
To activate the ATM traces:
/conn> verbose a
4.32. CONNECT TO A SLAVE FROM THE XCCM
Start BCI and type:
> msg/DBTable
DBTable gives the internal IP addresses of the the slave boards.
Exit BCI and from the xCCM open a Telnet session on the slave with its IP address:
> exit
xCCM-nodeb-/> telnet 192.168.13.1
From the slave board, type rtc > ip > dis to return to the xCCM.
4.33. ENABLE / DISABLE SOME TRACES
4.33.1 CONFIGURATION TRACES
Start BCI and type:
> cd pltf/blog
The lf command gives the trace list
pltf/blog> lf
== Fct == 1 CORE_NOMINAL - / - / ERR / PS G
…
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 32/46
== Fct == 2 CORE_SW_COMP_TRACES IN / OUT / ERR / PSG
…
== Fct == 13 NbapRouter on CCM IN / OUT / ERR / PSG
…
== Fct == 14 NbapManager on CCM IN / OUT / ERR / PSG
…
== Fct == 15 Callplib IN / OUT / ERR / P SG
…
To activate the NbapManager (14) traces (for example) type:
/pltf/blog> sf 14 ioep
To disable a trace, use the uf command:
/pltf/blog> uf 14 ioep
General traces activation if start_appli is launche d in automatic mode:
xCCM-nodeb-/> optf_read -f /rmem/messages
(or type m (alias))
Sample of the file pltf.bci is given in annex of the document.
4.33.2 TRACES REDIRECTION ON THE CONSOLE
By default the output of configured and default traces is a circular buffer. A way to redirect traces to the telnet console exist, syntax is as follow under BCI ‘>’ prompt:
> pltf/flr/output 0 3
> pltf/flr/output 1 0
> pltf/flr/output 2 0
> pltf/flr/output 4 0
All these commands can be put in the pltf.bci file in order to be automatically executed at startup of the xCCM board. Sample of these commands in the pltf.bci file is given in annex of the document.
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 33/46
4.34. LOAD A BOOTIMAGE VIA TFTP / BOOTP
When the bootImage fails to load, it is possible to download it via TFTP / BOOTP.
Install the wbootp.exe application on a Windows PC.
Launch wbootp and fill the following fields:
NAME: xccm
HA: Ethernet address of the xCCM (ie: 00:0e:62:fd:94:e7 this address is written on front panel of the xCCM)
IP: IP address of the xCCM (ie: 47.162.12.253)
SM: Subnet mask of the xCCM (ie: 255.0.0.0)
BF: Name of the bootImage to be loaded (click on the “Tftp Folder” button to specify the folder containing the bootImage file)
Figure 8: wbootp configuration
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 34/46
Click on the “Add” button to pass the configuration in the Inactive window.
Then double click on the line in the Inactive window to pass it to the Active window.
The wbootp TFTP server is now ready.
To proceed to the download, open a Pcons session on the xCCM and restart the board.
Press the space key 3 consecutive times when the RAM test starts.
Then type:
xCCM=> bootp
The bootImage download notification should appears both in the PCONS and on wbootp window:
Figure 9: bootImage download in the PCONS
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 35/46
Figure 10: bootImage download in wbootp
When the download is completed, return to the PCONS and type:
xCCM=> bootm
The Linux Image should start in RAM …
4.35. START THE TIL
The TIL is a useful multi purpose tool that permit to :
• Upgrade a iBTS
• Reset a board
• Read & write the I&C
• Check the BISTs, the Alarms
• Get the inventory, the DLU, the SW Marking …
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 36/46
• Mount a cell
• …
In your web browser type:
http://XCCM_DEBUG_IP_ADDRESS/til/index.html
Here is what you should see:
Figure 11: TIL starting page
Click on the Start button.
The TIL Applet should appear:
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 37/46
Figure 12: TIL window
5. U-BOOT ENVIRONMENT VARIABLES
xCCM=> printenv baudrate=38400 nfsboot=root=/dev/nfs rw nfsroot=:/home/bcsumts/roo tfs ip=:::255.255.240.0::eth2:on console=ttyCPM0,38400 bootdelay=1 loads_echo=1 serverip=0.0.0.0 rootpath=/home/ppc netmask=255.0.0.0 hostname=xCCM bootfile=bootImage mtdparts=mtdparts=Bootflash:30m@0(ffs0),30m@0x01e00 000(ffs1),4m@0x03c00000(data),62m@0x04000000(store),256k@0x07e00000(c rashdump),1280k@0x07e40000(spare),256k@0x07f80000(b oot1),256k@0x07fc0000(boot0) mtdids=nor0=Bootflash reserved=reserved=bists:0x0c000000,0x00080000;pmem: 0x0c080000,0x03c00000;spare:0x0fc80000,0x00180000;crashdump:0x0fe0000 0,0x00200000 initrd_high=0x0c000000 netretry=no flashuboot=tftp 0x2000000 u-boot-xccm.bin && protec t off 0xfffc0000 +0x40000 && erase 0xfffc0000 +0x40000 && cp.b 0x2000
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 38/46
000 0xfffc0000 0x40000 && protect on 0xfffc0000 +0x 40000 ethact=FCC2 ETHERNET ethaddr=00:0E:62:FD:94:FB eth1addr=00:0E:62:FD:94:FB eth2addr=00:0E:62:FD:94:FB ipaddr=47.237.83.18 gatewayip=47.237.82.1 sereverip=136.147.40.21 bootcmdnominal=bootp 0x2000000 && bootm;bist 0x2000 000 firmware/bistxCCM.bin;fsload 0x2000000 bootImage && bootm;reset bootcmd=run bist;bootp 0x2000000 && bootm;fsload 0x 2000000 bootImage && bootm;reset bist=fsload 0x100000 firmware/loadfpga.bin && dcbf 0x100000 1000 && fsload 0x400000 firmware/scfpga.rbf && fsload 0x6000 00 firmware/bblink.bit && go 0x100000 ramboot=root=/dev/ram rw ip=47.237.83.18:::255.0.0. 0::eth2:on console=ttyCPM0,38400 stdin=serial stdout=serial stderr=serial partition=nor0,0 bootid=0 bootargs=root=/dev/ram rw ip=47.237.83.18:::255.0.0 .0::eth2:on console=ttyCPM0,38400 mtdparts=Bootflash:30m@0(ffs0), 30m@0x01e00000(ffs1),4m@0x03c00000(data),62m@0x0400 0000(store),256k@0x07e00000(crashdump),1280k@0x07e40000(spare),256k@0 x07f80000(boot1),256k@0x07fc0000(boot0) board=xCCM mem=196608k reserved=bists:0x0c000000,0x00080000;pmem:0x0c08000 0,0x03 c00000;spare:0x0fc80000,0x00180000;crashdump:0x0fe0 0000,0x00200000 bootid=0 mem=196608k
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 39/46
6. ABBREVIATIONS AND DEFINITIONS
6.1. ABBREVIATIONS
0D Second set of prototypes ready for manufacturing ramp-up
1W First functional set of prototypes
A
ASU ATM Service Unit
AAL2 ATM Adaptation Layer 2 (Data)
AAL5 ATM Adaptation Layer 5 (Sign)
ALCAP Access Link Control Application Part
AN Acces Node / Passport (Iub: E1/T1 <-> SDH)
ASN.1 Abstract Syntax Notation One
ATM Asynchronous Transfer Mode
AWGN Additive white Gaussian noise (RF)
B
BCI Base Command Interpreter
BER Bit Error Ratio
BBU Base Band Unit
BIST Built In Self Test
BLER Block Error Rate
C
CAC Call Admission Control
CCM Core & Control Module
CCP Communication Control Port
CEM Channel Element Module
CN Control Node (RNC)
CP Control Plane (signaling)
CPRI Common Protocol Radio Interface: standard designed by several manufacturers (see www.cpri.info)
CQI Channel Quality Indicator (HSDPA)
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 40/46
CW Continuous Wave
CxOIM Generic name of all variants of the Optical Interface Modules. x is the number of optical fibers connected to this CxOIM module. ( x= 1, 2, 3)
D
DACS Direct Ambient Cooling System
DBP Digital Back Plane (implicitly of the UMTS BTS)
DBP602 Name of the 600mm Digital Back Plane specific of optical interfaces to RRH (The “2“ means second Digital Back Plane developed in the 600mm width.)
DDM Dual Duplexer Module
DL Down Link
DLU See MIB
DPCCH Dedicated Physical Control Channel
DPCH Dedicated Physical Channel
DPDCH Dedicated Physical Data Channel
DRF Build / DLU / MIB (bin file (*.txt) in /DATA part of the CCM)
DTX Discontinuous Transmission
E
E1 Standard European PCM link system (2.048Mbit/s)
F
Fc UMTS Chip frequency = 3.84MHz
FDD Frequency Division Duplex
FRS Feature Requirements Specification
G
GPOIM Board with GPSAM and OIM functions
GPSAM GPS & Alarm Module
H
H-ARQ Hybrid Rutomatic Repeat Request
HSDPA High Speed Downlink Packet Access
HS-DSCH High Speed Downlink Shared Channel
HS-PDSCH High Speed Physical Downlink Shared Channel
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 41/46
HS-SCCH High Speed Physical Downlink Shared Control Channel
HSSL High Speed Serial Link
HSSPC High Speed Serial Protocol Controller
HW Hardware
I
I&C Installation and Commissioning
ICU Interface and Control Unit
IMA Inverse Multiplexing ATM
IMT iBTS Maintenance Toolkit
IN Interface Node (RNC)
ISS Integration Sous Systeme
J
JFFS2 Journaling Flash File System version 2
K
KPI Key Performance Indicator
KTF Korean operator
L
LEC Linux Error Collector
LED Light Emitting Diode
LO Local Oscillator
M
MCA Manufacturing Commissioning and Alarm Module
MCPA Multi Carrier Power Amplifier
MDA Media Dependant Adaptor (xCCM)
MIB Management Information Base (also called DLU)
MIM EEPROM located on a BTS board which stores all the permanent parameters of the board (ex: IP address, active Flash File System…).
N
NAT Network Address Translation
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 42/46
NBAP Node-B Application Part
NCGL Nortel Carrier Grade Linux
NFS Network File System
NSP OMCB Java Client (Preside)
NPW Non Payroll Worker
NUSCM Test Endurance with Catapult
O
OAM Operations, Administration, and Maintenance
OBSAI Open Base Station Standard Initiative (see http://www.altera.com/end-markets/wireless/cellular/obsai/wir-obsai.html )
OIM Optical Interface function (it is a logical function)
OMCB Operation Maintenance Center – BTS
OS Operating System (ie: VxWorks, Linux)
OTSR Omni-directional Tx, Sectorized Rx
P
PCB Printed Circuit Board
PEC CODE Product reference in Nortel catalogue (PEC= Product Engineering Code)
PLMN Public Land Mobile Network
R
RAB Radio Access Bearer
RCU Radio Control Unit
RLC Radio Link Control
RNC Radio Network Controller
RF Radio Frequency
RRC Radio Resource Control
RRH Remote Radio Head
RSCP Received Signal Code Power
RSSI Received Signal Strength Indicator
RT RRH terminal (installation and debug)
RTWP Received Total Wideband Power (RSSI)
RU_NAME Replaceable Unit Name
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 43/46
S
SA Spectrum Analyzer
SAR Segmentation and Re-assembly
SDH Synchronous Digital Hierarchy
SFN System Frame Number
SHO Soft Handover
SII Internal Interface Specification
SKT Korean operator
SRB Signalling Radio Bearer
STM-1 Synchronous Transport Module –1
STSR Sectorized Tx, Sectorized Rx
SWACT Refers to the switch of activity from one iCCM to a redundant one.
SW Software
T
T1 Standard US PCM system (1.544Mbit/s)
TDD Time Division Duplex
TIL Local Installation Terminal
TMA Tower Mounted Amplifier
TRB Traffic Radio Bearer
TRAU Transcoding and Rate Adaptor Unit
TRM Transmiter & Receiver Module
TTI Transmission Time Interval
U
UC Unité Chargeable, specific SW application running into the digital card RAM
UE User Equipment
UL Up Link
UMTS Universal Mobile Telecommunications System
UP User Plane (data)
UTRAN Universal Terrestrial Radio Access Network
V
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 44/46
Vcc Couple Vp, Vc (ATM)
Vc Virtal Circuit (ATM)
Vp Virtual Path (ATM)
VVA Voltage Variable Attenuator
W
WG Wireless Gateway
WICL Wireless Interface Command Language (OMCB)
X
xCCM eXtended Core and Controller Module
xCOB xCCM Optical Board
6.2. DEFINITIONS
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 45/46
7. ANNEX: SAMPLE OF PLTF.BCI FILE
In this sample trace are redirect on the telnet console and only OAM traces are displayed.
# # Remove # character to uncomment and to set comm and line # # # # Traces undirection # /pltf/flr/output 0 3 /pltf/flr/output 1 3 /pltf/flr/output 2 3 /pltf/flr/output 4 3 # # # OAM traces # /pltf/blog/sf 2 iope s all #/pltf/blog/sf 2 iope s 0 #/pltf/blog/sf 2 iope s 1 #/pltf/blog/sf 2 iope s 2 #/pltf/blog/sf 2 iope s 3 #/pltf/blog/sf 2 iope s 4 #/pltf/blog/sf 2 iope s 5 #/pltf/blog/sf 2 iope s 6 #/pltf/blog/sf 2 iope s 7 #/pltf/blog/sf 2 iope s 8 #/pltf/blog/sf 2 iope s 9 #/pltf/blog/sf 2 iope s 10 #/pltf/blog/sf 2 iope s 11 #/pltf/blog/sf 2 iope s 12 #/pltf/blog/sf 2 iope s 13 #/pltf/blog/sf 2 iope s 14 # # # CallP traces # #/pltf/blog/sf 12 iope s all #/pltf/blog/sf 14 iope s all # # # Sepe traces # #/pltf/blog/sf 5 iope s all #/pltf/blog/sf 5 iope s 0 #/pltf/blog/sf 5 iope s 1 #/pltf/blog/sf 5 iope s 2 #/pltf/blog/sf 5 iope s 3 #/pltf/blog/sf 5 iope s 4 #/pltf/blog/sf 5 iope s 5 #/pltf/blog/sf 5 iope s 6 # #
xCCM Quick Start and debug Guide
Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization
UMT/BTS/DJD/022331 01.06 / EN Preliminary 01/Feb/2008 Page 46/46
# PM traces # #/pltf/blog/sf 6 iope s 1 #/pltf/blog/sf 7 iope s all #/pltf/blog/sf 7 iope s 1 #/pltf/blog/sf 7 iope s 2 #/pltf/blog/sf 7 iope s 3 #/pltf/blog/sf 7 iope s 4 #/pltf/blog/sf 7 iope s 5 #/pltf/blog/sf 7 iope s 6 #/pltf/blog/sf 7 iope s 7 #/pltf/blog/sf 7 iope s 8 #/pltf/blog/sf 7 iope s 9 #/pltf/blog/sf 7 iope s 10 #/pltf/blog/sf 7 iope s 11 #/pltf/blog/sf 7 iope s 12 # # # Alco traces # #/pltf/blog/sf 31 iope s all #/pltf/blog/sf 31 iope s 0 #/pltf/blog/sf 31 iope s 1 #/pltf/blog/sf 31 iope s 2 #/pltf/blog/sf 31 iope s 3 #/pltf/blog/sf 31 iope s 4 #/pltf/blog/sf 31 iope s 5 #/pltf/blog/sf 31 iope s 6 #/pltf/blog/sf 31 iope s 7 #/pltf/blog/sf 31 iope s 8 # # # ffs traces # #/pltf/blog/sf 30 iope s all #/pltf/blog/sf 30 iope s 8 #/pltf/blog/sf 30 iope s 10 #/pltf/blog/sf 30 iope s 14 #/pltf/blog/sf 30 iope s 15
���� END OF DOCUMENT