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 PLAN9
vni
vni(7d) Devices vni(7d)NAME
vni - STREAMS virtual network interface driver
DESCRIPTION
The vni pseudo device is a multi-threaded, loadable, clonable, STREAMS pseudo-device supporting the connectionless Data Link Provider
Interface dlpi(7P) Style 2. Note that DLPI is intended to interact with IP, meaning that DLPI access to applications is not supported. (For
example, snoop fails on the vni interface.)
The vni device is a software-only interface and does not send or receive data. The device provides a DLPI upper interface that identifies
itself to IP with a private media type. It can be configured via ifconfig(1M) and can have IP addresses assigned to it, making aliases pos-
sible.
The vni pseudo device is particularly useful in hosting an IP address when used in conjunction with the 'usesrc' ifconfig option (see
ifconfig(1M) for examples). The logical instances of the device can also be used to host addresses as an alternative to hosting them over
the loopback interface.
Multicast is not supported on this device. More specifically, the following options return an error when used with an address specified on
vni: IP_MULTICAST_IF, IP_ADD_MEMBERSHIP, IP_DROP_MEMBERSHIP, IPV6_MULTICAST_IF, IPV6_JOIN_GROUP, IPV6_LEAVE_GROUP. In addition, broadcast
is not supported.
Because there is no physical hardware configured below it, no traffic can be received through nor transmitted on a virtual interface. All
packet transmission and reception is accomplished with existing physical interfaces and tunnels. Because applications that deal with packet
transmission and reception (such as packet filters) cannot filter traffic on virtual interfaces, you cannot set up a packet filter on a
virtual interface. Instead, you should configure the policy rules to apply to the physical interfaces and tunnels, and if necessary, use
the virtual IP addresses themselves as part of the rule configuration. Also, note that the virtual interface cannot be part of an IP multi-
pathing (IPMP) group.
FILES
/dev/vni
64-bit ELF kernel driver
SEE ALSO ifconfig(1M), in.mpathd(1M), ip(7P), ip6(7P)SunOS 5.10 18 July 2004 vni(7d)
01-16-2020
