Module 02:
System Manager Installation
Module Duration:
© 2012 Avaya, Inc. All rights reserved, Page 1
Module Objectives
After completing this module, you will be able to:
Understand SMGR’s relation to other products in the network.
Know how to prepare for a successful SMGR Installation.
Install System Manager.
Troubleshoot a failed SMGR installation.
Module Duration: 15 Minutes © 2012 Avaya, Inc. All rights reserved. Page 2
Module 02: System Manager Installation
Lesson 01: System Manager Features & Benefits
Lesson Duration: 15 minutes
© 2012 Avaya, Inc. All rights reserved, Page 3
Lesson Objectives
After completing this lesson, you will:
Recall SMGR's place in the Aura network.
Lesson Duration: 15 Minutes
© 2012 Avaya, Inc. All rights reserved. Page 4
What part does SMGR play in
???
© 2012 Avaya, Inc. All rights reserved, Page 5
SMGR in Avaya Aura®
Centralized Product Management User Profile Management
– Administrators / communication users
Administration Central User Profile
Configuration User info shared
Licensing RBAC – Role Based Access Control
© 2012 Avaya, Inc. All rights reserved, Page 6
Avaya Aura® User Profiles
Unified
Communicatio
ns
Avaya Aura® user
Login
Name, Address, Contact
Service Profile
App Sequencing
CM / SM associations
© 2012 Avaya, Inc. All rights reserved, Page 7
SMGR – Additional Roles & Key Functions
Single sign-on to Event & alarm monitoring, SNMP Certificate Authority (CA)
central management (Simple Network Management enabling secured network
interface Protocol). communication.
Remote maintenance using Integrated WebLM for
Secure Access Link (SAL) licensing.
© 2012 Avaya, Inc. All rights reserved, Page 8
SMGR Specification – Capacity
Capacities SMGR 5.2 SMGR 6.0 SMGR 6.1 SMGR 6.2
Number of administrator logins 50 250 250 250
Number of simultaneous logins 10 50 50 50
Number of endpoints (total) 25,000 100,000 100,000 250,000
Number of SIP endpoints 25,000 100,000 100,000 100,000
Number of end users 25,000 100,000 100,000 250,000
Number of contacts per user 250* 250* 250* 250*
Number of public contacts 1,000 1,000 1,000 1,000
Number of personal contact lists, per user 1 1 1 1
Number of members in a personal contact list 250 250 250 250
Number of groups 50 300 300 300
Number of members in a group 300 400 400 400
Number of elements 10,000 25,000 25,000 25,000
Number of CMs (either as Feature Server or Evolution
Server) 100 500 500 500
(counts against the total number of elements)
Number of Branch Session Managers
n/a 250 250 250
(counts against the total number of elements)
Number of B5800 Branch Gateways
n/a n/a n/a 2,000
(counts against the total number of elements)
Note: 2000 requires
* There is a system limit of 2.5 million contact. several WebLM Servers
© 2012 Avaya, Inc. All rights reserved, Page 9
Module 02: System Manager Installation
Lesson 02: Installation Architecture Overview
Lesson Duration: 30 minutes
© 2012 Avaya, Inc. All rights reserved, Page 10
Lesson Objectives
After completing this lesson, you will:
Understand the hardware architecture of a SMGR installation.
Understand SMGR's relationship to System Platform (SP).
Understand how SMGR is virtualized as an easy-to-distribute
virtual appliance.
Have information needed for installation.
Lesson Duration: 30 Minutes
© 2012 Avaya, Inc. All rights reserved. Page 11
System Manager Installation
SMGR is a free entitlement
Customers become eligible to receive it by
purchasing:
– Avaya Aura® Standard or Enterprise Edition
– Communication Server 1000 (CS1K) 7.5 &
greater
– B5800 Branch Gateway 6.2 & greater
Obtaining System Manager software
– Downloadable from [Link]
– Order via Avaya Solution Designer (ASD) as an
optional extra
– Default option is no SMGR. (Enterprises don’t
need more than one!)
SMGR software is free – hardware can be
purchased from Avaya
– For more on hardware, see SMGR release notes
© 2012 Avaya, Inc. All rights reserved, Page 12
System Manager Installs as a System Platform Template
SMGR is not installed by executing an installer file from Linux command line
≠ Regular software installer
Instead, SMGR is distributed as a virtual machine template and is
designed to run in System Platform – Avaya’s virtual machine player
© 2012 Avaya, Inc. All rights reserved, Page 13
What is System Platform?
System Platform is a virtual machine manager that enables virtualised ‘pre-packed’
servers to be:
Easily distributed
Easily deployed
Tightly controlled
Deployed on one piece of physical hardware
© 2012 Avaya, Inc. All rights reserved, Page 14
System Platform Hypervisor
System Platform – software running on a server
XEN Hypervisor
● Controls Virtual Appliance access to shared hardware
● Provides ‘near native’ performance for Virtual Appliance
operating systems (OSs) - uses specially patched Kernels which
enable hypercalls
● XEN is open source & free
– No additional cost of goods shipped (COGS)
XEN Hypervisor - DOM-0
Proc HDD RAM NIC
Hardware
● Server box
● Processor, disks, etc
© 2012 Avaya, Inc. All rights reserved, Page 15
System Platform Utilities
CDom VM
Hosts web interface for:
● Deploying templates CDom Services
HTTP
● Managing templates VM
● Managing HA
● Viewing logs
CentOS CentOS
Utils
XEN Hypervisor - DOM-0
Proc HDD RAM NIC
© 2012 Avaya, Inc. All rights reserved, Page 16
System Platform Utilities (continued)
Services VM
● Contains Secure Access Link CDom Services
(SAL) Gateway VM
– Facilitates remote
connectivity
– Allows support engineer to CentOS CentOS
perform maintenance
remotely Utils
XEN Hypervisor - DOM-0
Proc HDD RAM NIC
© 2012 Avaya, Inc. All rights reserved, Page 17
System Platform Template
Space for a template of Virtual Appliances. What is a template?
CDom Services
VM
CentOS CentOS
Utils
XEN Hypervisor - DOM-0
Proc HDD RAM NIC
© 2012 Avaya, Inc. All rights reserved, Page 18
System Platform Template – Multiple Virtual Appliances
A System Platform template is a Presence
SMGR CM
collection of Virtual Appliances Services
(VAs). Each VA is…
– Pre-loaded with its own OS
– Pre-loaded with application(s) RHEL WIN Cent OS
– Pre-loaded with packages & drivers
– Optimised for performance & VA1 VA 2 VA 3
security App 1 App 2 App 3
A template is file. It is distributable
over web or on DVD RHEL Win Cent OS
All VAs within the template run in System Platform Template
the same System Platform, on a
single physical hardware box.
© 2012 Avaya, Inc. All rights reserved, Page 19
Templates are Deployed on System Platform
A template plugs in to System Platform, from where the VAs are ‘switched on’.
CDom Services VA1 VA 2 VA 3
VM App 1 App 2 App 3
CentOS CentOS RHEL Win Cent OS
Utils System Platform Template
XEN Hypervisor - DOM-0
Proc HDD RAM NIC
© 2012 Avaya, Inc. All rights reserved, Page 20
System Platform Template – Multiple Virtual Appliances?
Although a template may contain multiple VAs, it may also still contain only one.
The SMGR template contains just one VA, running on Red Hat Enterprise Linux.
Presence CM
SMGR SMGR
Services
RHEL WIN Cent OS RHEL
VA1 VA 2 VA 3
App 1 App 2 App 3 SMGR
RHEL Win Cent OS RHEL
System Platform Template SP Template
© 2012 Avaya, Inc. All rights reserved, Page 21
System Manager on System Platform
The Finished SP Architecture
CDom Services SMGR
CentOS CentOS RHEL
Utils Template
XEN Hypervisor - DOM-0
The specific System
Proc HDD RAM NIC Platform build + patches
needed will depend on the
version of SMGR being
deployed – be sure to check
Architecture of SMGR the SMGR release notes.
hosted on System Platform
© 2012 Avaya, Inc. All rights reserved, Page 22
Module 02: System Manager Installation
Lesson 03: System Platform Installation
Lesson Duration: 30 minutes
© 2012 Avaya, Inc. All rights reserved, Page 23
Lesson Objectives
After completing this lesson, you will understand how to:
Connect to the System Platform server.
Install the System Platform (O/S layer).
Lesson Duration: 30 Minutes
© 2012 Avaya, Inc. All rights reserved. Page 24
System Platform Installation
2 Routes through the material depending on your class environment.
Virtual Lab Physical
Environment Environment
(TECNet) (Travel Kit)
Outline the process Outline the process
Identify needed information Identify needed information
Will NOT install System Install System Platform
Platform
– Limitation of the virtual
environment
© 2012 Avaya, Inc. All rights reserved, Page 25
Hardware Support
SMGR is supported for deployment on:
Dell Poweredge R610
Avaya S8800 (IBM x3550)
HP Proliant DL360 G7
© 2012 Avaya, Inc. All rights reserved, Page 26
Installing System Platform
SP Installation Steps
1. Collect information
2. Connect to SP server CDom Services SMGR
3. Configure installation
CentOS CentOS RHEL
Utils Template
XEN Hypervisor - DOM-0
Proc HDD RAM NIC
Architecture of SMGR
hosted on System Platform
© 2012 Avaya, Inc. All rights reserved, Page 27
Installing System Platform
Need to have:
● 3 IP Addresses & Machine
names
– C-Dom CDom Services SMGR
– Services VM
– Dom 0 CentOS CentOS RHEL
● Network info Utils Template
– Gateway
– Subnet mask
XEN Hypervisor - DOM-0
– DNS
● Time settings
● Passwords Proc HDD RAM NIC
© 2012 Avaya, Inc. All rights reserved, Page 28
Exercise: Locate Installation Information
Objective & Outcome
The objective of this exercise is to gather the information needed to
install System Platform By the time you are done, you should have all the
information you need in order to perform an installation.
Locate the information needed to install System Platform in your
network. This includes:
● Reserved CDom / Dom0 IP address & hostname
● Network DNS server IP, default gateway & subnet mask
● Network Time Protocol (NTP) Server address (if available)
● Passwords (in this class we’ll simply use the defaults)
This info is found in your classroom layout document.
Make a note of your findings.
Individual Exercise
Student A Student B
© 2012 Avaya, Inc. All rights reserved. Page 29
Next…
Two options
© 2012 Avaya, Inc. All rights reserved, Page 30
Connecting to the System Platform Hardware: 2 Options
1. Connect monitor and keyboard 2. Connect computer to the services port
directly to server box of the server box for Telnet session
– 2nd Ethernet port, identified in the
OS as eth1
© 2012 Avaya, Inc. All rights reserved. Page 31
Installing System Platform – Boot Server with SP Disk
Obtain the System Platform ISO image
– Download from PLDS
– [Link]
Burn ISO to disk
Boot server with disk in drive
Server prompts for local response
– Will prompt for keyboard input
– Will wait for 30 seconds only
– After 30 seconds will look for Telnet session
Telnet installation
– Once switched to Telnet session, the local
keyboard and monitor can no longer be
used
– TIP: When performing local install, press
enter on keyboard within 30s
Once re-booted, the System Platform
wizard will appear
© 2012 Avaya, Inc. All rights reserved, Page 32
Connecting to the System Platform Install Wizard: 2 Options
Direct connection requires no preparation Connecting over Telnet through the services
other than physically connecting the keyboard port requires your computer to be on the
and monitor. same subnet as the server.
On boot up the System Platform wizard Next task is to change the laptop network
appears directly on the screen. settings.
© 2012 Avaya, Inc. All rights reserved, Page 33
Configuring Laptop Network Settings for Connection
Through Services Port
From a windows laptop
1. Click Start > Connect To >
Show all connections
2. Right-click on Local Area
Connection, and select
Properties
3. Double-click on Internet
Protocol (TCP/IP)
continued…
© 2012 Avaya, Inc. All rights reserved, Page 34
Configuring Laptop Network Settings for Connection
Through Services Port (continued)
4. Configure your local network exactly
as shown below:
– Select ‘Use the following IP Address’
– Enter IP: [Link]
– Enter subnet mask: [Link]
– Enter default gateway: [Link]
Once set, you will be able to Telnet
into the waiting installer.
© 2012 Avaya, Inc. All rights reserved, Page 35
Exercise: Configure Network Adapter
This exercise is only for students in physical lab environment:
Objective & Outcome
The objective of this exercise is to learn how to prepare your
computer for connecting to the services port of the server, prior
to installing System Platform By the time you are done, your
computer should be on the same subnet as the server.
1. Click Start > Connect To > Show all connections
2. Right-click on Local Area Connection, and select Properties
3. Double-click on Internet Protocol (TCP/IP)
Physical
4. Configure your local network exactly as shown below Environment only
Select ‘Use the following IP Address’ (Travel Kit)
Enter IP: [Link]
Enter subnet mask: [Link]
Enter default gateway: [Link] Individual Exercise
5. Click Ok
6. Test the connection by pinging [Link]
Student A Student B
© 2012 Avaya, Inc. All rights reserved, Page 36
Installation Via Services Port – Establishing Telnet Session
Launch Putty – connect to [Link]
Set the character encoding (UTF-8)
© 2012 Avaya, Inc. All rights reserved, Page 37
Exercise: Establish Telnet Session with Server
This exercise is only for students in physical lab environment:
Objective & Outcome
The objective of this exercise is to learn how to establish a Telnet session with
the server.
By the time you are done, you should have a Telnet session established and
should see the first System Platform installation wizard page on your screen
1. Open Putty client
2. Enter the SP server IP address: [Link]
3. Navigate to Window > Translation & set the received data to UTF-8
4. Click Open. The first System Platform installation wizard screen should appear.
Team Exercise
Physical
Environment only
(Travel Kit)
Student A: Lead Student B: Shadow
© 2012 Avaya, Inc. All rights reserved, Page 38
Next…
© 2012 Avaya, Inc. All rights reserved, Page 39
SP Installation – Step 1: Keyboard Type
● Select keyboard type
© 2012 Avaya, Inc. All rights reserved, Page 40
SP Installation – Step 2: Test CD
● Check installation disk?
● The install wizard can verify the disk image
● If this is the first time using the installation disk – definitely yes!
● Worth doing every now and again or when installation fails
???
© 2012 Avaya, Inc. All rights reserved, Page 41
SP Installation – Step 3: Dom 0 Configuration
● Hostname in FQDN format: [Link]
Already identified:
● 3 IP Addresses &
Machine names
– C-Dom
– Services VM
– Dom 0
● Network info
– Gateway
– Subnet mask
– DNS
● Time settings
● Passwords
© 2012 Avaya, Inc. All rights reserved, Page 42
SP Installation – Step 3: Dom 0 Configuration, IP Forwarding
● Confirm to enable IP Forwarding? Either…
● Allowing traffic received on one NIC to be forwarded to another, or
● Totally segregate traffic from different NICs?
© 2012 Avaya, Inc. All rights reserved, Page 43
Exercise: Configure System Platform Dom 0
This exercise is only for students in physical lab environment:
Objective & Outcome
The objective of this exercise is to learn how to configure Dom 0 VM network
settings. You will not be able to test success until of this exercise until the
installation is complete.
1. Configure the Dom 0 network options
2. Use the details reserved for your system – outlined in the
classroom layout document
3. Select to enable IP forwarding. (Traffic segregation in this
training lab will be cumbersome)
Team Exercise
Physical
Environment only
(Travel Kit)
Student A: Lead Student B: Shadow
© 2012 Avaya, Inc. All rights reserved, Page 44
SP Installation – Step 4: Services Configuration
● Hostname in FQDN format: [Link]
Already identified:
● 3 IP Addresses &
Machine names
– C-Dom
– Services VM
– Dom 0
● Network info
– Gateway
– Subnet mask
– DNS
● Time settings
● Passwords
© 2012 Avaya, Inc. All rights reserved, Page 45
SP Installation – Step 4: Services Configuration, VM size
● Choose VM Footprint Size suitable for your server
● Note the hint to help you select
© 2012 Avaya, Inc. All rights reserved, Page 46
SP Installation – Step 5: CDom Configuration
● Hostname in FQDN format: [Link]
Already identified:
● 3 IP Addresses &
Machine names
– C-Dom
– Services VM
– Dom 0
● Network info
– Gateway
– Subnet mask
– DNS
● Time settings
● Passwords
© 2012 Avaya, Inc. All rights reserved, Page 47
Exercise: Configure Services & CDom
This exercise is only for students in physical lab environment:
Objective & Outcome
The objective of this exercise is to learn how to configure Services and CDom
VM network settings.
You will not be able to test success until of this exercise until the installation is
complete.
1. Configure the CDom VM network settings
2. Configure the Services VM network settings & VM size
Use the classroom layout document for IP and Hostname details
Physical Team Exercise
Environment only
(Travel Kit)
Student A: Lead Student B: Shadow
© 2012 Avaya, Inc. All rights reserved, Page 48
SP Installation – Step 6: TimeZone
● Select the correct time zone for the server
© 2012 Avaya, Inc. All rights reserved, Page 49
SP Installation – Step 7: Date & Time NTP settings
● Check the time. Amend if necessary
● Enter address of NTP server (optional)
– A Network Time Protocol server serves to synchronise all
servers with the same, correct date and time.
© 2012 Avaya, Inc. All rights reserved, Page 50
SP Installation – Step 8: Set Passwords
● Default passwords:
– root / root01
– admin / admin01
– cust / cust01
– LDAP / root01
© 2012 Avaya, Inc. All rights reserved, Page 51
SP Installation – Step 9: Observe Installation
● Installation can take around 30 minutes
© 2012 Avaya, Inc. All rights reserved, Page 52
SP Installation – Step 10: Connect to System Platform Web
Console
Launch a browser on your desktop, and
enter System Platform CDom URL.
[Link] CDom IP>/webconsole
© 2012 Avaya, Inc. All rights reserved, Page 53
Exercise: Time & Passwords, Observe Installation & Test
This exercise is only for students in physical lab environment:
Objective & Outcome
The objective of this exercise is to learn how to Physical
configure Services and CDom VM network settings. Environment only
By the time you are done you should have the (Travel Kit)
System Platform Login on your screen.
1. Configure the server time settings
- Time zone
- Time
- NTP server (if available)
2. Enter the default server passwords
- root / root01
- admin / admin01
- cust / cust01
3. Allow the installation to complete. Monitor Team Exercise
its progress.
4. When complete open a browser on your
local computer and enter the System
Platform URL. [Link] CDom IP>/webconsole
Student A: Lead Student B: Shadow
© 2012 Avaya, Inc. All rights reserved, Page 54
Installing System Platform – Summary
© 2012 Avaya, Inc. All rights reserved, Page 55
Exercise: Reset your Network Adapter
This exercise is only for students in physical lab environment:
Objective & Outcome
To reset your computer network configuration to its
previous settings.
1. Click Start > Connect To > Show all connections
2. Right-click on Local Area Connection, and select
Properties
3. Double-click on Internet Protocol (TCP/IP)
4. Configure your local network exactly as shown below Physical
- Select button ‘ Use the following IP Address’
Environment only
(Travel Kit)
- Enter IP: Your previous IP address
- Enter subnet mask: Your previous subnet
- Enter default gateway: Your previous gateway Individual Exercise
5. Click Ok
Student A Student B
© 2012 Avaya, Inc. All rights reserved, Page 56
Module 02: System Manager Installation
Lesson 04: Checking for, downloading and installing System
Platform Patches
Lesson Duration: 30 minutes
© 2012 Avaya, Inc. All rights reserved, Page 57
Lesson Objectives
After completing this lesson, you will be able to:
Check for, download and install System Platform patches.
Lesson Duration: 10 Minutes
© 2012 Avaya, Inc. All rights reserved. Page 58
System Manager Template Deployment
Launch a browser on your desktop, and
navigate to the System Platform server.
Log into System Platform
[Link] IP>/webconsole
(Use the CDom IP you
Default: assigned during install)
admin
admin01
(set during install) VIRTUAL CLASS:
Open browser in your
remote student desktop –
Use VNC window
© 2012 Avaya, Inc. All rights reserved, Page 59
Patching System Platform
● If any patches are available, update System Platform with the latest fixes
● Go to Server Management > Patch Management > Download / Upload
© 2012 Avaya, Inc. All rights reserved, Page 60
Patching System Platform (continued)
● Patches can be obtained direct from PLDS, the SP server (once uploaded), and/or via CD / USB.
● Any patches for the class will be retrieved via HTTP from a central classroom HTTP server.
[Link]
© 2012 Avaya, Inc. All rights reserved, Page 61
Patching System Platform (continued)
● Click the patch and hit ‘Select’
● After viewing the patch, click to install it
Depending on the patch,
you may need to restart
the server
© 2012 Avaya, Inc. All rights reserved, Page 62
Exercise: Install System Platform Patch
Objective & Outcome
The objective of this exercise is to learn how to look for, download and install a
System Platform software patch. By the time you are done you should have a
new patch located and installed.
1. Connect to System Platform web console: [Link]
User ID: admin Password: admin01
2. Navigate to: Server Management > Patch Management > Download / Upload
3. Select to locate patches using HTTP
4. Use the classroom layout doc to find the HTTP server location
E.g. [Link] Your instructor will provide the URL
Find & install the latest SP patch
– NB: it may be the case that the SP has already been patched. You can check
the patched status of the server by clicking ‘manage’ under ‘Patch
Management’
– Even though one student in the pair will perform this exercise, there Team Exercise
is no harm in the second user navigating and looking around SP
– just don’t ‘action’ any changes as it may interfere with the exercise
Student A: shadow Student B: Lead
© 2012 Avaya, Inc. All rights reserved, Page 63
Module 05: System Manager Installation
Lesson 05: Deploying the System Manager Template
Lesson Duration: 30 minutes
© 2012 Avaya, Inc. All rights reserved, Page 64
Lesson Objectives
After completing this lesson, you will be able to:
Deploy the SMGR template to System Platform.
Configure the deployment with the correct parameters.
Lesson Duration: 30 Minutes
© 2012 Avaya, Inc. All rights reserved. Page 65
SMGR Template Deployment
Regardless of the type of lab environment, we’ll be performing all exercises
in this lesson!
Virtual Lab Physical
Environment Environment
(TECNet) (Travel Kit)
© 2012 Avaya, Inc. All rights reserved, Page 66
System Manager Template Deployment
Configure HTTP
proxy if using
PLDS
© 2012 Avaya, Inc. All rights reserved, Page 67
System Manager Template Deployment (continued)
● EPW = Electronic
Pre-Installation Worksheet
● Allows for configuring
??? deployment settings offline –
simplifying process onsite
● We'll not be using one
© 2012 Avaya, Inc. All rights reserved, Page 68
System Manager Template Deployment (continued)
● Confirm SMGR version you are installing
● SP will then begin to download the SMGR template
files from the HTTP location
● Ensure browser
allows pop-ups
© 2012 Avaya, Inc. All rights reserved, Page 69
System Manager Template Deployment – SMGR VM Settings
● Low level network
settings will be taken
from underlying SP
configuration.
● No need to change
these settings
FQDN created in format: [Link]
© 2012 Avaya, Inc. All rights reserved, Page 70
System Manager Template Deployment
● Accept non-root user (admin)
● We’ll need to authenticate as this user whenever
we need to SSH into the SMGR VM
Username: admin
Password: admin
● SNMP can be used to monitor
SMGR
● Suggested SNMP authentication
details:
User Name Prefix: user
Auth Password: password
Priv Password: privpassword
© 2012 Avaya, Inc. All rights reserved, Page 71
System Manager Template Deployment (continued)
● Review installation
settings
● Click Next Step
© 2012 Avaya, Inc. All rights reserved, Page 72
System Manager Template Deployment (continued)
● Accept Licence Terms Last
chance to edit settings.
If you’re happy…
● Proceed with the installation!
© 2012 Avaya, Inc. All rights reserved, Page 73
System Manager Template Deployment (continued)
● Installation will then continue
● You don’t need to keep the browser window open
● Will take 90 - 120 minutes
© 2012 Avaya, Inc. All rights reserved, Page 74
Exercise: Deploy SMGR Template
Objective & Outcome
The objective of this exercise is to learn how deploy the SMGR template in
to System Platform. By the time you are done, the SMGR template should
be deployed.
1. Navigate to ‘Virtual Machine Management > Solution Template
2. Locate the server using HTTP – enter the HTTP location outlined in the
classroom layout document
3. Select the [Link], and choose to continue without an EPW file
4. Click to install, and ensure that your browser allows the pop-up
5. Review network configuration from System Platform
6. Set the SMGR IP, hostname & domain name. Use classroom layout
document for data. Ensure no IP conflicts - these are difficult to fix later
7. Make note of non-root username (admin) Team Exercise
8. Set SNMP V3 parameters
- User Name Prefix: user
- Authentication Password: password
- Privacy Password: privpassword Student A: Lead Student B: Shadow
9. Accept License Terms and proceed with installation. (Takes 20-30 mins)
© 2012 Avaya, Inc. All rights reserved, Page 75
Module 02: System Manager Installation
Lesson 06: SMGR Installation Verification & Troubleshooting
Lesson Duration: 30 minutes
© 2012 Avaya, Inc. All rights reserved, Page 76
Lesson Objectives
After completing this lesson, you will be able to:
Verify that SMGR has deployed correctly.
Locate the installation log files.
Know what to do when things go wrong?
Lesson Duration: 30 Minutes
© 2012 Avaya, Inc. All rights reserved. Page 77
System Manager Installation Verification
Wrench = shortcut to Note
SMGR web console Just because the VM is running, it doesn’t
mean the services on the VM are healthy!
© 2012 Avaya, Inc. All rights reserved, Page 78
System Manager Installation Verification (continued)
Wrench = shortcut to SMGR web console
Uses SMGR FQDN – resolvable
through lab DNS
© 2012 Avaya, Inc. All rights reserved, Page 79
System Manager Installation Verification (continued)
Try accessing the SMGR web console
[Link] IP address>
If the page doesn’t become available, or reports that
maintenance is in progress, allow a little time (~20 minutes)
© 2012 Avaya, Inc. All rights reserved, Page 80
Exercise: Access SMGR Web Interface
Objective & Outcome
The objective of this exercise is to learn how access SMGR’s
web interface. By the time you are done you should see the
SMGR login screen in your browser.
1. Open a browser and enter SMGR web console URL
[Link] IP> or [Link] domain name>
Eg [Link]
2. Check that the UI is up & responsive
Individual Exercise – both students
Student A Student B
© 2012 Avaya, Inc. All rights reserved, Page 81
Unresponsive? How to Reboot SMGR VM
● To reboot the SMGR VM, click the VM link in SP menu
● Select the ‘Reboot’ option
© 2012 Avaya, Inc. All rights reserved, Page 82
Unresponsive? How to Reboot System Platform
● System Platform is typically very stable – long uptimes
● If System Platform does become unstable, you may want to try a soft reboot
This will reboot the entire
SP server – including any
deployed VMs
© 2012 Avaya, Inc. All rights reserved, Page 83
Exercise: Reboot SMGR VM
This exercise is only for students in physical lab environment:
Objective & Outcome
The objective of this exercise is to learn how reboot the
SMGR virtual machine. By the time you are done, your
SMGR virtual machine will have been rebooted.
1. Log into System Platform
2. Navigate to the SMGR VM summary page
3. Click to reboot the SMGR VM (not the whole SP)
Move on to the next exercise while the server cycles. Check
back every few minutes to see if SMGR responds to a request
from your browser.
Team Exercise
Physical
Environment only
(Travel Kit)
Student A: shadow Student B: Lead
© 2012 Avaya, Inc. All rights reserved, Page 84
System Manager Installation Verification – Logs
If there's a deployment error – you may need to troubleshoot
– Install logs give clues as to what went wrong
Customer support may benefit from inspecting SMGR installation logs (found on
SP CDom)
Avaya doesn’t expect customers to be experts at analyzing these logs, but they
may hold some useful clues
– Definitely worth checking!
© 2012 Avaya, Inc. All rights reserved, Page 85
System Manager Installation Verification – Accessing Logs
To access the logs, we’ll need to SSH into CDom
Launch Putty (or another SSH client)
SSH
© 2012 Avaya, Inc. All rights reserved, Page 86
System Manager Installation Verification – Logs
● Log in (cust / cust01)
● Promote to the root user (root / root01)
● Change to log directory
● List directory contents
cust01
root01
© 2012 Avaya, Inc. All rights reserved, Page 87
System Manager Installation Verification – Logs
Using less
Simple Linux text reader Searching
Use up / down / pgup / pgdown to ● Use ‘grep’
move through file ● To search for the final outcome of the installation:
# cat [Link] | grep ‘Workflow finished’
Exit by typing ‘q’
© 2012 Avaya, Inc. All rights reserved, Page 88
Exercise: View Installation Logs
Objective & Outcome
The objective of this exercise is to learn how access the installation logs. By the
time you are done, you should be able to locate the logs and know how to open
them and search for key words. Typically, an enterprise administrator will pass
these logs to Avaya support when problems occur.
1. Launch Putty. SSH into the CDom VM (cust / cust01). See student lab guide for
CDom IP address.
2. Promote to root (root / root01)
# su – root
Individual Exercise – both students
Password: root01
3. Change directory to /var/log/vsp then show directory listing to see log files
# cd /var/log/vsp
# ls
4. Take a look at the log files. Suggest start with [Link]
Student A Student B
# less [Link]
Navigate file with up/down & pageup/pagedown keys. Press Q to quit file
5. Optional: Search log for keywords. Close the log, then from the command line…
# cat [Link] | grep ‘Workflow finished’
Example output:
<14>Dec 27 01:02:33 SMGR-Lab-Cdom vspwebconsole[1584]: -07:00 2011 302 1
[Link] | 0 + Workflow finished, final state: COMPLETE
© 2012 Avaya, Inc. All rights reserved, Page 89