01-16-2020
Hello zmaus,
I found the reason, it's because I took out the ethernet adapter, so the partitions don't have the IP.
Naturally, I think HMC can connect to it LPARs by its own method, but instead it uses IP to connect.
After I assign the adapter again, the rmc state is active.
10 More Discussions You Might Find Interesting
1. AIX
Hi,
Anybody had a problem trying to rmdev a scsi device and get the following error :
root@:/> rmdev -dlscsi3 -R
Method error (/usr/lib/methods/ucfgncr_scsi):
0514-062 Cannot perform the requested function
because the specified device is busy.
I can't... (1 Reply)
Discussion started by: stumpy
1 Replies
2. AIX
Hello,
This is the foll error wen i try doin DLPAR from my VIO after adding the virtual adpaters on my clients:
HSCL294C DLPAR ADD Virtual I/O resources failed:
com.ibm.hsc.common.exceptions.PIHscClientException: HSCL294C DLPAR ADD Virtual I/O... (0 Replies)
Discussion started by: lildudesaif
0 Replies
3. AIX
Hi all,
I have the following configuration
2 ds3524 storage disk systems located over 2 locations
2 P720 server located over 2 locations
DS3524 are connected to san switch.
Each vio server has 1 fc adapter attached to a san switch.
per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies
4. AIX
I am trying to generate a report to track dlpar operation performed on a MS and was wondering if anyone has done this before.
I can get history from HMC using lssvcevents , but this does not give me details as to what quantity was added or removed .
Any thoughts ?
Thanks (3 Replies)
Discussion started by: mk8570
3 Replies
5. UNIX for Advanced & Expert Users
Can anyone please let know difference between LPAR/DLPAR/WPAR.
and its purpose ??? (3 Replies)
Discussion started by: Pavithran
3 Replies
6. AIX
I cannot find the post with the comment that DLPAR capability was not working with IVM.
The two commands that need to be run are (as root, padmin does not know this command):
VIOS: lsrsrc IBM.MngNode
CLIENTS: lsrsrc IBM.MCP
Examples:
# lsrsrc IBM.MngNode
Resource Persistent Attributes for... (2 Replies)
Discussion started by: MichaelFelt
2 Replies
7. AIX
Hi Admins,
I am having a whole system lpar in open firmware state on HMC.
How can I bring it to running state ?
Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies
8. AIX
Hi all,
is any of you using RMC for monitoring your LPARs? Is it viable?
I know the IBM Magazine article and the Redbooks about it but I would like to hear from first hand.
Thanks in advance for sharing your experience! (7 Replies)
Discussion started by: zaxxon
7 Replies
9. AIX
There can be configurations in IBM Server wherein a
standalone partition is created on some supported IBM Server
Or
A VIOS - VIOC LPARs created.
Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..?
On a... (2 Replies)
Discussion started by: Manish00712
2 Replies
10. AIX
Hey All,
I have running dual VIOS on a P9 systems, and just created a new LPAR profile. My objective is to create LPAR Client VFC adapters, and then DLPAR VFC Server adapters on the VIOS.
In the HMC v9 Enhanced GUI, I have DLPAR a VFC adapter to both VIOS, however, you can't specify the... (1 Reply)
Discussion started by: aixkidbee
1 Replies
HY(4) Kernel Interfaces Manual HY(4)
NAME
hy - Network Systems Hyperchannel interface
SYNOPSIS
/sys/conf/SYSTEM:
NHY hy_controllers # Hyperchannel
DESCRIPTION
The hy interface provides access to a Network Systems Corporation Hyperchannel Adapter.
The network to which the interface is attached is specified at boot time with an SIOCSIFADDR ioctl. The host's address is discovered by
reading the adapter status register. The interface will not transmit or receive packets until the network number is known.
DIAGNOSTICS
hy%d: unit number 0x%x port %d type %x microcode level 0x%x. Identifies the device during autoconfiguration.
hy%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
hy%d: can't initialize. The interface was unable to allocate UNIBUS resources. This is usually due to having too many network devices on
an 11/750 where there are only 3 buffered data paths.
hy%d: NEX - Non Existent Memory. Non existent memory error returned from hardware.
hy%d: BAR overflow. Bus address register overflow error returned from hardware.
hy%d: Power Off bit set, trying to reset. Adapter has lost power, driver will reset the bit and see if power is still out in the adapter.
hy%d: Power Off Error, network shutdown. Power was really off in the adapter, network connections are dropped. Software does not shut
down the network unless power has been off for a while.
hy%d: RECVD MP > MPSIZE (%d). A message proper was received that is too big. Probable a driver bug. Shouldn't happen.
hy%d: xmit error - len > hy_olen [%d > %d]. Probable driver error. Shouldn't happen.
hy%d: DRIVER BUG - INVALID STATE %d. The driver state machine reached a non-existent state. Definite driver bug.
hy%d: watchdog timer expired. A command in the adapter has taken too long to complete. Driver will abort and retry the command.
hy%d: adapter power restored. Software was able to reset the power off bit, indicating that the power has been restored.
SEE ALSO
intro(4N), inet(4F)
BUGS
If the adapter does not respond to the status command issued during autoconfigure, the adapter is assumed down. A reboot is required to
recognize it.
The adapter power fail interrupt seems to occur sporadically when power has, in fact, not failed. The driver will believe that power has
failed only if it can not reset the power fail latch after a ``reasonable'' time interval. These seem to appear about 2-4 times a day on
some machines. There seems to be no correlation with adapter rev level, number of ports used etc. and whether a machine will get these
``bogus powerfails''. They don't seem to cause any real problems so they have been ignored.
3rd Berkeley Distribution August 20, 1987 HY(4)