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
xna(7) Miscellaneous Information Manual xna(7)
NAME
xna - The DEMNA Ethernet interfaces
SYNOPSIS
config_driver xna
DESCRIPTION
The xna driver provides access to a 10-MB Ethernet network through the DEMNA adapter. The DEMNA is an Ethernet-to-XMI adapter.
The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl. The xna driver employs the Address Resolution Protocol,
as described in arp(7), to map dynamically between Internet and Ethernet addresses on the local network.
The SIOCSPHYSADDR ioctl can be used to change the physical address of the adapter and SIOCRPHYSADDR can be used to read its physical
address. SIOCADDMULTI and SIOCDELMULTI can be used to add or delete multicast addresses. The xna driver supports a maximum of 12 multi-
cast addresses. The argument to the latter ioctls is a pointer to an ``ifreq'' structure found in <net/if.h>.
SIOCRDCTRS and SIOCRDZCTRS ioctls can be used to read or read and clear network counters. The argument to the latter two ioctls is a
pointer to a counter structure ``ctrreq'' found in <net/if.h>.
The ioctls SIOCENABLBACK and SIOCDISABLBACK can be used to enable and disable the interface loopback mode.
RESTRICTIONS
The PUP protocol family is not supported.
EXAMPLES
To obtain the physical address of the adapter, use the SIOCRPHYSADDR ioctl as in the following program example: #include <stdio.h>
/* standard I/O */ #include <errno.h> /* error numbers */ #include <sys/socket.h> /* socket definitions */ #include
<sys/ioctl.h> /* ioctls */ #include <net/if.h> /* generic interface structures */
main() {
int s,i;
static struct ifdevea devea;
/* Get a socket */
s = socket(AF_INET,SOCK_DGRAM,0);
if (s < 0) {
perror("socket");
exit(1);
}
strcpy(devea.ifr_name,"xna0");
if (ioctl(s,SIOCRPHYSADDR,&devea) < 0) {
perror(&devea.ifr_name[0]);
exit(1);
}
printf("Address is ");
for (i = 0; i < 6; i++)
printf("%X ", devea.default_pa[i] & 0xff);
printf("
");
close(s); }
To enable external loopback, use the SIOCENABLEBACK ioctl as in the following program example: #include <stdio.h> /* standard
I/O */ #include <errno.h> /* error numbers */ #include <sys/socket.h> /* socket definitions */ #include <sys/ioctl.h>
/* ioctls */ #include <net/if.h> /* generic interface structures */
main() {
int s;
struct ifreq data;
/* Get a socket */
s = socket(AF_INET,SOCK_DGRAM,0);
if (s < 0) {
perror("socket");
exit(1);
}
strcpy(data.ifr_name,"xna0");
if (ioctl(s,SIOCENABLEBACK,&data) < 0) {
perror("SIOCENABLEBACK:");
exit(1);
}
close(s); }
ERRORS
The DEMNA errors are coded as follows: Adapter did not pass the power-up self-test during autoconfiguration time. The port attachment
fails. The xna driver was unable to allocate memory for adapter data structures. The port attachment fails. The xna driver was unable to
map memory for adapter data structures. The port attachment fails. The xna driver was unable to bring the adapter into the initialized
state. The port attachment fails. The xna driver failed to prepare the adapter for run-time use. The xna driver was unable to bring the
adapter into the initialized state during a port reset. The adapter port command failed. The error code gives reason for failure. Too
many multicast requests have been made.
RELATED INFORMATION
Files: arp(7), inet(7), intro(4), netstat(1) delim off
xna(7)