Sponsored Content
Full Discussion: Wpar network,i'm confused
Operating Systems AIX Wpar network,i'm confused Post 302937672 by Linusolaradm1 on Saturday 7th of March 2015 02:43:05 PM
Old 03-07-2015
Quote:
Originally Posted by agent.kgb
you have to write routing table. look at smitty mkroute
I have tried manually
Setting ip for wpar

Code:
chwpar -N address=192.168.4.76 interface=en0 netmask=255.255.255.0 ibmunix2

Then add route

Code:
 chwpar -i -I rtdest=192.168.4.0  rtnetmask=255.255.255.0 rtgateway=192.168.0.44 rtinterface=en0 ibmunix2

Code:
chwpar -i -I rtdest=192.168.0.0  rtnetmask=255.255.255.0 rtgateway=192.168.0.44 rtinterface=en0 ibmunix2

192.168.0.44 is the address of host wpar
i tried also 192.168.0.1 wich is the router but
doesn't work,the ping for 192.168.0.0/24 are dropped
and outside(4.4.4.4 or any internet address) said "network unreachable"
Where is wrong?
 

10 More Discussions You Might Find Interesting

1. 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... (5 Replies)
Discussion started by: mrbig1492
5 Replies

2. 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 #... (0 Replies)
Discussion started by: avazeer
0 Replies

3. 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:... (0 Replies)
Discussion started by: 03sep2011
0 Replies

4. 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.. ... (4 Replies)
Discussion started by: ppchu99
4 Replies

5. 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 Replies)
Discussion started by: aix_admin_007
7 Replies

6. UNIX for Advanced & Expert Users

LPAR,DLPAR and WPAR

Can anyone please let know difference between LPAR/DLPAR/WPAR. and its purpose ??? (3 Replies)
Discussion started by: Pavithran
3 Replies

7. AIX

Versioned WPAR's

Hi everybody. is anyone using versioned WPAR's? Has anyone clustered them with PowerHA? Please share your experience. Regards, firefox (7 Replies)
Discussion started by: firefox111
7 Replies

8. 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 Replies)
Discussion started by: The Doctor
4 Replies

9. 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... (0 Replies)
Discussion started by: TomR
0 Replies

10. 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 Replies)
Discussion started by: sandra25350
2 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 11:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy