Справочник Пользователя для IBM Flex System V7000 Expansion Enclosure 4939H29
Модели
4939H29
Appendix A. CLI Setup and Configuration
583
Draft Document for Review January 29, 2013 12:52 pm
8068AppA-CLI.fm
8. Highlight the new session and click Open to connect to the IBM Flex System V7000
Storage Node. A PuTTY Security Alert opens; confirm it by clicking Yes (Figure A-14).
Figure A-14 Confirm Security Alert
9. PuTTY now connects to the system and prompts you for a user name. Enter admin as the
user name and press Enter (Example A-1).
Example: A-1 Enter user name
login as: admin
Authenticating with public key "rsa-key-20101006"
IBM_4939:FlexSystem_V7000:admin>
Authenticating with public key "rsa-key-20101006"
IBM_4939:FlexSystem_V7000:admin>
You have now completed the tasks that are required to configure the CLI for IBM Flex System
V7000 Storage Node administration.
V7000 Storage Node administration.
Example commands
A detailed description about all the available commands is beyond the intended scope of this
book. In this section are sample commands that we have referenced in this book.
book. In this section are sample commands that we have referenced in this book.
With earlier releases of the IBM SAN Virtual Controller and the IBM Storwize V7000 there
were prefixes required to run CLI commands; these were
were prefixes required to run CLI commands; these were
svcinfo
and
svctask
and are no
longer needed in the IBM Flex System V7000 Storage Node. If you have scripts from those
platforms that use these prefixes, they run without problems. If you type
platforms that use these prefixes, they run without problems. If you type
svcinfo
or
svctask
and press the Tab key twice, all the available subcommands are listed for those prefixes.
Pressing the Tab key twice also auto-completes commands if the input is valid and unique to
the system.
Pressing the Tab key twice also auto-completes commands if the input is valid and unique to
the system.
Enter
lsvdisk
, as shown in Example A-2, to list all configured volumes on the system. The
example shows that three volumes are configured.
Example: A-2 List all volumes
IBM_4939:FlexSystem_V7000:admin>lsvdisk
id name IO_group_id IO_group_name status mdisk_grp_id mdisk_grp_name capacity type FC_id FC_name RC_id
RC_name vdisk_UID fc_map_count copy_count fast_write_state se_copy_count RC_change
0 Hyper-V_PCO_Node1 0 io_grp0 online many many 100.00GB many
600507680185853FF00000000000000F 0 2 empty 0 no
1 ESXi-PCO 0 io_grp0 online many many 100.00GB many
600507680185853FF000000000000010 0 2 empty 0 no
2 ESXi-Redbooks 0 io_grp0 online many many 400.00GB many
600507680185853FF000000000000011 0 2 not_empty 0 no
3 Hyper-V_PCO_Node2 0 io_grp0 online many many 101.00GB many
600507680185853FF000000000000012 0 2 empty 0 no
id name IO_group_id IO_group_name status mdisk_grp_id mdisk_grp_name capacity type FC_id FC_name RC_id
RC_name vdisk_UID fc_map_count copy_count fast_write_state se_copy_count RC_change
0 Hyper-V_PCO_Node1 0 io_grp0 online many many 100.00GB many
600507680185853FF00000000000000F 0 2 empty 0 no
1 ESXi-PCO 0 io_grp0 online many many 100.00GB many
600507680185853FF000000000000010 0 2 empty 0 no
2 ESXi-Redbooks 0 io_grp0 online many many 400.00GB many
600507680185853FF000000000000011 0 2 not_empty 0 no
3 Hyper-V_PCO_Node2 0 io_grp0 online many many 101.00GB many
600507680185853FF000000000000012 0 2 empty 0 no