You are on page 1of 2

USERID@FSM40F2E9585006:~> smcli importupd -v /home/USERID/8737/

ATKUSC206I Generating SDDs for path: "/home/USERID/8737".


ATKUPD293I Update "ibm_fw_imm2_1aoo64l-4.50_anyos_noarch" was successfully impor
ted to the library.
ATKUPD293I Update "elx_fw_fc_ibm14a-10.2.261.36-1_vmware_x86-64" was successfull
y imported to the library.
ATKUPD293I Update "qlgc_fw_fc_3.11af.d-8g-flex_vmware_x86-64" was successfully i
mported to the library.
ATKUPD293I Update "ibm_utl_uxsp_b2sp05p-2.15b_virtual_32-64" was successfully im
ported to the library.
ATKUPD294I Update with SDD file "ibm_fw_imm2_1aoo40e-2.00_anyos_noarch.pd.sdd" a
lready exists in the library, skipping update. This is not an error.
ATKUPD294I Update with SDD file "elx_fw_fc_ibm14a-2.02x11-30_vmware_x86-64.pd.sd
d" already exists in the library, skipping update. This is not an error.
ATKUPD294I Update with SDD file "qlgc_fw_fc_3.80.09-16g-flex_vmware_x86-64.pd.sd
d" already exists in the library, skipping update. This is not an error.
ATKUPD294I Update with SDD file "elx_fw_cna_ibm14a-oc11-10.2.261.36-1_vmware_x86
-64.pd.sdd" already exists in the library, skipping update. This is not an error
.
ATKUPD294I Update with SDD file "ibm_fw_dsa_dsyte2f-9.61_anyos_32-64.pd.sdd" alr
eady exists in the library, skipping update. This is not an error.
ATKUPD294I Update with SDD file "ibm_fw_uefi_b2e142a-1.50_anyos_32-64.pd.sdd" al
ready exists in the library, skipping update. This is not an error.
ATKUPD294I Update with SDD file "brcd_fw_cna_3.2.4.1.a_vmware_x86-64.pd.sdd" alr
eady exists in the library, skipping update. This is not an error.
ATKUPD573I Running compliance for all new updates that were found.
ATKUPD286I The import updates task has completed successfully.
USERID@FSM40F2E9585006:~> smcli importupd -v /home/USERID/CMM
ATKUSC206I Generating SDDs for path: "/home/USERID/CMM".
ATKUPD293I Update "ibm_fw_cmm_2pet12p-2.5.1p_anyos_noarch" was successfully impo
rted to the library.
ATKUPD573I Running compliance for all new updates that were found.
ATKUPD286I The import updates task has completed successfully.
USERID@FSM40F2E9585006:~> smcli importupd -v /home/USERID
ATKUSC206I Generating SDDs for path: "/home/USERID".
ATKUPD293I Update "ibm_fw_scsw_en2092-7.8.7.0_anyos_noarch" was successfully imp
orted to the library.
ATKUPD573I Running compliance for all new updates that were found.
ATKUPD286I The import updates task has completed successfully.
USERID@FSM40F2E9585006:~>
USERID@FSM40F2E9585006:~>
USERID@FSM40F2E9585006:~>
USERID@FSM40F2E9585006:~>
USERID@FSM40F2E9585006:~>
ATKSRV640I Service Location Protocol (SLP) cannot be reached at IP address 10.32
.36.114. If the resource is not fully discovered,
enable SLP, ensure that Flex System Manager can reach SLP, and rerun discovery.
smcli manageV7000 -i 10.32.35.107 -p vpbs@123
SLP is not functioning on the ESXi host.
SSH must be enabled to run these commands. SSH can be disabled when complete:
/etc/init.d/sfcbd-watchdog stop
/etc/init.d/sfcbd-watchdog start

/etc/init.d/slpd restart
/opt/ibm/director/data/admin_PRIVATE_10_32_35_107
http://pic.dhe.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm
.acc.8731.doc%2Fmanaging_storwize_v7000_automatically.html
I was wondering if someone could explain how the FSM can manage my Vmware Enviro
nment?
I understand that you can use vmcontrol, but do you need to install agents on th
e vcenter server?
does the vcenter server need to live on a node within the chassis or can it be a
nother node (rack server)?
thanks for your response.
Regarding your question. There's been some confusion in the way IBM represents V
Mcontrol. In my experience VMcontrol can do some things for VMware like put a ho
st in maintenance mode and/or migrate VMs between hosts among some other feature
s. These jobs can be scheduled as well as run in real-time. However, it is confu
sing in that it makes it appear as if agents need to be installed in ESXi, this
is not the case and only applies to Power system visualization. For what you wan
t you need to manage your vCenter server and it does not need to live within the
PureFlex Chassis.
To
1)
2)
3)

do this perform the following:


Go to System Discovery then enter the IP address of your vCenter server.
Once found gain access by clicking on the 'No Access' link.
After access is gained, collect inventory on the vCenter server.

Once these steps are completed you should begin to see your ESXi hosts populate
as virtual servers. If they do not, you may want to run inventory on the individ
ual hosts as well.
Last thing is to ensure everything in your chassis is at the lastest code level
especially the FSM.