D2c Software MGMT, Bkup, Restore, PM With AMS PDF

7302-7330-7360 ISAM
Software Management, Bkp-Rst & PM with

5520 AMS
Student Guide
TAC42055_V1.1-SG Edition 2.0
COPYRIGHT ALCATEL-LUCENT @@YEAR. ALL RIGHTS RESERVED.
Passing on and copying of this document, use and communication of its

contents not permitted without written authorization from Alcatel-Lucent
Copyright 2013 Alcatel-Lucent. All Rights Reserved.
Course outline
to 7302-7330-7360 ISAM
1. Welcome
Maintenance
1.
NE SW Management
Software
Management, Bkp-Rst & PM with 5520 AMS
2. Backup & Restore
1. Maintenance
3.
Performance Monitoring
1. NE SW Management
4. Syslog
2. Backup & Restore
3. Performance Monitoring
4. Syslog
3
@@PRODUCT
@@COURSENAME
COPYRIGHT ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.
Course objectives
Upon
completion of this
course, you should be able to:
7302-7330-7360
ISAM
Software
Bkp-Rst
& PM
with
5520 AMS
Describe
howManagement,
software management
is done
by the
5520AMS,
Create an OSWP on 5520AMS,
Download
an OSWP
to an
NE, you should be able to:
Upon completion
of this
course,
Overrule SW on a specific LT,
Activate an OSWP on an ISAM,
Commit
Describean
how
OSWP
software
on an
management
ISAM,
is done by the 5520AMS,
Describe
how
database
management
is done,
Create an OSWP on 5520AMS,
Retrieve on NE which database container is active,

Download
an OSWP
an NE,
Take
a backup
of antoNE,
both direct and scheduled,

Restore
OverruleaSW
backup
on a specific
to an NE,
LT,
Activate
theOSWP
PM counters
(xDSL PON and others) on an NE,

Activate an
on an ISAM,
Use the most common CLI commands & AMS for the PM,

Committhe
an OSWP
on an
ISAM,
Explain
concept
of Threshold
Crossing Alarms (TCA),

Describewhat
how adatabase
done,to set one up,
Explain
protocolmanagement
trace is andis how
Explain
need
for database
the SYSLOG
serveristo
collect tracing information,

Retrievethe
on NE
which
container
active,
Configure the SYSLOG server and protocal tracing via CLI and AMS.
Take a backup of an NE, both direct and scheduled,
Restore a backup to an NE,
Activate the PM counters (xDSL PON and others) on an NE,
Use the most common CLI commands & AMS for the PM,
4
COPYRIGHT ALCATEL-LUCENT
ALL RIGHTS RESERVED.
Explain the concept of Threshold Crossing
Alarms2013.
(TCA),
@@PRODUCT
@@COURSENAME
Explain what a protocol trace is and how to set one up,
Explain the need for the SYSLOG server to collect tracing information,
Configure the SYSLOG server and protocal tracing via CLI and AMS.
Your feedback is appreciated!

Please feel free to Email your comments to:
training.feedback@alcatel-lucent.com
Please include the following training reference in your email:
Thank you!
Learning experience powered by

Alcatel-Lucent University
Section 1
Maintenance
Module 1
NE SW Management
TAC42055_HO01 Edition I2.0
7302-7330-7360 ISAM
Software Management, Bkp-Rst & PM with 5520 AMS
111
Maintenance NE SW Management
7302-7330-7360 ISAM Software Management, Bkp-Rst & PM with 5520 AMS

Module objectives
Upon completion of this module, you should be able to:
Describe how software management is done by the 5520AMS
Create an OSWP on 5520AMS
Download an OSWP to an NE
Overrule SW on a specific LT
Activate an OSWP on an ISAM
Commit an OSWP on an ISAM
Describe how database management is done
Retrieve on NE which database container is active
SW migration (with different DB version) will not be covered!
113

Table of Contents
1 Software Management in NE
2 How
to Upgrade Software on ISAM
1.1 Software management
on 7302-7330-7360 ISAM
3 Database
Management
1.2 Software package (SWP)
4 Exercises
1.3 SWP descriptor file - Example
1.4 AMS: view SWP descriptor file on NE
1.5 Overall software packages (OSWP)
1.6 OSWP descriptor file - Example
1.7 SWP and OSWP descriptor files
1.8 Download software
1.9 OSWP states
1.10 OSWP state transitions
1.11 Retrieval of software information
2 How to Upgrade Software on ISAM
2.1 Import SWP to AMS
2.2 Step 1 : Copy ISAM software from ALED web to AMS
2.3 Step 2 : Repack the SW
2.4 Step 3 : Prepare ISAM SW PKG on AMS server - Create OSWP
2.5 Download OSWP to NE How we have the two OSWPs
2.6 Download OSWP to NE Make an OSWP available
2.7 Download OSWP to NE Download to NE
2.8 Download OSWP to NE - Downloading
2.9 SW overrule on LT
2.10 Activate OSWP on NE (SW perspective)
2.11 Activate OSWP on NE (equipment perspective)
115
2.12 NECommit
activated OSWP
Maintenance
SW Management
2.13 OSWP New Status
2.14 OSWP Status Transition - Overview
2.15 Configure OSWP & database settings using CLI
2.16 CLI OSWP commands: download, abort, activate, commit
3 Database Management
3.1 Database in NE
3.2 Upgrade versus migration
3.3 DB version and OSWP compatibility
3.4 Database management in NE
3.6 Database states for active OSWP
3.7 Example of DB state transitions
3.8 Consult database containers on ISAM
4 Exercises
4.1 Software Management exercises

Page
7
8
9
13
14
15
16
17
18
24
25
27
28
29
30
35
37
39
40
41
46
48
49
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
7
28
57
66
117

1.1 Software management on 7302-7330-7360 ISAM

Management of software packages
SHUB SW is part of the same SW package
Software upload and download uses TFTP

ISAM is TFTP-client
AMS and/or an external server is TFTP-server
AMS
Download Request
Activation Request
Commit Request
Abort Request
Manager
CLI or TL1
ISAM
agent
SNMP / CLI / TL1
TFTP GET SW Request

Can reside
on AMS
TFTP
TFTP
client
TFTP server
118

NT
Storage
Device
1.2 Software package (SWP)
SWP = Software package

Software files for
NANT-x
SW for IACM:
Software files for

FANT-x
Software file(s) per board:

Software files for
NALT-E
Different types of SW files
SW for SHUB is included too

Software files for
ECNT-C
SW file type H
119
Software files for

NVLT-C
Software files for
Each board requires its specific software. The software for a specific board can consist out of
different software files.
A SW file corresponds to an executable for a specific board type (or for SHUB).
Two types of SW files can be distinguished:
Type
A:
boot packages files
Type
B:
the common operation SW files and
the specific operational SW files.
For
NTs, there are many more SW files and types. Also SHUB SW (type H).

Nomenclature (see customer documentation):

Type-A:
FPGA SW, startupfile, etc... for NT or LT
Type-B:
OSW for NT or LT
Type-C:
NT OSW selector file
Type-D:
FPGA selector file
Type-E:
OFLT selftest selector file (autonomous)
Type-F:
OFLT selftest selector file (interactive)
Type-G:
Data Driven ISAM Configuration file
Type-H:
LANX OSW file
Type-I:
Type-A file ODM boards
Type-J:
Type-B file for ODM boards

1.2 Software package (SWP) [cont.]

SOFTWARE PACKAGE (SWP)
SWP consists of:

Compilation of
software files
Software files
Software descriptor file
Software File(s)
for NANT-x
Software files for

FANT-x
Software file(s)
for ECNT-C
SWP descriptor file defines:

DB version nr
Software file(s)
for NALT-E
Software file(s)
for NVLT-C
Per board
Software file(s)
for xxx
Applicable SW files
Name, format, size
Compressed: yes/no
Minimum set: yes/no
Software Descriptor File
1 1 11
Each individual SWP consists of
one SWP descriptor file and at least one software file.
The SWP descriptor file, as well as the overall descriptor file (OSWP descriptor file), are ASCII text files.
An SWP descriptor file contains following information:
The
version number of the compatible database. This is the version number of the database that can be
interpreted by the considered ISAM-CORE SWP. (see further)

For
each supported board type, the SWP descriptor file indicates whether the board expects the applicable
software in compressed or uncompressed format.

For
each supported board type, the SWP descriptor file indicates whether the SW files of that board belong
to the minimum set for that specific SWP or not.

For
each applicable SW file of a specific board type, the SWP descriptor file contains the file name, the file
format, and the file size.

The following sets of files exist for an OSWP:

Minimum
Set of Files:
This is the set of files that are really needed for the activation of the considered OSWP.
The Overall descriptor file and the descriptor files of the supported SWPs always belong
to this minimum set. The SWP descriptor files specify, for each supported SW file,
whether it belongs to the minimum set or not.
Actual
Set of Files:
This is the set of files that belong to the minimum set of the considered OSWP, together
with the files applicable for LT types that are detected and/or planned (but without board
type mismatch and without being blocked).
Complete
Set of Files:
All the files (SW files and descriptor files) supported by the considered OSWP.

1.3 SWP descriptor file - Example

DESCRIPTOR-FILE L6GQAA36.231
DESCRIPTION NVLT-C
BEGIN
BEGIN
SYNTAX-VERSION : 01.00;
TARGET
COMPRESSION : NO;
: ASAM-CORE;
MINIMUMSET : NO;
DBASE-VERSION : A3.600;
DESCRIPTION AGNT-A
BEGIN
TYPE-A
: MWEJAA33.010 1826124 TAR;
TYPE-B
: MWEDAA36.231 4576330 LZ77;
END
COMPRESSION : YES;
DESCRIPTION NVLT-D
MINIMUMSET : NO;
BEGIN
TYPE-A
: NAGMAA36.231 23 ASCII;
TYPE-A
: NAGNAA36.231 15 ASCII;
TYPE-A
: NAGPAA36.231 16 ASCII;
TYPE-A
: MERYAA36.231 3388823 ASCII;
TYPE-A
: M16UAA36.002 1040536 EXE;
TYPE-B
: M16RAA36.231 9675090 EXE;
TYPE-G
: MJN5AA36.231 235520 TAR;
TYPE-H
: MTJ9AA36.900 3423405 EXE;
END
COMPRESSION : NO;
MINIMUMSET : NO;
TYPE-A
: MWEJAA33.010 1826124 TAR;
TYPE-B
: MWEDAA36.231 4576330 LZ77;
END
DESCRIPTION NVPS-A
BEGIN
COMPRESSION : NO;
MINIMUMSET : NO;
DESCRIPTION ECNT-A
BEGIN
COMPRESSION : YES;
TYPE-A
: MW39AA36.022 800742 TAR;
TYPE-B
: MW4BAA36.213 3442866 LZ77;
END
MINIMUMSET : NO;
TYPE-A
: L6GSAA36.231 22 ASCII;
1 1 13
Every SWP for ISAM is an IACM SWP.

The descriptor file describes the database version. In this example, A3.600 is for ISAM R3.6.
For each board, there are typically several software files. For LTs, there are typically two. But
for NTs, there are many more!

1.4 AMS: view SWP descriptor file on NE

Network
Select NE
Infrastructure
Software
SWP
Select SWP
Contained file
1 1 14

1.5 Overall software packages (OSWP)

An OSWP comprises:
One software packages (SWP)
An overall descriptor file
OSWP
Overall descriptor file
Name of the SWP

IP-address of TFTP-server(s) where SWP can be found
SWP
SWP descriptor file
SW files
1 1 15
The above drawing illustrates how an OSWP is composed.

The overall descriptor file contains information over the SWP which belongs to the OSWP:
- the name of the SWP
- the IP-address of the TFTP-server where the SWP can be found.
The OSWP concept was introduced in the 7301 ASAM and there it was possible to have
several SWPs (for IACM and server boards, like the ISM) combined into one OSWP. For ISAM,
there will be only one SWP per OSWP.

1.6 OSWP descriptor file - Example

/var/opt/ams/shared/ams-ams-9.1.10.0-148894 /ne/OSWP/<name of
OSWP> (The ams-9.1.10.0-148894 is for AMS in 9.1.10)
/ams/swm/ne/iSAM/R4.4.04/SWP/L6GQAA44.628/<name of OSWP> (for
AMS R9.2.10)
Overall descriptor file Name
OVERALL-DESCRIPTOR-FILE L6GPAA44.628
SWP name
BEGIN
ASAM-CORE
: L6GQAA44.628/L6GQAA44.628 172.31.230.23 0.0.0.0;
END
SWP-Descriptor-File
Path on TFTP server:
/ASAM-CORE/L6GQAA44.628/
1 1 16
Primary
TFTP server
Secondary
TFTP server
When the AMS acts as the TFTP server, theres no need to fill in any IP-addresses for the
TFTP servers.
After
the OSWP is downloaded to the NE, the IP-address of the AMS is filled as primary
TFTP server.

1.7 SWP and OSWP descriptor files

The OSWP info consists of two parts:
The path on the TFTP-server where SWP can be found:
Primary and secondary TFTP server
The name of the SWP descriptor file itself

String with same syntax as SW files (defined by Alcatel)
e.g., for ISAM :L6GQAA37.100
Cannot be changed
Restrictions:
SWP descriptor file name = SWP name
SWP descriptor file in the same directory as the SWP SW files
Name of OSWP itself: L6GPxxxx.yyy controlled by operator
1 1 17
There is a restriction, that the descriptor file and the software files of a specific SWP must be
located in the same directory on the same TFTP server.
The name of the SWP and SWP descriptor file are defined by Alcatel and shouldnt be
changed.
The name of the OSWP can be defined by the operator, as long as the syntax is respected.
For ISAM, the name of the OSWP has to start with L6GP.
The path on the TFTP server is defined by the operator.

1.8 Download software

Download of OSWP instead of separate SWFiles
SW
Perspective
Maximum 2 OSWPs on an ISAM

Downloading an OSWP is only possible
if NE contains only 1 OSWP
NE
Download SW to NE
NT
OSWPy
1 1 18
OSWPx
The ISAM is able to handle two OSWPs simultaneously. When two OSWPs are already residing
in the ISAM and the operator requests to download a third OSWP, an error message will be
thrown.

1.8 Download software [cont.]

The OSWP descriptor files, SWP descriptor files and SW files:
On the AMS itself or
On an external TFTP server
Its possible to use several TFTP servers

OSWP descriptor file and SWPs neednt be on the same server
TFTP server 2
TFTP server 1
7302-7330-7360 ISAM
AMS
1 1 19


The download of an OSWP is initiated by the manager
The download request contains:
Path for the Overall Descriptor file.
IP address of the TFTP-server(s) where the Overall Descriptor file can be found.
NE
NT
OSWPy
OSWPx
EMPTY
Enabled
Active
Download Request
Committed
AMS
Conf.
1 1 20
1) A download request contains the following information:

Path name of the corresponding Overall Descriptor file
IP address(es) of the TFTP-server(s) where the Overall Descriptor file can be found
The information specified in the download request is configured by the operator in the AMS:
Via
OSWP management for OSWP descriptor files stored on the TFTP server running on
the AMS.
Via
External OSWP management for OSWP descriptor files stored on an external TFTP
server.
The download request will only be accepted in case only one OSWP is available in the system.
After acceptance of the download request, the download process is started.


TFTP
server1
NE
TFTP Client
NT
OSWPy
EMPTY
OSWPx
Enabled
Active
Committed
AMS
Conf.
The overall descriptor file contains:

Name of the SWP
IP-address of TFTP-server(s) where SWP can be found
1 1 21
2) Get Request for Overall Descriptor File

The TFTP client in the ISAM now knows all the information necessary to get the OSWP
descriptor file from the TFTP server.
The transfer of files (descriptor file, SW file, or database tar-file) will be a part of some
SW-DB-processes. The file transfer will be performed via TFTP and a specific service inside
the ISAM (i.e. the TFTP service) will be responsible for the handling of the TFTP protocol.
Files will always be transferred between the ISAM and an TFTP server. This TFTP server can
be collocated on the same machine as the SNMP manager or it can be located on (a) separate
machine(s).
3) Overall Descriptor File uploaded to the ISAM, via TFTP


NE
TFTP
server2
NT
OSWPy
Enabled
NotActive
Uncommitted
OSWPx
Enabled
Active
Committed
Conf.
AMS
5
1 1 22
Checks
Definition of the SW files that are
not yet residing on the ISAM:
Minimum set
Actual set
Available resources in the ISAM
4) Retrieval of Software Descriptor Files of SWPs

The OSWP descriptor file specifies for each SWP the path name of the corresponding SWP
descriptor file and the TFTP-server where that SWP descriptor file can be found.
The system downloads the SWP descriptor file of each SWP, specified in the overall descriptor
file and not yet available in the system.
5) Check
Each SWP descriptor file specifies the different SW files supported by the corresponding SWP.
The exact size of each SW file is also mentioned in the SWP descriptor file. Based on this
information, the system defines all the SW files that still need to be downloaded.
After selection of all the files that must be downloaded, the system first checks if sufficient
resources are available for their persistent storage.

6) Download of SW files
A SW file specified in one of the SWP descriptor files of the OSWP will only be downloaded in case
it is not yet available in the system.
Each SWP descriptor file specifies the different applicable SW file(s) and whether or not they
belong to the minimum set of the OSWP. The system downloads the SW files that are specified in
the downloaded SWP descriptor files on the following conditions:
Sufficient
resources are available for their persistent storage.
The
SW file is not yet available in the system.
The
SW file belongs to the actual set of the new OSWP, which means that the SW file belongs
to the minimum set of the new OSWP or to a board type that is planned and/or detected in
the system.
The system downloads the selected SW files in the following order:
The
SW files that belong to the minimum set of the new OSWP.
The
SW files belonging to the actual set, but not to the minimum set of the OSWP (if
requested by the manager).

Note: The SHUB SW file is part of a SWP and is handled as any other SW file.

1.9 OSWP states

Network
Select NE
Infrastructure
Software
OSWP
OSWP activition status
OSWP commit status
Active
Committed
Not active
Uncommitted
OSWP availability status
Committing
Enabled
Disabled
Downloading
Aborting
1 1 24
OSWP Availability Status
- Enabled: The OSWP is ready to become active or is already active. All files of the
considered OSWP are available on the system.
- Disabled: The OSWP cannot become active, since at least one of the files is not available
on the system.
- Downloading: The OSWP cannot become active, since the download of the requested set of
files is still ongoing.
- Aborting: The system is still busy removing the files not belonging to the current Active
OSWP from the file disk.
OSWP Activity Status
-Active: The OSWP is currently operational. The value of the Availability Status must be
Enabled.
-Not Active: The OSWP is not operational. Any value of Availability Status is now possible.
OSWP Commit Status
- Committed: The value of the Availability Status must be Enabled .

- Uncommitted
- Committing: The system is still busy on the requested commit operation, i.e., removing files
from the file disk that dont belong to the committed OSWP.
1.10 OSWP state transitions

Network
Activate
Upgrade to a new OSWP / rollback
Commit
Commit active OSWP to remove the inactive OSWP
Select NE
Infrastructure
Abort
ISAM deletes all files from the NT that dont belong to
the enabled/active/committed OSWP
Status of OSWP that you want to abort is
NotActive/Uncommitted
Re-download
Download additional files from the active OSWP for
new types of boards
1 1 25
Software
OSWP
Activate
Commit
Abort
Re-download
Activating OSWP allows an operator to perform upgrade/rollback of an NE. The software on all boards
will be upgraded at once. (For SW upgrade of individual LT boards refer to SW overrule.)
Concerning Committing OSWP, the ISAM will commit an OSWP only if two OSWPs are available.
The commit operation is only possible on an enabled/Active/uncommitted OSWP and the other OSWP
must have status enabled/NotActive/committed. It can only be initiated by an explicit request from
the management station. After the acceptance of the commit request, the system will remove all
persistent stored files that are not related to the Active OSWP. When the commit request is
terminated, the Active OSWP is the only OSWP in the system. The status of this OSWP will be
Enabled/Active/Committed.
Concerning Aborting OSWP, the manager also has the possibility to request the ISAM to remove an
OSWP from its storage device, on the condition that this OSWP is NotActive and uncommitted or to
stop the downloading of an OSWP.
Boards for which the SW Overrule parameter is enabled will be loaded with the applicable SW files
belonging to the Enabled/Active/Committed OSWP. The SW Overrule parameter will automatically be
disabled by the ISAM.
There are two ways of deleting an OSWP: abort and commit. These commands are useful in different
situations:
To
get rid of a committed, but inactive OSWP, youll have to commit the other OSWP, which is
active but uncommitted.
To
get rid of an OSWP which has never been committed, youll have to use the command Abort.
1.10 OSWP state transitions [cont.]

1
OSWPx
Normal procedure with ok result
OSWPy
OSWPx
OSWPy
Enabled
Enabled
EMPTY
EMPTY
Active
Active
Committed
Committed
Abort OSWP y
Download
OSWP y
Commit
Command also possible when

OSWP is in availability status
Downloading
Activate
Not active OSWP
OSWPx
OSWPy
Enabled
Enabled
Active
Committed
Implicit Rollback
OSWPx
OSWPy
Enabled
Enabled
Not Active
Not Active
Active
unCommitted
Committed
unCommitted
Activate
Not active OSWP
1 1 26
Initially, the ISAM contains one OSWP. This OSWP is committed and its software is active on
the different ISAM boards.
Next, the manager (on explicit operator command) requests the ISAM to download a new
OSWP.
The ISAM itself fetches the requested OSWP from the file server. After the download process,
two OSWPs are available in the ISAM: the current active OSWP and the new downloaded
OSWP.
In a next step (assuming the operator wants to keep the new downloaded OSWP), the
manager (on explicit operator command) requests the ISAM to activate the software of the
downloaded OSWP on all the boards. The previously active OSWP will stay available in the
ISAM. By doing this, the manager still has the possibility to request the ISAM to rollback to
this previous active OSWP in case the operator is not satisfied with the new OSWP.
Finally, (when the operator is satisfied with the new OSWP), the manager requests the ISAM
to commit the new OSWP. The previously active OSWP will be removed from the ISAM
software storage device.
If the operator changes his mind while downloading a new OSWP or after completing the
download (as long as the OSWP has never been committed), he can abort the OSWP.
1.11 Retrieval of software information

For each SWP and OSWP residing on the
ISAM, you can retrieve:
OSWP availability status
Network
Select NE
Infrastructure
OSWP activity status
Software
OSWP commit status

OSWP
SWP
SWPs included in the OSWP

Primary and secondary TFTP server of
relevant SWP
1 1 27

1 1 28

2.1 Import SWP to AMS
Import software package (SWP) to AMS from CD ROM or FTP

Import SWPs to directory:
/var/opt/ams/shared/common/ne/software
All SWPs in this directory will be recognized when you create an overall
SW package (OSWP)
1 1 29
29
The directory /var/opt/ams is the default directory for data. At installation time, the installer
may decide to select a different directory.
First you must put the SWP in the dedicated directory:
/var/opt/ams/shared/ne/software
When you create the OSWP, the AMS will look in this directory for any SWPs. These SWPs
will appear in the list. You can pick your choice.

2.2 Step 1 : Copy ISAM software from ALED web to AMS

Sign in from http://www.alcatel-lucent.com/
1
2
h
1 1 30

2.2 Step 1 : Copy ISAM software from ALED web to AMS [cont.]
1
2
3
Select the Release

Select the Sub-Release
5
6
1 1 31

1
Be Patient. It takes some time to appear
Again be patient. It takes some time to appear
1 1 32

It takes sometime to start the downloading
Downloading to selected folder in PC
Download complete. It took 6:26 minutes.
1 1 33

FTP
ISAM sw package downloaded, in this case, in /shared/ISAM

1 1 34

AMS
2.3 Step 2 : Repack the SW

This step is only necessary in AMS release prior to R9.2.30
In R9.2.30, ams_sw_repack.sh script is no longer available
Use ams_sw_repack.sh script found in /opt/ams/software/<ams release>/bin/ to repack

the sw and put it in the right path so the AMS sees it to prepare it in the next step.
1 1 35

2.3 Step 2 : Repack the SW [cont.]

This step is only necessary in AMS release prior to R9.2.30
In R9.2.30, ams_sw_repack.sh script is no longer available
1 1 36

2.4 Step 3 : Prepare ISAM SW PKG on AMS server - Create OSWP

1
6
7
h
8
9
1 1 37
Therere two options in the creation of NE SW Releases:

NE SW Release From Repacked Archive create SW from repacked archive generated in step 2. (please refer
to slides 2.8)
NE SW Release create SW from archive downloaded from OLCS. (please refer to slides 2.2-2.5)
From R9.2.30 onwards, AMS hides the script ams_sw_repack.sh by which the operator can manually change
the structure in previous releases. The process of repacking is performed by AMS automatically. The
generated repacked archive locates at the folder /shared/common/ne/software/repacked which is
introduced in R9.2.30. As long as the existence of a repacked archive, ONT SW Release From Repacked
Archive can be used to create the ONT SW package as well. If an un-repacked archive is chosen, an error will
pop up indicating The file has an invalid structure.

2.4 Step 3 : Prepare ISAM SW PKG on AMS server - Create OSWP [cont.]
Previous step created OSWP from SWP
name e.g. L6GPAA45.187
L6GP OSWP for ISAM
45 major release 4.5
187 build
Leave all as Used.

The ISAM decides which ones are needed. If you
put one as Unused, the rest will be mandatory,
which can fill up the flashcard, or you will get an
error message of not enough space.
1 1 38

2.5 Download OSWP to NE How we have the two OSWPs
OSWP status
1 1 39
We will look at the OSWP, with Activation Not Active and Commit Uncommited.

2.6 Download OSWP to NE Make an OSWP available
2
3
Bottom right side

Abort to empty the OSWP
Or let the AMS remove the passive OSWP automatically while downloading
1 1 40
From R9.2.30 onwards, there is an additional option in the function of OSWP downloading by check which AMS
will remove the passive OSWP automatically (see slide 2.14).

2.7 Download OSWP to NE Download to NE
The OSWP2 is
empty as the
result of the abort
ISAM
AMS
2
ISAM SW
1 1 41

2.7 Download OSWP to NE Download to NE [cont.]
7
4
6
h
Check this to skip the step

of aborting OSWP manually
1 1 42
Continues in slide 45
Next two slides another option in Downloading
to NE

1 1 43

In this case, the AMS is the

File Server
1 1 44


Download of complete software package to NE(s)
SW
Perspective
Download to NE
ISAM
NT
1 1 45
Click as task Download software to NE.

Select NE(s) or NE group(s).
Select the appropriate OSWP.
Click finish and confirm.
The download will take a while.

After the download, this OSWP will be present on the NE, but it wont be activated yet.

2.8 Download OSWP to NE - Downloading
1 1 46

2.8 Download OSWP to NE - Downloading [cont.]
1 1 47

2.9 SW overrule on LT
NE
Test new SW on single LT:

Select board SW overrule-Enable
The inactive SW will be used on this LT
NT
Network
OSWPy
Enabled
NotActive
unCommitted
Select NE
NE
OSWPx
Enabled
Active
Committed
Conf.
Rack
Subrack
Slot LT
1 1 48

2.10 Activate OSWP on NE (SW perspective)

Select NE SW Release
Select actions: activate (keep or erase persistency)
SW
Perspective
NE SW Releases
1
2
3
1 1 49
When you activate new SW, this operation is service affecting!

When you activate the new software, you have two options: either you keep the data or you
start again from a default database (erase persistency).
In order to get rid of the OSWP which is not activated yet, you can abort the OSWP. The
OSWP will then be deleted from the NE.
You
cannot use the operation abort in order to remove an OSWP which is activated.

2.10 Activate OSWP on NE (SW perspective) [cont.]

7
4
Keep or erase persistency
1 1 50

2.11 Activate OSWP on NE (equipment perspective)

Select inactive OSWP on NE
Actions activate
Network
Select NE
Infrastructure
OSWP1
Software
OSWP
OSWP2
Select inactive OSWP

Actions
Activate
Bottom right side

1 1 51

2.12 Commit activated OSWP

Commit activated OSWP in order to remove the inactive OSWP
Network
Select NE
Infrastructure
2
3
Software
OSWP
Select active OSWP
Actions
Commit
1 1 52

2.13 OSWP New Status
1 1 53

2.14 OSWP Status Transition - Overview

STATUS
OSWP1
OSWP2
ACTIVATION
NOT ACTIVE
ACTIVE
AVAILABILITY
ENABLED
ENABLED
COMMIT
UNCOMMITTED
COMMITTED
Command ABORT OSWP1

ACTIVATION
NOT ACTIVE
ACTIVE
AVAILABILITY
EMPTY
ENABLED
COMMIT
UNCOMMITTED
COMMITTED
Command DOWNLOAD SW
ACTIVATION
NOT ACTIVE
ACTIVE
AVAILABILITY
DOWNLOADING
ENABLED
COMMIT
UNCOMMITTED
COMMITTED
Status: NEW SW
ACTIVATION
NOT ACTIVE
ACTIVE
AVAILABILITY
ENABLED
ENABLED
COMMIT
UNCOMMITTED
COMMITTED
Command ACTIVATE OSWP1

ACTIVATION
ACTIVE
NOT ACTIVE
AVAILABILITY
ENABLED
ENABLED
UNCOMMITTED
COMMITTED
COMMIT
Command COMMIT OSWP1
1 1 54
ACTIVATION
ACTIVE
AVAILABILITY
ENABLED
COMMIT
COMMITTED
NOT ACTIVE
EMPTY
UNCOMMITTED
COPYRIGHT ALCATEL-LUCENT
2013. ALL RIGHTS RESERVED.

Only necessary if inactive

OSWP has SW inside
2.15 Configure OSWP & database settings using CLI

First configure file server for OSWP download:
configure software-mngt oswp (index)
primary-file-server-id <IP-@> second-file-server-id <IP-@>
activate manually | after-download
Configure database settings (activate / (auto-)backup)

configure software-mngt database
(no) activate <SwMngt::DbAutoAct>
(no) backup <SwMngt::DbAutoBackup>
(no) auto-backup-intvl <SwMngt::DbAutoBackIntvl>
1 1 55
configure software-mngt database

[no]
activate
: determines when to active database (default = manually)
[no]
backup
: backup destination of database (default = manually)
[no]
auto-backup-intvl: the interval period for automatic backup (default = 24)

2.16 CLI OSWP commands: download, abort, activate, commit

Launch the OSWP download:
admin software-mngt oswp (1 or 2) download <OSWP name>
Abort an OSWP download:

admin software-mngt oswp (index) abort-download
Activate an OSWP:
admin software-mngt oswp (index)
activate manually | after-download
Commit an OSWP:
admin software-mngt oswp (index) commit
1 1 56

1 1 57

3.1 Database in NE
NE
MIB
Management Information Base
MIB = set of files on flash memory in a dedicated directory.
Each file in this directory contains data: e.g.
Equipment information
Profiles
VLANs
bridge ports
Alarm- and trap settings
System data
Software is not part of the MIB!

1 1 58
Each NE has its own Management Information Base with his own set of standard set of
statistical and control values. In case of an ISAM this means:
equipment information
profiles
VP/VC
parameters (in case ATM is used, e.g. for multi-DSL and SHDSL)
bridge
ports
VLANs
VLAN
associations
alarm and
and trap settings
system data
All of this information is stored in separate files in some dedicated directory on the NE.
The MIB is stored on the FLASH of the NT board. Software is also stored on the FLASH, but
is not part of the MIB.
This is important because a backup only contains the configuration data, i.e. the MIB, and not
the software!
3.2 Upgrade versus migration

Upgrade:
During SW update the DB is not modified. No new database is created.
e.g. upgrade within the same major release, from 3.3.x to 3.3.y
Migration:
A system software update during which the DB is modified and must be
converted to be compatible with the new SW release.
e.g. migration when you update SW from one major release to
another, e.g. from 3.6 to 3.7
A migration tool is needed to modify the DB
1 1 59

3.3 DB version and OSWP compatibility

SWP descriptor file specifies the DB-version that can
be interpreted by the SWP
SWP
SWP Descriptor File
DESCRIPTOR-FILE L6GQAA36.231
DB version nr
per board
applicable SW files
name, format, size
BEGIN
TARGET
compressed: yes/no
minimum set: yes/no
type
: ASAM-CORE;
DBASE-VERSION : A3.600;
An OSWP will be linked to a database if the OSWP is

compatible with the database
Compatible same DB version
1 1 60

SW Files

Many to one relationship between OSWPs and DB
OSWP1
Contains
Contains
SWP1
Can
interprete
OSWP1
OSWP2
Contains
SWP1
SWP2
IACM
DB
Version 01.000
with config x
Can
interprete
IACM
DB
Version 01.000
1 1 61
IACM
DB
Version 02.000
Case 1
Suppose we have an NE with a certain initial configuration. The NE is using that configuration
=> it is the actual configuration.
We want to do a software upgrade => You download a new OSWP that is also compatible
with DB-version x. In this case, the DB can be linked to the 2 OSWPs. Of course, only one
OSWP can be active at a time.
Case 2
An OSWP can be compatible with only one DBversion. Or in other words, it is not possible
that one OSWP can be linked with two DBs with different DB-version.


Each available OSWP will be linked to at most two available
databases at a time
Active OSWP1
Not Active OSWP2
SWP1
SWP2
Linked to
Container 1
Container 2
Container 3
IACM
DB1
Version 01.000
With Config x
IACM
DB2
Version 01.000
With config y
IACM
DB3
Version 02.000
With config y
1 1 62
When an OSWP is linked to more than one DB, the states would typically be actual and
previous. For more information on DB states, see the following slides.

3.6 Database states for active OSWP
Actual
DB currently used by the active OSWP
Preferred
DB not used yet but will be used after a successful reactivation of the active
OSWP
Previous
Previously actual database of the active OSWP
Failed
Compatible DB, but OSWP fails to use it.
Not useful
DB is not compatible with OSWP
1 1 63
A database that used to be actual can never become preferred afterwards.

The state will then be previous instead.
In a similar way, different states are defined for the inactive OSWP:
Actual
DB that will be used after a successful activation of the inactive OSWP, unless theres
a preferable DB
(DB may or may not have been used by the inactive OSWP before.)
Preferable
DB not used yet. There is also a actual DB available.

Preferable DB will be used after the successful activation of the inactive OSWP.
Previous
Previous database at the time this inactive OSWP was still active.
Failed
Not
useful
3.7 Example of DB state transitions

OSWP1 DB container 1 contents: x
Take backup of DB (contents: x)
Change configuration (e.g. plan a new board)
DB container 1 has now contents y
Restore the previous configuration

DB container 2 has contents x
NE restarts with database in container 2
DB container 1
DB container 2
DB container 3
actual
previous
actual
1 1 64
On the slide, you can see the state transitions of DB containers on ISAM.
When you do a restore, there are several phases in the process:
First
you download the data from the backup in an available DB container (in this case:
DB container 2). This DB container gets the (intermediate) state: preferred.

Then
the NE restarts with the preferred DB (in this case with DB container 2).
This one will become the actual and the one that used to be actual gets the state
previous.
In the example, the OSWP is linked to two DB containers (DB container 1 previous; DB
container 2 actual).

3.8 Consult database containers on ISAM

CLI: show software-mgmt database
AMS:
Network
Active OSWP1
Select NE
Container 1
Container 2
actual: active
Version A3.600
Actual:not-active
config x
config y
Infrastructure
Software
Not Active OSWP2
Version B3.350
Container 3
EMPTY
DB
1 1 65
In this example, the node had two OSWPs:

OSWP1
ISAM R3.6 (active)
OSWP2
ISAM R3.3 (not-active)
There are two database containers used:

Container
1 is the actual DB for the active OSWP1. Since it not compatible with OSWP2,
it is not useful for OSWP2.

Container
2 is the actual DB for the not-active OSWP2. Since it not compatible with
OSWP1, it is not useful for OSWP1.

4 Exercises
1 1 66

Software Management exercises

Have a look at the SWP descriptor file of the active OSWP on your DSLAM. Where can you
find this?
Create a new OSWP. Ask your teacher which SWP to use.
Download your OSWP to your NE. Check the status afterwards (enabled?).
(What do you need to do is theres no room for an additional OSWP on the NE?)
Select an LT and overrule the software for this board. How can you check which SW is
used?
Activate your OSWP. Check the status of both OSWPs on your system.
Insert a new type of board in your NE. What is the operational status of this board? What
do you need to do to make this board operational?
What can you do to get rid of the old OSWP? Try it.

Module Summary
After completing this section, you are able to:
Describe how software management is done by the 5520AMS
Create an OSWP on 5520AMS
Download an OSWP to an NE
Overrule SW on a specific LT
Activate an OSWP on an ISAM
Commit an OSWP on an ISAM
Describe how database management is done
Retrieve on NE which database container is active
SW migration (with different DB version) was not covered!
1 1 68

End of module
NE SW Management
1 1 69


This page is left blank intentionally
Document History
Edition
Date
Author
Remarks
01
Oct/2012
Alcatel-Lucent University Madrid
R4.4-AMS 9.1.10
02
Sept/2013
ALU - University Madrid
R4.5/R4.6 - AMS R9.2.30


Page
1 ISAM Backup / Restore
1.1 Backing up the database
1.2 Backup Parts: IACM & xHUB
1.3 Direct backup
1.4 Backup Restore Perspective - overview
1.5 Taking backup from Backup Restore Perspective
1.6 Delete a backup
1.7 Scheduled Backup
1 8 Scheduled job
1.8
1.9 Manual Restore
1.10 Copy a backup file from one NE to another
1.11 Exporting a NE backup file to a file on the AMS server
1.12 Importing NE backup files from the AMS server
1.13 Check Backup Consistency
1.14 Backup File Management
2 Backup / Restore with CLI
2.1 CLI - ISAM backup / restore configuration
2 2 CLI - Automatic backup
2.2
2.3 CLI - Manual backup / Restore
2.4 Restore: AMS status check before/after restore via CLI
3 7302/5520 Hands-on
3.1 Exercise 1
3.1 Exercise 2
3.1 Exercise 2

7
8
9
10
11
12
15
18
22
25
26
27
28
30
31
32
33
34
35
37
38
39
40
41
Entry level requirements:

In this section youll learn:
How
to take a manual or direct backup via the AMS
How
to schedule periodic backups via the AMS
How
to restore a backup of the IACM via the AMS
How
to restore a backup of the service hub via CLI

The backup of a database also includes the profiles. So when you restore the configuration theres NO need to
download the profiles prior to the restore.
Backup and/or restore can be triggered manually and/or automatically via the Backup Restore view. Automatically
is configured by a schedule script.


Backup files are stored in the following folder :
AMS R8.3: /opt/ni/ne/backup/3/ (where /opt is the default directory for the installation of the core
AMS software)
AMS R8.4 onwards: /var/opt/ams/shared/ams-4.0.-50677/ne/backup/[ID] (where [ID] stands for the
IACM agent internal ID)
AMS R9.0.1 onwards (including R9.2.30): /var/opt/ams/shared/common/ne/backup (individual ISAMs
have their own directory with their IP address as a name)
From AMS R9.0.1 onwards (including R9.2.30), the name of the backup files is composed as follows:
<IP-address>_IACM_<softw-version>_xx_<yyyy>_<mm>_<dd>_<hh>_<mm>_<ss>.gz
Where xx stands for the two option you can see when taking a backup:
1.
Including OAM channel information (for migration) : n or y (no or yes)
2
2.
Never deleting file : n

n or y
y (no or yes)










Before we can setup an automatic backup, we need to create a scheduler.

With the scheduler template, we can configure several schedule details, once; daily; weekly; monthly; etc.



The unschedule job will remove the job, in this case the Backup, inside this schedule, leaving the schedule.


(Optional) Select the Forced Restore check box if you do not need to validate the file version you are restoring. If
there is a version mismatch, an error message is displayed.
There is no automatic restore implemented in 5520AMS. Typically, operators prefer to have some control of what
is being restored.





PBMT : Push Button Migration Tool

The PBMT is not used for the consistency check, but the check script is part of the PBMT, so needs to be present on
AMS Server.

PBMT : Push Button Migration Tool

The PBMT is not used for the consistency check, but the check script is part of the PBMT, so needs to be present on
AMS Server.

Backup files are stored in the following folder :
AMS R8.3: /opt/ni/ne/backup/3/ (where /opt is the default directory for the installation of the core
AMS software)
AMS R8.4 onwards: /var/opt/ams/shared/ams-4.0.-50677/ne/backup/[ID] (where [ID] stands for the
IACM agent internal ID)
AMS R9.0.1 onwards: /var/opt/ams/shared/common/ne/backup (individual ISAMs have their own
directoryy with their IP address as a name))





BACKUP EXAMPLE VIA CLI

leg:isadmin># admin software-mngt database upload actual-active:172.31.79.244:dm.tar
leg:isadmin>admin>software-mngt>database$ show software-mngt upload-download
==================================================================================
upload-download
upload
download table
==================================================================================
disk-space : 151539712
free-space : 122060800
download-progress : download-success
upload-progress : upload-ongoing
download-error : no-error
upload-error : no-error
auto-activate-error : no-error
==================================================================================
leg:isadmin>admin>software-mngt>database$ show software-mngt upload-download
==================================================================================
upload-download table
==================================================================================
disk-space : 151539712
free-space : 122060800
download-progress : download-success
upload-progress
upload
progress : upload
upload-success
success
download-error : no-error
upload-error
upload
error : no
no-error
error
auto-activate-error : no-error
==================================================================================
leg:isadmin>admin>software-mngt>database$
Upload options:
leg:isadmin># admin software-mngt database upload ?
actual-active:<...> ! actual database for active OSWP
preferred-active:<...>! preferable database for active OSWP
previous-active:<...> ! previous database for active OSWP
failed-active:<...> ! failed database for active OSWP
actual-not-acti*:<...>! actual database for not-active OSWP
preferred-not-a*:<...>! preferable database for not-active OSWP
previous-not-ac*:<
previous-not-ac
:<...>!
>! previous database for not-active OSWP
failed-not-acti*:<...>! failed database for not-active OSWP

After rebooting the system, the preferable becomes actual and the actual one becomes the previous.


1.
Take a manual backup of your ISAM (both IACM and xhub!) using the AMS. How do you proceed? (2 possibilities). What is the file
name given by the AMS?
2.
Show a list of all backups of the ISAM you have been working on (2 possibilities).
3.
Can I take a backup of multiple ISAMs at the same time? Y/N

If it possible, how? Do it. How are the different backups differentiated?
4.
Display a list of all backup files at Unix level. In which directory do you need to look?
5.
Restore the IACM backup taken in (1). (Notify the other trainees working on the same ISAM!) What happens?
6
6.
Can I restore IACM backups on multiple ISAMs at the same time?
7.
Restore the service hub backup taken in (1) via CLI. (Notify the other trainees working on the same ISAM!)
1. Try to find out if the automatic backup feature is active and at what time the backup is taken.
2. Delete the backup files you created on the AMS.
Review Questions
1.
What is the meaning of "backing-up the ISAM?
2. In which window can you perform a manual backup?
3. What are the differences between a manual and an automatic backup parameter wise?




Page
1 Performance Statistics in CLI
1.1 What is PM?
1.2 Retrieve PON port statistics
1.3 Retrieve xDSL user port statistics
2 Performance Statistics in AMS
2.1 PM Perspective
2.2 How to start monitoring 1 or more PM counters
2.3 How to show results
2 4 How to export the data
2.4
2.5 Navigate to Show PM counters
2.6 Navigate to Show NE History of Counter
2.7 XDSL PM Table view
2.8 XDSL PM Graphical View
2.9 Select counter-show NE History
2.10 Select various counters-show NE History
2.11 Select traceable value-Start Monitoring
2.12 Traceable value-Show in Data view
2 13 Traceable Value-Delete/Suspend
2.13
Value Delete/Suspend
2.14 SFPs: Inventory
2.15 SFPs: Navigate to Show PM Counters
2.16 CPU Load: Start Monitoring
2.17 CPU Load: Proceeding
2.18 CPU Load: Stop Monitoring
2.19 CPU Load: Display Memory Size and Used Memory
2.20 CPU Load: Navigate to Show PM Counters
2.21 Thermal Sensor NT
2.22 Thermal Sensor NT: Navigate to Show PM Counters
2.23 Thermal Sensor NT: Start Monitoring
2.24 Thermal Sensor NT: Monitoring-Show in Data View
2.25 Thermal Sensor NT: Monitoring-Delete/Suspend
2.26 Thermal Sensor LT
2.27 Physical Layer
2.28 PON port PM counters: Navigate to Show PM Counters
2.29 PON port PM counters: Enable GEM Port PM Collection
2.30 PON port PM counters: Enable MC GEM Port Collection
2.31 ONT PM counters: Navigate to Show PM Counters
2 32 ONT PM counters: Navigate to PM Collection
2.32
2.33 ONT Optical Measurement: Enable Monitoring
2.34 ONT Optical Measurement: Monitoring View
2.35 ONT Ethernet Port PM counters: Navigate to Show PM Counters
2.36 ONT Ethernet Port PM counters: Enable PM Collection
2.37 ONT UNI PM counters: Navigate to Show PM Counters
2.38 ONT UNI Traffic counters: Navigate to Show PM Counters
2.39 ONT UNI PPPoE Statistics counters: Start
2.40 ONT UNI PPPoE Statistics counters: Display
2 41 Internet Traffic counters (ADSLx): Navigate to Show PM Counters
2.41
2.42 OAM F5 Test
2.43 Internet Traffic counters (VDSL2): Navigate to Show PM Counters
2.44 Troubleshooting Counters PON: Start
2.45 Troubleshooting Counters PON: Display
2.46 Troubleshooting Counters PON: Stop
2.47 Troubleshooting Counters PON: Navigate to Show PM Counters
2.48 Troubleshooting Counters ONT UNI: Start
2.49 Troubleshooting Counters ONT UNI: Display
2.50 Troubleshooting
g Counters ONT UNI: Stop
p

7
8
9
10
12
13
15
16
17
18
19
20
21
22
24
26
30
33
34
35
37
38
39
41
42
43
44
45
47
49
50
51
52
53
55
57
58
59
60
61
62
63
64
65
66
67
69
70
71
72
73
74
75
76
77
Page
2.51 Troubleshooting Counters ONT UNI: Navigate to Show PM Counters
2.52 Troubleshooting Counters ADSL: Start
2.53 Troubleshooting Counters ADSL: Display
2.54 Troubleshooting Counters ADSL: Stop
2.55 Troubleshooting Counters ADSL: Navigate to Show PM Counters
2.56 IGMP Statistics
2.57 IGMP Statistics: Navigate to Show PM Counters
2.58 Traffic in the network port
2 59 Threshold Crossing Alarms (TCA)
2.59
2.60 TCA in AMS on ONT
2.61 TCA in AMS on xDSL line
3 Performance Statistics Hands-on
3.1 Your turn (PON)
3.2 Your turn (xDSL)

78
79
80
81
82
83
84
85
87
88
89
90
91
92

5529 SDC can retrieve these counters from the NE and forward them to an OSS for
further analysis and interpretation.





























admin system cpu-load nt-a monitor start


admin system cpu-load nt-a monitor stop

show system cpu-load nt-a detail

show system memory-usage


show equipment temperature nt-a







show equipment temperature lt:w/x/y

show xdsl counters


















admin atm port rack/subrack/slot/port:vpi:vci f5-loopback-ete start
info admin atm port rack/subrack/slot/port:vpi:vci

show vlan port-curr-15min-stats w/x/y/z detail

show vlan vlan-day-stats <ID_VLAN_INETx> port w/x/y/z detail















For NANT-A:
show interface shub statistics 1 detail


For a list of all parameters and supported counters, see the ISAM customer document
System Description.








Learning experience powered by

Alcatel-Lucent University
Section 1
Maintenance
Module 4
Syslog
7302-7330-7360 ISAM
Software Management, Bkp-Rst & PM with 5520 AMS
141
Maintenance Syslog

Module objectives
Upon completion of this module, you should be able to:
Explain what a protocol trace is and how to set one up
Explain the need for syslog server to collect tracing information
Configure both via CLI and AMS
143
Maintenance Syslog

Table of Contents
1 Concepts & Principles
2 Configuring
with CLI
1.1 SYSLOG
3 Configuring
with AMS
1.2 Syslog messages
4 Exercises
1.3 Priority
Page
1.4 Message
1.5 In the ISAM
1.6 Protocol tracing
2 Configuring with CLI
2.1 Syslog in CLI
2.2 Command layout
3 Configuring with AMS
3.1 Create a destination (Syslog Server)
3.2 Create a Syslog Message
3.3 Create a Protocol Trace
4 Exercises
145
Maintenance Syslog

7
8
9
10
11
12
13
14
15
16
19
20
21
22
24
26
7
14
20
26
Table of Contents [cont.]
146
ThisCOPYRIGHT
page ALCATEL-LUCENT
is left blank
intentionally
2013. ALL RIGHTS RESERVED.
Maintenance Syslog

147
Maintenance Syslog

1.1 SYSLOG
IP
CPE
event ?
Syslog message
Syslog server
Syslog generates messages and sends them to a collector (server)

indicating status, actions, possible problems etc.
Within the ISAM several applications are able to generate messages:
protocol tracing, CLI, TL1, Alarms,
Very useful for equipment monitoring
148
Maintenance Syslog
System logging (SYSLOG) allows you to trace and audit system behavior related to operator
activities. System log entries are issued by actions such as CLI and TL1 user logins that are
processed and recorded in system log files.
With system logging, you can do the following:
create
up to 64 custom system logs that can be saved locally or to a remote server
location
create
filters to determine which messages are sent
monitor
system logs

1.2 Syslog messages

Syslog messages are sent by default over UDP port nr. 514
Syslog message exists out of 2 parts, ASCII encoded

Priority (PRI) = facility code + severity value
Message (MSG)
(3 to 6 bytes)
(0 .. 1018 bytes)
Priority (PRI)
149
Maintenance Syslog
Message (MSG)

1.3 Priority
Priority = facility code + severity value
Facility: indicates from which process the message is generated
Severity: best mapped to the message level
The sum of the 2 values is always unique
Process
Facility
Fac. code
Kernel
Kernel (kern)
Firewall
Authentication (auth)
32
Severity
Value
NAPT
Local4
160
Emergency
SNMP
Logalert (alert)
112
Alert
Login
Authentication (auth)
32
Critical
SNTP
ntp
96
Error
IPsec
Security & info
80 & 6
Warning
PPP
Local0 & authorization
128 & 32
Notice
PPTP
Local0
128
Informational
DHCP
Local2
144
Debug
RIP
Local1
136
1 4 10
Maintenance Syslog
The syslog standard specifies a lot more facility codes but these are not used by the ST
modem. For all these processes a number of messages are defined by TMM.

1.4 Message
The MSG layout
Timestamp
Date & time
Hostname
IP address
Tag
Context (message description)
Process that generated the message (max. 32 char.)
Example of a Syslog collector:
1 4 11
Maintenance Syslog

1.5 In the ISAM

NE supports SYSLOG according to RFC3164
System statistics logs are user configurable and you can create up to
64 system logs. System logs can be saved locally, to a remote server,
or to all active CLI or all active TL1 terminals
Using filters, you can determine which messages are sent using which
facility
The severity of the various application messages is predefined. It is
reported as follows:
Service Affecting alarm messages: EMERGENCY
Authentication messages: ALERT
Configuration change messages: NOTICE
Other CLI/TL1 messages (admin, Show, retrieve): INFO
protocol tracing: DEBUG
videoCDR reporting: NOTICE
1 4 12
Maintenance Syslog


Allows tracing of protocol messages
IGMP
DHCP
IGMP, DHCP &

ARP tracing
ARP
On the following
CPE
xDSL line
ATM PVC
SHDSL line
Ethernet line
Logged via syslog messages
1 4 13
Maintenance Syslog

1 4 14
Maintenance Syslog

2.1 Syslog in CLI

configure system syslog ..
[no] destination: where to sent the syslog messages
[no] route: which messages must be sent and how to set some syslog
parameters
Command layout
destination <name> type <file|udp|all-cli|all-tl1|all-users>
file:<filename>:<max. filesize>
udp:<ip-address>:<udp port nr.>:<max. transfer rate>
For console logging (all-xxx) no extra parameters are needed
1 4 15
Maintenance Syslog
UDP port number to use is 514. This is the default port number used by most syslog server.

2.2 Command layout

configure system syslog
route <name> msg-type <type> facility <facility> <severities>
msg-type
All
! messages of any type
Authentication
! authentication messages
cli-config-chgs
! cli configuration change messages
tl1-config-chgs
! tl1 configuration change messages
cli-msgs
! cli messages
tl1-msgs
! tl1 messages
tracing1
! protocol tracing messages
tracing2
tracing3
video-cdr
! video cdr messages
So which messages need to be sent

1 4 16
Maintenance Syslog
Udp port number to use is 514. This is the default port number used by most syslog server.

2.2 Command layout [cont.]

configure system syslog
route <name> msg-type <type> facility <facility> <severities>
facility
Kern, user, mail, daemon, auth, syslog, pr, news, uucp, cron, local0, local1, local2,
local3, local4, local5, local6 or local7
So which facility to use for these messages
<severities>
[no] emergency
: pass messages of severity emergency
[no] alert
: pass messages of severity alert
[no] critical
: pass messages of severity critical
[no] error
: pass messages of severity error
[no] warning
: pass messages of severity warning
[no] notice
: pass messages of severity notice
[no] information
: pass messages of severity info
[no] debug
: pass messages of severity debug
1 4 17
Maintenance Syslog
Severities indicated in blue are the ones that can be sent by the ISAM.
As mentioned a couple of slides ago, the severities correspond with the following:
Emergency:
Alert:
service affecting alarm messages
authentication messages
Notice:
configuration change and video call detail records (CDR) messages
Information:
Debug:
other CLI/TL1 messages
protocol tracing messages
Note: be aware that depending on the message type defined previously in the command, only
one severity might be sent! For example, when the message type is set to tracing1 (or 2 or
3) only messages with a severity debug can be sent. This is because the tracing message
type contains the protocol tracing messages which all have a severity debug. So enabling
other severities under this will have no effect.

Example:
leg:isadmin>configure>system>syslog#
configure
info
system
#------------------------------------------------------------ echo
"system"
#------------------------------------------------------------ syslog
destination
KPNsyslogger type udp:172.31.79.243:514:unlimited
exit
route
KPNsyslogger msg-type all facility local7
emergency
alert
notice
information
debug
exit
route
KPNsyslogger msg-type tracing1 facility user
debug
exit
exit
#-------------------------------------------------------------


configure debug-trace
protocol-trace <subject> protocol <prot.> [no] events syslog <msg-type>
[no] packet-summary
subject
dsl-line:<...>
! the xDSL line
atm-pvc:<...>
! the PVC of the ADSL line
shdsl-line:<...>
! a static shdsl line interface
ethernet-line:<...>
! an ethernet line interface
uni:<...>
! GPON ONT uni interface
voip:<...>
! virtual uni identifier
protocol
IGMP, DHCP/DHCPv6 or ARP
msg-type
tracing1, tracing2 or tracing3
1 4 19
Maintenance Syslog

1 4 20
Maintenance Syslog

3.1 Create a destination (Syslog Server)

Network
Select NE
Infrastructure
Syslog
2
Create
Syslog Server
1 4 21
Maintenance Syslog
Give the server or destination for syslog messages a name.

Choose a type. In case of UDP, you can specify on which IP address the Syslog collector will
reside (e.g. 172.31.79.244) and the port number (by default this is 514).
In case of File, specify the filename and the maximum file size.

3.2 Create a Syslog Message

Network
Select NE
Infrastructure
Syslog
Select Syslog Server
Create
1
Syslog Message
1 4 22
Maintenance Syslog
A Syslog Message corresponds with what is called a route under configure system syslog in
the CLI.

3.2 Create a Syslog Message [cont.]

Network
Select NE
Infrastructure
5
Syslog
Select Syslog Server
Create
6
Syslog Message
1 4 23
Maintenance Syslog
A Syslog Message corresponds with what is called a route under configure system syslog in
the CLI.
Choose as facility syslog.
Decide with Severity levels you will collect (to make it easy you can select all).

3.3 Create a Protocol Trace

Network
NE
Rack
Subrack
LT
PON Port
5
ONT (provisioned)
ONT Card
Ethernet Port
Protocol Traces
Create
GPON UNI Protocol Trace
1 4 24
Maintenance Syslog
Choose for which protocol you want to set up a trace: IGMP, DHCP or ARP.

3.3 Create a Protocol Trace [cont.]

Network
NE
Rack
6
Subrack
h
LT
PON Port
ONT (provisioned)
ONT Card
Ethernet Port
Protocol Traces
Create
GPON UNI Protocol Trace
1 4 25
Maintenance Syslog
Select the tracing level: Events, packet summary or combination of the two.
Select one of the message types: Tracing1, Tracing2 or Tracing3.

4 Exercises
1 4 26
Maintenance Syslog

1.
Set up a Syslog Server, with IP address 172.31.79.244 and port number 514. Create a Syslog
Message type all.
2.
Create a Protocol Trace on your port, checking for ARP messages.
3.
Create a Protocol Trace checking e.g. for IGMP messages on your port. Make sure the correct
configuration is there to watch multicast and see whether IGMP requests are collected on the server.

Module summary
Upon completion of the module you are able to:
Explain what a protocol trace is and how to set one up
Explain the need for syslog server to collect tracing information
Configure both via CLI and AMS
1 4 28
Maintenance Syslog

End of module
Syslog
1 4 29
Maintenance Syslog

Last but one page
Congratulations
You have finished the training
Your feedback is appreciated!

Please feel free to Email your comments to:
training.feedback@alcatel-lucent.com
Please include the training reference in your email (see cover page)
Thank you!
All Rights Reserved Alcatel-Lucent @@YEAR
@@PRODUCT
@@COURSENAME

@@COURSENAME - Page 1
All rights reserved Alcatel-Lucent

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
@@COURSENAME - Page 2

D2c Software MGMT, Bkup, Restore, PM With AMS PDF

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

D2c Software MGMT, Bkup, Restore, PM With AMS PDF

Caricato da

Copyright:

Formati disponibili

7302-7330-7360 ISAM

Software Management, Bkp-Rst & PM with

COPYRIGHT ALCATEL-LUCENT @@YEAR. ALL RIGHTS RESERVED.

Passing on and copying of this document, use and communication of its

COPYRIGHT ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

Explain what a protocol trace is and how to set one up,

Your feedback is appreciated!

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

Learning experience powered by

COPYRIGHT ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

Describe how software management is done by the 5520AMS

Create an OSWP on 5520AMS

Activate an OSWP on an ISAM

Commit an OSWP on an ISAM

Describe how database management is done

Retrieve on NE which database container is active

SW migration (with different DB version) will not be covered!

COPYRIGHT ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

COPYRIGHT ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

1.1 Software management on 7302-7330-7360 ISAM

Software upload and download uses TFTP

SNMP / CLI / TL1

TFTP GET SW Request

COPYRIGHT ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

1.2 Software package (SWP)

SWP = Software package

Software files for

Software file(s) per board:

Different types of SW files

SW for SHUB is included too

Software files for

COPYRIGHT ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

the common operation SW files and

the specific operational SW files.

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

Nomenclature (see customer documentation):

FPGA SW, startupfile, etc... for NT or LT

NT OSW selector file

FPGA selector file

OFLT selftest selector file (autonomous)

OFLT selftest selector file (interactive)

Data Driven ISAM Configuration file

LANX OSW file

Type-A file ODM boards

Type-B file for ODM boards

Copyright 2013 Alcatel-Lucent. All Rights Reserved.

1.2 Software package (SWP) [cont.]

SWP consists of:

Software files for

SWP descriptor file defines:

Software Descriptor File

Each individual SWP consists of

COPYRIGHT ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

one SWP descriptor file and at least one software file.

interpreted by the considered ISAM-CORE SWP. (see further)

software in compressed or uncompressed format.