Then, on AIX lpar (vio client) create new virtual ethernet. Then use smitty tcpip to configure the IP.
I can end up pinging the aix lpar
Regarding your question, this frame is no longer used in prod, so I took it as my test machine with few lpar and 1 VIOS only.
I have internal disks(SAS). But I wonder, if I have only 1 physical FC connected with LUN, Could I reuse it also for another virtual FCs to connect to other Lun? or I need another physical FC to do that?
Hey
May be a dumb question
Can I use a SPOT which is at 5.3 TL6 to boot an LPAR (with 5.3 TL8) in to maintenance mode? Will it work ?
Is it mandatory that SPOT should be of same or higher version in such case?
Bala (1 Reply)
I am trying to script and came up with a conclusion that I need a do while loop in my statement. I am stuck with the
do while syntax. I need to use it alongwith the if then else statement. Can I use it is a big question? I actually need to get all the files
that are there from within run_dt to... (1 Reply)
1.Write an automated shell program(s) that can create, monitor the log files and report the issues for matching pattern.
(i) Conditions for creating log files.
Log file is created with date (example 2010_03_27.log). If the log file size is 10 Mb for a particular day then automatically the log... (3 Replies)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Hi All,
I have a p520 box running 3 LPARs, 1 x VIOS, 1 x AIX 6.1 and 1 x AIX 7.1 and no HMC, all configuration is performed via VIOS/IVM
Until recently the box did not have the AIX7.1 LPAR and everything was fine with the box.
We needed to use AIX 7.1 for a new project, so I created a... (11 Replies)
Hi All,
I have a source file with data
Name ~ Groups
Muni~abc,was,USA_ax,123
Chaitanya~USA_12,was
Balaji~123,xyz,was
Ramu~123,xyz
From the second column i want to extract only the groups that matches the pattern 'USA_%' or if the group = 'was', and ignore any other columns.
... (8 Replies)
Please help in creating script for below requirement.
I will be running 1 command and will get below entries in a text file say file44.txt
*******************************
DFDL1005 06:30 00:05
ABFL2003 10/22 01:10
CFTL1256 10/24 00:10
10/25 09:20 PM
********************************
.... (3 Replies)
Discussion started by: Vinay_3308
3 Replies
LEARN ABOUT SUNOS
ifdhcreatechannelbyname
IFDHCreateChannelByName(3SMARTCARD) Smartcard Library Functions IFDHCreateChannelByName(3SMARTCARD)NAME
IFDHCreateChannelByName - create a communication channel with an IFD
SYNOPSIS
#include <smartcard/ifdhandler.h>
RESPONSECODE IFDHCreateChannelByName(DWORD Lun, LPSTR devicename);
PARAMETERS
The IFDHCreateChannelByName() function takes the following parameters:
Input
Lun Logical Unit Number
devicename Device name path
DESCRIPTION
The IFDHCreateChannelByName() function opens a communication channel with a card terminal specified by devicename. This function can use
open(2) or other system call to open the device and establish a communication path. The caller of this function (smart card framework)
assigns a logical unit number Lun per card terminal and slot and passes this value to IFDHCreateChannelByName(). If the IFD handler sup-
ports multiple terminals with one instance of the handler (as indicated by capability TAG_IFD_SIMULTANEOUS_ACCESS), it communicates with
the card terminal corresponding to this Lun.
If the IFD handler supports only one terminal with one slot per instance, it can choose to ignore the Lun.
The Logical Unit Number, Lun is encoded as 0xXXXXYYYY, where
YYYY represents the lower 16 bits that correspond to the slot number for terminals with multiple slots. Most of the readers have only
one slot, in which case YYYY is 0.
XXXX represents the next 16 bits that correspond to the card terminal and can range between 0 and a number returned by TAG_IFD_SUMULTA-
NEOUS_ACCESS.
RETURN VALUES
The following values are returned:
IFD_SUCCESS Successful completion.
IFD_COMMUNICATION_ERROR An error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO attributes(5)NOTES
This manual page is derived from the MUSCLE PC/SC IFD Driver Developer Kit documentation. License terms and attribution and copyright
information for this interface are available at the default location /var/sadm/pkg/SUNWocfh/install/copyright. If the Solaris Operating
Environment has been installed anywhere other than the default location, modify the path to access the file at the installed location.
SunOS 5.10 4 Dec 2002 IFDHCreateChannelByName(3SMARTCARD)
01-16-2020
