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
fza(4) Kernel Interfaces Manual fza(4)
Name
fza - DEFZA FDDI Network Interface
Syntax
device fza0 at ibus? vector fzaintr
Description
The interface is a high speed TURBOchannel bus to a 100 Mbit/second Fiber Distributed Data Interface (FDDI) timed token ring network
adapter. The interface allows the host system to be an FDDI single attachment station.
The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl. The interface employs the address resolution protocol
described in to map dynamically between Internet and FDDI addresses on the local network.
The maximum frame size for the interface is 4500 bytes, which is substantially larger that the 1500 bytes maximum packet size of the Ether-
net interfaces. The interface does not support the BSD trailer encapsulation, which is specific to the VAX architecture.
The SIOCRPHYSADDR ioctl can be used to read the physical address of the DEFZA adapter. The physical address of the DEFZA adapter can not be
changed.
The SIOCADDMULTI and SIOCDELMULTI ioctls can be used to add or delete multicast addresses. The DEFZA supports up to 64 multicast
addresses.
The SIOCRDCTRS ioctl can be used to read the FDDI driver counters. The DEFZA adapter status and characteristics can also be read through
this ioctl by providing a FDDI_STATUS flag . The argument to this ioctl is a pointer to a counter or status structure, found in <net/if.h>.
The SIOCENABLBACK and SIOCDISABLBACK ioctls can be used to enable and disable the interface loopback mode, respectively.
The SIOCEEUPDATE ioctl can be used to update the adapter's firmware.
The SIOCIFRESET ioctl can be used to reset the adapter.
Diagnostics
Diagnostic error messages contain information provided by the driver. For example:
fza%d: fzaprobe selftest failed
The DEFZA adapter did not pass the power-up selftest during autoconfiguration.
fza%d: port init failed
The DEFZA adapter cannot be initialized.
fza%d: port in the Halt State -> CNS hardware fault
The DEFZA adapter went to the Halt state because of an adapter firmware fault.
fza%d: LINK unavailable
The network link went down which means that the station is not on the FDDI ring.
fza%d: Ring Init Received
A Ring Initialization unsolicited event has been received from the fza%d interface.
See Also
arp(4p), inet(4f), intro(4n)
fza(4)