Thank for your suggestion. I remove the IP from physical adapter, create new virtual adapter with "shared ethernet adapter".
Run again the command:
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 DEBIAN
ipsec_tncfg
IPSEC_TNCFG(5) [FIXME: manual] IPSEC_TNCFG(5)NAME
ipsec_tncfg - lists IPSEC virtual interfaces attached to real interfaces
SYNOPSIS
ipsec tncfg
cat/proc/net/ipsec_tncfg
OBSOLETE
Note that tncfg is only supported on the classic KLIPS stack. It is not supported on any other stack and will be completely removed in
future versions. A replacement command still needs to be designed
DESCRIPTION
/proc/net/ipsec_tncfg is a read-only file which lists which IPSEC virtual interfaces are attached to which real interfaces, through which
packets will be forwarded once processed by IPSEC.
Each line lists one ipsec I/F. A table entry consists of:
+
an ipsec virtual I/F name
+
a visual and machine parsable separator '->', separating the virtual I/F and the physical I/F,
+
a physical I/F name, to which the ipsec virtual I/F is attached or NULL if it is not attached,
+
the keyword mtu=,
+
the MTU of the ipsec virtual I/F,
+
the automatically adjusted effective MTU for PMTU discovery, in brackets,
+
a visual and machine parsable separator '->', separating the virtual I/F MTU and the physical I/F MTU,
+
the MTU of the attached physical I/F.
EXAMPLES
ipsec2 -> eth3 mtu=16260(1443) -> 1500
shows that virtual device ipsec2 with an MTU of 16260 is connected to physical device eth3 with an MTU of 1500 and that the effective MTU
as a result of PMTU discovery has been automatically set to 1443.
ipsec0 -> wvlan0 mtu=1400(16260) -> 1500
shows that virtual device ipsec0 with an MTU of 1400 is connected to physical device wvlan0 with an MTU of 1500 and no PMTU packets have
gotten far enough to bump down the effective MTU from its default of 16260.
ipsec3 -> NULL mtu=0(0) -> 0
shows that virtual device ipsec3 is not connected to any physical device.
FILES
/proc/net/ipsec_tncfg, /usr/local/bin/ipsec
SEE ALSO ipsec(8), ipsec_manual(8), ipsec_eroute(5), ipsec_spi(5), ipsec_spigrp(5), ipsec_klipsdebug(5), ipsec_tncfg(8), ipsec_version(5),
ipsec_pf_key(5)HISTORY
Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Richard Guy Briggs.
[FIXME: source] 10/06/2010 IPSEC_TNCFG(5)