Sponsored Content
Full Discussion: LPAR Networking: Can't ping
Operating Systems AIX LPAR Networking: Can't ping Post 302673097 by PPPP on Tuesday 17th of July 2012 12:30:51 PM
Old 07-17-2012
I can't ping even the default GW. You will notice it says 100% packet loss.
 

10 More Discussions You Might Find Interesting

1. AIX

LPAR and CFGMGR

I have a P570 that for some reason is not allowing the P1-T6 NIC to be recognized. I have confirmed from the HMC that it is set for the LPAR, but when I do a cfgmgr, it won't recognize it. It though is recognizing the slot cards just fine which are P1-C3 for one shelf and P1-C3 of another shelf.... (1 Reply)
Discussion started by: LegendMan
1 Replies

2. IP Networking

ping and networking

Dear friends, Please explain the functionality of the ping command and explain the network details, and IP layers. I want some more clarification about following things i) switch ii) hub iii) routers iv) proxy (3 Replies)
Discussion started by: thangappan
3 Replies

3. AIX

LPAR

I am planning for System P with 2 number of 2-core processor (4 core in total). Can I make 3 LPARS with this processor configuration without the support of micropartitioning, that means with simple LPAR only. (3 Replies)
Discussion started by: pchangba
3 Replies

4. AIX

LPAR creation

can i get a step b syep explanation in creating LPAR... i have searched for tutorials i couldn't find the right one.... (2 Replies)
Discussion started by: udtyuvaraj
2 Replies

5. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

6. Shell Programming and Scripting

Animation Ping on Solaris Like Cisco Ping

Hi, I develop simple animation ping script on Solaris Platform. It is like Cisco ping. Examples and source code are below. bash-3.00$ gokcell 152.155.180.8 30 Sending 30 Ping Packets to 152.155.180.8 !!!!!!!!!!!!!.!!!!!!!!!!!!!!!. % 93.33 success... % 6.66 packet loss...... (1 Reply)
Discussion started by: gokcell
1 Replies

7. AIX

Networking Issue (Cant Ping the gateway)

Hi, I installed AIX 7.1 on a blade though (hmc with vio). I can ping the IP address, but not the gateway. Is there anything that I should configure? Is there anything that I have to check with vio setting or Am I missing any configuration? Please let me know further. Thank you (5 Replies)
Discussion started by: pjeedu2247
5 Replies

8. Shell Programming and Scripting

How to get reason for ping failure using perls Net::Ping->new("icmp");?

Hi I am using perl to ping a list of nodes - with script below : $p = Net::Ping->new("icmp"); if ($p->ping($host,1)){ print "$host is alive.\n"; } else { print "$host is unreacheable.\n"; } $p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies

9. AIX

How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)?

There can be configurations in IBM Server wherein a standalone partition is created on some supported IBM Server Or A VIOS - VIOC LPARs created. Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..? On a... (2 Replies)
Discussion started by: Manish00712
2 Replies

10. Programming

Ping test sends mail when ping fails

help with bash script! im am working on this script to make sure my server will stay online, so i made this script.. HOSTS="192.168.138.155" COUNT=4 pingtest(){ for myhost in "$@" do ping -c "$COUNT" "$myhost" &&return 1 done return 0 } if pingtest $HOSTS #100% failed... (4 Replies)
Discussion started by: mort3924
4 Replies
VLAN(4) 						   BSD Kernel Interfaces Manual 						   VLAN(4)

NAME
vlan -- IEEE 802.1Q Virtual LAN network device SYNOPSIS
pseudo-device vlan DESCRIPTION
The vlan interface provides support for IEEE 802.1Q Virtual Local Area Networks (VLAN). This supports the trunking of more than one network on a single network interface. This is particularly useful on routers or on hosts which must be connected to many different networks through a single physical interface. To use a vlan interface, the administrator must first create the interface and then specify the VID (VLAN identifier, the first 12 bits from a 16-bit integer which distinguishes each VLAN from any others) and physical interface associated with the VLAN. This can be done by using the ifconfig(8) create, vlan, and vlanif subcommands from a shell command line or script. From within a C program, use the ioctl(2) system call with the SIOCSIFCREATE and SIOCSIFVLAN arguments. To be compatible with other IEEE 802.1Q devices, the vlan interface supports a 1500 byte MTU, which means that the parent interface will have to handle packets that are 4 bytes larger than the original Ethernet standard. Drivers supporting this increased MTU are: - drivers using the DP8390 core (such as ec(4), ne(4), we(4), and possibly others) - bge(4) - bnx(4) - ea(4) - eb(4) - epic(4) - etherip(4) - ex(4) - fxp(4) - gem(4) - hme(4) - le(4) - sip(4) - ste(4) - stge(4) - ti(4) - tl(4) - tlp(4) - vge(4) - vr(4) - wm(4) - xi(4) vlan can be used with devices not supporting the IEEE 802.1Q MTU, but then the MTU of the vlan interface will be 4 bytes too small and will not interoperate properly with other IEEE 802.1Q devices, unless the MTU of the other hosts on the VLAN are also lowered to match. EXAMPLES
The following will create interface vlan0 with VID six, on the Ethernet interface tlp0: ifconfig vlan0 create ifconfig vlan0 vlan 6 vlanif tlp0 After this set up, IP addresses (and/or other protocols) can be assigned to the vlan0 interface. All other hosts on the Ethernet connected to tlp0 which configure a VLAN and use VID six will see all traffic transmitted through vlan0. The same VLAN can be created at system startup time by placing the following in /etc/ifconfig.vlan0: create vlan 6 vlanif tlp0 SEE ALSO
ifconfig(8) HISTORY
The vlan device first appeared in NetBSD 1.5.1, and was derived from a VLAN implementation that appeared in FreeBSD and OpenBSD. BUGS
The vlan interfaces do not currently inherit changes made to the physical interfaces' MTU. BSD
December 16, 2010 BSD
All times are GMT -4. The time now is 03:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy