I am having trouble with getting this to work. I don't control the iSCSI side of the equation so I am just trying to make sure everything is correct on the UCS side. When we boot we get an the "Initialize error 1"
If I attach to FI via ssh I am able to ping the target ip's. The SAN administrator says that the UCS has to register before itself (which isn't occuring) prior to him giving it space. Everything I have seen the LUN's and Mask are created prior to boot...is this required?
We have another blade the other chasis that has ESX installed on the local drive and is using the iSCSI SAN as it datastore, therefore I know I connectivity to the SAN. The storage array is a emc CX4-120.
I used your docs and video for most of my setup (Good Stuff). The SAN administrator has said that he needs my initiators to be registered before he can mask them, is this true or does the actual SAN stuff need to be completed prior to boot? I have checked vnic and it has vlan 2000 set to native. I have also found other instance where the
iscsi_get_config shows a vlan value of 0, on your setup did it show the actual vlan? After I made some changes to the target I did get different results as stated above:
dhcp status: false
IP Addr: 192.168.0.109
Subnet Mask: 255.255.255.0
Target Idx: 0
Prev State: ISCSI_TARGET_DISABLED
Target Error: ISCSI_TARGET_LUN_INIT_ERROR
Is this better as in have I attached to the SAN but just don't have any luns avaialble?
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
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...