Avaya Virtualization Provisioning Service

Transcription

Avaya Virtualization Provisioning Service Fundamentals
Release 1.0.2
NN4600-100
Issue 2.01
January 2013
© 2013 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of
such changes.
Licence types
Documentation disclaimer
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating instructions
and performance specifications that Avaya generally makes available
to users of its products. Documentation does not include marketing
materials. Avaya shall not be responsible for any modifications,
additions, or deletions to the original published version of
documentation unless such modifications, additions, or deletions were
performed by Avaya. End User agrees to indemnify and hold harmless
Avaya, Avaya's agents, servants and employees against all claims,
lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation,
to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked
websites referenced within this site or documentation provided by
Avaya. Avaya is not responsible for the accuracy of any information,
statement or content provided on these sites and does not necessarily
endorse the products, services, or information described or offered
within them. Avaya does not guarantee that these links will work all the
time and has no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on its hardware and Software
(“Product(s)”). Refer to your sales agreement to establish the terms of
the limited warranty. In addition, Avaya’s standard warranty language,
as well as information regarding support for this Product while under
warranty is available to Avaya customers and other parties through the
Avaya Support website: http://support.avaya.com. Please note that if
you acquired the Product(s) from an authorized Avaya reseller outside
of the United States and Canada, the warranty is provided to you by
said Avaya reseller and not by Avaya. “Software” means computer
programs in object code, provided by Avaya or an Avaya Channel
Partner, whether as stand-alone products or pre-installed on hardware
products, and any upgrades, updates, bug fixes, or modified versions.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO ARE
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN
AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE
USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY
INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
2
Avaya grants you a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License. The applicable
number of licenses and units of capacity for which the license is granted
will be one (1), unless a different number of licenses or units of capacity
is specified in the documentation or other materials available to you.
“Designated Processor” means a single stand-alone computing device.
“Server” means a Designated Processor that hosts a software
application to be accessed by multiple users.
Designated System(s) License (DS). End User may install and use
each copy of the Software only on a number of Designated Processors
up to the number indicated in the order. Avaya may require the
Designated Processor(s) to be identified in the order by type, serial
number, feature key, location or other specific designation, or to be
provided by End User to Avaya through electronic means established
by Avaya specifically for this purpose.
Heritage Nortel Software
“Heritage Nortel Software” means the software that was acquired by
Avaya as part of its purchase of the Nortel Enterprise Solutions
Business in December 2009. The Heritage Nortel Software currently
available for license from Avaya is the software contained within the list
of Heritage Nortel Products located at http://support.avaya.com/
LicenseInfo under the link “Heritage Nortel Products”. For Heritage
Nortel Software, Avaya grants Customer a license to use Heritage
Nortel Software provided hereunder solely to the extent of the
authorized activation or authorized usage level, solely for the purpose
specified in the Documentation, and solely as embedded in, for
execution on, or (in the event the applicable Documentation permits
installation on non-Avaya equipment) for communication with Avaya
equipment. Charges for Heritage Nortel Software may be based on
extent of activation or use authorized as specified in an order or invoice.
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, or hardware
provided by Avaya. All content on this site, the documentation and the
Product provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is
protected by copyright and other intellectual property laws including the
sui generis rights relating to the protection of databases. You may not
modify, copy, reproduce, republish, upload, post, transmit or distribute
in any way any content, in whole or in part, including any code and
software unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use without
the express written consent of Avaya can be a criminal, as well as a
civil offense under the applicable law.
Third Party Components
“Third Party Components” mean certain software programs or portions
thereof included in the Software that may contain software (including
open source software) distributed under third party agreements (“Third
Party Components”), which contain terms regarding the rights to use
certain portions of the Software (“Third Party Terms”). Information
regarding distributed Linux OS source code (for those Products that
have distributed Linux OS source code) and identifying the copyright
holders of the Third Party Components and the Third Party Terms that
apply is available in the Documentation or on Avaya’s website at: http://
support.avaya.com/Copyright. You agree to the Third Party Terms for
any such Third Party Components.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications system
by an unauthorized party (for example, a person who is not a corporate
employee, agent, subcontractor, or is not working on your company's
behalf). Be aware that there can be a risk of Toll Fraud associated with
Avaya Virtualization Provisioning Service - Fundamentals
Comments? infodev@avaya.com
January 2013
your system and that, if Toll Fraud occurs, it can result in substantial
additional charges for your telecommunications services.
Avaya Toll Fraud intervention
If you suspect that you are being victimized by Toll Fraud and you need
technical assistance or support, call Technical Service Center Toll
Fraud Intervention Hotline at +1-800-643-2353 for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support website: http://support.avaya.com. Suspected security
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: securityalerts@avaya.com.
Trademarks
Avaya Aura ® is a registered trademark of Avaya Inc.
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation and Product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third
parties. Users are not permitted to use such Marks without prior written
consent from Avaya or such third party which may own the Mark.
Nothing contained in this site, the Documentation and Product(s)
should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners,
and “Linux” is a registered trademark of Linus Torvalds.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website: http://support.avaya.com.
Contact Avaya Support
See the Avaya Support website: http://support.avaya.com for product
notices and articles, or to report a problem with your Avaya product.
For a list of support telephone numbers and contact addresses, go to
the Avaya Support website: http://support.avaya.com, scroll to the
bottom of the page, and select Contact Avaya Support.
January 2013
3
4
January 2013
Contents
Chapter 1: Introduction...................................................................................................... 7
Purpose..................................................................................................................................................... 7
Related resources..................................................................................................................................... 7
Documentation................................................................................................................................. 7
Training............................................................................................................................................. 8
Avaya Mentor videos........................................................................................................................ 8
Support...................................................................................................................................................... 8
Chapter 2: New in this release........................................................................................... 9
Other changes........................................................................................................................................... 9
Chapter 3: Overview........................................................................................................... 11
Introduction............................................................................................................................................... 11
VPS Navigation tree.................................................................................................................................. 12
Logon page............................................................................................................................................... 13
Dashboard................................................................................................................................................. 13
Status and tools................................................................................................................................ 19
One Hop Up Provisioning configuration.................................................................................................... 23
Network Profile service............................................................................................................................. 24
Rule binding service.................................................................................................................................. 25
Reporting................................................................................................................................................... 26
Audit logs.................................................................................................................................................. 26
License administration.............................................................................................................................. 26
vCenter event types.................................................................................................................................. 27
VPS backup and restore........................................................................................................................... 28
Chapter 4: VMware vCenter............................................................................................... 31
User access control................................................................................................................................... 31
Core Services............................................................................................................................................ 31
Distributed services................................................................................................................................... 32
vCenter plug-ins........................................................................................................................................ 32
vCenter services interfaces....................................................................................................................... 33
January 2013
5
6
January 2013
Chapter 1: Introduction
Purpose
This document provides an overview of the Avaya Virtualization Provisioning Service (VPS)
application and how to use it to manage your network.
Related resources
Documentation
See the following related documents.
Title
Purpose
Link
Avaya Virtualization
Provisioning Service –
Interface (NN46500-500)
Overview
http://support.avaya.com/
Fundamentals
(NN46500-100)
Fundamentals
Provisioning Service
Installation and
Commissioning
(NN46500-300)
Installation
Release Notes
(NN46500-400)
Reference
January 2013
7
Introduction
Training
Ongoing product training is available. For more information or to register, you can access the
Web site at http://avaya-learning.com/.
Avaya Mentor videos
Avaya Mentor is an Avaya-run channel on YouTube that includes technical content on how to
install, configure, and troubleshoot Avaya products.
Visit http://www.youtube.com/AvayaMentor and do one of the following:
• Enter a key word or key words in the Search channel to search for a specific product
or topic.
• Click the name of a playlist to scroll through the posted videos.
Support
Visit the Avaya Support website at http://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for notices,
release notes, downloads, user guides, and resolutions to issues. Use the Web service request
system to create a service request. Chat with live agents to get answers to questions. If an
issue requires additional expertise, agents can quickly connect you to a support team.
8
January 2013
Chapter 2: New in this release
The following sections detail what is new in Avaya Virtualization Provisioning Service – Fundamentals,
NN46500-100, Release 1.0.2.
Other changes
See the following section for information about changes that are not feature-related.
New Introduction chapter
The Introduction chapter replaces the Purpose of this document and Customer service
chapters.
January 2013
9
New in this release
10
January 2013
Chapter 3: Overview
This chapter provides an overview of the Avaya Virtualization Provisioning Service (VPS) application.
• Introduction on page 11
• VPS Navigation tree on page 12
• Logon page on page 13
• Dashboard on page 13
• Network Profile service on page 24
• Rule binding service on page 25
• Reporting on page 26
• Audit logs on page 26
• License administration on page 26
• vCenter event types on page 27
• VPS backup and restore on page 28
Introduction
VPS is an application that connects the vCenter server to the Avaya Configuration and
Orchestration Manager (COM) to help the data center administrator configure the network
changes that apply to the data center. Before the introduction of VPS, server administrators
viewed only the virtualized server environment while the network operators viewed only the
network topology. VPS bridges these two environments to deliver an end-to-end view of the
virtualized data center from servers, to virtual machines (VM), to networking devices.
Avaya VPS is a plug-in component to COM, and relies on COM for network device inventory,
topology and configuration. VPS provides a link mechanism to the VMware vCenter server to
transport data between vCenter and COM so you can view both the virtual server and network
environment. As a result, the server administrator and the network operator are able to work
more efficiently together, such as a more effective troubleshooting process, as well as the
ability to audit and track the creation, migration and deletion of virtual machines within the data
center. The connection strategy between VPS and VMware vCenter is part of the server
virtualization, a solution that allows you to run multiple virtual machines on a single physical
server. This consolidation of servers helps reduce power consumption and cooling costs.
VPS connects to the VMware vCenter server and gathers the virtualized server topology (VMs
and vSwitches). VPS identifies the physical connectivity of each of the ESX servers to the
January 2013
11
Overview
Avaya data switches and the data switch connectivity for the VMs. By stitching this information
to the network topology data that is automatically discovered through COM, you can use VPS
to view a complete end-to-end virtualized Data Center.
VPS is an important component of the Avaya Virtual Enterprise Network Architecture. The
Virtual Enterprise Network Architecture is an open, end-to-end virtualization architecture that
enables enterprises to build their own private cloud infrastructure. With a private cloud
infrastructure, you can improve work efficiency and reduce time-to-service. A unified fabric is
formed to establish a resilient infrastructure and maximize use of available bandwidth to
simplify provisioning.
You can use VPS to automate device provisioning by following VMs as they migrate through
the network. As you move VMs from one server to another, you add and delete the appropriate
port profiles (QoS, ACLs) from the edge devices that are connected to the physical servers. If
you require a change in the network configuration, the change occurs automatically in VPS,
or you can manually request the action before the VM change is implemented. This ensures
that the network is configured before you migrate VMs from one server to another, to ensure
proper connectivity for the VM traffic.
VPS Navigation tree
The VPS navigation tree is located on the left side of the Web page. The following items are
displayed:
• Dashboard— The main page of the VPS application. You can view applications, servers
and network devices across both physical and virtual environments.
• Network Profiles—Provides the data center and network administrator a configuration
interface to define a network profile. A network profile consists of a set of configurations
applied to a network switch on a VLAN-id interface basis.
• Rules—Conditions applied to the virtual machine event to determine which of these
network profiles apply to which virtual machine event.
• Reports—Displays current and historical data from the data center and the network
connectivity, as well as any configuration changes that occurred within the data center.
• Audit Log—Displays details about configuration changes made to devices, as well as
major operations, and details about the inventory audit and the port scan.
• Preferences—Displays details of VPS preferences in vCentre Server, Logging and
General categories.
The following image shows the VPS Navigation tree.
12
January 2013
Logon page
Logon page
You can launch the VPS application from the COM navigation pane. The initial password is
the password assigned when you install COM. If no activity occurs on the VPS web client for
30 minutes, the idle timer expires. If there is activity, the session timer expires after 120 minutes.
In both cases when you attempt to use the client again, you are redirected to the logon page
and must log on again.
Dashboard
The Dashboard is the default web page that appears when you launch the VPS application.
To launch VPS, you must log in to COM and select the VPS launch icon from the navigation
pane. The Dashboard provides you with a read-only view of different aspects of the virtualized
data center. You can view the details of the vCenter server connection to VPS such as the
server IP address and the status of the link. If the link is lost, a red circle icon appears—if you
hover your cursor over this icon, details show the cause of the lost connectivity, as well as
troubleshooting tips to fix the issue.
January 2013
13
Overview
The following image shows the VPS Dashboard.
The top portion of the Dashboard contains status information represented by four icons,
including an Operating Mode option. For VPS 1.0.1, you cannot edit this option, and therefore
remains in a Default mode. Use these status information icons to view and update status
information that exists or has changed within the network. The following image shows the
status information bar:
For more information about the purpose and importance of the status information bar, see
Status and tools on page 19.
The Dashboard contains the following panes:
• Server Information pane
• Monitor pane
• Applied Configurations pane
• Pending/Failed Actions pane
Filtering the VPS dashboard display
For release 1.0.1, filtering enhancements have been made to increase the usability of the
Server Information and Pending/Failed Action panes. By clicking the column heading, a pull
down menu appears, providing sorting and search options. In the example that follows, the
VM Name column is sorted using a string in the Filters-> Search box.
14
January 2013
Dashboard
Server Information pane
The Server Information pane displays an inventory of virtual machines that are managed within
VPS and the data switch connectivity for the virtualized server topology. If a virtual machine is
part of the managed devices, the details of this virtual machine are displayed in the Server
Information pane. The following figure shows the Server Information pane:
The bottom portion of the Server Information pane contains a pagination option as well as a
manual refresh icon. You can configure the pane to refresh automatically at a specific time
interval by clicking on the Refresh timer located in the upper right corner. Scrollbars are
available to navigate from left to right and from top to bottom. You can resize the pane by
clicking on the resize button located in the upper right corner. If you choose to maximize the
Server Information pane, all the other panes disappear from the Dashboard view.
For release 1.0.1, the following columns in the Server Information pane can be filtered:
• Data center name
• Server name
• server Location
• VM Name
• VM Application Server Type
• Switch (v/dv)
• Port Group name
• PG VLAN Id
• VM Adaptor
January 2013
15
Overview
• Uplink (v/dv)
• Physical Adaptor
• Switch IP
Filtering is not supported for the Slot/Port and SMLT columns.
Hide or Unhide Columns: For release 1.0.1 you can hide (or unhide) columns to better
manage the overall quantity of information in the Server Information pane. Use the pull-down
menu in the Server column to display (unhide) or hide one or more columns. In addition, you
can sort the Server column in ascending or descending order and filter the results.
Monitor pane
The Monitor pane allows you to view historical and current data about the virtual machine
events occurring in vCenter and the actions that happened with VPS in order to process each
virtual machine event. A virtual machine event can imply that you create, migrate, or delete a
virtual machine from the network. If you want to view events related to a specific virtual
machine, you can select the virtual machine in the Server Information pane and click on the
filter icon in the Monitor pane. The virtual machine is highlighted in yellow initially, and when
you click the filter symbol in the monitor pane all of the events related to that specific virtual
machine appear in the Monitor pane.
16
January 2013
Dashboard
Details in the Monitor pane provide information, including the type of event that is created as
well as the status, the rule, and network profile that is applied to the given event. The status
allows you to view if an event is successful or if errors occurred during the event process. If
an event failed or is in a partial success state, you can troubleshoot by clicking the failed or
partial success event and view the details in the Failed/Actions pane to resolve the issue. If
you click on the network profiles or rules attached to an event, the related network profiles or
rules table appears so you can view those details.
Similar to the Server Information pane, the Monitor pane displays a pagination option and a
manual refresh icon. A Refresh timer option is available if you want to configure an automatic
refresh at a given time interval. If you maximize the Monitor pane, the rest of the panes
disappear from the Dashboard.
Applied Configurations pane
An Applied Configurations pane displays all successful configuration changes that occurred
on the various devices. If you select an event from the Monitor pane that is in a success or
partial success state, the related information is displayed in the Applied Configurations pane.
If required, a message is displayed in the Message column. Other details include the switch
IP, the number of the associated slot/port, and the time at which the configuration occurred.
You can resize the pane vertically or horizontally. You can maximize the Applied Configurations
pane; however, only the Pending/Failed Actions pane disappears from the Dashboard. The
Server Information pane and the Monitor pane are still displayed.
The Applied configurations pane is shown in the following image.
January 2013
17
Overview
Pending/Failed Actions pane
The Pending/Failed Actions pane includes any triggers or events that did not apply. If an action
is in a pending or failed state, the reason is shown in the Message column. For example, if you
select an event that is failed in the Monitor pane, the related information appears in the
Pending/Failed Actions pane. You can review this information and if you want to mark the action
as complete, you can do so by clicking the red check mark in the Pending/Failed Actions
pane.
For release 1.0.1, the following columns appear in the Pending/Failed Action pane. Filtering
is not supported for these columns.
• Action
• Switch IP
• Parameter
• Status
• Message
• Timestamp
With the VPS Dashboard, you can customize the layout of the panes in different ways. You
can resize the panes either vertically or horizontally, and collapse some or all of the panes, or
enlarge one pane if you want to view only that given pane. If you want to define the number of
columns to display in each pane, right-click on a column heading in one of the panes and select
the columns you want to display in a given pane. An example is shown in the following figure:
18
January 2013
Dashboard
For more information about the different icons available in the Dashboard, see Status and
tools on page 19.
Status and tools
The status information and VPS tools are available in the Dashboard, within the Server
information pane. The icons on the left side contain the tools you use to commission the VPS
application and to view updated network changes. The icons on the right side are for the
available status information options. The status information and tools are identified by the
following icons.
Device Management
Network Discovery.
vCenter Connector link is active.
vCenter server link is lost. You can hover over this icon to view the status of the
vCenter server connection and troubleshooting tips.
Refresh timer icon.
Device management
The Device Management icon is located at the top bar just above Server Information pane in
the dashboard. You can use this icon to view managed devices in COM, and manage or
unmanage devices in VPS. Clicking the Device Management icon displays device information
as shown in the following image:
January 2013
19
Overview
The Manage Devices window displays the details of the devices.
• You can manage or unmanage edge and core devices.
• If stackable device, you can manage or unmanage stack units in the Stack Units tab.
• You can specify uplinks for the edge device (which is connected to ESX/ESXi server) in
the Neighbor tab. If the selected uplink is an MLT/SMLT, the UI automatically selects other
links of the MLT/SMLT.
• By selecting an uplink for the edge device, VPS automatically manages the core devices
(BEB) which are connected to the edge device.
• You can validate links between the edge and the core device (BEB).
• You can save the settings.
• You can manage-All and unmanage All.
• You can view only managed devices.
• You can filter by device IP or type.
Note:
• After re-discovery of devices in COM, you may need to re-select the devices in the
device management.
• The device management will disable the selection of neighbor links if the remote device
(BEB) is not SPBm supported.
• Clicking on Refresh button will reload the entire device information. However, any unsaved data will be lost.
20
January 2013
Dashboard
Note:
Moving a device from the managed to unmanaged state causes the VPS application to
recapture all the related inventories and topology of the device. Avaya recommends that
you minimize such state changes.
Viewing connected devices
To view the devices which are linked to the ESX Server or a VM, a filter is provided in the
Device Inventory Manager. In the Filter drop-down, a filtering option can be used to show only
the devices linked to the VM(s). The search can be further refined by entering a search string
in the Filter box. In the example, the filter option Connected to VM (name) is used.
Network discovery
For release 1.0.1, inventory audit and port scans are performed together and the results
displayed in a common window.
Inventory audit
The Inventory audit information ensures that VPS captures important information, such as all
data centers, clusters, ESX servers, virtual machines, and related Vswitches/Dvswitches,
PortGroups. Each time you start the VPS application, an inventory audit is automatically
performed to capture this information and keep VPS updated. vCenter server details and
credentials are found in the VPS Preferences vCenter Server tab.
Port Scan
After the Network Discovery is complete, you can view the entire network connectivity of the
virtual machines in the data center. A port scan is automatically performed every 24 hours to
ensure that any notifications or changes that dropped are scanned. You can configure this
interval by accessing the VPS preferences file and changing the automatic port scan
schedule.
The following image shows the Network Discovery information window:
January 2013
21
Overview
vCenter Connectivity status information
This type of information contains the status of the connection of the vCenter server to VPS.
After you configure the VPS preferences file, launch VPS to confirm the vCenter is linked
properly to VPS. If the vCenter is properly connected, the status is confirmed by a green circle
icon. If the connection is lost, a red circle icon is displayed. Hovering the cursor over this icon
shows the details of the connection. If the connection is lost, a description of the status is
displayed along with troubleshooting tips.
Refresh timer
You can select the option to refresh the Server Information pane and the Monitor pane at
regular timed intervals by clicking the Refresh timer icon. The Refresh timer is Off by default.
However, you can click on the icon if you want the panes to automatically refresh at every
following interval:
22
January 2013
One Hop Up Provisioning configuration
• 30 seconds
• one minute
• five minutes
• 10 minutes
Note:
An Operating Mode option is also situated in the right corner; however, for VPS 1.0.1, you
cannot edit this option and therefore the Operating Mode is always in Default mode.
One Hop Up Provisioning configuration
Many data networks are virtualized using the Shortest Path Bridging (SPB) technology. VPS
will now help the operator in virtualizing the end-to-end network.
• Configuration of the VLAN on the edge devices of the SPB Cloud.
• Configuration of the VLAN, Traffic Profile/ACL/Bandwidth on the Access ports connected
to the virtual world (ESX/ESXi)
The VLAN/Traffic profile on the devices is applied using the pre-configured network profile auto
triggered by rules.
You can virtualize the entire end-to-end network using VPS to configure the VLAN connectivity
using pre-defined Port Profile or Rules at the edge device connected to ESX, and the
distribution or the core device which forms the edge of the SPB Cloud.
VPS device management is enhanced to support the One Hop Up Provisioning (OHP) feature.
The OHP feature provisions the shortest path bridging MAC (SPBM) core network devices
automatically in addition to provisioning the edge devices. This feature facilitates the
management of edge and core devices, providing flexibility in response to virtual machine (VM)
life cycle changes.
In order to provision a network device using VPS, the device must be managed in VPS. A
network switch that is connected directly to an ESX server is considered an edge device. By
selecting the uplinks from an edge device, the VPS operator can specify the core devices to
be managed . The core device forms the edge of the SPB cloud and is known as the backbone
edge bridge (BEB).
One hop up provisioning requirements
The following requirements must be completed to configure the one hop up feature. Once
completed, the VPS is ready to configure OHP.
• COM Discovery is complete
• Preferences (port dissociation for edge and core is configured correctly)
• Using the device management interface:
- Select the Edge devices and units if stacked to be managed.
January 2013
23
Overview
- Select the uplinks to core (BEBs) devices using the Neighbor tab.
- Validate the link between the edge and the core device (BEB).
- Save the settings and Confirm to trigger a port scan.
Note:
• After the re-discovery of devices in COM, you may need to re-select the devices in the
device management.
• The device management will disable the selection of neighbor links if the remote device
(BEB) is not SPBm supported.
If there’s a VM event, the corresponding events can be seen in the monitor.
Device details are provided in the Pending/Failed Actions and Applied Configurations
panes.
For configuration examples of the OHP feature, see the Avaya VPS Installation and
Commissioning Guide (NN46500-300).
Network Profile service
To support the VM traffic, you have to have configured the data switch. VPS provides you with
a template called network profile that you complete with the information of what needs to
happen on the data switch. You can define a set of configurations and save it so that when a
change happens on the device, you can apply the network profile to the data switch. The set
of configurations that you can define are the VLAN and port configurations that apply on a
switch port. A network profile provides a holistic view of the VLAN, bandwidth, metering, access
control and QoS configuration, and ensures that the trunk is correctly configured to support
the VM traffic. You can apply a network profile to different devices such as 45xx, 55xx, and
86xx.
You can use the network profile service to maintain the Vlan mapping table. A Vlan mapping
table is data that contains a mapping of Vid, VLAN ID and ISID. Network administrators use
the VLAN IDs which is a list of VLAN IDs on the network. The ISID is a number used in the
SPBM networks and is uniquely assigned to a customer.
VLAN configuration
VLAN configuration is mandatory in a network profile, and ensures that the correct VLAN
information is available for the traffic of the virtual machines as you activate or migrate these
virtual machines in the data center. The VLAN configuration information includes the STG
mode, STG id, VLAN ID you configure, VLAN name, High Priority and the QoS level.
Note:
VPS 1.0.1 only supports provisioning of VLANs by Port. All other fields, except VLAN type
which is always by Port, that are required in a VLAN creation have default values.
24
January 2013
Rule binding service
Traffic Profile/ACL configuration
The Traffic Profile/ACL configuration is optional, and ensures that the correct network
characteristics, such as Access Control Lists (ACLs), filters, bandwidth and QOS parameters
are properly configured on the network ports that are used for the virtual machine traffic. VPS
supports port level traffic profile configuration. Port level traffic profile allows you to configure
a device port to allow or drop traffic that meets the specified criteria. The stackable devices,
such as ERS 45xx, 55xx, and 56xx, use the QoS classifiers and sets as means of configuring
traffic profile. The modular devices, such as ERS 86xx and ERS 88xx use the access control
template/list/entry. A network profile provides separate sections for defining traffic profiles for
stackable and modular devices. If a network profile is defined without the Traffic Profile/ACL
configuration, only the VLAN configuration is applied on the network device.
VLAN mapping
If you use an Avaya SPBM, there is an additional mapping of ISID that you need to configure
for each network Profile. With the VLAN-ISID-VID mapping, you decide the customer VLAN to
which a service is associated with for SPBM networks. You can define the ISID value that is
associated with each Customer Vlan.
Note:
Avaya recommends that the VLAN ID in the VLAN-ISID-VID mapping table be the VLAN ID
that is referenced in the Network Profile, and that the VID be the VLAN ID of the associated
Port Groups in the Data Center.
For VPS 1.0.1, Avaya also recommends that the VID be equal to the VLAN ID.
Rule binding service
Rules are conditions to which network profiles are applied. Network profiles are applied to
switch ports based on preconfigured rules. As a result the rule binding service is dependent
on the network profile service. VPS provides a rule infrastructure to determine which network
profiles are applied to which virtual machine. You can define rules based on the location of the
ESX server, the application server type of the virtual machine, and the VLAN ID of the port
groups to which a virtual machine is connected.
A rule may have simple or complex criteria, and is executed for a virtual machine event only if
the event matches a single rule. You can configure rules to occur automatically or manually.
Automatic rules imply that if an exact rule match is found for a virtual machine event, then the
configuration defined in the related network profile is applied on the device. Manual rules imply
that, if a rule is matched for a virtual machine event, the configuration defined in the associated
network profile is not automatically applied to the network devices and you can apply the rule
manually. For more information about network profiles, see Network Profile service on
page 24.
January 2013
25
Overview
Reporting
You can generate reports to view the current and historical data of the end-to-end data center
and network connectivity, as well as the configurations performed on the network devices in
response to the changes in the data center. You can generate the following types of reports:
• VM Topology Report—Shows the connectivity of the VMs, the ESX server that the VMs
are hosted on, the Vswitch/ Dvswitch to which the VMs are connected, as well as the
network devices providing the link for these VMs.
• Applied Configurations Report—Shows the configurations applied to the network devices.
You can generate this type of report to include only a specific time period.
• Pending/Failed Actions Report—Shows the network device actions that are pending or
failed. Details about the result of the actions are displayed. You can generate this type of
report to include only a specific time period.
After you generate a report, you can print or export the given report in different formats, such
as Excel, Postscript, PDF, Word and PowerPoint. For more information about printing and
exporting reports, see Avaya Virtualization Provisioning Service—Interface (NN46500–500).
Audit logs
Use the audit logs to view the operations you performed within VPS. Audit logs display the
virtual machine events processed and the configurations that were made on the network
devices. The audit logs detail changes that occurred to events, when these changes happened,
and the status of the event processing.
You can configure the audit log preferences by accessing the Preferences section in VPS. In
the Preferences section, you can set boundaries in regards to file size and the level at which
debug logs and audit logs appear. For more information, see the Avaya Virtualization
Provisioning Service—Interface (NN46500–500).
License administration
During the VPS installation process, you can only add one license file. If you want to add more
than one license file to the VPS application, you can use the License Administration available
in COM after the VPS installation is complete. With the License Administration, you can add
and export licenses, or generate license reports. You can export a license and keep it for future
reference. For example, you can refer to the license if you need to reinstall the application.
Furthermore, the license report provides details about the licenses applied to the applications
in the tabular format, and you can save it for further use.
26
January 2013
vCenter event types
Licenses are available at the Avaya Licensing Portal. You can obtain a trial license that is valid
for 60 days through the Avaya Professional Services. A VPS license is installed as a base
license or in increments. With a base license, you can manage 20 switches, whereas each
increment supports 50 switches. You can apply a maximum of four increments to a VPS base
license, which supports a maximum of 220 nodes. If you install a VPS license on a stackable
device, each unit of the stack is considered as a separate license unit in VPS.
Note:
A VPS license is only valid if you have a valid COM license.
For more information about VPS licensing, see Avaya Virtualization Provisioning Service —
Installation and Commissioning (NN46500–300).
vCenter event types
The vCenter server processes the following types of events, to which VPS listens and
processes.
The following table describes these events.
Table 1: Virtual Machine Event
VMEvent
Description
VmBeingCreatedEvent
Virtual machine is being created.
VmBeingDeployedEvent
Virtual machine is being deployed from a
template.
VmBeingMigratedEvent
Virtual machine is being migrated.
VmBeingHotMigrated
Virtual machine is being hot-migrated.
VmBeingRelocatedEvent
Virtual machine is being relocated.
VmRelocatedEvent
Virtual machine is successfully relocated.
VmCloneEvent
Base event for all clone operations.
VmCloneFailedEvent
The virtual machine clone operation failed.
VmCreatedEvent
Virtual machine is successfully created.
VmDeployedEvent
Virtual machine deployment operation is
complete.
VmDeployFailedEvent
The deployment from a template failed.
VmDisconnectedEvent
Virtual machine is disconnected.
VmFailedMigrateEvent
The virtual machine migration failed.
January 2013
27
Overview
VMEvent
Description
VmMigratedEvent
Virtual machine migration.
VmReconfiguredEvent
Virtual machine is reconfigured.
VmRelocateFailedEvent
The virtual machine relocation failed.
VmRemovedEvent
Virtual machine is removed from the vCenter
management.
VmRenamedEvent
Virtual machine is renamed.
VmUpgradeCompleteEvent
Upgrade operation is completed.
VmUpgradingEvent
Virtual hardware on a virtual machine is
being upgraded.
VPS backup and restore
The VPS database table is the repository of the data that VPS updates during backup or
recovery. The backup operation makes a backup of the VPS system along with COM and UCM
to create restoration files in the event that the system state becomes corrupted. In release
1.0.1, while using scripts for Windows and Linux, VPS automatically updates the database
tables during a combined backup of COM and VPS. You are then able to restore the system
back to the checkpoint created by the backup file.
Note:
Avaya recommends that you backup COM along with the VPS application.
VPS database tables
The VPS application has both configured user/system and system discovered data. The
following is the list of information that the system or users configures:
• Network profile
• Rules
• VPS managed device
• VPS historical event information
The VPS properties file is found in the following area:
${JBOSS_HOME}/server/default/conf/vps/VpsPreferences.properties
The following table contains a list of database tables that corresponds to the VPS during
backup:
28
January 2013
VPS backup and restore
Table 2: Database tables
Database table
eem_vps_applied_vm_profile_switch
eem_vps_networkprofile
eem_vps_clusterinfo
eem_vps_physicaladaptor
eem_vps_com_device_inventory_view
eem_vps_portgroup
eem_vps_datacenterinfo
eem_vps_portgrp_vndsport
eem_vps_device
eem_vps_preferences
eem_vps_device_unit
eem_vps_preferences_element
eem_vps_deviceinventoryview
eem_vps_rule
eem_vps_deviceinventoryview_withNoSwitch
eem_vps_serverinfo
eem_vps_deviceinventoryview_withSwitch
eem_vps_serverinfo_vnds
eem_vps_div_servervm
eem_vps_switch_portgroup_view
eem_vps_div_servervm_noswitch
eem_vps_vminfo
eem_vps_div_servervm_noswitch_data
eem_vps_vnd_switch
eem_vps_div_serverswitch
eem_vps_vnds_uplink
eem_vps_monitor
eem_vps_vnic
eem_vps_monitor_action
eem_vps_uplink_physical_adaptor
eem_vps_monitor_appliedconfig
eem_vps_vlanisidmap
eem_vps_monitor_event
January 2013
29
Overview
30
January 2013
Chapter 4: VMware vCenter
VPS connects the VMware vCenter to the Configuration and Orchestration Manager (COM). VMware
vCenter is part of the VMware vSphere, a system that manages collections of infrastructure such as
storage and networking of a data center. VMware vCenter Server provides important data center services
such as access control, performance monitoring and configuration. For more information about VMware
vShere, visit http://www.vmware.com/support.
Within a server, you can use the vCenter Server to control the data center, and configure policies to enable
management of assignments and resources of virtual machines. After proper configuration, if the network
fails, servers are not impacted. Furthermore, VMware vCenter provides the list of MAC addresses through
VPS; however, information pertaining to the network switch and the slot or port is not delivered through
the VMware vCenter.
vCenter gathers resources from ESX/ESXi hosts and sends them to the system administrator. The system
administrator can then provision these resources to virtual machines. The following are the vCenter
components:
• user access control
• core services
• distributed services
• plug-ins
• various interfaces
User access control
The User Access Control allows you to create and manage different levels of access to vCenter
Server for different classes of users.
Core Services
Core Services are comprised of a management service for virtual machines. The following
table details the Core Services components:
January 2013
31
VMware vCenter
Component
Description
Virtual machine provisioning
Provisions virtual machines and their
resources
Host and VM Configuration
Virtual machine and host configuration
Resources and virtual machine inventory
management
Organizes virtual machines and resources in
the virtual environment and facilitates their
management.
Statistics and logging
Logs and reports on the performance and
resource of virtual machines, hosts, and
clusters.
Alarms and event Management
Tracks and warns of potential resource
overuse or event conditions.
Task scheduler
Schedule actions to occur at a given time.
Consolidation
Analyzes the capacity and use of the data
center's physical resources.
vApp
A vApp is similar to a virtual machine – it is
multi-tiered, but is a separate entity. With
vApps, you can perform operations, such as
cloning, rebooting and shutting down.
Distributed services
The vCenter Server manages and configures the Distributed services. Distributed services are
solutions that enable wider functionality within VMware vSphere. These solutions include
VMware DRS, VMware HA, and VMware vMotion.
vCenter plug-ins
Plug-ins are applications that add features and functionality to the vCenter Server. vCenter
Server plug-ins include VMware vCenter Converter and VMware Update Manager.
The VMware vCenter Converter allows you to convert physical machines and virtual to ESX/
ESXi virtual machines. You can import converted systems into any location in the vCenter
Server inventory. The VMware Update Manager allows you to enforce security standards
across ESX/ESXi hosts and managed virtual machines.
32
January 2013
vCenter services interfaces
vCenter services interfaces
vCenter Server contains the following interfaces:
• ESX management — Connects to vCenter agent
• VMware vSphere API — Connects to VMware management clients and third-party
solutions.
• Database interface — Connects to Oracle, Microsoft SQL Server, or IBM DB2 to store
information, such as virtual machine configurations, host configurations, resources and
virtual machine inventory, performance statistics, events, alarms, user permissions, and
roles.
• Active Directory interface — Obtains user access control information.
January 2013
33
VMware vCenter
34
January 2013

Avaya Virtualization Provisioning Service

Transcription

Similar documents

Avaya B179 Conference Phone

Avaya Aura® Contact Center helps specialist clothing brand prepare

Avaya Communication Server 1000E

Avaya Virtualization Provisioning Service

April 2009 Product Catalog

A Sample Configuration of Avaya IP Office IP Trunks

PDC and VPS Application Note

report of the broadcast of the total lunar eclipse 2014 - Sky

luxury series vinyl windows

the PDF

CWA/Avaya Contract