Skip to main content

Commands to restart RMC connection (t...

Commands to restart RMC connection (to HMC from LPAR)

It has become very common with the IBM HMC to LPAR (logical/micro partition) communication to drop for unknown reasons.  Most of the time this is not a problem unless there is a need to do a dynamic logical partition operation (or DLAPR operation to add/remove resources on the fly).  This will become evident during the DLPAR operation when HMC complains about having no RMC connection to LPAR in operation.  When this happens run the following commands on the LPAR in question before reattemping the operation.  The DLPAR operation will still work with out this connection, but the LPAR needs a restart to see the change in the resources. 

Restart the RMC connection on the LPAR:

# /usr/sbin/rsct/install/bin/recfgct
# /usr/sbin/rsct/bin/rmcctrl -p

Verify the connection by running:

lsrsrc IBM.ManagementServer

This will show the HMC IP/hostname and the LPAR information.
Labels:

Popular posts from this blog

Network throughput test between 2 AIX servers

The easiest way to test throughput between 2 AIX servers is to do a FTP test, generating data transfer with ‘dd’ command.  This will provide the throughput/speed for the specified amount of data transfer: #src-system> ftp dst-system … … ftp>  put "|dd if=/dev/zero bs=32k count=10000" /dev/null 200 PORT command successful. 150 Opening data connection for /dev/null. 10000+0 records in 10000+0 records out 226 Transfer complete. 327680000 bytes sent in 1.406 seconds (2.277e+05 Kbytes/s) local: |dd if=/dev/zero bs=32k count=10000 remote: /dev/null ftp>bye   This is the same test IBM recommends in the redbook and also during a support call
Read more

Converting SEA on VIO from access to trunk mode

Shared Ethernet Adapters on VIO server can be configured in two different modes while accessing the external network. 1.  Simple mode 2. Trunk mode or 802.1Q mode In a Simple mode, the SEA is not aware of any VLAN information and bridges all the network packets to the external switch.  the external switch then determines the target and routes/discards it accordingly.  This is very useful when there is only one VLAN that needs to be serviced through the SEA to the LPARs using these VIO servers.  The configuration on the switch as well as the VIO (SEA) is simple and straight forward.  In a Trunk mode (802.1Q complaint), the SEA is aware of the VLANs and bridges only the packets that is part of the ‘Additional VLANs’ list.  The external switch then determines the target and routes/discards it accordingly.  This is very useful when there is a need to service multiple VLANs through the same SEA adapter.  This will provide the ability to create LPARS from multiple networks to reside on t
Read more