Differences

This shows you the differences between two versions of the page.

--- aix:hmc_cmd [2023/11/19 20:50]
manu
+++ aix:hmc_cmd [2024/03/29 11:49] (current)
manu
@@ Line 9: / Line 9: @@
 hmc@hscroot > mksysconn -o auto
 </cli>
+. Server type, make and serial number do not update, vterm sessions fail to open.
+Ensure you know the BMC admin password (Login to ASM).
+Remove the connection:
+<cli prompt='#'>
+# rmsysconn -m <server name as shown in lssysconn -r all> -o r
+</cli>
+Add the connection back.
+If the connection is DHCP private network:
+<cli prompt='#'>
+# mksysconn -o auto
+</cli>
+Wait a few minutes, re-enter the password when prompted.
+If the connection is static:
+<cli prompt='#'>
+# mksysconn --ip <bmc ip> -u admin --passwd <admin password>
+</cli>
+Wait several minutes for the VMI IP address to be discovered.
+. System toggles from “Pending Authentication” to “No connection” and showing Password expired 0806-0000-00000000.  This is because the default user ID is admin and the default password is admin (the password is set to expired).
+Set the ID and password that your HMC will use to authenticate and manage the system. This is the same ID and password that you will use to access the ASMI. To set the system password, select the BMC, then select Actions > Update System Password.
+Helpful commands
+The lssysconn command will list both the eBMC and VMI IP addresses and connection states.  Each server must have a valid IP address for both.  The VMI address must show connected when the server is standby or operating.
+<cli prompt='#'>
+# lssysconn -r all
+resource_type=sys,type_model_serial_num=9105-42A*13BEA00,sp_type=ebmc,ipaddr=192.168.128.215,user_name=admin,alt_ipaddr=unavailable,state=Connected,vmi_ipaddr=192.168.128.216,vmi_state=Connected
+</cli>
+To check the vmi configuration:
+<cli prompt='#'>
+# lssysconn -r vmi -m <server name>
+resource_type=vmi,type_model_serial_num=9105-42A*13BEA00,interface=eth1,ipv4addr=10.254.0.33,gateway=0.0.0.0,net_mask=255.255.255.0,ipv4addr_orig=dhcp
+resource_type=vmi,type_model_serial_num=9105-42A*13BEA00,interface=eth0,ipv4addr=9.1.1.9,gateway=9.1.1.1,net_mask=255.255.255.0,ipv4addr_orig=dhcp
+</cli>
+To check for configuration errors:
+<cli prompt='#'>
+lssyscfg -r sys -F name,state,state_detail
+</cli>
 ===== list UAK (update access key) on Power 8 and later =====
@@ Line 74: / Line 116: @@
 $SERVER_OR_CLIENT        server (Adding on VIOS), client (Adding on LPAR)
 </code>
+List virtual slot type **fc**
+<cli prompt='>'>
+hscroot@sfohmc1:~> lshwres -r virtualio --rsubtype fc --level lpar -m Server-8233-E8B-SN0623B7P
+lpar_name=vio1,lpar_id=2,slot_num=31,adapter_type=server,state=1,is_required=0,remote_lpar_id=4,remote_lpar_name=lpar1,remote_slot_num=21
+lpar_name=vio1,lpar_id=2,slot_num=32,adapter_type=server,state=1,is_required=0,remote_lpar_id=5,remote_lpar_name=lpar2,remote_slot_num=21
+lpar_name=vio1,lpar_id=2,slot_num=33,adapter_type=server,state=1,is_required=0,remote_lpar_id=6,remote_lpar_name=lpar3,remote_slot_num=21
+lpar_name=vio1,lpar_id=2,slot_num=34,adapter_type=server,state=1,is_required=0,remote_lpar_id=7,remote_lpar_name=lpar4,remote_slot_num=21
+lpar_name=vio2,lpar_id=3,slot_num=31,adapter_type=server,state=1,is_required=0,remote_lpar_id=4,remote_lpar_name=lpar1,remote_slot_num=22
+lpar_name=vio2,lpar_id=3,slot_num=32,adapter_type=server,state=1,is_required=0,remote_lpar_id=5,remote_lpar_name=lpar2,remote_slot_num=22
+lpar_name=vio2,lpar_id=3,slot_num=33,adapter_type=server,state=1,is_required=0,remote_lpar_id=6,remote_lpar_name=lpar3,remote_slot_num=22
+lpar_name=vio2,lpar_id=3,slot_num=34,adapter_type=server,state=1,is_required=0,remote_lpar_id=7,remote_lpar_name=lpar4,remote_slot_num=22
+lpar_name=lpar1,lpar_id=4,slot_num=21,adapter_type=client,state=1,is_required=0,remote_lpar_id=2,remote_lpar_name=vio1,remote_slot_num=31,"wwpns=c0507602f66f0000,c0507602f66f0001"
+lpar_name=lpar1,lpar_id=4,slot_num=22,adapter_type=client,state=1,is_required=0,remote_lpar_id=3,remote_lpar_name=vio2,remote_slot_num=31,"wwpns=c0507602f66f0002,c0507602f66f0003"
+</cli>
 Adding a virtual fibre channel device to an LPAR:
@@ Line 101: / Line 158: @@
 </cli>
-  * Add a virtual FC adapter on VIOs and the targeted LPAR (Commands from the HMC)
+Removing a virtual adapter in slot 31 from an VIOS:
-  For the VIO
+<cli prompt='#'>
-(DLPAR vfc "server" on LABVIO01 into slot 34, for LPAR labaix01 slot 14)
+# chhwres -r virtualio -m $MACHINE_NAME -o $ADD_OR_REMOVE -p $LPAR_NAME -s $VIRTUAL_SLOT
+# chhwres -r virtualio -m Server-9009-22A-SN8675309 -o r -p vios01 -s 31
+</cli>
+Now save the runing config (it overwrites profile with actual running config)
 <cli prompt='#'>
-# chhwres -r virtualio -m lab-01-p740 -o a -s 34 -p LABVIO01 --rsubtype fc -a "adapter_type=server,remote_lpar_name=labaix01,remote_slot_num=14"
+# mksyscfg -r prof -m Server-9009-22A-SN8675309 -o save -p vios01 -n vios --force
 </cli>
@@ Line 813: / Line 875: @@
 hscroot@hmc01:~> chhmc -c kerberos -s add --realm <kerberos_hostname> -a <kerberos_ip>
 </cli>
+==== Led management ====
+Turn off / on a LED on a server
+<cli prompt='>'>
+hscroot@hmc01:~> lssyscfg -r sys -F name
+Power10_01_siteA
+</cli>
+Check to see if the attention LED is active
+<cli prompt='>'>
+hscroot@hmc01:~> lsled -r sa -t phys -m Power10_01_siteA
+state=on
+</cli>
+Use the chled command to turn off the system attention LED
+<cli prompt='>'>
+hscroot@hmc01:~> chled -r sa -t phys -m Power10_01_siteA -o off
+</cli>
+To check the status of system attention LED you can use the lsled
+<cli prompt='>'>
+hscroot@hmc01:~> lsled -r sa -t phys -m Power10_01_siteA
+state=off
+</cli>
+On partitions:
+<cli prompt='>'>
+hscroot@hmc01:~> lsled -r sa -t virtuallpar -m Power10_01_siteA
+lpar_id=22,lpar_name=AIXA001,state=off
+lpar_id=17,lpar_name=AIXA002,state=off
+lpar_id=13,lpar_name=AIXA003,state=off
+</cli>

wiki

User Tools

Site Tools

Differences

Page Tools