RMC Network Connection to the Partition is Not Present

I have a problem working with dynamic operations with a specific partition "it's VIO"
A RMC network connection to the partition is not present. Verify the network settings on the partition and the HMC. If you select OK you will have to restart the partition for the resource changes to take effect.
Please share your opinions because I tried lot of steps and it still!

>----Original Message----
>De: email@removed
>Fecha: 05/03/2013 08:35
>Para: "mabeleira"email@removed
>Asunto: RE:[ibm-aix-l] RMC Network Connection to the Partition is Not
Present
>
>
>
>I can ping from the VIO partition to the HMC also I can telnet on port
657!!
>Should I still need to make private network?
>

Hi Zatarra, didn't get your point!
What do you mean by VIOS ID must have exact match with HMC?
However from the HMC in GUI the VIOS listed as:
VIOS_A with ID (1)
Also from the VIO AIX prompt:
#uname -L
1 VIOS_A

Try ping/preferably ssh from hmc to vios and vice versa using hostnames. If it resolves and works, network should be alright, otherwise check name resolution with nslookup for both hosts if dns in use.

Who said that we should resolve with names from any partition to the HMC!!
As I know there is no need to resolve with names from the partition to the HMC
and what prove my words the other partitions don't work so!!

There are a number of articles on this out on the forums. Have you EVER had
a connection? If not, then the first thing I'd check is that you can
connect from the partition to the HMC using telnet on the RMC port.

In general, start on the HMC and issue "lspartition -dlpar". Check for the
partition of interest. In particular, see if your partition is listed. If
it's listed, make sure the Active status is 1. Both must be true to have
communication. Without calling IBM, about the only thing you can do on the
HMC side is to restart the HMC. That may or may not solve your problem.
There are several things you can do on the partition side. Nearly every
update to HMC fixes some problem with the RMC connection and it still
hasn't been completely fixed. You might try upgrading your HMC to the lates
level. Are you running 1 or 2 HMCs. If 2, you might have a connection to
one HMC and not the other.

Also, be aware that even if you do correct the underlying problem, it make
take more than 5 minutes to get the connection to be show active.

In general, probably the easiest thing is to call IBM support (hopefully
you have a support contract). They seem to be pretty adept at getting these
connections up. And, if necessary, they can give you the password for a
pesh login.

If you never had an RMC connection you are out of luck.
Wait till the first possible outage window and correct the matter...

Simple telnet tests do not prove everything here.
You need proper vice versa communications between HMC and VIOS since VIOS boot.
It's catch-22 trying to setup RMC communications in flight if the only requirement is to have RMC communications working from from the start.

You could check netmask, gateway, routing and firewall settings and restart the services on the VIOS and get really lucky, but the HMC is not lying to you. It's fine to doubt everything you see, but the bad news is what it is...

...i've got an important production dlpar in flight right now with both RMC interfaces erronymously configured in the wrong vlan.
An immediate check after the boot would have saved me to make all other apologies made so far that I cannot change anything until the approved outage window next Easter.

Take my advice and start pushing your management for an outage instead.
Do the read of the above suggested materials and even consider a dual VIOS setup so you CAN shutdown one of them in case of big changes or trouble.

Hi All,
I have faced RMC connection issues for LPM on Power 7. You need to enable
communication between hmc ip and lpar ip. you need to open port 657 tcp/udp
bidirectional. then refresh rmc daemons on hmc using pesh password, reboot
hmc. your partitions may not show immediately wait some for time and hmc
will start showing all partitions. try dlpar operations now and it should
work. you can also check dlpar capability using lspartition -dlpar on your
hmc. dcaps value should be non-zero for dlpar to work.
if there are firewalls in between you will have to request firewall teams
to open port 657.