Wpar network,i'm confused

10 More Discussions You Might Find Interesting

1. AIX

Error doing clogin into a wpar

I have this error when I'm trying to do clogin from AIX 7200-00-00-0000 into a wpar with AIX 5.2 abanksPaDesa2:/> clogin AbanksBDPA_wpar exec: A file or directory in the path name does not exist somebody can help me to fix this? I'm restoring the wpar from wpar mksysb not a mksysb from...

2. AIX

No iscsi available in newly created AIX wpar

AIX 7.1 New to WPAR, hopefully just missing something simple here. Creating the WPAR like this..... (The box where the WPAR is hosted does have an iscsi protocol device) mkwpar -h wpar08 -l -n wpar08 -N interface=en0 address=xxx.xx.xx.xxx netmask=255.255.255.0 -D devname=/dev/iscsi0 -D...

3. AIX

How to Load a CICS IPC Kernel Extension in a versioned "rootvg" WPAR ?

Anyone running CICS TX in a WPAR ? In my attempts to run CICS TX 5.1.0.1 in a WPAR..... CICS fails to start due to unable to load a CICS IPC Kernel Extension. The Kernel Extension is 64 bit (so not a 32 vs 64 bit issue). Base system/LPAR is Power8 and AIX 7.1 TL3 SP5. WPAR is versioned...

4. AIX

Versioned WPAR's

Hi everybody. is anyone using versioned WPAR's? Has anyone clustered them with PowerHA? Please share your experience. Regards, firefox

5. UNIX for Advanced & Expert Users

LPAR,DLPAR and WPAR

Can anyone please let know difference between LPAR/DLPAR/WPAR. and its purpose ???

6. Shell Programming and Scripting

WPAR monitoring shell script suggestions needed

Hi All, This is for WPAR monitoring shell script, earlier opened thread was closed, had to open a new thread, as suggested I have used script as below, But am trying to get the output in below format, need suggestions with it. Below is the lswpar output, required output format. ...

7. AIX

Virtualization: WPAR vs LPAR

seems to be WPAR is quite easy to set up..without additional licenses.. If I don't need Linux and all my legacy and new apps are happy in AIX 7.1 (the latest OS), I could save all troubles and use WPAR. Can someone comment on this ?? One copy of OS to maintain, so to speak.. ...

8. AIX

Unexpected Behaviour with WPAR

Hello, We have a system running AIX 6.1.7.1. We have created a Workload Partition(wpar) on this system with wpar specific routing enabled. On wpar, we are running DNS (UDP/53) and syslog (UDP/514). en0: 1.1.1.1/255.255.255.0 NOT assigned to any wpar en1:...

9. Infrastructure Monitoring

snmpget not working on AIX shared wpar

Hi, I have a shared AIX wpar configured. I have started snmpd process on shared AIX wpar. But when i tried to query a MIB id using the following command /opt/OV/bin/snmpget -d -v 1 -c public -p <hostname> .1.3.6.1.2.1.1.7.0 i get the following error message #...

10. UNIX for Dummies Questions & Answers

Network Woes!! Please help! :confused:

Hello, We have an old Axil running SunOS Release 5.5.1. Recently, we updated our network, so the gateway and domain changed. Our network admin forgot (or didn't know) that we had this machine on the network, so it quietly lost its mind. Now we are trying to add it back to the network. He...

LEARN ABOUT HPUX

securenets

securenets(4)						     Kernel Interfaces Manual						     securenets(4)

NAME

       securenets - NIS map security file

DESCRIPTION

       The  file  defines  networks  and  hosts  that  can  access the NIS maps on a server.  Each line in the file gives a network mask and a net
       address.  For example:

       The format of the file is as follows:

       o  Lines beginning with the character are treated as comments.

       o  Lines that are not comment lines contain two fields separated by white space.  The first field is a netmask, and the second field  is  a
	  network.

       o  The netmask field can be one of the following:

	      o  255.255.255.255 (IPv4)
	      o  ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff (IPv6)
	      o  the string indicating that the second field is a specific host to be allowed access.

       The file can have any number of netmask/net pairs.

       When  is  started  on  the  server,  it	checks	for the existence of and reads its contents into memory if it exists.  must be stopped and
       restarted for any changes in to take effect.

       Upon startup, the netmask and the net address are converted to binary format and logical ANDed.	The result must equal the net address (the
       second address) to be legal.

       If  the netmask is 255.255.255.255 (all 1's in binary), any address in the net address argument will match it.  If any field in the netmask
       is 0, the corresponding field in the net address must be 0.  When used in this way, the portion of the addresses given as 0 acts as a  wild
       card.

       When  a	client attempts to bind to the server, checks the client's IP against those given in the file.	Again, the address is converted to
       binary and logical ANDed with the netmask.  The result must equal the net address given in the file.  If the client address does not  match
       any pairs in the file, the binding is refused with the message, "no such map in server's NIS domain".

       The file can be used to limit access to specific hosts or to subnets using the wildcard capability.

       If there are syntax errors in the file, messages are logged to the logging file (default and is not started.

       If a host has multiple interfaces, each interface address must be allowed in the securenets file for that host to have reliable NIS access.

EXAMPLES

       The following examples show entries for the file.

       Either of the following entries provides access only to the host with address 192.33.33.33:

	      or

       The following entry allows access by any host on the 192.33.33 subnet:

       For broader access, such as an entire enterprise, the following entry allows any host whose address begins with "15" to be served:

       Either of the following entries allows access for an individual IPv6 address:

	      or

       The following entry allows access for all IPv6 addresses starting with "fec0":

SEE ALSO

       ypserv(1M).

																     securenets(4)

AIX