03 Como Operar AMS Ed 01

Prévia do material em texto

©Nokia Internal Use
Como Operar o 5520 AMS
Subtitle with specific product name, course number or detail
Last Title Substitution:
MetaMSubstitutionAuthor 
MetaMSubstitutionDate
MetaDesignName
Welcome to the course Getting Started with 5520 AMS.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
1. INSTALANDO 5520 AMS CLIENT
2
Let’s move on to the first chapter. In this chapter we shall understand what is AMS and how to install it.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Visão Global
Operator’s Intranet
AMS 5520 
ISAM
. . . 
CPE
CPE
Router
ISP and
WWW
. . . 
ONT
ONT
3
[1] So what is AMS?
The Access Management System (AMS) is the centralized management system for the Intelligent Services Access Manager network (ISAM) family.
If you wish to have a graphical representation of the ISAM, first you need to install a client application on the operators PCs or workstations. In general, the AMS client is available for Windows as well as for Red Hat Enterprise Linux OS. Installation and post-installation uses of both the OS is similar.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Usando AMS client pela primeira vez
Download
AMS Client reside no servidor do AMS como um arquivo :
Para Windows um arquivo .zip
Para Linux um arquibo .bin 
Extração
Extraia arquivos zippados para rodar em ambiente Windows.
Execute .bin para rodar em ambiente Linux.
Abrir 
Abra AMS client e faça login no AMS.
Use
Gerencie sua rede.
4
This slide provides you with the overview of the installation process. 
First and foremost you must make sure that the AMS server is installed and it is running.
Then, check the installation guide for other pre-requisites, such as workstation and PC requirements. Once these both are done, you are all set to proceed further. Now let’s see how to install the AMS client.
[1] Initially you have to download the AMS client software. It can be found on the server as a compressed zip file for Windows and as an executable bin file for Linux. You can choose any one, based on your requirement. 
[2] then, you must extract the downloaded file. 
For Windows, you can extract the downloaded file to the directory of your choice. 
In case of Linux you have to execute the self-extracting binary file and follow all the installation prompts.
[3] So once the installation is complete, you can start the AMS client and log in to the AMS.
To start the client in Windows, double-click the amsclient.exe file that would be present in the directory which you choose as the download directory.
In case of Linux, you can launch the client by executing the command ./amsclient from the installation directory or you can also double-click the amsclient file in the installation directory.
If you follow this the ams client window will get opened!
[4] You can then login with your credentials and use the client to manage the Network Elements NEs. 
For a newly installed AMS server, the access network within the AMS might be empty, therefore create the NEs if needed.
Let’s learn each of the steps in detail in the following slides.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Microsoft Windows PC
Download arquivo zip de http://servername:8080/ams-client. 
Red Hat Linux workstation
5
[1] Let’s get started with the first step - the procedure to download the AMS client. 
[2] It is a very simple process. In your web browser, access the server by providing the IP or the Fully Qualified Domain Name (FQDN) of the AMS in the URL, as shown on the slide. 
[3] If you have a Windows PC, which is commonly used, click the link “Download Client - Windows PC”.
[4] If you have a Red Hat system, click the corresponding link, as shown on the slide.
[5] Depending on your web browser settings, you might be prompted to specify the folder where the file should be stored. Input the details accordingly, with this the first step is done.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Extraia o .zip para um diretório de sua preferência.
6
[1] Next let’s proceed to the second step - the extraction step.
Here we perform the extraction of the downloaded file on a PC running with Windows .
[2] 7-Zip decompression program is used for the same.
The zip file contains a directory named “ams”, which has a set of files and subdirectories.
Due to the extraction method chosen, the “ams” directory appears as shown.
If you take a look at this, you can notice that JRE is included in this zip file. Therefore, the AMS client will use its own runtime environment and not the Java version, which might already been installed on your computer.
You must pay special attention to the path and the filenames of the extracted files. The filename and the extension should not exceed 256 characters.
[3] Once the extraction is complete, you can navigate to the “ams” directory which was created now.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Extraia para Linux
Execute the bin file.
 Abra um terminal no diretório Downloads.
	 Exemplo: cd /home/edu/Downloads
 Dê privilégio de execução.
	 Example: chmod +x ams-client-redhat-x86_64.bin
 Execute o arquivo .bin.
	 Example: ./ams-client-redhat-x86_64.bin
 Responda as perguntas:
	
	Q1. Java: Select the default.
	Q2. Single installation for Multiple operators: Select the default.
	Q3. Multiple GUIs: Select the default.
	Q4. Restrict usage: Select the default.
	Q5. Top directory: Enter the directory.
		Exemplo: /home/edu/Documents
Abra o AMS.
1
1
2
2
3
3
4
4
7
[1] Now that you are familiar with the extraction procedure in a windows system, let’s now focus on how to perform the extraction of the downloaded file on a PC with Red Hat Linux.
In case of Red Hat, you must ensure that the correct JRE is installed on the machine before installing the client. Currently, JRE 1.8 is required.
If you see here in this slide all the steps are explained.
Initially, you must login to the server, here the user “edu” is logged in to the Red Hat Linux workstation.
[2] after you had logged in, open a terminal window and change from the current directory to the download directory by using the “cd” command.
[3] Next, you give execute permissions to the file by the “chmod” command.
[4] Once this is done you will be able to execute the file.
[5] While you proceed further, you would be prompted to answer few questions. Answer the questions accordingly, and if more help is needed with this, refer to the AMS customer documentation. 
For most of the questions you can proceed with the proposed default values.
When it prompts you to enter the top directory, ensure that you enter the full path. In this case, an “ams” directory will be created, in which all the files and directories will get extracted from the self-extracting binary file.
Once this is done navigate to the “ams” directory which you had created, by the graphical Explorer of the Red Hat Linux workstation.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Abrindo o AMS Client
 Duplo clique no amsclient.exe
“amsclient” para Linux
“amsclient.exe” para Windows
8
[1] We are done with the extraction procedure, let’s now launch the AMS client from the directory where it was extracted. Double-click the corresponding icon, “amsclient.exe” in case of Windows installation, and “amsclient” in case of Linux installation.
Now the AMS client will start to load.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Abrindo o AMS Client [Cont.]
 Login no AMS com IP do servidor usuário e senha
9
[1] As you can see on the slide, the login window appears, prompting you to enter the server, user name and password. For the first time login, you should provide the IP address or the Fully Qualified Domain Name (FQDN) of the AMS server, the username and the password. Be aware that the username and password are case-sensitive. 
Once you click on the finish button, the client contacts the server, the name of the AMS assigned during the installation of the server, as well as all the possible IP addresses will be retrievedand stored in the local workspace of the client. When you log in the next time, the client will use that name of the server automatically.
[2] Once the credentials are verified successfully, you will be logged in to the AMS.
[3] Note that the user’s details are visible in the status bar.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Abrindo o AMS Client [Cont.]
Instale os plugins de ISAM/versões.
10
[1] As you can see here, this screen notifies that there are new plugins available. This could be the first access or a subsequent access to the AMS whenever new plugins are installed on the server.
The plugins are, for example, new node types or the same node type but with a different software release. On the later slide, more details about plugins are explained.
Be aware that if no plugins are installed, you will not be able to manage any node.
[2] For a customized installation of the plugins, you must select the option “Select plugins - advance installations only”. 
Automatic installation is the recommended option. So, just click “OK” to start the installation.
[3] Once the installation of all the plug-ins are completed successfully, you will be prompted to restart the client. Choose “Yes”, so that the installed plug-ins can be used by the client.
[4] After the client restarts,
[5] The login screens appears. 
Note that the AMS name appears in the “Server” field. 
Enter the username and password and click “Finish” to log in.
A new window will appear and shows you the complete list of plugins available on the server to install on the client. 
Here, you can select all the items needed.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Plugins: arquitetura modular
Plugins
Funcionalidades adicionais, entregues separadamente
Hot-pluggable
Types
NE-specific plugins
Enhanced applications
(Patches)
5520 AMS = Core Functions + Addon Functions
Red Hat Enterprise Linux
CORE - Access Management Platform R9.6.xx
73xx R6.2 
7342 Rx.y 
Network Element Support
Enhanced
Applications
5529 APC 
Patches
R9.6.01a
11
Now that you know how to install the plug-ins in the AMS, let’s get an insight about the plug-ins and its types. 
[1] The modular architecture starts from a base platform - core. This is updated only with a major new release of the AMS. 
Minor release updates are handled by the patches that are installed as plugins onto the core.
You can see the plugins as extensions that provide additional functionality or features to a base system.
This modular approach allows us to start from a base platform where plugins can be added later on, according to the needs of the customers.
In addition to patches, the most common type of plugins are the NE-specific plugins that support specific types of ISAM - such as 7302 or 7330 or 7360 or 7342, as well as any new ISAM software release because it usually involves a change in the MIB structure. 
The Enhanced Applications are also plugins and are a part of the 5529 VAP - Value Added Applications suite, containing applications such as: 
5529 Access Provisioning Center - APC, a powerful and consistent service provisioning through the embedded GUI or service-provider Operation Support System - OSS.
5529 OSS Alarm Dispatcher - OAD, an advanced interface for intelligent alarm forwarding to the network-wide alarm management OSS.
5529 Inventory Data Manager - IDM, a specialized application for the mass collection of inventory data in the access network and
5529 Statistics and Data Collector - SDC, an intelligent collection and dispatch of network data to performance and Quality of Service applications. 
5529 Large-scale Release Manager – LRM, this ‘enhanced application’ also called ‘value added application’ is designed to do large-scale upgrades across the network in an automated and predictable fashion, with minimal manpower.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Gerencie sua rede
12
[1] Once the client is successfully installed and updated with the needed plugins, you can start to use the client to manage NEs or the AMS itself, such as user management and AMS system behavior. The user credentials or permissions determine what can be performed.
Let’s see about the basic client handling in the next chapter. 
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
2. NAVEGANDO NO GRAPHICAL USER INTERFACE (GUI)
13
As you have completed your learning about the AMS and its installation procedure, lets move on to the second chapter which will help you with browsing the Graphical User Interface.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
AMS layout
14
The screen which is visible on the slide is the AMS GUI.
 [1] The AMS screen consists of five parts:
[2] a Menu Bar at the top, 
[3] a Navigation Bar beneath it,
[4] a Perspective Bar on the top right,
[5] the AMS Perspective at the center and 
[6] a Status Bar at the bottom of the screen.
Let’s know talk about the functionalities of these bars in the following slides.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Navegação e Menu Perspective
Login, Logout, Lock Screen
Create Group, NE, Link
Navegação (Back, Forward, Up), History
Troca de senha, Cut Through, Find
15
[1] Lets start with the navigation bar. This bar has several icons which aids you with the quick access to the main GUI functions such as: 
[2] Login, Logout, and Lock Screen icons.
[3] Create a Group icon – this icon allows you to group the NEs, for example, by city and to create an NE or a link.
[4] The Navigation option allows you to go back, forward, and up of what was selected within the GUI, and the History icon allows you to see the selections made within the Element Tree View.
[5] The Change Password icon, the Cut-Through icon provides you with access to a node via CLI commands, and the Search icon helps you to search for a task.
[6] Another important bar to note is the Perspective bar. Here, you can add, if desired, more perspectives in the form of tabs with the help of “Open Perspective” icon. 
[7] As shown in the picture, only the Network perspective is opened to enable the users to access the nodes.
[8] Moving on to the Menu Bar, this bar shows the options per-menu item. Once selected, most of these are self- explanatory, and a quick overview per menu item is shown on this page.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Perspectives
Administration: Users, NE-specific, AMS platform, licenças
Alarm: Tabela de alarmes, histórico, objeto com alarme, causas prováveis
Backup Restore: Backup da MIB do ISAM
PM: Monitoração da performance ao longo do tempo
Scheduler: Agendamento de tarefas
Software: Gerenciamento de SW do NE e ONT
16
[1] Lets now see about the available perspectives, each with their own purpose. 
So what is a perspective?
A perspective is a collection of “Windows” with one or more “Views” organized in tabs which occupies the full workspace. 
 Some of the perspectives available are: 
[2] Administration: it contains system configuration options such as user management, NE release specific global settings, AMS platform settings, Alarm handling settings and so on. 
[3] Alarm: It contains options to view the alarm tables and get into the alarm details.
[4] Backup Restore: It contains options such as backup and restore.
[5] PM: It helps to runs Short duration Performance Monitoring tasks.
[6] Scheduler: This option is used to view and modify scheduled tasks.
[7] Software: This perspective manages the NE and Optical Network Termination software (ONT).
Remember that not all perspectives provides you all the options. It depends on your role, certain tasks or actions could be limited or not available.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
AMS customer documentation
AMS Guide
Enhanced applications Guide
NE plugin Guide
17
It is necessary for you to know about the help contents available in the AMS GUI.
[1] The help menu in the menu bar provides you with the help content. Click on it to access the following customer documentation:
[2] AMS platform guides.[3] Enhanced application or Value Added Application guides for the installed VAPs.
[4] NE plugin guides for the installed plugins.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Perspectives
18
[1] As you know, the 5520 AMS GUI offers several perspectives to work with the AMS windows.
The Network perspective is shown here, as an example. It has the following windows with views:
[2] A window with one tab that contains the “Network Tree” view.
[3] A window with two tabs that contain the “Network Alarm Summary” and “Network Event Summary” views.
[4] A window with one tab that contains the “Graphical View” view.
[5] A window with two tabs that contain the “Object Details” and “Comments” views.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Perspectives [cont.] 
Tabs Closed
Reposition
Resized
19
[1] If you want to personalize, you can resize, reposition, close, and open the views or tab to create your preferred layout of that perspective.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Perspectives [cont.] 
20
To open additional views or to open the views closed earlier, you can go to the Window option in the menu bar and select Show View option.
[1] To see all the possible views that can be opened, select the “Other…” option.
[2] A new window opens with a list of views. You can navigate and select the required view to be shown.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Perspectives [cont.] 
Reset perspective para layout default 
Layout Default de Network Perspective
21
[1] After resize, move, add, and close of a view, you might not like the current layout. In such cases, you can easily return to the default layout on any perspective: 
First navigate to the “Perspective Bar”.
Right-click the perspective you want to reset to the default layout, and 
Select the “Reset” option from the drop-down list.
[2] After a confirmation, the perspective will be reset to the default layout.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Status bar
 
User, Messages
AMS Connection, AMS Alarm Count
Unreachable NEs, Partially Managed NEs 
22
[1] You can view the following information in the Status bar.
[2] The users name and messages.
[3] The health of the connection between the AMS client and the server and the server’s aggregated alarm indication.
[4] The number of managed NEs that cannot be reached and the number of NEs that can be partially managed. 
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Preferências
23
[1] You can configure the preferences in the AMS with the help of the Menu Bar option “Windows”. Click on Windows and select “Preferences”.
Some of the preferences available are:
[2] The Alarm Sound Settings: This is to set audible alarms. Once an alarm appears in the AMS, an audible sound is heard.
[3] The Date-Time Format: This includes the time zone, which is useful if the client and the server are in different time zones. You must set this preference correctly if you use schedules.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Configurações
Selecione objeto
Configure parâmetros
Aplique mudanças
24
Let’s now move on to the Configuration options. 
[1] As you know, the AMS client is designed to manage the NEs: once assigned in the AMS, the NEs can be opened and configured.
The configuration of the NE is typically done from the network perspective.
[2] Navigate and select the object that needs to be configured in the “Network Tree” view and the “Graphical View” view.
[3] In the “Object Details” view, configure the parameters as required. In this example, set the “Administrative State” to “Unlocked” to turn on the port chosen. To change the “Object Details” view, first navigate and select the desired object which shows you the parameters that can be configured on that object.
[4] Finally you click the apply button to apply the changes.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Configurações [cont.]
Selecione objeto
Botão direito
Selecione opções e sub-opções no menu suspenso
Configure parâmetros
	na janela aberta 
25
[1] Lets look on to the other way to configure the NE. 
First navigate and select the object that needs to be configured in the “Network Tree” view and the “Graphical View” view.
Right-click the selected object and
Then select the required option presented; sometimes options have sub-options.
Some option when selected immediately performs the action, after a confirmation. 
Other options cause a new window to be opened in which the parameters should be configured before the action is performed.
Note that all possibilities or options shown are not explained here. The configuration steps, options and parameter details are explained in other courses depending on the course objectives.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
3. DECLARANDO ISAM NO AMS
26
Let‘s move on the last chapter of this course. This chapter will help you in bringing the ISAM under AMS control.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Create NE group
27
[1] Before you can manage 'Network element’s’ in short NE’s, they have to be created in the AMS.
You can view the NEs managed by the AMS in the “Network Tree” view on the “Network” perspective. 
Groups are typically created in a logical manner, so that too many NEs would not be under the network tree root. 
In this slide, you can see how to add a new group - such as a province, a city, or a region within a city:
On the Network perspective, you can navigate to the network tree to the place where the group should be created.
Right-click on it and select “Create” – “Group”. 
Alternatively, you can use the “Create Group” icon.
[2] You need to provide a name and as an option, the geographical co-ordinates, in the Map Info tab if you want to position the group correctly in the map.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Create NE
28
[1] To create a Network Element:
[2] Navigate to the Network tree and
Select the group, right-click on it and 
Select Create - NE, or use the icon Create NE, as shown in the picture. 
[3] Then, select the NE type - such as ISAM or ISAM FTTN or IHUB or FTTB, and the release of the NE and click Next.
[4] A new window called the Create NE window will appear, as shown on the right. You can configure the Name, IP address of the node, and the SNMP profiles for the AMS to manage the node. Match the SNMP configuration with the SNMP profiles in the NE with their settings; if not, the NE cannot be managed.
If no SNMP profiles are available or the profiles available are not the ones needed, you need to create a profile. An option to create profiles will appear in the pop-up window when you click the Browse button. Let’s see this on the next slide.
Here, as you see, the two SNMP profiles are needed for this type of node. One gives rights to the AMS to access the core part of the node - the IACM, the controller-NT, LT cards and functions, and the other is the switch or router - SHUB or IHUB. Without these, you will not be able to configure the node or retrieve the node configuration through the AMS.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Create NE [cont.]
29
[1] As soon as you click the Browse button for the SNMP Profile selection seen on the previous slide, a new pop-up window appears. 
[2] You can see that some SNMP profiles are already created, but you can also create new ones.
[3] In the window that opens, you have to name the SNMP profile, select the SNMP version - versions 1, 2, and 3 are supported, and ensure that you give the same name for the read and write communities. For SNMP v3, additional information and additional settings are required. To get a detailed information of it, refer to the AMS customer documentation.
Due to your role restrictions, sometimes you might not be able to create the SNMP profiles. Contact the AMS administrator in such cases. Usually, the required SNMP profiles are already created by the AMS administrator and you just have to select them as needed.
© Nokia 2019- Nokia Confidential
DRAFT
‹nº›
Reachability Test – teste de conectividade do ISAM com o AMS
30
[1] Once the NE is created in network, you can verify the connectivity between the AMS and the NE. This is recommended before you supervise an NE.
[2] In the Network tree, select the NE.
[3] Right-click and select Supervision, Reachability Test, Regular.
[4] You can see the connectivity results of the IP, SNMP, and also the CLI and TL1 cut-through credentials if provisioned. 
The Reachability test, therefore, not only tests if the IP of the node is reachable from the AMS but also tests if the AMS has the proper SNMP rights to access the node to configure - write or retrieve – read, the configurations already done.
If any one of the tests fails, resolve that issue first before you start to supervise the NE.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›
Start supervision
Declared
(Not supervised yet)
Supervised
Partly
Supervised
Unreachable
Partly
Reachable
Supervising
31
[1] The last step is to supervise the node.
[2] In the Network tree, select the NE. 
[3] Right-click and select; Supervision, Start.
[4] and Confirm the Start Supervision.
[5] Once successfully completed, close the result window.
[6] This slide also shows the different types of status possible in an NE once it is supervised.
Note that it is possible to have a scenario where the IACM is reachable whereas the SHUB or IHUB would not be reachable.
© Nokia 2019 - Nokia Confidential
DRAFT
‹nº›