Unable to connect VIO client

10 More Discussions You Might Find Interesting

1. AIX

Need to replace a broken PV in a VIO VG used for client LPARs (and it won't release the old one)

I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is...

2. AIX

Chef client on VIOs? How do you manage your VIO configs?

I know the VIOs are generally to be treated as an appliance and one should never drop down to oem_setup_env. In reality however, oem is a very useful tool to get the job done. So that leads me into the question of using the Chef client on a VIO. Currently a big push to manage all our *nix...

3. Linux

Unable to connect to Server machine from a client machine using ftp service

Hi, Could you please help me with the below issue.. I'm running RHEL6 OS on both server (192.168.0.10) and client machines (192.168.0.1). I'm trying to connect to server from the client machine using ftp service. I have installed vsftpd daemon on both the machines. I'm getting...

4. AIX

cdrom confusion on the vio client lpar

Hi In my vio server I have the below output $ lsvopt | grep -i SAPSITGS sapsitgs_cdrom TL12UP.iso 3182 In my vio client lpar I have the below output root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server cd1...

5. AIX

vio server ethernet to vio client ethernet(concepts confusing)

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...

6. AIX

how will i know if a lun has been already mapped to a vio client

Hi im logged in to the vio servers now. when i give # lspv | wc -l i get the count as 6246 how will i know if a lun has been already mapped to a vio client or it is left free without mapping to any of the vio client ?

7. AIX

Possible to connect a LPAR to two different VIO's?

Just a question which may seem dumb to some out there, but then again I am not a super technie so that's my excuse. Is it possible to say provision a test AIX LPAR (has a 10gb boot lun and 20gb data) under a VIO which has connectivity to SAN Array A so it can see the disks provisioned to it,...

8. AIX

Finding cpu information on vio client

Hi, I am having single p series blade with Single Physcial CPU with dual core, on that vio server is installed, I have created vio client allocate 0.9 each cpu , now when I am running prtconf command on vio client it is showing "2" no of processor, My query using which command it will...

9. AIX

rebooting vio client

Hi, I would like to reboot vio client but I am not able to access vio client(I am not able to get putty) , I am able to get putty of vio server, is there any command by using which from vio server I can reboot vio client?

10. AIX

vio server and vio client

Hi, I want to know wheather partition size for installation of vio client can be specified on vio server example If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while...

LEARN ABOUT DEBIAN

ipsec__updown

_UPDOWN(8)							  [FIXME: manual]							_UPDOWN(8)

NAME

       ipsec__updown - kernel and routing manipulation script

SYNOPSIS

       _updown is invoked by pluto when it has brought up a new connection. This script is used to insert the appropriate routing entries for
       IPsec operation on some kernel IPsec stacks, such as KLIPS and MAST, and may do other necessary work that is kernel or user specific, such
       as defining custom firewall rules. The interface to the script is documented in the pluto man page.

VARIABLES

       The _updown is passed along a number of variables which can be used to act differently based on the information:

       PLUTO_VERSION
	   indicates what version of this interface is being used. This document describes version 1.1. This is upwardly compatible with version
	   1.0.

       PLUTO_VERB
	   specifies the name of the operation to be performed, which can be one of prepare-host, prepare-client, up-host, up-client, down-host or
	   down-client. If the address family for security gateway to security gateway communications is IPv6, then a suffix of -v6 is added to
	   this verb.

       PLUTO_CONNECTION
	   is the name of the connection for which we are routing.

       PLUTO_NEXT_HOP
	   is the next hop to which packets bound for the peer must be sent.

       PLUTO_INTERFACE
	   is the name of the ipsec interface to be used.

       PLUTO_ME
	   is the IP address of our host.

       PLUTO_MY_CLIENT
	   is the IP address / count of our client subnet. If the client is just the host, this will be the host's own IP address / max (where max
	   is 32 for IPv4 and 128 for IPv6).

       PLUTO_MY_CLIENT_NET
	   is the IP address of our client net. If the client is just the host, this will be the host's own IP address.

       PLUTO_MY_CLIENT_MASK
	   is the mask for our client net. If the client is just the host, this will be 255.255.255.255.

       PLUTO_PEER
	   is the IP address of our peer.

       PLUTO_PEER_CLIENT
	   is the IP address / count of the peer's client subnet. If the client is just the peer, this will be the peer's own IP address / max
	   (where max is 32 for IPv4 and 128 for IPv6).

       PLUTO_PEER_CLIENT_NET
	   is the IP address of the peer's client net. If the client is just the peer, this will be the peer's own IP address.

       PLUTO_PEER_CLIENT_MASK
	   is the mask for the peer's client net. If the client is just the peer, this will be 255.255.255.255.

       PLUTO_MY_PROTOCOL
	   lists the protocols allowed over this IPsec SA.

       PLUTO_PEER_PROTOCOL
	   lists the protocols the peer allows over this IPsec SA.

       PLUTO_MY_PORT
	   lists the ports allowed over this IPsec SA.

       PLUTO_PEER_PORT
	   lists the ports the peer allows over this IPsec SA.

       PLUTO_MY_ID
	   lists our id.

       PLUTO_PEER_ID
	   lists our peer's id.

       PLUTO_PEER_CA
	   lists the peer's CA.

SEE ALSO

       ipsec(8), ipsec_pluto(8).

HISTORY

       Man page written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Michael Richardson. Original program written by Henry
       Spencer.

[FIXME: source] 						    10/06/2010								_UPDOWN(8)

AIX