Hey there ZBlock--most of your attachments didn't come across. Could you post your Q on the DC IE forum? (The private message part of CLN is incapable of handling lots of attachments.)
I have found that trying to populate anything iscsi within the confines of a template (versus an actually instantiated service profile) is prone to barfing. For purposes of the exam, I decided that I would spin up a basic service profile from a template, and configure iscsi after instantiation.
But post on the forum so i can see your screenshots. MM
I did post on the CCIE DC Study group and can confirm I have not private messages this across to anyone. all the attachment's that I posted are on the thread - I have used multiple browsers to search and can see all the attachments I have posted.
so just to confirm you think it would be better to create a service profile template > create a service profile from the template and add a ISCSI vnic and boot information afterwards ? my question is that would we not be able to make changes to that service profile as all the information has been derived from the service profile template itself. in other words would we have to disassociate from the service profile template , make and then make the changes to the profile by creating a ISCSI vnic and also make changes to the boot policy ?
after messing around with the UCS for abit , ive found the only way to do this is to 1; make the service profile template initial, rather than updating, or 2; unbind the service profile from the service profile template.
but would be easier to unbind as then we can modify the vnic templates to make the ISCSI vlan native if not done before.
good morning Zblock--I'm responding here so everyone has the benefit of the conversation. I apologize if this answer is duplicative. (Also, now I'm seeing all of your screenshots.)
For some reason, UCS is very particular about iSCSI configurations. And it seems that UCS ISCI has been that way for a while now. I went back to Brian McGahan's DC Bundle (on Releaase 1.x code!), and he had similar experiences.
after messing around with the UCS for abit , ive found the only way to do this is to 1; make the service profile template initial, rather than updating, or 2; unbind the service profile from the service profile template
This is my experience also. I would have thought that UCS would have liked to have been more scalable, but since ISCSI doesn't have a mechanism like FC zoning, I would surmise that this was how the UCS creators answered the whole storage concept of one initiator: one target. That's total speculation on my part, BTW. I have nothing to back that up.
For purposes of the exam, I would suggest that you spin up a service profile as fast as you can, and then just configure the iSCSI on top of that. I tried to figure out a fast way to iSCSI while I was configuring a template, and the only shortcut that I came up with was to have a vnic template to configure the underlaying "physical" vnic. But that only really gets you the iSCSI VLAN as native on that interface.