I have some unclear about how VIOS uses its resources.
Assume that VIOS lpar has only 1 physical FC, and we use that to connect to the Lun. Then we install VIOS for the lpar on that Lun.
So my question is, afterward, we can still use that physical FC for the virtual FC we create later?
This can be same mechanism with virtual ethernet?
I have 1 physical ethernet assigned to vios, and configure IP on that, everything is fine until I tried to map another virtual ethernet to it and got the issue below:
Code:
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 2
Adapter ent0 has an interface configured over it, or it belongs to another SEA, VLAN or EtherChannel
Command did not complete.
All of these mean that we have to use another physical device (FC, ethernet) for virtual devices??
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
ifdhtransmittoicc
IFDHTransmitToICC(3SMARTCARD) Smartcard Library Functions IFDHTransmitToICC(3SMARTCARD)NAME
IFDHTransmitToICC - transmit APDU to a smart card
SYNOPSIS
#include <smartcard/ifdhandler.h>
RESPONSECODE IFDHTransmitToICC(DWORD Lun, SCARD_IO_HEADER SendPci, PUCHAR TxBuffer, DWORD TxLength, PUCHAR RxBuffer, PDWORD RxLength,
PSCARD_IO_HEADER RecvPci);
PARAMETERS
The IFDHTransmitToICC() function takes the following parameters:
Input
Lun Logical Unit Number
SendPci Send-Protocol structure
TxBuffer Buffer containing the APDU to be sent
TxLength Length of sent APDU
Output
RxBuffer Received buffer for response APDU
RxLength Length of APDU-response
RecvPci Receive-Protocol structure
DESCRIPTION
The IFDHTransmitToICC() function performs an Application Protocol Data Unit (APDU) exchange with the card or slot specified by Lun. The IFD
handler is responsible for performing any protocol-specific (such as T0/T1) APDU exchanges with the card.
The Protocol structure SCARD_IO_HEADER contains the following members:
Protocol Values range from 0 through 14, inclusive, indicating protocol T=0, T=1, ..., T=14.
Length Not used.
RETURN VALUES
The following values are returned:
IFD_SUCCESS Successful completion.
IFD_RESPONSE_TIMEOUT The response timed out.
IFD_ICC_NOT_PRESENT The card is not present.
IFD_PROTOCOL_NOT_SUPPORTED The protocol is not supported
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 IFDHCreateChannelByName(3SMARTCARD), 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 IFDHTransmitToICC(3SMARTCARD)
01-16-2020
