Unable to start VMs in new Hosts – An emulator required to run this VM failed to start

Unable to start VM with vGPOU assigned on HOST with NVIDIA Card.

Getting error:

vm-start failed: “An emulator required to run this VM failed to start”


Internal LOG:

Dec 6 09:10:13 localhost vgpu-2[11384]: demu_initialize: PLUGIN CONFIG: /usr/share/nvidia/vgx/grid_p40-1b.conf,gpu-pci-id=0000:d8:00.0Dec 6 09:10:13 localhost vgpu-2[11384]: notice: pluginconfig: /usr/share/nvidia/vgx/grid_p40-1b.conf,gpu-pci-id=0000:d8:00.0Dec 6 09:10:13 localhost vgpu-2[11384]: notice: Loading Plugin0: libnvidia-vgpuDec 6 09:10:13 localhost vgpu-2[11384]: notice: Successfully update the env symbols!Dec 6 09:10:13 localhost vgpu-2[11384]: error: vmiop_log: Initialization: vGPU not supported with ECC Enabled.#012 error 0Dec 6 09:10:13 localhost vgpu-2[11384]: error: vmiop_log: init_device_instance failed for inst 0 with error 1Dec 6 09:10:13 localhost vgpu-2[11384]: error: vmiop_log: Initialization: init_device_instance failed error 1Dec 6 09:10:13 localhost vgpu-2[11384]: error: vmiop_log: display_init failed for inst: 0Dec 6 09:10:13 localhost vgpu-2[11384]: error: vmiope_process_configuration: plugin registration errorDec 6 09:10:13 localhost vgpu-2[11384]: demu_initialize: vmiope_process_configuration failed with 1Dec 6 09:10:13 localhost vgpu-2[11384]: __set_error: Demu is returing error vmiopDec 6 09:10:13 localhost vgpu-2[11384]: demu_teardown: <VMIOP_VGA_INITIALIZEDDec 6 09:10:13 localhost vgpu-2[11384]: demu_deregister_memory_space: a0000 - bffff

Related:

USB Boot not working for E5491 with symentec Ghost 11.5 for multicast

I need a solution

USB Boot not working for E5491 with symentec Ghost 11.5

I did create an USB Boot for E5491 but I am getting following error
when i tried to boot with it Error:
Unable to locate the PCI LAN Adapter/ The following are possible causes:
1. The system may not support the PCI bus.
2. The PCI adapter may not be properly installed in a slot.
3. Some of the PCI adapter resources in configuration space may be invalid. Check for possible errors listed above and run adapter diagnostics.
Failure: Driver did not load, NDIS environment invalid.

I did download the driver for MS-DOS from intel ® Ethernet Connection I219-LM , PRODOS.exe 23.5.2 I made following changes on to the USB boot but still i am getting the same error any help very much appreciated as we have an bulk order for E5491
Autoexec.bat
@echo off
prompt $p$g
netnetbind.com
MOUSE.COM
cd ghost
echo Loading..
GHOST.EXE -fni

Also remember to add the driver name to the protocol.inf, so it looks like this:

[protman]
drivername=PROTMAN$

[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66

[nic]
drivername = e1000$

0

Related:

Advice on Symantec DLP Solution

I need a solution

Good day all,

We have recently deployed the Symantec DLP solution at our Organization.

I have a few questions that the community will hopefully be able to help me with, I have downloaded the Symantic_DLP_15.1_Admin guide, to assist with the process. Unfortunately it is huge and I am struggling to find the steps or points within the documentation in helping me configure the following sections, I need the DLP solution to detect and block emails in the following senarios :

  • Detect and block PCI, PAN and SAD data.
  • Detect and block Personal Information data (PI) such as ID numbers, Social Security Numbers and so forth.
  • Detect and block source code.
  • Detect and block encrypted attachements

Another question I have, does the admin guide have explain how to deploy this solution securely?

If anyone can point out where I need to be looking within the admin guide above I would be highly appreciative as I have been searching and I am battling to find an decent answer that explains the above mentioned. Even if I get the page numbers on where to look that will also do.

Thanks in advance

0

Related:

Action Response Rule-Prevent and allow

I need a solution

Hello. I’m new to DLP but so far i have done by my self the deploy of all the application.

I want to know if there is any response rule to activate when a user try to send a doc into USB and he/she trigger the PCI-DSS policy for example.

We as admin are notified and if we think that the word doc is ok to be copied to allow that ?

For example with Trend Micro we block mail trying to go out of the company based on some rules. If the think that is false positive we can allow that.

Thank You

0

Related:

RSA Archer PCI Management

EMC logo


What are the basics of PCI-DSS Compliance?

The Payment Card Industry Data Security Standard (PCI-DSS) defines a consolidated set of security best practices endorsed by major card brands, which are designed to reduce fraud risk associated with credit card processing. Organizations that fail to comply may lose their ability to accept credit card payments, which could greatly impact their ability to conduct business. However, with the continually increasing velocity and sophistication of new threats, maintaining an effective PCI- DSS compliance program has become an increasingly costly business requirement as well – and those costs can be substantial.

 

The PCI-DSS is considered one of the more prescriptive and technical compliance mandates that companies must typically deal with. This can be both good and bad. In contrast, many higher level government mandates like federal regulations are often written in broader terms that can be difficult to interpret into actionable specifics like precise internal control definitions. The more a company has to guess at what’s expected, the greater the chance of guessing wrong and either undercompensating (raising the inherent risk of running afoul of the regulation); or overcompensating, which can increase the internal costs and burden of compliance unnecessarily.

 

The benefit of PCI’s more prescriptive language is better clarity in terms of understanding what’s expected, how it will be audited, and specific reporting requirements. However, the other side of the coin with PCI is the extensive technical breadth and depth of its coverage. Encryption, network segmentation, multi-factor authentication, and external vulnerability scanning are a few areas where companies often struggle, either because of technical limitations or significant additional technology investments needed.

 

Why is a program approach to PCI Compliance so important?

Companies able to gain efficiencies by optimizing their operational compliance efforts will be more successful at reducing compliance costs and gaps. Consolidating organizational compliance initiatives into a single comprehensive view is the most effective way to identify and eliminate duplicate efforts and reduce overall compliance risk. The technical nature of PCI can often force companies to undertake process improvements, technical infrastructure overhauls, and even facility construction projects simultaneously. A streamlined program approach helps to keep things organized and drive consistent, successful outcomes.

 

RSA Archer PCI Management

RSA Archer Controls Assurance Program and RSA Archer Controls Monitoring Program provide a solid foundation for managing any organizational compliance initiative. However, PCI’s unique characteristics and pervasive global reach offer an opportunity to take things several steps further. RSA Archer PCI Management is designed to do just that, by enabling organizations to streamline the compliance process, simplify stakeholder participation, and reduce overall compliance effort and cost.

 

RSA Archer PCI Management guides merchants through identifying and defining cardholder data flows and environments, engaging the proper stakeholders, completing self-assessment questionnaires (SAQs), testing and gathering evidence for all required controls, and managing the gap remediation process.

 

Key features include:

  • Easy-to-use project workflows to manage CDE (cardholder data environment) scoping and multiple, ongoing compliance assessment projects.
  • Structured content libraries linking each discreet control requirement in the PCI-DSS to an extensive control testing repository ensuring full coverage across internal and external assessment activities.
  • Persona-driven dashboards and questionnaires that simplify the attestation and evidence gathering process and provide clear insight into compliance activity status.
  • Aggregated issues management functionality for tracking findings and gaps and managing the remediation process.
  • One-click reporting templates to assemble all required deliverables into a properly formatted Report on Compliance (ROC) for easy review and submission.

 

Customers can also enjoy seamless integration with other RSA Archer use cases designed to tackle all aspects of Integrated Risk Management in their unique environments. Organizational leaders with optimized programs in place have a distinct advantage for exploring the opportunity landscape, by enabling them to identify with confidence the business risks that are worth taking.

 

For more information, please visit RSA.com and review the Datasheet.


Update your feed preferences


   

   


   


   

submit to reddit
   

Related:

Ghost 11.5 Unable to start TCP/IP

I need a solution

There are two same LAN IC WGI210AT on our motherboard.LAN1 is on Chipset H110 PCIE port 9,LAN2 PCIE port10. LAN1 can run PXE ghost normally.But during runing PXE ghost by LAN2,there is an error which is Application Error 19913, show as the attachment. During the process of linking server, the MAC address is LAN2’s address. But after started PC dos,the Current MAC Address is LAN1’s.It is confusing. When we disabled LAN1, LAN2 can run PXE ghost normally. What is wrong about this issue? How can I configure PXE ghost?

0

Related:

How to troubleshoot common SR-IOV related issues

Common error scenario #1: A VM fails to have SR-IOV network assigned.

  1. Please make sure there are enough available VFs to be assigned to the VM by checking “remaining-capacity”. This can be confirmed from XenCenter or xe CLI.
  • XenCenter

User-added image

  • xe CLI
  1. )Get the UUID of the SR-IOV Network:

xe network-sriov-list

  1. )Check remaining-capacity of the network

xe network-sriov-param-list uuid=<SR-IOV_Network_UUID>

Sample output

User-added image

  1. In case of NIC legacy driver is updated in Dom0, please double check whether following parameters are changed in /etc/modprobe.d/<driver_name>.conf configuration file. If any of the value is incorrect, please manually change the value based on your requirement again.

param name

default max_vfs

sysfs interface support


Common error scenario #2: When trying to assign SR-IOV Network to a VM from XenCenter, there is no SR-IOV Network option in “Add Virtual Interface” Wizard for the VM.

If the VM is newly created in XenServer 7.6, please check if the VM has <restriction field=”allow-network-sriov” value=”1″/> tagged in recommendations by xe vm-param-list uuid=<vm_uuid> command.

If there is no such tag, that means the OS of the VM does not support SR-IOV feature, you should not assign SR-IOV network to that VM.

Output sample for a guest OS that supports SR-IOV Network:

recommendations ( RO): <restrictions><restriction field=”memory-static-max” max=”1649267441664″/><restriction field=”vcpus-max” max=”32″/><restriction field=”has-vendor-device” value=”false”/><restriction field=”allow-gpu-passthrough” value=”1″/><restriction field=”allow-vgpu” value=”1″/><restriction field=”allow-network-sriov” value=”1″/><restriction max=”255″ property=”number-of-vbds”/><restriction max=”7″ property=”number-of-vifs”/></restrictions>

Please note, if a VM is exported from a previous XenServer version, even the guest OS supports SR-IOV feature, it has no above restriction field. You will need to assign SR-IOV Network to that VM by xe CLI.


Common error scenario #3: SR-IOV Network is assigned to a VM by xe CLI, while inside the VM, the SR-IOV Network is not visible.

In this case, please make sure

  1. The guest OS supports SR-IOV. Please refer to scenario 2 to check if the OS supports SR-IOV feature.
  2. The NIC driver has been installed on the guest already.

Example for Windows Server OS:

User-added image

Example for Linux Server:

ethtool -i eth1

driver: ixgbevf

version: 3.2.2-k-rh7.4

firmware-version:

expansion-rom-version:

bus-info: 0000:00:05.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: no

supports-register-dump: yes

supports-priv-flags: no

  1. If the VM was running when you were assigning SR-IOV Network to it. For Windows Server OS, SR-IOV Network will not be visible until the VM has been shut down and rebooted.

Please understand, you can assign SR-IOV Network to any VM by xe CLI. So please be sure that you are assigning it to a guest that supports this feature. Even SR-IOV Network may work on a non-supported guest, Citrix does NOT support this use case if any problem occurs.


Common error scenario #4: VM fails to start after SR-IOV Network has been assigned.

In this, you need to check kern.log and xensource.log with keyword “sriov” to find more information.

Reference:

For your reference, here are messages are outputted for working scenario.

xensource.log output when VF is attached and active for the VM.
broadman xenopsd-xc: [debug|localhost.localdomain|16 |Async.VM.start R:34ed6712dab6|xenops] Device.NetSriovVf.add domid=90 devid=2 pci=0000:03:10.1 vlan=none mac=fa:75:91:01:17:41 carrier=true rate=none other_config=[] extra_private_keys=[net-sriov-vf-id=2; xenopsd-backend=classic] extra_xenserver_keys=[static-ip-setting/mac=fa:75:91:01:17:41; static-ip-setting/error-code=0; static-ip-setting/error-msg=; static-ip-setting/enabled=0; static-ip-setting/enabled6=0; mac=fa:75:91:01:17:41]



broadman xenopsd-xc: [debug|localhost.localdomain|16 |Async.VM.start R:34ed6712dab6|xenops] adding device B0[/local/domain/0/xenserver/backend/net-sriov-vf/90/2] F90[/local/domain/90/xenserver/device/net-sriov-vf/2] H[/xapi/8f93c150-0fe5-a053-8748-47a22d1ef023/hotplug/90/net-sriov-vf/2]

xensource.log output which indicates SR-IOV is not active on the VM yet.

broadman xenopsd-xc: [debug|localhost.localdomain|4361 |org.xen.xapi.xenops.classic events D:de40a7d84a1f|xenops] VM = 8f93c150-0fe5-a053-8748-47a22d1ef023; domid = 34; Device is not active: kind = net-sriov-vf; id = 2; active devices = [ ]

Common error scenario #5:In SR-IOV network enabled usage case, a host may not be able to join an existing pool.

If you have enabled SR-IOV network on a host, and want to have that host join an existing pool, it will fail. Only when the not having SR-IOV configured, it can join an existing pool. Please refer to the below table for more details.
pool (Network SR-IOV enabled)
pool(Network SR-IOV not configured)
host (Network SR-IOV enabled) Joining to existing pool will be blocked since the new host can be considered as a not clean host. Joining to existing pool will be blocked since the new host can be considered as a not clean host.
host (Network SR-IOV not configured) The host can join the pool, but with following notice:

1. The SR-IOV network of the newly joined host will be enabled AUTOMATICALLY if and only if the NIC on host and the NIC on pool master have same NIC type and same NIC position; this is checked by XAPI;

2. If PCI type of same NIC position for pool master and newly joined host are different, then SR-IOV network will not be enabled for that NIC in the joined host; even the host can join the pool.

3. Different types of SR-IOV physical PIFs can NOT be put into one network;

4. In the pool, user can enable a SR-IOV network for the newly joined host by XE CLI if the SR-IOV PIF has same type with the pool master’s PIF in that network, even they are in different positions.
The host can join the existing pool.

Common error scenario #6: A VM is configured as both SR-IOV VF and vGPU assigned, but when the VM is started, it has no SR-IOV VF assigned.

If a VM is configured as both SR-IOV VF and vGPU assigned, the selection of host to start the VM will respect vGPU’s host selection only. After host selection based on vGPU resource, XAPI only asserts on the selected host based on SR-IOV network remaining capability. This is because that vGPU is a more expensive and rarer resource than SR-IOV VF.

Related:

Re: DataDomain with IBMI Direct-Connection

Hardware

Switched connectivity supported by the host operating system. Please verify with Compatibility Guide.

Power 8 hardware: Direct or FC Switch connect

  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 8 drives on each port)
  • EN0A/577F- 16Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required
  • EN0B/577F- 16Gb PCIe2 “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required

Power 7 hardware: Direct or FC Switch connect

  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0 :(best practice is 4 drives on each port)
  • 5749/576B – 4Gb PCI-x “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0:(best practice is 8 drives on each port)
  • 5273/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0::(best practice is 8 drives on each port)
  • EN0A/577F- 16Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required
  • EN0B/577F- 16Gb PCIe2 “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port)

Power 6 hardware: Direct or FC Switch connect with Smart IOA

  • 5761/280D – 4Gb PCI-x HBA (best practice is 4 drives on each port)
  • 5704/5704 – 2Gb PCI-x HBA IBM i v5.4.5, v6.1.1:(best practice is 2 drives on each port) IOP 2844 & FC Switch required
  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5749/576B – 4Gb PCI-x “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 8 drives on each port)
  • 5273/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 8 drives on each port)

Power 5 hardware: NO Direct, FC switch required

  • 5761/280D – 4Gb PCI-x HBA (best practice is 4 drives on each port) IOP 2844 & FC Switch required
  • 5704/5704 – 2Gb PCI-x HBA IBM i v5.4.5, v6.1.0, v6.1.1:(best practice is 4 drives on each port) IOP 2844 & FC Switch required

The 5704 and 5761 IOAs support a maximum of 16 devices per card (IOP 2844 & FC Switch required to use on DD)

The 5774, 5749, 5735, 5273, EN0A & EN0B Smart-IOA’s (2 ports) support a maximum of 64 devices per port, and 128 per card, with a limit of 32 devices per tape library device

Software

The IBM i License for the VTL will need to be installed before starting any VTL connections.

It is recommended to set the Auto Configure System Value QAUTOCFG (Auto configure Devices) to 1 during the configuration of new tape devices. To change the system value from the command line enter the command CHGSYSVAL SYSVAL(QAUTOCFG) VALUE(‘1’). This value can be changed back after the configuration of the tape library and devices.

Tape Management Applications

Data Domain VTL for IBM i supports the following tape management applications along with the Native CL commands:

  1. IBM Backup and Recovery Media Services (BRMS) @ i5/OS, IBM i v5.4.5, v6.1, v6.1.1, v7.1, v7.2 and v7.3.0.
    1. Since BRMS is a licensed program product, the operating system release level will determine the BRMS release level, which is consistent with the OS level.
  2. Help Systems Robot/SAVE v12.13; only on i5/OS v7.2.0, v7.1.0 & v6.1.1

Help Systems Robot/SAVE v11.32; only on i5/OS v5r4m5, IBM i 6.1.0 & v6.1.1.

  1. LXI Enterprise Storage (MMS) v5.4.3; only on i5/OS v7.1.0 & v6.1.1, v6.1.0.

PTFs

To display individual PTFs level with a MF prefix type the follow command DSPPTF and press Enter. Look for “Release of base option”, this is the level of the hardware.

To display individual PTFs with a SI prefix type the follow command DSPPTF and press Enter TWICE. Look for “Release of base option”, this is the level of the software.

IBM i PTF (Software Patches) Levels

Table 129 IBM i PTF (SW patches) Levels

V5R4M5

V6.1.0

V6.1.1

V7.1.0

V7.2.0

Cumulative

12094

14197

14197

14283

14276

Hiper

203

186

186

125

18

DB2 for IBM i

33

32

32

32

3

Backup Recovery solution

57

52

52

39

5

Tech Refresh Level

9

1

Note

EMC supports legacy PTF levels up to what is listed in the table. Customers do not have to

be at the levels shown in the table to receive support.

V5R4M5

V5R4M5 requires PCI-x based HBAs with a separate IOP for Fiber Tape connectivity. The IOP based 5704 and 5761 are the only HBAs that are supported on V5R4M5 of i/OS.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended lowest PTF levels are:

SF99540 Cumulative PTF Package: Level 10117 (C0117540)

SF99539 Group HIPER: Level 129

SF99504 DB2 for IBM i: Level 26

SF99186 Backup Recovery Solutions: Level 32

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.



v6.1.0

V6R1M0 has been qualified to use the 5704 and 5761 IOAs on Power5 hardware, while Power6 hardware allows the use of either 5704/5761 or the “SmartIOA” cards, 5749 / 5774 / 5735. EMC highly recommends the use of the SmartIOA to get the best possible throughput when running Tape jobs. A SmartIOA also gives a larger number of VTL tape emulations for more processing resources. The latest Cumulative package should have all PTFs required for Old IOAs but if the SmartIOA is used the following will apply.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended Lowest PTF levels are:

Cumulative: SF99610

Release:

V6R1M0

Abstract:

Cumulative PTF package C1256610

Level:

11256

Oct 13, 2011

Group: SF99609

Release:

V6R1M0

Abstract:

Group Hiper

Level:

00110

Dec 6, 2011

Group: SF99601

Release:

V6R1M0

Abstract:

DB2 for IBM i

Level:

00021

Oct 8, 2011

Group: SF99187

Release:

V6R1M0

Abstract:

Backup Recovery Solutions

Level:

00024

Nov 30, 2011

However if the client cannot apply these levels above, then they can apply the minimal subset supplied below:

MF54179

MF53670

MF53550

MF52469

MF52324

MF52219

MF51777

MF51773

MF51356

MF50808

MF50176

MF46933

MF46409

v6.1.1

V6R1 has been qualified to use the 5704 and 5761 IOAs on Power5 hardware, while Power6 hardware allows the use of either 5704/5761 or the “SmartIOA” cards, 5749 / 5774 / 5735. Power7 hardware requires the use of the “SmartIOA” cards and V6.1.1 of the operating system.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended Lowest PTF levels are:

SF99610 Cumulative PTF Package: Level 10215 (C0215610)

SF99609 Group HIPER: Level 70

SF99601 DB2 for IBM i: Level 15

SF99187 Backup Recovery Solutions: Level 16

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.

Also, ensure the following individual PTFs are applied on V6.1.1 while using Smart IOAs:

There is no support for i6.1.1 in combination with applied PTF MF50093. If not needed do not apply!

SI36084

SI35218

SI34026

SI32538

MF50751

MF50691

MF50671

MF50587

MF49463

MF49458

MF49246

MF49234

MF47237

Review the Informational APAR for PTF requirements on the IBM website for the latest PTF requirements for Smart-IOAs:

II14355 – PTF PREREQUISITES AND SPECIFIC SUPPORT DATES FOR THE SMART-IOA (IOPless) FIBRE CHANNEL, SAS, and SCSI LVD ADAPTERS SUPPORT:

http://www-01.ibm.com/support/docview.wss?uid=nas27f65244c38e39c46862573cb0041f343



V7.1.0 , V7.2.0, V7.3.0

Fully supported with Data Domain OS 5.2 and Higher

V7.1.0, V7.2.0 & V7.3.0 has been qualified to use the “SmartIOA” cards.

Power 7 and Power 8 hardware has been qualified to use the “SmartIOA” cards listed above.

Required PTF due to IBM i OS FC failover:

PTF MF61618 for i 7.2

PTF MF61619 for i 7.3

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.

VIOS (Virtual IO Server)

Fully supported with Data Domain OS 5.2.

Virtual Input Output Server, also known as PowerVM. PowerVM is a virtualization layer

supporting the IBM i on blades and the Power6 platform at V6.1 and above. VIOS can only connect with the Data Domain System through a NPIV Switch and a 5735/577D – 8Gb PCIe “SmartIOA” card.

  • Data Domain OS v5.2 and higher supports
    • IBM VIOS versions: v2.1.x & v2.2.x
    • IBM i OS: v6.1.0, v7.1.0, v7.2.0, & V7.3.0
    • Only IOA supported: 5735/577D – 8GB PCIe “SmartIOA”



The IBM i License for the VTL will need to be installed before starting any VTL connections.

The IBM i utilizes a hardware virtualization layer commonly referred to as the Licensed Internal Code, or LIC, to provide access from the operating system to physical hardware. All peripheral equipment must emulate IBM equipment, including IBM tape libraries and devices, when presented to the operating system.

Additionally, there are no hardware drivers used by i/OS. All drivers are embedded in the LIC, or in LIC PTFs, or Program Temporary Fixes. In most cases, hardware configuration settings cannot be manually configured, as only IBM or IBM emulated equipment will be attached, requiring only fixed configuration settings.

Fiber Channel devices can be connected directly to IBM i host through an arbitrated loop (FC-AL) topology or through a switched fabric (FC-SW) topology, the DD VTL supports both switched fabric for connectivity or direct connect. The IBM i Fiber Channel host bus adapters or IOAs (Input / Output Adapters) can negotiate at 2 GB, 4GB, and 8GB speeds in a FC-SW environment without any configuration on the operating system other than plugging in the cable at the host.

While the IBM i HBAs support switched or direct connection for tape, the Data Domain VTL can also use switched connectivity or direct connect. Switched connectivity also allows access to a greater number of HBAs and increase flexibility and scalability, as well as the ability to share a single library among multiple systems.

A zone is comprised of a set of devices that access one another, in an initiator to target model. It is required that only one target and one initiator be in each VTL zone. Additional HBAs may be assigned to a VTL HBA by adding another zone. Soft zoning is recommended, in which the zone will consist of the WWPN or alias of one of the HBA ports on the Data Domain VTL, and the WWPN or alias of one of the IBM i HBA ports. Zones are then added to a zone set and activated.

4 Gb or 8 Gb switches are recommended for connectivity to IBM i. The list of IBM i qualified switches are listed in the IBM interoperability matrix.

Once the cabling of the VTL and the IBM i HBA has been completed, create appropriate tape zones with one initiator and one target: the WWPN of the VTL HBA and the WWPN of the IBM i HBA. The IBM i does not allow multiple paths to tape devices, so the zoning for each library or tape device should consist of only one initiator and one target.

Related:

Re: Single Proc E460 (13th Gen) – definitely no PCIE cards allowed?

Hi There,

I’m wondering if someone can clear something up for me:

Is it true that a single processor E460 (13th Gen) can not take any PCIE NICs? Not even one?

The network guide says the following, but i just want to be certain that you can’t add a single PCIE NIC to these nodes:

“Up to three additional PCI-e NIC can be added to the node, except single processor E460”

Input greatly appreciated, thanks.

Related: