This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
aix:vios_command_line [2024/01/04 00:17] manu [Which vfchost on LPAR] |
aix:vios_command_line [2024/01/04 00:26] (current) manu [Which vfchost on LPAR] |
||
|---|---|---|---|
| Line 107: | Line 107: | ||
| </cli> | </cli> | ||
| + | //Note// If your VIOS is not running the latest VIOS code, 3.1.3.00, you'll find that the "FC adapter name on VIOS" attribute will be blank | ||
| + | |||
| + | |||
| + | == You can mask theses informations on the VIOS == | ||
| + | |||
| + | It is worth noting that you can prevent this information from being available to the client LPAR by changing the secure_va_info attribute on your 3.1.3.00 VIOS. | ||
| + | |||
| + | For example, if we were to change the secure_va_info value from no to yes, like so: | ||
| + | <cli prompt='$'> | ||
| + | $ chdev -dev viosnpiv0 -attr secure_va_info=yes | ||
| + | viosnpiv0 changed | ||
| + | |||
| + | $ virtadapinfo -list | ||
| + | secure : yes | ||
| + | </cli> | ||
| + | |||
| + | Then the client LPAR will see the following (Secure) output for that VIOS: | ||
| + | <cli prompt='#'> | ||
| + | # cat /proc/sys/adapter/fc/fcs1/hostinfo | ||
| + | VFC client adapter name : fcs1 | ||
| + | Host partition name (VIOS) : Secure | ||
| + | VFC host adapter name : Secure | ||
| + | VFC host adapter location code : Secure | ||
| + | FC adapter name on VIOS : Secure | ||
| + | FC adapter location code on VIOS : Secure | ||
| + | </cli> | ||
| ===== Virtual tape drive / library ===== | ===== Virtual tape drive / library ===== | ||