Technical Assessment for Avaya Aura(TM) System Manager.
SIP
HTTPS
SSH
INADS
True
False
True
False
Desk location
Session Manager & Branch Session Manager affiliation
Email address and presence handles
Associated CM Station profile (if one exists)
Https://135.122.100.10/webconsole
Https://135.122.100.11/webconsole
Https://135.122.100.12/webconsole
Https://135.122.100.12/SMGR
System Manager is distributed and deployed as an Avaya Aura System Platfrom Template
The utilities domain (C-DOM) of System Platfrom hosts a web console through which we manage the System Manager VA
The System Manager template may be installed over the network, from optical media or from USB
Once deployed into DOM-0, System Manager no longer relies on the utilities domain
System health monitoring & User Profile Management
Secured remote connectivity & protection against server failover
Secured remote connectivity & system health monitoring
User information
Group definitions
Application configuration
All of the above
SMGR will always be deployed in a network where a WebLM server has also been deployed
SMGR must be co-resident with a WebLM server
SMGR has no direct connection to a WebLM server - they are completely separate products
SMGR contains an integrated WebLM server
DOM-0 of the System Platform hosts the SAL Gateway used to connect to the System Manager
SAL Agents monitor specific product log files, and send alarms and events recorded there to a central logging service running in SMGR
SMGR requires a SAL Enterprise Server in the local network in order to run
C-DOM hosts a SAL Gateway that remote administrators can use to access SMGR
The SAL Policy Server stores which users can connect remotely using SAL and what they can gain access to
The SAL Policy Server enforces which users can gain access to which servers by acting as a connection gateway
The SAL Policy Server stores all System Manager roles and permissions
Before connecting to a remote enterprise network, a support engineer must first turn off the SAL Policy Server
SSH access details
Subnet
SNMP access details
CM access details
The SDK will not be made available to Avaya partners
The System Manager SDK will accelerate adoption of System Manager within Avaya
It is hoped the SDK will be made available to developers beyond Avaya to help bring added value and innovation to Avaya Aura network
The System Manager SDK consists of documentation, code samples, and development libraries to be used in creating System Manager based admin tools
True
False
True
False
SMGR uses System Platform high availability features and allows a single backup to take over from a primary should it fail
SMGR allows for a cluster of several SMGR instances to share access to the same master database
DOM-0 is home to the SAL Gateway which enables engineers to remote connect to and debug SMGR
DOM-0 is home to the XEN Hypervisor which is responsible for hosting the C-DOM, and the template domains and enabling them all to share access to the server hardware
DOM-0 contains the file system for the entire server and makes it available to virtual guests via NFS
DOM-0 hosts the database layer for System Platform templates, and therefore is used by SMGR
System Platform is the hardware platform for running the optimized SMGR VA
SMGR runs as a VA on the System Platform, which acts as a virtual hosting layer
Once deployed onto a server, System Platform simplifies turning that server into a VA using XEN - System Manager is once such server
System Platform is an optional plug-in for SMGR
To enable an administrator to configure instances of Modular messaging in the network
To enable an administrator to configure NRP on Session Managers in the network
To enable an administrator to configure CMs in the network
SMGR enforces time of day routing policies
SMGR enables system administrators to view system alarms and notifications
SMGR allows you to control a variety of Avaya products deployed in the Enterprise network
SMGR allows you to create and manage users and System Administrators
True
False
By successfully logging into the SMGR web interface, you learn that the network, SMGR web application, and database components are working
It is not necessary to validate the SMGR installation since the System Platform deployment process guarantees it
XEN runs in the server firmware
XEN is a hypervisor
XEN is responsible for scheduling how SMGR gets access to the hardware
XEN runs in DOM-0 of the System Platform
/vsp-template/
/var/log/vsp/
/Avaya/logs
True
False