3FL00324_AAlcatel-Lucent University
University
During class please switch off your mobile, pager or other that may interrupt.
Entry level requirements:
Start the AWS
Manage the ISAM
*
Hands-on . . . . . . . . p.67
From Solaris Welcome Window:
access to the functions of 5523 AWS.
AWS Management System icon
5523 AWS Icon Menu
Icons on the AWS Front Panel explained
Top row of the Front Panel (from left to right) includes the:
Clock icon, which displays the current time on your WS.
Date display, which indicates the day and date and allows you to access calendar.
WS activity icon, which indicates the internal activity of the WS.
Help icon, which allows you to launch the help application.
Padlock icon, which allows you to lock your WS.
Workspace icons, which allow you to access different workspaces. There are only two available workspaces in the 5523 AWS.
Printer icon, which allows you to access the printing facilities. You can drag a file to the printer icon to print it, or just access the printer information.
Letter icon, which gives access to the electronic mail service.
File Manager Icon, which allows you to access the files in your home directory.
Terminal icon, which launches an terminal command shell on your workstation (only privileged users have access to the terminal icon).
AWS Management System icon, which gives you access to the functions offered by the 5523 AWS.
Bottom row of the Front Panel (from left to right) includes the:
Alcatel logo icon
*
Launch AWS Application Manager
Allows to select the application
Visible after clicking on the triangle above AWS Mgmt System icon
Starting and stopping an ANEL session.
After logging in to the UNIX workstation, you can start an AWS session.
You can get there by clicking on the arrow above the icon labeled 5523 AWS, which normally is the rightmost icon in CDE’s front panel.
A subpanel expands, from which you can reach the Network Elements application (ANEL = AWS Network Element List).
Once you’re finished doing your job, you can stop the AWS session.
For doing this, select the Views-menu, then click on Close (or hit Alt-F4).
After that, make it a good habit to log off from the UNIX workstation.
Starting an stopping the other applications
The other applications ( Administration, Alarm application, Network Events…) can be started and stopped in a similar way.
AWS version
.
Note — Depending on your access rights, you may or may not have access to some of the applications.
CAL = Current Alarm List
USM = User Service Manager (the process that delivers the GUI)
ANEL = AWS Network Element List
*
Via Process monitoring
Display the details about the processes.
Start/Stop AWS core processes:
or:
How to reach the administrative functions
For this purpose, you need to login to the AWS, and make sure you reach the administrative functions.
The administrative functions can be reached by clicking on the administration icon.
Getting into DPC (=Distributed Process Control).
To start/stop the DPC-USM, you have to double click on the maintenance icon, then on the process monitoring icon.
From the DPC-USM you can do a whole lot more than just firing up or bringing down the AWS core processes, but they are out of the scope of a basic OAM course.
Procedure
First select a process or a process group, or just select the AWS label in the left window pane to start or stop all AWS core processes.
Then, either …
- use the actions menu to reach the start/stop commands
- right click to reach the actions popup from which you can also select the start/stop commands
9.bin
DPC-USM
To see more info on a process:
menu Actions - Show Info
GREEN: Process(es)
BLUE: At least one
process has been stopped
This process has been stopped
When process lanxim_101 is started, this is what you’ll see.
148.bin
in the Icon window
DPC Icon: Green, Blue or Red
Status Window
information about the AWS workstations
displays EML/Presentation workstations which are installed to become part of the AWS.
button to launch Process Monitoring
AWS
Monitoring AWS core processes
For monitoring the AWS core processes, double click on the status icon in the maintenance window.
The AWS status and AWS status window appears.
The AWS status window lists all unix computers in the AWS cluster.
The window displays IP-address, type (Master/EML/Presentation), connectivity and status in the 5523 AWS system. The workstations status can take values Incorporated, rejected and Stand By ‘(Incorporated’ means running).
By clicking on the appropriate button – and you really can’t miss it – the process monitoring tool can be entered, from which you can get a view on the individual core processors. This is useful when the AWS status icon is red.
If you really want to have this icon on your desktop all the time, simply minimize the AWS status window.
Double clicking on the status icon to show the status window again.
Press Quit to exit the application.
17.bin
Multiple licenses possible, e.g.:
passive license key
Maintenance
AWS
License
On AWS, multiple licenses are possible (and not all of them are applicable to the 7302 ISAM), e.g.:
7321 RU
7324 RU
Start license process in DPC-USM
Clear: to erase the license key
Audit: to show info on (+possibly save)
number of ports
button ‘list logged in users’
License
Maintenance
Clear
Audit
Import
AWS
users
When pasting the key into the “Active License Key” field and pressing OK the license process will start validating your license. This can take up to 15 minutes before the license is completely validated.
You can verify the operation of the license through the license button.
If you select a certain license in the list, your rights will be shown.
If you have an invalid key or the expiration date has passed an operator will not be able to open the ANEL or EML USM windows.
Import: to retrieve the previous license key. This can be useful in case of:
minor upgrade where no new licence key is necessary
AWS rollback
*
View Area: table containing one NE per row.
In hierarchical mode, only NEs within the selected folder are shown
Information given per row: supervision tag, type, ...
Menu Bar
View Area
Tree Area
Progress Indicator
Misaligned tag
Structure of the ANEL window
By default, two window panes are shown in the ANEL window.
The left window pane – the tree area - gives you a tree like view on the areas in the network, not on the NE’s in your network!
Clicking on the small square expands or collapses the tree, so you can get a full view of the structure of your network (hierarchical view).
When clicking on the name of an area, or the colored square to the left of it, the right window pane is updated.
The right window pane – the view area - gives you a sorted list of the NE’s available in the area selected. One row for each NE is displayed with the following relevant information
Supervision state: gives information relative to the supervision state of the NE.
Type, Release, Name and Location of NE
Alarm status: indicates the highest severity alarm currently present on the NE.
Reachability state: relates to the ability for the NE and the AWS to communicate with each other.
Scoped Command Tag: represents an ongoing scoped command that includes the NE.
Command feedback: displays the current state of the NE with respect to the last (multiple) NE action in which the NE was involved.
The numbers at the bottom right in the Message Area indicate how many NE’s are available in the full network, as well as the amount of NE’s in the selected area. Total : x Visible : y
where x = the total number of NEs in the list, y is the number of NEs currently visible
(for a flat structure both values are the same)
Alarm tags
*
Supervision State
Color of tag indicates severity of highest alarm on NE
Misaligned tag
Supervision Tag:
Declared: the NE is not being supervised because it has just been declared to the AWS.
Supervised: the NE is under supervision.
Activating: the NE is being brought under supervision and no management tasks can be performed on it.
Deactivating: the supervision process on the NE is being stopped and no management tasks can be performed on it.
Reachability Tag:
Disabled: either the communication link between the AWS and the NE is interrupted or the NE is internally facing a major failure.
Enabled: the NE is either in the activating, deactivating or supervised supervision state and communication between the NE and AWS is possible.
Note — The reachability state is only relevant for supervised NEs. If an NE is not supervised, its reachability state is per definition disabled.
Misaligned tag
The tag is shown when one or more EML IM or SGM-IM processes are down. In such circumstances, to guarantee the uniqueness of the configuration parameters (i.e. the NE IP address) it will not be allowed to create or modify a NE.
NEs managed by EML IM processes that are down, will not be shown in the list. In this case, the text "One or more EML-IMs are down" is displayed in the message area at the bottom right corner of the screen.
FilterTag
Alarm status:
Indicates the highest severity alarm currently present on the NE.
There are six possible severity levels: Critical, major, minor, warning, indeterminate, clear
*
Sort
The list of the NEs in the View area can be sorted by:
Name,
Location,
Type,
Release,
Layout
Hierarchical
Flat view
ANEL
Refresh
Sort
Layout
Views
Being able to change the view on all the different NEs (network elements) is especially important for operators with an extensive network
Refresh: An automatic refresh of the View Area is performed regularly. However, a manual refresh of the NE states displayed by the View Area can be performed by this function.
Sort: The table is by default sorted (ascending) on the "Name" column (the full name, not the displayed abbreviated name)
Layout
Hierarchical structure (Default) lets the operator group the different NEs in folders. These folders can be nested and can e.g. be used to group the NEs according to their geographical location
In this mode, only the NEs with the selected location in the hierarchy will be shown (subject to filtering according to security)
The hierarchical structure is actually based on the Location Name of the NEs.
If the Location Name of some NEs in the system is "Belgium/Flanders/Antwerp", then the Root of the tree will have a subtree "Belgium", which will have a subtree "Flanders", which will have a subtree "Antwerp". An NE without Location Name, ends up in the Root of the tree.
You can create new location names at the time you create ASAMs.
If you already selected an area name before you create an ASAM, the location name field in the create ASAM window already contains the name of the area selected. Creating sub-areas in an area can be done by using the slash.
Note : A network element will only be visible when selecting the containing folder !
In the Flat structure only a flat list of NEs is shown in the View Area. In this mode, all NEs in the system will be shown (subjected to filtering according to security).
*
By default no filter is applied
You can create and save a new filter or apply an existing one.
Filter icon in the lower right corner
Views
Filter
ANEL
Filter: Via a number of conditions, one can apply a filter on the list of NEs. This can be useful in case of an extensive network. Filter conditions can include all the attributes that are displayed in the ANEL window :Name, Location, Supervised status, etc...
*
(in case of the 7302 ISAM)
Show
Customer id search is not case sensitive
Customer id’s that start with the substring that you enter
Views
IM Load
Shows the load of all IM processes (e.g. in case of 7302 IM: EML-IM and LANX-IM processes).
Show
Via the Show submenu, you can navigate to the following applications :
Equipment: zooming in on the ASAM, displaying the rack layout it starts the EML USM.
Show alarms : This command allows the operator to navigate to the alarm application (AS-USM) showing the alarms on the selected NE.
PM Collected data: This command allows the operator to navigate to the PM Viewer application.Performance of the different PM counters (see later)
Show network events: This command allows the operator to start the Event browsing application
TL1 CL1: To start the Transaction Language 1 (TL1) Command Line Interface on the 5523 AWS. If this application has to run, then TL1 GW and CLI software needs to be installed.
Note - For navigation towards EML-USM, AS-USM Network Events or TL1 CLI only one NE may be selected. This NE has to be in the supervised state, otherwise the commands are greyed out .
Go to … port by customer
*
Views menu
NE Search
Via the menu Views - Find, one can make a search through the list of NEs. A common search is searching for a particular ASAM based on some criteria. These filter criteria include for search on ASAM
Presence of SW Files/OSWPs
Active NT SW File/OSWP
IP Address
System ID
The system will display the result in a separate window that allows you to navigate directly to the NE.
Note — The commands are not available when the location containing some NEs is selected from ANEL Tree Area. The selection of individual NEs is mandatory.
Appliques Search
This command is only available when at least one NE of R4.2 or above is selected in the ANEL Main View. If the selected NEs contain NEs other than Advanced Services Access Manager (ASAM) R4.2 and above, these are ignored.
It is not possible to detect appliques in SD subracks.
Active Ppoints
*
Find (sub)NEs matching criteria.
SW files/OSWPs present
ANEL
You need the service menu when you want to configure or show the system parameters for the services Video/IGMP, VLAN and Ethernet/IP.
With Service Definition you can create, modify… VLANs. Different modes of VLANs exist: Intelligent Bridge (also called: Residential bridge), Cross-connect and Layer 2 terminated VLAN. For Intelligent bridge and Layer2 terminated VLANs you need to create the VLANs beforehand and associate them afterwards to a port (after having deployed the VLAN on a set of ISAMs). For cross-connect VLANs the VLAN can be created on the fly when you associate the VLAN to a logical port (in EML-USM).
More explanation on creation of VLAN and deployment to an ISAM will be given in a later section. For now, it is enough that you can e.g. retrieve the VLANs that have been created on the AWS and that you can see on which ISAMs they are deployed, etc.
When you want to create a new VLAN, you may want to check which VIDs are still available. You can see all the free VIDs with the command Service Utilities Get free VLANs.
Alcatel-Lucent University Antwerp
EML-USM opens
Rack view : shelves in the NE
Subrack view: boards in a subrack
Board view: ports on a board
Port view: connections on a port
ANEL-USM
How to navigate on the EML-USM window?
When double clicking on an NE in the ANEL window, another window opens. This window is managed by the EML-USM, and initially shows the NE view, i.e. it shows the shelves available in the NE.
By double clicking on the objects shown in the view Area, you go one level down in the NE, and the screen is updated. By double clicking on the container icon to the top left in the main window pane, you go up a level in the NE, and again the screen is updated. By pressing the page-up key, you go back to the previous screen.
Rack view
The rack is a logical container from the AWS point of view. It can exist or not in the field. An NE without rack can be perfectly functional. For this reason, the NE representation can differ from the hardware situation in the field. The AWS is able to discover subrack presence. By default, all the possible racks will be displayed.
The presence of a subrack will force the AWS to show it. The subrack positioning inside all the racks will be provided by the hardware PLID jumper setting related to each subrack. This setting must be unique for each subrack inside a NE. The check of subrack hardware jumper setting is done by the NE.
Subrack view
For a 7301 ASAM the appiique cards are visible; for a 7300 ASAM they’re not.
Board view
Port view
*
One level up:
ANEL-USM
Navigation to different views
*
Window Title
The title of the main view, which is located above the menu bar describes the NE type and its version.
Menu Bar: The menu bar allows navigation, configuration and supervision functions to be performed on an NE Alarm Synthesis PanelThe alarm panel comprises two separate subpanels. The left subpanel shows alarm counters on a per-severity basis. The subpanel on the right shows per-domain alarm counters.
View Title Area : This area contains the title (container 'type' + its name) of the view that is currently displayed in the view area. It is located below the alarm synthesis panels.
Status Icon Bar : The vertical status icon bar shows the value of the NE global statuses. For each status, a value is displayed with an appropriate color and shape.
View Ara: The view area is the region in the primary EML-USM window where the graphical representation of the specific views is displayed. The views have the following characteristics:
Each view has its own specific menu stacks which appear between the Supervision and Help menu entries.
The main window is dynamically updated, i.e. it receives notifications, to reflect the state of the NE in real time.
Still, the operator can force a refresh of the main view by sending the necessary requests directly to the NE. This can be done via the Refresh menu entry in the Views menu stack.
Several main views can be opened at the same time showing different domains of the same NE, or different NEs. However, this number is limited.
The icons are ordered, i.e. the Id(entity) of the object is always displayed.
*
Views navigate between views
Service configure SVC, ILMI and Video Channels
PM Performance Monitoring
Help Help application
Permanent menu items
Context-specific menu items
*
color
Colored (round) according to the severity: alarms present
Per-domain alarm subpanel
color
Green (square - “Normal”): no alarm
Colored (round) according to the highest severity among the active alarms
S Alarms Per-severity alarm subpanel = S Alarms Per-domain alarm subpanel
Alarm Synthesis Panel
The alarm panel comprises two separate subpanels. The left subpanel shows alarm counters on a per-severity basis. The subpanel on the right shows per-domain alarm counters.
The per-severity alarm subpanel shows the synthesis of alarms for the NE as a whole. For each severity, the number of alarms currently present on the NE is displayed inside a square containing an acronym which corresponds to the severity.
The per-domain alarm subpanel also shows the synthesis of alarms for the whole NE. For each domain, the number of active alarms is displayed inside a square containing an acronym which corresponds to the domain name.
The domains are:
Supervision state:
SUP brown (Round) : Supervision not active
Operational state: Reachability of the NE
ISO Green (Square) : NE is reachable
ISO Red (Round) : NE not reachable
Protection mode: NT redundancy mode.
OFF yellow (Square) : Redundancy not active
ON yellow (round) : Redundancy active
A Green (Round): Chain A Active
B Green (Round): Chain B Active
Synchronization mode : NT database synchronization
NSY yellow (Square): No synchronization
SYN yellow (Square): Synchronization
Status Icon Bar
Supervision state (acronym SUP). This state indicates whether the operator is managing the NE or not. If the NE is in the state declared, the operator does not manage it and there is no communication with it. When supervision is active, the SUP icon is green in color and when the supervision stops the icon is brown in color.
Operational state (acronym ISO). This state represents the 'reachability' of the NE and is disabled if there is a communication failure, meaning that the AWS cannot communicate with the NE. It corresponds to a Resource Isolation alarm. When the NE is reachable, the icon is green in color and when supervision is stopped, it is red.
Protection mode (acronym A, B, ON, OFF). The Protection status tag representing the redundancy state in the network element is shown on the NE status area. It displays the protection operational status of the redundancy in the NE.
*
Backup/restore mode: ongoing B/R operation on NE
B/R Green (Square) : No B/R operation ongoing on NE
B Blue (Round) : Backup ongoing
R Red (Round) : Restore ongoing
Persistency status: persistent data loss
PRS green (Square): No persistent data loss
PRS red (Round) : Persistent data loss
PPPoE server
802.1x authenticator
Status Icon Bar
Backup/Restore status tag (acronym B/R). This icon represents the NE backup restore operation status. The backup/restore status tag provides information about the ongoing backup/restore operation on the network element.
Persistency Status Tag (acronym PRS). This icon represents the persistency status of the NE. It is red in color if there is an NE persistent data loss and green in color if there is no persistent data loss.
61.bin
62.bin
Alarm Synthesis tag = summary of
alarms of the object itself,
and alarms of the contained objects.
All alarms cleared:
At least one alarm present:
…
*
EML-USM - Alarm Display - Alarm status tag
Alarm Status tag: summary of alarms of the object itself only.
If the Alarm Status tag is selected, then the alarm overview area/ panel displays the alarms of the object.
All alarms on object cleared
At least one alarm present on object
Alarm on object
Fly over
Most tags are hot spots. This means that when the mouse pointer flies over the tag, a textual message appears in the status line which is situated at the bottom of the window.
*
Alcatel-Lucent University Antwerp
Alarm status tag in Icon Container: ASAM related alarms
NT redundancy failure, Label mismatch, Address conflict …
Alarm synthesis tag on subrack summarizes alarms of:
subrack itself
contained boards.
Alarm status tag on first subrack of the rack: status of the RACK
External alarms, Power and equipment alarm on Rack level
*
Mismatch
Missing
Top shelf
Protection Status: LT Redundancy (XD - R.4.410 - R4.4.11)
N+1 LSM Protection enabled (Active) tag represents the LSM Protection Switch over state "active" value. If the relevant LSM board has been switched over to the spare LSM board.
N+1 LSM Protection enabled (Standby) tag is displayed if spare LSM board is in "standby".
LSM = Line Service Module
N+1 LSM Protection can be enabled from the rack view or from the subrack view.
In the rack view, the menu ‘N+1 protection’ is sensitive if:
only 1 planned subrack which supports N+1 protection is selected
N+1 protection is disabled
(of course you can also use the menu ‘N+1 protection’ to disable N+1 LSM protection)
74.bin
Alarm status tag in Icon Container: status of the shelf
Power problem, equipment malfunction, configuration issue
Alarm Synthesis tag and Alarm Status tag per board
Alarm Status tag per applique
Administrative state
Mismatch
Missing
Service hub
Protection tags
Protection enabled (Standby)
Protection enabled (Active)
Auto configuration is not supported on the 7302 ISAM. Therefore there’s no icon for autoconfiguration to be found.
Autoconfiguration is supported on 7300 ISAM.
No NT redundancy supported yet on the 7302 ISAM.
N+1 LSM Protection can be enabled from the rack view or from the subrack view.
In the subrack view, the menu ‘N+1 protection’ is sensitive if:
the subrack supports N+1 protection
the rightmost LSM slot position has no planned board
N+1 protection is disabled
(of course you can also use the menu ‘N+1 protection’ to disable N+1 LSM protection)
84.bin
One row for each logical group: bonding
Below one bonding group row, one row for each port part of this group.
Port Area
Bonding Area
The board view window shows the list of all ports it contains in its main window pane.
View Area in the board view window
Table with port and bonding group area (if applicable).
Table structure
One row for each unconfigured and configured port not part of a bonding group.
Ports are sorted in numerical order on the Id Label.
One row for each bonding Group.
Below one bonding group row, one row for each port part of this bonding group. For the same bonding group, ports are sorted in numerical order on basis of the Id Label. IMA groups are also sorted in numerical order on the Id Label.
Double clicking on the container icon brings you one level up.
Double clicking on one single port in this list brings you one level down.
The customer-id field shows you the customer identity which is set when configuring a port, and can be used to e.g. show the telephone number of the subscriber connected to this port.
It’s possible to select multiple ports (CTRL or SHIFT click) before executing a particular command, which then will affect all of the ports selected!
86.bin
13. Carrier Data Collection
Information given per row
1. View mode button: reduced view or extended view
2. Row type tag: native port, ADSL bonding group (if supported)
3. Type tag: on service hub: ASAM port, control port, network port, subtending port, out-of-band management port, user port.
On EBLT: user port
5. Status tag: available, reserved, faulty or used.
On 7302 ISAM: no ILMI, no SVC! (ATM is not as important here as in case of the 7300/7301 ASAM!)
97.bin
98.bin
View mode button
"Expand" button indicates that the row is in "reduced“ mode.
Click to expand “reduced” row(s)
"Expand all" button: at least one row is in "reduced" mode.
In reduced mode, not all commands are available
Dots tag
*
Row type tag
Port/bonding group status tag
In expanded view max. 8 alarm status tags are used.
Basic states - Definitions
available port can be used to assign profiles to (=configure port)
faulty port cannot be used because e.g. there is a hardware failure
reserved port cannot be used for any customer, e.g. because it already is assigned to another customer.
used port
Remark: this diagram may be slightly different in different releases!
Typical state transition
Most typically, the first state a port is in, is unconfigured.
The next state is configured, i.e. xDSL service and spectrum line profiles are applied to the line.
After that, connections are created (or better: ATM termination points). A port must be configured before connections can be defined!
Then one or more services (VLANs) can be deployed to the logical port (see further).
Transitions which are not allowed
Some state transitions are not allowed, e.g. you cannot unconfigure a port while there are still connections defined on that port.
*
Operational state
or
Note: The ATM global loopback is grayed out! The only loopback that is supported is the F4/F5 loopback (but then there’s no icon appearing).
ATM Global Loopbacks on the Port/bonding group
ILMI is also grayed out.
On 7300/7301 ASAM it is supported. The icons are:
ILMI channel tag
ILMI channel configured
1144.bin
15 minutes
24 hours
IGMP control channel configured
Carrier Data Collection
On 7302 ISAM, SVC is grayed out. There are no ATM connections to be set up. ATM is terminated on the LT already.
On 7300/7301 ASAM SVC is supported. In that case the icons used are:
SVC signaling channel state
Configured SVC signaling channel
Locked SVC signaling channel
View area
Table with:
One tree for each service/VLAN associated to that logical port
View Area
The port view window shows the list of all termination points + services it contains in its tree setup.
Double clicking on the container above the connections brings you one level up.
*
Administrative state
802.1x enabled
141.bin
142.bin
143.bin
144.bin
Connection
Create
EML-USM
You can associate one or more VLANs to an ATM termination or you can delete an existing VLAN association, or show the current VLAN associations, etc.
Alcatel-Lucent University Antwerp
NE information
Type, Release, Name, Location...
EML-workstation and EML-IM process
Possibility to enable SNTP
OAM interface at EML
NE Defaults
NE defaults
When you create an ISAM (type LEEU), automatically the corresponding service hub is created too.
Location name
As seen before when discussing the ANEL view, the hierarchical structure is actually based on the Location Name of the NEs.
Specification of EML-Workstation and EML-IM process
Auto – in this case auto balancing is performed
Access Control Domain : The specification in this field indicates to which OAD (=Object Access Domain – see Advanced AWS course: security) the ASAM belongs. Depending of an operators profile, an operator will be able to see, perform certain actions on this NE or not
To see the information on the NE you can use the Show Info command under the same Menu
There is a possiblitiy to modify NE information. The fields which can be modified are:
1) In NE information: Location, Access Control Domain, Comment.
2) Operation, Administration & Maintenance (OAM) Interface at NE: All fields (IP address cannot be modified in supervised mode).
3) OAM Interface at EML: All fields only if NE is not supervised, else none.
Deleting an NE is only possible if the NE is not supervised. You can delete multiple NEs at the same time. But in that case all NEs must be in the unsupervised state otherwise the command is greyed out.
SNTP = Simple Network Time Protocol (see further).
Supervision can be started manually:
Via Create NE window
NE defaults:
*
on IP level
on Ethernet level
ANEL
NE
Supervision
Reachabililty
Test
Start
Stop
(OAM
Supervision
Once the supervised state is established, an association between the NEs and the 5523 AWS is created. Thus ANEL will be able to animate the symbol's color associated with the state changes of the NE.
You can start/stop supervision on multiple NEs at the same time. In the case of starting supervision all the selected NEs must be in the unsupervised state. Otherwise the command is greyed out.
In case of stopping supervision on multiple NEs at the same time, all selected Nes must be in the supervised state.
When supervision is stopped on an NE all the alarms related to these NEs are removed from the current alarm list.
Reachability Test
IP connectivity is tested by a ping command. Details are shown when clicked on the Detail-button.
For the SNMP connectivity or Transaction test to pass, IP connectivity must at least be established.
Transaction Test: test by which the AWS tries to open and close a transaction with the ASAM
OAM Counters (not supported in case the NE is an ISAM)
OAM Counters display the performance counters at the OAM interface port of the NE on IP Level / Ethernet level in case of outband management
*
Lock board
Lock port
Restricts all communication over the port, also the physical layer.
Lock NT port
Restricts communication over 1 or more links of an NT link aggregation group.
Lock ATM termination point
Alcatel-Lucent University Antwerp
Alcatel Service Hub
Service specific functions performed on Service Hub
Service Hub and ASAM-CORE
ASAM/LT shelf (ASAM-CORE)
Service specific functions performed on ASAM-CORE
The set-up of a VLAN has to be configured both at service hub level and at ASAM-CORE level.
*
General CLI
Via TL1
Service Hub CLI
Configuration possibilities release dependent
*
use the same interface as the user data path
An Ethernet 100BaseT or1000BaseT network link of the Service Hub is used for OAM data and for user data
Possible ports: 18 24
use a different interface as the user data path
A dedicated Ethernet 100BaseT or 1000Base T network link of the SHub is exclusively used for OAM data
configured as out-of-band management port
Possible ports: 18 24,
Via RS232
Connecting to the TL1/ Full CLI on the ASAM part
Login to the ISAM Full CLI
Telnet session
DCE DB9 interface
Craft Terminal
GigEoptical
ACU
SMAS
CLI Basic operations (1/4)
Full CLI can be used to configure and manage ISAM equipment
ASAM Core and Service Hub
The root node is the highest level.
Directly below the root node you find the command nodes
Important command nodes are ‘configure’ and ‘show’.
Show a short explanation on what can entered at this position in the command..
Enter ?
Enter help
Show configuration
Enter info
Shows only the parameters which don’t have the default value.
Enter info detail
*
press <left arrow>
press <right arrow>
Recall previous command
Recall successive commands
Delete previous input character
press <delete>.
press <insert>.
Press <Space> or <Tab>
Go one level up
exit all
Go to the previous level you were at before you entered the last command
Enter back
Enter history
Enter tree
Enter <telnet IP address>
Telnet session towards Service Hub CLI possible without having IP address assigned to Service
<telnet shub> command
or connection closed by telnet server (session inactivity-time protection)
Filter
Alcatel-Lucent University Antwerp
*
Exercises
ANEL features of AWS
Logon
Log on to the AWS. The trainer will provide you with logon-ids and passwords.
What is the version of the AWS?
Set up the CDE so that you have the network elements view (ANEL) in one "workspace" and the NE you will be working on (EML) in another.
Start / Stop the AWS
Is the AWS currently running? How is this indicated? What is the status? How did you check the status?
Is it a stand-alone or distributed set-up that you are working on? How can you see this? Give 2 possibilities.
Make sure that you can see the AWS status, without keeping the processing-monitoring window open.
*
Exercises
ANEL features of AWS
Review Questions
What is the application to start when you want to see the network elements?
How can we be notified in a very simple way that something goes wrong with a process?
What is the application to open when you want to see the different boards of the NE?
How can you have more details on the running processes?
ANEL
You have a very large network. The NEs are organized in a lot of different folders/locations. You had to go away for a while. You want to have a fast view on all the supervised NEs in the network, which have critical and major alarms.
*
Exercises
ANEL features of AWS
License Key of 5523 AWS
Customer "Smith" calls the helpdesk (you). He has some problems with his connection. You don't know to which ASAM he is connected. How can you quickly find the port of that customer?
Check the IM load of EML-IM process 100.
Check the IP connectivity between the AWS and your NE.
Stop the supervision on the NE and try again. What happens and why?
How many Residential Bridge VLANs are created on the AWS?
*
Exercises
ANEL features of AWS
License key
What is the host ID of the AWS?
*