Avaya Aura System Manager

6,496 views

Published on

Avaya Aura System Manager

Published in: Technology

Avaya Aura System Manager

  1. 1. © 2011 Avaya Inc. All rights reserved. System Manager Overview 1
  2. 2. © 2011 Avaya Inc. All rights reserved. System Manager Introduction System wide management of CM-Next Generation  System Manager provides IT and Telecom Operations the means to manage the core elements of CM-Next Generation together as a System  System Manager optimizes management functions for provisioning, operations and fault/performance monitoring to simplify and reduce management complexity and solution servicing – Reduces complexity of operations for distributed multi-site networks with multiple control points (inherent with SIP) – Increases the value of convergence through tight integration with the enterprise IT infrastructure (Identity, Security, Master Data, ITIL Processes)  Key Customer Benefits – End-to-End View, Single unified console with workflow-based management – Better skill set re-use and increased productivity through easy-to-use tools – Integrated provisioning to reduce configuration errors – Reduces TCO and reduces service support costs through automation of time- consuming, error-prone tasks – Accelerate customer application integration with standards-based interfaces 2
  3. 3. © 2011 Avaya Inc. All rights reserved. Summary of Avaya Customer Input  Simplify – Enter user data only once across the enterprise environment (too many management tools requiring separate entry) – Single view and administration point of Avaya solutions – Consistent level of management across products  Secure – Roles based permissions with standard AAA – Secure management protocols  Integrate – Provide SNMP consistency across all solutions – Directory integration for user data – Accessible from other tools using industry standard interfaces 3
  4. 4. © 2011 Avaya Inc. All rights reserved. System Manager – Functional Components  System Manager includes both framework and management services: – A browser-based, extensible common console framework – With UI design patterns to ensure consistent user experience – A set of shared management services that – Manage shared resources across all elements – For example – User Profile Management – Provide centralized data store and single point of access – Are extensible for element specific data, UI, logic, etc. – A common installation framework – An Element Manager to manage itself  Element Managers provide element unique management services and UIs to manage element resources – System Manager works in conjunction w. Element Managers to deliver a common and uniform management experience 4
  5. 5. © 2011 Avaya Inc. All rights reserved. System Manager Functionality Infrastructure  Web-console with single sign on  User permissions  Logging  Alarming  SAL integration for alarm, remote access, inventory  Trust mgmt (certificates)  Health monitoring (Lifecycle)  Enhanced security management Central mngt services  User profile management (UPM)  Network routing policy (NRP) administration 5
  6. 6. © 2011 Avaya Inc. All rights reserved. Avaya Management Today  Each Element does its own management, no consistency  Some common central management  Same data may be entered multiple times (limited shared data)  Various integrations with enterprise management With System Manager  Key management functions centralized with extensible services  Common console  Consistent UI  Single point of entry  Seamless navigation (SSO)  Consolidated logs and alarms  Systematic integration with enterprise management Application Voice Portal Element Manager Application Element Manager IQ Element Manager Application Element Manager Element Manager Administrator Element Element Manager Element Element Manager Element Element Manager Element Element Manager System Manager Managem ent ServicesEP Managem ent ServicesEP Managem ent ServicesEP Management Services EP Administrator Common Console 6
  7. 7. © 2011 Avaya Inc. All rights reserved. Solution Architecture Avaya Flare® Experience Avaya ACETM Application Application SBC TDM Trunks SIP Trunks PSTN G860 GatewayAvaya CS 1000 Avaya Aura® Communication Manager Avaya Aura® for Survivable Remote 3rd Party PBXs Avaya one-X® SIP endpoints SM SMSMSM SM AAM VP PSAAC SMGR HA Pair SMGR HA Pair Data Center 2 Data Center 1 7
  8. 8. © 2011 Avaya Inc. All rights reserved. System Manager Geo-Redundancy Overview 9
  9. 9. © 2011 Avaya Inc. All rights reserved. Geographic Redundancy (GR) Overview  Allows a pair of geographically redundant SMGRs in different locations (IP subnets) in a primary- secondary configuration Primary SMGR GR System Managers Secondary SMGR  The Secondary SMGR is normally in warm standby mode and becomes a fully functional SMGR upon activation by the administrator  While in standby mode, the secondary SMGR has restricted services  The secondary SMGR is synchronized to the primary SMGR on a per transaction batch basis while in warm standby mode – When activated to provide full SMGR services the Secondary will have the same information as the Primary SMGR – Exception being any transactions that did not replicate at the time of primary failure  Either the primary or secondary SMGR, or both, can be deployed in a High availability (HA) configuration. HA support is based on System Platform HA.  No WebLM License is Required for SMGR GR 10
  10. 10. © 2011 Avaya Inc. All rights reserved. General Geographic Redundancy (GR) Requirements and Recommendations  System Manager Server Environment – The two servers have the same version of software – All servers are identical (manufacture, model, platform resources) – The two servers can reach each other on the network – The clocks are synchronized between the servers (network time sync recommended)  Network Requirements and Recommendations – Recommend the use of DNS so name resolution is automatic. Else IP Address and Host name resolution needs to be done in the /etc/hosts file. – Ensure required ports are open to support the SMGR-GR Feature. Ports are identified in the SMGR 6.3 Port Matrix that will be posted on the Avaya Tech Support Website (Examples: Ports 57, 443, 636, 5432, 30868) – Recommended minimum data-pipe between SMGR Primary and Secondary is T1 (1.544Mbs) – Recommended to have less than 500 ms of network latency. No impacts on 6.3 SMGR GR in testing. Primary SMGR GR System Managers Secondary SMGR 11
  11. 11. © 2011 Avaya Inc. All rights reserved. SMGR Servers Supported Server SMGR 6.0 SMGR 6.1 SMGR 6.2 SMGR 6.3 S8510 with 8GB RAM √ √ × × S8800 SMGR with 12GB RAM √ √ √ √ HP ProLiant DL360 G7/G8 × √ √ √ Dell PowerEdge R610/620 × √ √ √ 12
  12. 12. © 2011 Avaya Inc. All rights reserved. SMGR Client Browsers Supported Client Browser SMGR 6.1 SMGR 6.2 SMGR 6.3 Microsoft Internet Explorer 7.x √ √ x Microsoft Internet Explorer 8.x √ √ √ Microsoft Internet Explorer 9.x x x √ Microsoft Internet Explorer 10.x x x √ Mozilla Firefox 3.5 √ √ x Mozilla Firefox 3.6 √ √ x Mozilla Firefox 8.0 x x √ Mozilla Firefox 9.0 x x √ Mozilla Firefox 10.0 x x √ 13
  13. 13. © 2011 Avaya Inc. All rights reserved. System Manager Capacity (SMGR 6.3 capacities will remain the same as SMGR 6.2) * There is a system limit of 2.5 million contacts. Capacities SMGR 6.2 SMGR 6.3 Number of administrator logins 250 250 Number of simultaneous logins 50 50 Number of endpoints (total) 250,000 250,000 Number of SIP endpoints 100,000 100,000 Number of end users 250,000 250,000 Number of contacts per user 250* 250* Number of public contacts 1,000 1,000 Number of personal contact lists, per user 1 1 Number of members in a personal contact list 250 250 Number of groups 300 300 Number of members in a group 400 400 Number of elements 25,000 25,000 Number of Communication Managers 500 500 Number of Branch Session Managers (counts against the total number of elements) 250 250 Number of B5800 Branch Gateways (counts against the total number of elements) 2,000 2,000 Number of roles 200 200 Number of roles, per user 20 20 Number of licensing clients 1,000 1,000 Number of trust management clients 2,500 2,500 14
  14. 14. © 2011 Avaya Inc. All rights reserved. System Manager ASD Offer Help Description System Manger (SMGR) Order Options : 1. Software & 1 Server - Standalone SMGR running one Avaya supplied server 2. Software & 2 Servers - Standalone SMGR in a High Availability (HA) pair configuration running on two Avaya supplied servers or a SMGR Geographic Redundancy (GR) pair configuration running on two Avaya supplied servers. Either configuration can be supported with the two servers, but not both. 3. Software & 4 Servers – Two SMGR pairs in a High Availability (HA) and a Geographic Redundancy (GR) configuration running on four Avaya supplied servers. For example: Two data centers, each with a SMGR HA Pair in a Geographic Redundant configuration across the two data centers. 4. Software Only – Option if customer already has an Avaya supplied server, that they will repurpose for SMGR utilization. The Avaya supplied server hardware used by the customer for the ‘software only’ option, must comply with the hardware specifications for the release of SMGR software being ordered. Only Avaya supplied servers are supported by SMGR. 5. None - Only one SMGR domain is required and supported per Enterprise. Selecting ‘None’ means that the System Manager application in a Standalone, HA or GR configuration already exists for this customer and no materials (either software or hardware) will be provided. [DEFAULT SETTING] Note: When ordering multiple servers for HA or GR, all servers must be identical 15
  15. 15. © 2011 Avaya Inc. All rights reserved. System Manager 6.3 Material Codes for New Installations and Upgrades SAP Code Description Avaya Aura System Manager 6.3 Software 216899 System Manager 6.3 License 231831 System Manager 6.3 Upgrade License Avaya Aura System Manager 6.3 Hardware 700501093 HP ProLiant DL360 G7 700504530 System Manager 6.3 DVD 700504627 System Platform 6.2.2 DVD 16
  16. 16. © 2011 Avaya Inc. All rights reserved. Key Session Points  SMGR 6.3 Delivers Increased Reliability through System Manager Geographic Redundancy  SMGR 6.3 can reduce operational expenses associated with User Management through Application based provisioning via Web Services  SMGR maintains concurrency with all new features introduced by Communications Manager  SMGR 6.3 can be ordered in a 1 Server, 2 Server or 4 Server configuration in ASD and EC.  SMGR 6.3 can run on existing hardware deployed in the field and supported on SMGR 6.2 (Dell R610, HP DL 360 G7 and S8800)  The Dell PowerEdge R610 will no longer be available as an alternative server for new System Manager Orders. HP ProLiant DL360 G7 is the only choice for new orders 17

×