Beruflich Dokumente
Kultur Dokumente
Version 9.0
IBM®
Product overview
The IBM® Security Access Manager virtual appliance helps organizations secure and manage user access and protect
applications against fraudulent and unauthorized access.
5 Step 5: (Option 1) Install the firmware in a virtual machine environment other than the XenServer
hypervisor
1. Create a new virtual machine with the following minimum specifications:
v Disk space requirement: 100 GB
v Memory requirement: 4 GB
v Virtual network devices: 1 (Maximum 8)
v Virtual DVD/CD-ROM drive
2. Configure the virtual machine to start from the supplied .iso file.
3. Start the virtual machine. The firmware installer starts automatically.
4. (Previously partitioned virtual disk only) Select a language from the list of available languages.
5. (Previously partitioned virtual disk only) The system prompts you to install the firmware. Enter yes.
6. (Previously partitioned virtual disk only) When the firmware installation is complete, the system prompts you to
restart. The virtual machine restarts to the appliance console unconfigured login prompt.
6 Step 6: (Option 2) Install the appliance on a XenServer hypervisor by using XenCenter
1. In the XenCenter console, expand the XenCenter icon on the left.
2. Right-click the attached hypervisor and select Import. In the Import Source window, click Browse and select the VHD
image to be imported. Click Open and then Next.
3. In the VM Definition window, specify the name, number of CPUs, and memory of the virtual machine and click Next.
In most scenarios, assign the virtual machine at least one processor and 2 GB of memory. These settings can be
adjusted after the virtual machine starts running.
4. In the Location window, select the destination hypervisor from the drop-down list on the right and click Next.
5. In the Storage window, select Place imported virtual disks onto specified target SRs and click Next.
6. In the Networking window, select the network for the first management interface and click Next.
7. In the OS Fixup Settings window, select Don't use Operating System Fixup and click Next.
8. In the Transfer VM Settings window, specify the settings for your network environment and click Next. If DHCP is not
available in the network, you must specify a valid IP address, subnet, and gateway.
9. In the Finish window, click Finish. The import operation might by lengthy. You can click the Logs tab to check the
progress of the import.
10. When the import is complete, run the following commands on the XenServer console to set the image to
paravirtualized mode:
xe vm-list (to get the uuid for the VM)
xe vm-param-set uuid=<vm uuid> HVM-boot-policy=""
xe vm-param-set uuid=<vm uuid> PV-bootloader=pygrub
xe vm-disk-list (to get the uuid for the disk - VBD entry)
xe vbd-param-set uuid=<disk uuid> bootable=true
11. Start the imported virtual machine. You must configure at least one network interface for the appliance to start.
Sometimes the XenCenter must be restarted before the new virtual appliance can be started correctly.
Note: To install the appliance using XenAPI or xe command line, see the IBM Knowledge Center at
http://www.ibm.com/support/knowledgecenter/SSPREK/welcome.
More information
See the IBM Knowledge Center at http://www.ibm.com/support/knowledgecenter/SSPREK/welcome
?
IBM Security Access Manager Virtual Appliance 9.0 Licensed Materials - Property of IBM. © Copyright IBM Corp. 2015. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the web at “Copyright and trademark information” (www.ibm.com/legal/copytrade.shtml).
Printed in Ireland