We have 2 separate UCS installations, identical hardware config; 2, FI's, NetApp direct-attached storage, and upstream HP switches.
I have one installation up and running, iSCSI boot working fine.
The other installation was configured by another engineer, and he got servers up and running, booting over iSCSI. However, I have now gone back to provision some more blades with the template used on the existing blades and iSCSI boot won't work. I have cloned a template from a working blade, iSCSI boot won't work, I have even created a new template, compared to my own working installation, still no joy.
The server boots, I get the 'initilize error 1' from both of the nic's. The vnic's have the iSCSI vlan set as native. The iSCSI vlan is configured under the Appliance and LAN clouds. I am using different iqn's on each VNIC. I don't see any logins on the netapp (I do from our existing blades, but not these new blades).
I came back to site this morning, booted a blade and got the Option ROM sucessfully installed message, having made no config changes. I booted the vmware installer, however it still could not see the LUN. I could see the session on the netapp though. I pinned the traffic to one port channel, same result.
After about 1 hour, the server just started to see the Initialize Error 1 message.
My suspicion is that there are some upstream network issues causing this behaviour? What dependency do the uplinks from the FI have on iSCSI boot?
Your iSCSI vNICS are overlayed on top of the regular vNICS and the traffic from these vNICS will go through the ethernet uplinks, to me it clearly sound like some uplink network issue, to simplify things just use one vNIC and just one single uplink if you can and give it a try.
Please email me email@example.com to poke around and do a webex session if needed.
Strange behavior indeed. iSCSI has no different dependencies than any ethernet traffic. The traffic will be pinned to one of your border interfaces (or port channels). When you get the Initiliazation Error 1 it means there is an invalid value returned by MCPERR_EINVAL ~ initiator can't reach the target.
What I suggest you try is the following.
1. Boot the blade but enter into the BIOS (F2) when prompted. This will keep the iSCSI option ROM connected/ing.
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...
Introduction This document will run you through a step by step
configuration example of Inter VRF route leaking in Cisco Application
Centric Infrastructure(ACI). This article describes the steps with
screen shots of example configuration and some verifica...