30-07-15

VCP6-CMA Study Guide : Section 5: Allocate and Manage vRealize Automation Resources

VCP6-CMA-sm-logo_120_108

As I predicted in my last blog post, VMware have announced that starting at VMworld 2015 in August, it will be possible to schedule VCP6 exams such as VCP-DCV, VCP-DTM and VCP-CMA. Hopefully this will mean that my beta score for my CMA exam is not too far away now, it would be nice to get a full house of VCPs!

Anyway, also as per my last blog post, I’m publishing section 5 of the study guide, which is as far as I got. Unless I fail the beta and have to resit, I don’t envisage me having the time to go back and complete the remaining sections. Hopefully it will be of some use to people planning on having a go at the CMA, any feedback is welcome via Twitter as always.

Objective 5.1: Create and Manage Fabric Groups

Adding and configuring vSphere Endpoints

  • Creating an endpoint creates access to compute resources on a virtualised platform
  • The process involves creating a credential set, defining a cloud endpoint and mapping resources for consumption
  • Log in to the vRealize Automation console as an IaaS administrator.
  • Select Infrastructure > Endpoints > Credentials.
  • Click New Credentials.
  • Enter a name in the Name text box. (Optional) Enter a description in the Description text box.
  • Type the username in the User name text box.
    • Must be in domain\username format, for example mycompany\admin. The credentials must have permission to modify custom attributes
  • Type the password in the Password text boxes.
  • Click the Save icon (green tick)
  • Select Infrastructure > Endpoints > Endpoints.
  • Select New Endpoint > Virtual > vSphere.
  • Enter a name in the Name text box.
    • This must match the endpoint name provided to the vSphere proxy agent during installation or data collection fails.
  • (Optional) Enter a description in the Description text box.
  • Enter the URL for the vCenter Server instance in the Address text box.
  • Select the previously defined Credentials for the endpoint.
    • If your system administrator configured the vSphere proxy agent to use integrated credentials, you can select the Integrated credentials.
  • Only select Specify manager for network and security platform if you plan to integrate with an existing NSX or vCNS instance

Adding and configuring vRealize Automation endpoints

  • I’m assuming here that this refers to Orchestrator!
  • Same process as for vSphere endpoint, except you choose to create a vCO credential using administrator@vsphere.local (assuming using the vCO engine as part of the vRO appliance)
  • Create a new Orchestration endpoint for vCenter Orchestrator
  • Give it a meaningful, type in the address (typically https://vcoserver:8281/vco)
  • Select the appropriate vCO credential you just created
  • Add a custom property VMware.VCenterOrchestrator.Priority and set it to 1. This is mandatory.

Map compute resources to endpoints

  • A compute resource is an object that represents a host, host cluster, or pool in a virtualization platform, a virtual datacenter, or an Amazon region on which machines can be provisioned.
  • An IaaS administrator can add compute resources to or remove compute resources from a fabric group.
  • A compute resource can belong to more than one fabric group, including groups that different fabric administrators manage.
  • After a compute resource is added to a fabric group, a fabric administrator can create reservations on it for specific business groups. Users in those business groups can then be entitled to provision machines on that compute resource
  • Compute resources such as storage and networking can be assigned from endpoints to Business Groups
  • Reservations are used to carve up resource from compute resources to apply to a Business Group

Assign correct permissions to manage Fabric Groups

  • An IaaS administrator can organize virtualization compute resources and cloud endpoints into fabric groups by type and intent. One or more fabric administrators manage the resources in each fabric group.
  • Fabric administrators are responsible for creating reservations on the compute resources in their groups to allocate fabric to specific business groups. Fabric groups are created in a specific tenant, but their resources can be made available to users who belong to business groups in all tenants.
  • Fabric administrators are created and assigned when creating the Fabric Group
  • A Fabric Administrator can do the following:-
    • Manage build profiles
    • Manage compute resources
    • Manage cost profiles
    • Manage network profiles
    • Manage Amazon EBS volumes and key pairs
    • Manage machine prefixes
    • Manage property dictionary
    • Manage reservations and reservation policies

Perform compute resource data collection

  • vRealize Automation collects data from both infrastructure source endpoints and their compute resources.
  • Data collection occurs at regular intervals. Each type of data collection has a default interval that you can override or modify.
  • IaaS administrators can manually initiate data collection for infrastructure source endpoints and fabric administrators can manually initiate data collection for compute resources.
  • To perform a manual data collection, Log in to the vRealize Automation console as an IaaS administrator.
  • Select Infrastructure > Endpoints > Endpoints
  • Point to the endpoint for which you want to run data collection and click Data Collection.
  • Click Start.
  • (Optional) Click Refresh to receive an updated message about the status of the data collection you initiated.
  • Click Cancel to return to the Endpoints page
  • There are seven different types of data collection:-
    • Infrastructure Source Endpoint Data Collection (Updates information about virtualization hosts, templates, and ISO images for virtualization environments. Updates virtual datacenters and templates for vCloud Director. Updates regions and machines provisioned on them for Amazon. Updates installed memory and CPU count for physical management interfaces.)
    • Inventory Data Collection (Updates the record of the virtual machines whose resource use is tied to a specific compute resource, including detailed information about the networks, storage, and virtual machines. This record also includes information about unmanaged virtual machines, which are machines provisioned outside of vRealize Automation.)
    • State Data Collection (Updates the record of the power state of each machine discovered through inventory data collection. State data collection also records missing machines that vRealize Automation manages but cannot be detected on the virtualization compute resource or cloud endpoint.)
    • Performance Data Collection (vSphere compute resources only) (Updates the record of the average CPU, storage, memory, and network usage for each virtual machine discovered through inventory data collection)
    • vCNS inventory data collection (vSphere compute resources only) (Updates the record of network and security data related to vCloud Networking and Security and NSX, particularly information about security groups and load balancing, for each machine following inventory data collection)
    • WMI data collection (Windows compute resources only) (Updates the record of the management data for each Windows machine. A WMI agent must be installed, typically on the Manager Service host, and enabled to collect data from Windows machines.)
    • Cost data collection (compute resources managed by vRealize Business Standard Edition only) (Updates the CPU, memory, and storage costs for each compute resource managed by vRealize Business Standard Edition. The costs of catalog items that can be provisioned by using the compute resources are updated.)

Perform resource monitoring tasks

Resource Monitoring Scenario Privileges Required Location
Monitor the amount of physical storage and memory on your compute resources that is currently being consumed and determine what amount remains free. You can also monitor the number of reserved and allocated machines provisioned on each compute resource Fabric Administrator (monitor resource usage on compute resources in your fabric group) Infrastructure > Compute Resources > Compute Resources
Monitor physical machines that are reserved for use but not yet provisioned. Fabric Administrator Infrastructure > Machines > Reserved Machines
Monitor machines that are currently provisioned and under vRealize Automation management Fabric Administrator Infrastructure > Machines > Managed Machines
Monitor the amount of storage, memory, and machine quota of your reservation that is currently allocated and determine the capacity that remains available to the reservation Fabric Administrator (monitor resource usage for reservations on your compute resources and physical machines) Infrastructure > Reservations > Reservations
Monitor the amount of storage, memory, and the machine quota that your business groups are currently consuming and determine the capacity that remains on reserve for them. Tenant Administrator (monitor resource usage for all groups in your tenant)Business Group Manager (monitor resource usage for groups that you manage) Infrastructure > Groups > Business Groups

Objective 5.2: Create and Manage Reservations

Create and Manage Reservations

  • Before members of a business group can request machines, fabric administrators must allocate resources to them by creating a reservation.
  • Each business group must have at least one reservation for its members to provision machines of that type.
  • Log in to the vRealize Automation console as a fabric administrator
  • A tenant administrator must create at least one business group
  • Select Infrastructure > Reservations > Reservations
  • Select New Reservation > Virtual and select the type of reservation you are creating
  • (Optional) Select an existing reservation from the Copy from existing reservation drop-down menu.
  • Data from the reservation you chose appears, and you can make changes as required for your new reservation
  • Select a compute resource on which to provision machines from the Compute resource drop-down menu.
  • Only templates located on the cluster you select are available for cloning with this reservation.
  • The reservation name appears in the Name text box.
  • Enter a name in the Name text box
  • Select a tenant from the Tenant drop-down menu.
  • Select a business group from the Business group drop-down menu.
    • Only users in this business group can provision machines by using this reservation
  • (Optional) Select a reservation policy from the Reservation policy drop-down menu.
    • This option requires additional configuration. You must create a reservation policy
  • (Optional) Type a number in the Machine quota text box to set the maximum number of machines that can be provisioned on this reservation.
    • Only machines that are powered on are counted towards the quota. Leave blank to make the reservation unlimited.
  • Type a number in the Priority text box to set the priority for the reservation.
    • The priority is used when a business group has more than one reservation. A reservation with priority 1 is used for provisioning over a reservation with priority 2.
  • (Optional) Deselect the Enable this reservation check box if you do not want this reservation active.
  • (Optional) Add any custom properties

Specify Reservation Information

  • A reservation is a share of provisioning resources allocated by the fabric administrator from a fabric group and reserved for use by a particular business group
  • A virtual reservation is a share of the memory, CPU, networking, and storage resources of one compute resource allocated to a particular business group.
  • Each reservation is for one business group. A business group can have multiple reservations on a single compute resource. A business group can also have multiple reservations on compute resources of different types.
  • A physical reservation is a set of physical machines reserved for and available to a particular business group for provisioning.

Create and Manage a Cloud Reservation

  • A cloud reservation provides access to the provisioning services of a cloud service account for a particular business group.
  • A group can have multiple reservations on one endpoint or reservations on multiple endpoints.
  • A reservation may also define policies, priorities, and quotas that determine machine placement.
  • The reservation must be of the same platform type as the blueprint from which the machine was requested
  • The reservation must be enabled
  • The reservation must have capacity remaining in its machine quota or have an unlimited quota.
    • The allocated machine quota includes only machines that are powered on. For example, if a reservation has a quota of 50, and 40 machines have been provisioned but only 20 of them are powered on, the reservation’s quota is 40 percent allocated, not 80 percent
  • The reservation must have the security groups specified in the machine request.
  • The reservation must be associated with a region that has the machine image specified in the blueprint.
  • For Amazon machines, the request specifies an availability zone and whether the machine is to be provisioned a subnet in a Virtual Private Cloud (VPC) or a in a non-VPC location. The reservation must match the network type (VPC or non-VPC).
  • If the cloud provider supports network selection and the blueprint has specific network settings, the reservation must have the same networks.
    • If the blueprint or reservation specifies a network profile for static IP address assignment, an IP address must be available to assign to the new machine.
  • If the blueprint specifies a reservation policy, the reservation must belong to that reservation policy.
    • Reservation policies are a way to guarantee that the selected reservation satisfies any additional requirements for provisioning machines from a specific blueprint. For example, if a blueprint uses a specific machine image, you can use reservation policies to limit provisioning to reservations associated with the regions that have the required image.
  • If no reservation is available that meets all of the selection criteria, provisioning fails.

22-07-15

VCP6-CMA Study Guide – Section 4: Configure and Administer Tenants and Business Groups

VCP6-CMA-sm-logo_120_108

I started to publish a draft study guide a while back for the VCP-CMA beta exam, and never really finished it before I sat the exam itself. I have two more sections completed (out of ten, poor!) so I’m putting them out there for folks to reference. The exam itself is still in the beta process and has not been released to schedule, but I’m guessing they’ll be trying to get it ready for VMworld next month.

I wrote a previous post about my beta exam experience, which you can read here but it may well not reflect the finished article (i.e the released exam). Anyway, on with Section 4 of the study guide.

Objective 4.1: Create and Manage Business Groups

Identify Business Group roles and their specific privilege levels

  • A business group associates a set of services and resources to a set of users, often corresponding to a line of business, department, or other organizational unit.
  • Business groups are managed on the Infrastructure tab but are used throughout the service catalog. Entitlements in the catalog are based on business groups. To request catalog items, a user must belong to at least one business group.
  • A business group can have access to catalog items specific to that group and to catalog items that are shared between business groups in the same tenant. In IaaS, each business group has one or more reservations that determine on which compute resources the machines that this group requested can be provisioned.
  • A business group must have at least one business group manager, who monitors the resource use for the group and often is an approver for catalog requests. In IaaS, group managers also create and manage machine blueprints for the groups they manage. Business groups can also contain support users, who can request and manage machines on behalf of other group members.
  • Business group managers can also submit requests on behalf of their users. A user can be a member of more than one business group, and can have different roles in different groups.

Identify and Manage Business Group Manager role

  • Manages one or more business groups.
  • Typically a line manager or project manager.
  • Business group managers manage catalog items and entitlements for their groups in the service catalog.
  • They can request and manage items on behalf of users in their groups. They are also service architects in Infrastructure as a Service.
  • Responsibilities include:-
    • Create and publish business group–specific machine blueprints from IaaS.
    • Manage business group–specific catalog items and entitlements.
    • Monitor resource usage in a business group

Identify and Manage Support User role

  • A role in a business group.
  • Support users can request and manage catalog items on behalf of other members of their groups.
  • This role is typically an executive administrator or department administrator
  • Responsibilities:-
    • Request and manage items on behalf of other users within their business groups.

Identify and Manage User role

  • Presumably this means the “Business User” role, which is an end user, or consumer of catalog items from the self service portal
  • Responsibilities:-
    • Request and manage services.

Assign Active Directory Users and Groups to Business Group Roles

  • Done in the Infrastructure -> Groups -> Business Groups tab
  • Under the User Role field, enter search string and click the search icon
  • Select AD user or group you want to add and then click OK

Create and manage Machine Prefixes

  • Machine prefixes are added to VMs provisioned from within vRA but can be overridden if need be by Business Group managers
  • Managed within the Business Group by clicking the ellipsis to the right of the field for default machine prefix
  • Either select existing machine prefix or create a new one by entering the machine prefix, number of digits and next number (eg. vm-001)
  • Machine prefixes are shared across all tenants and must be created by a fabric administrator
  • Can also be created and managed under Infrastructure -> Blueprints -> Machine Prefixes

Identify and Configure Custom Properties

  • You can add custom properties to a blueprint to specify attributes of a machine or to override default specifications.
  • You can also add build profiles to a blueprint as a convenience for specifying multiple custom properties
  • A machine owner, business group manager or fabric administrator can add, change, or delete custom properties for a provisioned machine.
  • Custom properties can be added to Business Groups by editing the Business Group, scrolling to the bottom and clicking “New Property”. Add a name, value and whether or not you want to encrypt it (usually only used for passwords) and whether or not to prompt the user for a value (machine name, for example).
  • Custom properties can be used for various tasks including for example placing all VMs from a certain Business Group into a vCenter folder for management
  • Custom properties can also be added to Blueprints
  • Custom properties can be marked as required values when creating a blueprint
  • The Windows guest agent records property values on the provisioned machine in the %SystemDrive %\VRMGuestAgent\site\workitem.xml file.
  • The Linux guest agent records property values on the provisioned machine in the /usr/share/gugent/site/workitem.xml file

Objective 4.2: Create and Manage Tenants

Configure branding for the vRealize Automation console

  • System administrators control the default branding for tenants. Tenant administrators can use the default or reconfigure branding for each tenant
  • Log in to the vRealize Automation console as a system administrator or tenant administrator
  • Select Administration > Branding.
  • Clear the Use default check box.
  • Create a banner.
  • Click Choose File to upload a logo image. Follow the prompts to finish creating the banner.
  • Click Next.
  • Type the copyright information in the Copyright notice text box and press Enter to preview your selection.
  • (Optional) Type the URL to your privacy policy in the Privacy policy link text box and press Enter to preview your selection.
  • (Optional) Type the URL to your contact page in the Contact link text box and press Enter to preview your selection.
  • Click Update. The console is updated with your changes.

Add and configure Tenant-specific inbound and outbound email notifications

  • Tenant administrators can add an outbound email server to send notifications for completing work items, such as approvals.
  • Each tenant can have only one outbound email server. If your system administrator has already configured a global outbound email server, you can override this at tenant level
  • Select Administration > Notifications > Email Servers
  • Click the Add icon
  • Select Email – Outbound. Fill out the form as needed, choose to Test Connection if required
  • Select Administration > Notifications > Email Servers
  • Click the Add icon
  • Select Email – Inbound, fill out the form as needed.
  • Click OK.

Override and Revert to system default email servers

  • To override these settings at tenant level, Select Administration > Notifications > Email Servers.
  • Select the Outbound/Inbound email server.
  • Click Override Global, fill out the form as needed
  • If the system administrator has configured a system default outbound/inbound email server, tenant administrators can override this global setting.

Identify and add Identity Stores in vRealize Automation

  • vRA uses the concept of Identity Stores to perform authentication of users and leverage existing users and groups to assign to roles.
  • If the Identity Appliance is AD joined, the default tenant can use native AD mode (i.e not LDAP lookup)
  • Any subsequent tenants must use LDAP
  • Click Administration -> Identity Stores
  • Click Add Identity Store to add a new identity store
    • Choose a Name
    • Select the type (OpenLDAP or Active Directory)
    • Enter the URL for the identity store. For example, ldap://10.141.64.166:389 (636 for LDAPS).
    • Enter the domain name of the identity store
    • Enter an optional domain alias (shortens the login from the vRA appliance page)
    • Enter the login user Distinguished Name. For example, cn=demoadmin,ou=demo,dc=dev,dc=mycompany,dc=com
    • Enter the password for the identity store login user.
    • Enter the group search base Distinguished Name. For example, ou=demo,dc=dev,dc=mycompany,dc=com.
    • Enter the user search base Distinguished Name.
  • Click Test Connection.
  • Click Add.

Create and assign user roles to an Identity Store Group

  • Log in to the vRealize Automation console as a tenant administrator
  • Select Administration > Users & Groups > Identity Store Users & Groups.
  • Enter a user or group name in the Search box and press Enter. (Do not use an at sign (@), backslash (\), or slash (/) in a name).
    • You can optimize your search by typing the entire user or group name in the form user@domain.
  • Click the name of the user or group to whom you want to assign roles.
  • Select one or more roles from the Add Roles to this User list.
    • The Authorities Granted by Selected Roles list indicates the specific authorities you are granting.
  • (Optional) Click Next to view more information about the user or group.
  • Click Update.
  • Users who are currently logged in to the vRealize Automation console must log out and log back into the vRealize Automation console before they can navigate to the pages to which they have been granted access.

12-06-15

VCP6-CMA Beta Exam Experience

VCP6-CMA-sm-logo_120_108

I just got back from sitting the beta VCP6-CMA exam so I thought I would jot down a few thoughts in case it helps others out. Firstly, it was my first VCP exam for around 2.5 years, so I’d actually forgotten what kind of level the questions were pitched at! I’m used to VCAP level now, which usually means labbing the shit out of the blueprint so you can get to the exam and be able to hit the ground running with the practical and/or design canvas questions.

Although I’ve only really had dirty hands on vRealize Automation (I’m going to pronounce it as “Vera” I think in the future!) for about 6 weeks. You’d think that not really long enough to go ahead and sit a VCP, but even though the product scope is large, I’ve found it relatively easy to get up to speed with how it works. Enough to sit the exam anyway, and as it was at a special price until the end of the beta today (£36), I thought why not? As a partner we have big plans around the cloud space, so having the VCP can only help.

As for the exam itself, as usual it’s pretty faithful to the exam blueprint. There are 110 questions to be completed in 120 minutes, I believe non-native English speakers get a bit longer. I completed all the questions within about an hour. The exam itself was form based, multiple choice and exhibit based questions, as per most VCP exams I’ve ever sat. With 110 questions, VMware are able to very broadly go across all features of the product (including vRealize Business and App Director) and test you to a reasonable degree. Obviously not as testing as VCAP, but it’s not the same level.

I found myself falling back on my old exam technique of going with my gut response and when I wasn’t sure of an answer, I’d rule out the ones I knew were incorrect and then play the odds with the ones that were left.

There were only a couple of spelling mistakes and a couple of questions I didn’t think were worded too well, but the exam room was quite noisy which didn’t help my concentration, so it may be I was a bit distracted. I didn’t flag any answers for review and I didn’t add comments to any questions. It seems a pretty fair test of product knowledge and a good exam to pass.

Apparently I won’t know if I’ve passed for about 8-10 weeks as the beta exam process runs it’s course (hopefully it may be shorter as today is the last day), so I’ll have to forget about it for now and move on to the VCP-NV which I sit on the 30th. My gut feeling was I’d done enough to pass (around 3/4 correct by my estimation), so we’ll see when the time comes.

A totally different experience to a VCAP and not as intense, but I enjoyed it none the less. Fingers crossed now and onto VCP-NV!

 

11-06-15

VCP6-CMA Study Guide – Section 3: Create and Administer Cloud Networking

VCP6-CMA-sm-logo_120_108

Objective 3.1: Explain NSX Integration with vRealize Automation

Manage network services from within vRealize Automation

  • Network profiles are used to map networks in vRA to port groups in vSphere (for example)
  • Create a network profile from the vRealize Appliance, logged in as a fabric administrator
  • Go to Infrastructure -> Reservations -> Network profiles
  • Click New Network Profile and select the appropriate type (External, NAT, private, routed – all are created at time of provisioning except External which is a pre-existing vSphere port group)
  • Give the profile a name and configure the subnet mask (and optionally, DNS details and gateway)
  • Click IP Ranges tab and add a range of IP addresses for that profile to consume by using New Network Range button
  • Fill out a name and a start and end IP address for the range, click OK
  • A CSV file may also be used to define a large range of IP addresses

Configure NSX Integration

  • Prerequisites include an existing NSX Manager instance associated to a vCenter Server and a vSphere endpoint instance
  • Also credentials for the NSX Manager (Infrastructure -> Credentials -> New Credentials) and NSX plug-in into Orchestrator
  • Login to the vRealize Appliance as an IaaS administrator
  • Edit the vSphere endpoint in Infrastructure -> Endpoints
  • Select “Specify manager for network and security platform”
  • Add the IP address or DNS name of the NSX Manager appliance
  • Select the NSX Manager credential set previously added
  • Run a data collection from the Infrastructure -> Compute Resources section in vRealize Appliance (ensuring the network discovery is enabled)
  • Before you consume NSX services, you must run the Enable Security Policy Support for Overlapping Subnets Workflow in vRealize Orchestrator, using the NSX Manager endpoint previously used as the input parameter for the workflow.
  • After you run this workflow, the Distributed Firewall rules defined in the security policy are applied only on the vNICs of the security group members to which this security policy is applied

Configure IaaS for Network Integration

  • Configuration requires steps in this order:-
    • Configure the Orchestrator endpoint in IaaS
    • Create a vSphere instance integrated with NSX (see above)
    • Run the Enable Security Policy Support for Overlapping Subnets Workflow (see above)
    • Create a network profile (see above)
    • Add or amend an existing reservation, click on the Network tab
    • Select an external network in the Network Paths list
    • Select the transport zone, security group and routed gateway

Objective 3.2: Configure and Manage vRealize Automation Networking

Identify the available NSX for vSphere Edge network services

    • NSX Edge Services include:-
      • Dynamic Routing (Provides the necessary forwarding information between layer 2 broadcast domains, thereby allowing you to decrease layer 2 broadcast domains and improve network efficiency and scale. NSX extends this intelligence to where the workloads reside for doing East-West routing. This allows more direct virtual machine to virtual machine communication without the costly or timely need to extend hops. At the same time, NSX also provides North-South connectivity, thereby enabling tenants to access public networks.)
      • Firewall (Supported rules include IP 5-tuple configuration with IP and port ranges for stateful inspection for all protocols)
      • Network Address Translation (Separate controls for Source and Destination IP addresses, as well as port translation)
      • DHCP (Configuration of IP pools, gateways, DNS servers, and search domains)
      • Site-to-Site Virtual Private Network (VPN) (Uses standardized IPsec protocol settings to interoperate with all major VPN vendors)
      • L2 VPN (Provides the ability to stretch your L2 network)
      • SSL VPN-Plus (SSL VPN-Plus enables remote users to connect securely to private networks behind a NSX Edge gateway)
      • Load Balancing (Simple and dynamically configurable virtual IP addresses and server groups)
      • High Availability (High availability ensures an active NSX Edge on the network in case the primary NSX Edge virtual machine is unavailable)
      • Multi-Interface Edge

Configure DHCP/NAT/VPN/Load Balancer

  • Configuration of NSX is done from the vSphere Web Client
  • Uses a plugin under the Networking & Security button
  • Go to NSX Edges and create an Edge Gateway for the services
  • Provide CLI username and password for appliance
  • Enable SSH and HA if required
  • Pick datacenter, appliance size (compact, large, X-Large, Quad-large)
  • Choose cluster and datastore for Edge appliance deployment
  • Configure NIC and which VDS you want to attach the appliance to
  • Configure IP addresses and subnet, MTU size (1600 for VXLAN, remember)
  • Services are configured by double clicking on the Edge appliance and going to the Manage tab

Sub-allocate IP Pools

  • IP Pools are created and edited under the NSX Edge Gateway object in the vSphere Web Client. Look under the Manage tab, then click Pools and the add button. Configure the pool as appropriate

Add static IP addresses

  • Static IP addresses are created under the Edge Gateway Manage tab, the DHCP and bindings. Click the add button and add VM or MAC binding as needed.
  • Interface, VM Name, VM vNIC interface, Host name and IP address are required fields.

Configure syslog

  • The syslog server is configured by logging into the NSX Manager appliance management interface, Manage Appliance Settings button and fill out the Syslog server under General settings.
  • IP address, port number and protocol (TCP/UDP) are required