Sunteți pe pagina 1din 12

Technical Support Note

TS-BSC-SW-0922-I13.0

BSCLogcol for collecting logs

Radio Controllers
BSC
S16_2, BSC16, SRAN16.2

Approval date: (09-May-2014)

This document contains following


type of information
Informative X
Preventive
Corrective
Additional categorization
Urgent
Security
Release Upgrade
SW Update
Parameterization
Information is classified as
Internal
Public X
Customer Specific

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its
products and services. We would like to encourage you as our customers and users to join us in working
towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations
for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia Solutions and Networks for additional information.

TS-BSC-SW-0922-I13.0 - Page 1/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
Table of Contents
1. Validity .....................................................................................................................................4
2. Compatibility / Dependencies to other products ......................................................................4
3. Keywords.................................................................................................................................4
4. Executive Summary ................................................................................................................4
5. Detailed description .................................................................................................................4
6. SOLUTION / INSTRUCTIONS ................................................................................................5
7. Notes .....................................................................................................................................11
8. References ............................................................................................................................11

Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:

12-Mar-2014 0.1 The first version


09-May-2014 1.0 Approval date
19-May-2014 2.0 Changed from internal to public
13-Jun-2014 3.0 Added mcBSC eSW collection option. Added CD
installation history collection into all options.
02-Oct-2014 4.0 S16_2 validation
18-Nov-2014 5.0 Possibility to use different username for ftp.
New BSCLogcol_2_2_13.
14-Jan-2015 6.0 New BSCLogcol_2_2_16.
12-Mar-2015 7.0 New BSCLogcol_2_2_16_1. Highly recommended
to use BSC Logcol version 2_2_16_1. Earlier
versions may result PCU2 crash during log
collection.
07-Apr-2015 8.0 New BSCLogcol_2_2_17.
Handling SWUs with unknown username.
Fixed problem with handling ETIP prompts.
Containing characters.
MOCN commands added.
MCBC reset info collected
ZWTI:PI; collected.
Fixed a deadlock situation when printing
databases when low number of connections to
element is available.

27-Apr-2015 9.0 New BSCLogcol_2_2_18_1


Option to define log collection directory. Highly
recommended to use BSC Logcol version
2_2_18_1. Earlier versions may result PCU2 crash
during log collection.
19-May-2015 10.0 BSC16 validation
20-Dec-2015 11.0 SRAN16.2 validation, Removing S16 & S16.1
15-Apr-2016 12.0 New BSCLogcol _2_2_23
- Added ZWKP:FULL:EMODE; output to SW
configuration.

TS-BSC-SW-0922-I13.0 - Page 2/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
2_2_22
- Corrected PCU logging to work with changed ST
MML (remote session to computer C000,<PCU>
not working anymore, using real MB address
instead)
2_2_21
- Added data classification output
2_2_20
- Corrected occasional hanging after OMU/MCMU
"overload" situation (over load protection active)
- Added warning for cases when user account
does not have sufficient access rights
- Added some output commands to ETIP
- Added some output commands to ETPs
05-Jul-2016 13.0 2_2_24
- Removed etpver -dsp output from ETP units due
to overload it causes to unit

TS-BSC-SW-0922-I13.0 - Page 3/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
Purpose
This document contains generic information about products. These can be instructions that
explain problem situations in the field, instructions on how to prevent or how to recover from
problem situations, announcements about changes or preliminary information as requirements
for new features or releases.

1. VALIDITY

Product SR20 S16_2 BSC16 SRAN16.2


BSC3i X X
Flexi BSC X X
TCSM2A/E
TCSM3i
mcBSC X X
mcTC
Single RAN X

2. COMPATIBILITY / DEPENDENCIES TO OTHER PRODUCTS

N/A

3. KEYWORDS

BSCLogcol, logs, troubleshooting, problem reporting

4. EXECUTIVE SUMMARY

Introducing BSCLogcol macro for collecting logs in case of problems in BSC.

5. DETAILED DESCRIPTION

BSClogcol collects all configuration data and computer logs of all units. Additionally BSC
logcol collects two sets of message monitorings every time it is executed, one for telecom
processes and one for O&M processes. Optionally it can also collect measurement files from
the BSC. It is mandatory to collect logs from the BSC with BSClogcol, before any trouble
reports is opened and attach those collected logs into the ticket.

The macro is executed on Windows PC connected to the LAN and requires BSC IP address,
username and password as input. By default macro uses Telnet and FTP connections to
collect data from the BSC. If telnet is not available the connection will be automatically made
with SSH and if FTP is not available, then SFTP is used.

By default same username and password is used for MML/ST and FTP access, but it is
possible to use different username for FTP access, by using optional –X startup option to
provide FTP username. Password for FTP access will then be requested during the startup of
the script. Different username for FTP access is available starting from BSClogcol version
2_2_13.

Macro uses direct connectivity from the PC to BSC if it exists i.e. telnet/SSH connection from
PC can be opened to the BSC. If the PCs LAN does not have direct connectivity to the BSC,
the connection will be attempted via SSH “server” (usually NetAct), which needs to support

TS-BSC-SW-0922-I13.0 - Page 4/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
SSH tunneling to enable the telnet/SSH connectivity to the BSC. Should this happen, user
needs to also provide the IP address, username and password of the SSH server.

The macro “bsclogcol.exe” and BSC SW are evolving quite rapidly, therefore the latest
available macro version in NOLS is always required.

Bsclogcol.exe User Interface (UI) provides following symptom report options:

(1) Collect basic data (Select this, unless instructed otherwise)


(2) Emergency log collection (Select this in emergency only)
(3) Collect basic data and measurements (Takes long time)
(4) Collect basic data and do database (DB) integrity check (Takes long time)
(5) Collect basic data, measurements and do DB integrity check (Takes long time)
(6) Collect mcBSC embedded SW info. Note! Collecting this is very slow

6. SOLUTION / INSTRUCTIONS

BSCLogcol usage

1. Extract BSCLogcol.zip
2. A. Double click “bsclogcol.exe” file
B. Start Command Prompt and start BSCLogcol from prompt with –X option to use
different FTP username:
Bsclogcol –X <ftp username> or
Bsclogcol –X
C. Start Command Prompt and start BSCLogcol from prompt with –d option to define the
log collection directory
Bsclogcol –d <log directory>
3. Give BSC IP address

4. Give BSC name. Name is used only as directory name for log storing.

TS-BSC-SW-0922-I13.0 - Page 5/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
5. A. Give BSC username and password.

B. Give BSC MML/ST username and password and FTP username and/or password.

TS-BSC-SW-0922-I13.0 - Page 6/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
6. Logcol will attempt the connection to the BSC. If it is available, continue from 8. If
connection to the given BSC address is not available, give the IP address of the SSH
tunneling server or press CTRL-C to cancel.

7. Give SSH-tunnel server username and password.

8. Select collection type (from 1 to 5)

TS-BSC-SW-0922-I13.0 - Page 7/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
9. Wait for log collection to complete (from 5min to 35 min depending of the size of the BSC)

Logs will be saved to the PC hard disk into a subdirectory of the BSCLogcol installation
directory or into a subdirectory of user defined directory. Subdirectory name is
<installation_directory >\logfiles\<BSC_name>_logs\<yyyymmddhhmm>\ or
<defined_directory > \<BSC_name>_logs\<yyyymmddhhmm>\
e.g.
D:\logcol\logfiles\PYHA_logs\201404171230
Log folders:

Info.txt file contains list of executed commands, execution time of the command and duration
of the command execution. Actual outputs of the executed commands are in their log files

TS-BSC-SW-0922-I13.0 - Page 8/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
divided into different directories. Content of all sub directories should be included into the
trouble ticket.

Most log files can be opened with any text editor e.g. Ultra Edit. UE has also “find in files”
functionality, which helps finding the correct log file containing the output of the desired
command:

Setup the searched string, “root” directory of the log files and tick “Search Subdirectories”.

Search results will be displayed in output window and the log file(s) containing the searched
string can be opened by double-clicking the file name in search results:

TS-BSC-SW-0922-I13.0 - Page 9/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
Example of the macro execution:

BSCLogcol can be started also from command line and optional parameters can be given.
Command line options can be viewed by using –v option I command line:

D:\logcol>bsclogcol.exe -v
Version: 2_2_3
All parameters are optional. If omitted, the tool will ask values for mandatory
parameters
-c <Configuration file. If omitted, default configuration file is used>
-i <IP address file>
-u <Username>
-p <Password>-t <mode>
The modes are 0 and 1. 1 will add time stamp to directory name
Default value is 1, so time stamp is added
-z If option -z exists, the output will be a zip file
-a <ip address of the network element. This can be given instead of -i>
-n <name of the network element. This can be given instead of -i>
-d <destination directory. If omitted, current directory is used>
-r <remote zipping of monitorings before transfer>
-y <data_collection_configuration.cfg>
-v <shows this info>

Advanced parameters: -m 1 #Only start monitorings


-m 2 #Only stop and collect monitorings -
#These parameters require that get_monitorings option
#in the .ini file has bigger value than zero

IP address and username/password -parameters can also be given with capital letter and
those options are used for SSH tunneling server:
-A <IP address of the SSH server>
-U <username of the SSH server>
-P <password of the SSH server>

E.g.
Connection to BSC at 10.16.66.10 via SSH server at 10.8.3.42:
bsclogcol -a 10.16.66.10 -n PYHA -u SYSTEM -p SYSTEM -A 10.8.3.42 -U SYSTEM -P
SYSTEM

Log collection of different BSCs can made easier by creating dos batch files for each BSC:
1. Open texteditor e.g. notepad or UE.
2. Add line (with valid option values):
bsclogcol -a <BSC_IP_ADDRESS> -n <BSC_NAME> -u <BSC_USERNAME> -p <BSC_PASSWORD>
Save file e.g. “<BSC_name>.bat” to BSClogcol installation directory.
Collect logs from the BSC by double-clicking the x.bat file and selecting which log collection
option you want to use.

TS-BSC-SW-0922-I13.0 - Page 10/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
7. NOTES

BSCLogCol can be downloaded from NOLS.

8. REFERENCES

BSC Problem Reporting, DN991432

TS-BSC-SW-0922-I13.0 - Page 11/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential
Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may
not be used except for the purposes defined in the agreement between You and Nokia Solutions and
Networks (“Agreement”) under which this document is distributed. No part of this document may be used,
copied, reproduced, modified or transmitted in any form or means without the prior written permission of
Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if
that Agreement has expired or has been terminated, You may not use this document in any manner and
You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of
the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right
to change any such information and statements without notice. Nokia Solutions and Networks has made all
reasonable efforts to ensure that the content of this document is adequate and free of material errors and
omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,
Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction
of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY
ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and
Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners, and they are mentioned for identification purposes only.
Copyright © 2016 Nokia Solutions and Networks. All rights reserved.

TS-BSC-SW-0922-I13.0 - Page 12/12 © Nokia Solutions and Networks 2016


Version 13.0
Confidential