Sponsored Content
Full Discussion: Network Problem
Operating Systems AIX Network Problem Post 302461759 by lordofdarkness on Tuesday 12th of October 2010 07:13:03 AM
Old 10-12-2010
Error Network Problem

Hi everbody;
I have 2 p520 machines and created a vio server for each one (vio01 - vio02). I created 3 AIX 5.3 lpars on vio02 and 3 AIX 6.1 lpars on vio01. The problem is when 2 lpars are activated, i can ping gateway from both lpars and vio; but when i activate 3rd lpar, network downs and none of the lpars can ping the gateway. I have the same problem in vio02. I use only one physical network adapter and created shared ethernet adapter for lpars with same VLAN ID. Is there any limitations to use same shared ethernet? If yes how can i solve this problem? If not what can be the problem?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Network problem Unix

Changed from a broken Switch to a working HUB everyting else in my network is ok after the change but not my RS/6000! It refuses to get connected, get time out on Pings both ways - strange? Could it be some problem with ARP?:confused: (2 Replies)
Discussion started by: jolun
2 Replies

2. Solaris

Network problem.

Hi All, This is regarding problem with two servers... EX:- server1(HP) is not able to connect with proxy server server2(SUN BOX) But we can able to login.... server1 is not able to pickup any data from the proxy server... checked in the sunbox... # ping bdhp5050 server1 is alive ... (1 Reply)
Discussion started by: jeelans
1 Replies

3. SCO

Network interfaces problem

Hi, I have problems with my SCO unix network interfaces. Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot. Installed driver using SCO Software manager - successfully Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies

4. AIX

network printer problem

I have AIX 5.3 OS. After issuing the print command, the printer state immediately goes down. I have checked the /etc/qconfig flle, resatrted the qdaemon but again same problem is occuring. I am using HP 5100 connected to jetdirect. what is the problem and it's solution? (4 Replies)
Discussion started by: prashantchavan
4 Replies

5. IP Networking

Network problem

Folks; I have 2 SUSE servers (192.168.157.100 & 192.168.157.101) both are similar and has the same gateway 192.168.157.1 I can connect to the second one from my PC just fine (192.168.157.101). The problem is i couldn't connect to the first one using SSH even after i disabled the firewall. when i... (3 Replies)
Discussion started by: Katkota
3 Replies

6. Solaris

Problem in network configuration

Hi everybody, I have a very strange problem ; if somebody could help me it would be very kind. I'll try to explain my problem. I have 2 unix machines absolutely identical running solaris 9. For network reasons I need to change the IP address of the 2 machines. I proceed exactly the same on the... (11 Replies)
Discussion started by: aribault
11 Replies

7. AIX

AIX OS problem? network problem?

Dear ALL. I installed AIX OS on customer sites. but Only one site is too slow when I connected telnet, ftp.. Ping is too fast. but telnet and FTP is not connected.. of course i check the configuration file on aix but it's normal. Do any Idea?? thanks in advance. - Jun - (3 Replies)
Discussion started by: Jeon Jun Seok
3 Replies

8. Solaris

Network interface problem

Hi i have replace a NIC card on solaris 10 when i give the following command ifconfig -a it just show the lo0 (only loop back with inet 127.0.0.1) when i give the following command to config the interface, ifconfig elxl0 plumb ifconfig: plumb: elxl0: no such interface please help... (11 Replies)
Discussion started by: malikshahid85
11 Replies

9. Debian

/etc/network/interfaces problem

Hello i am configuring a debian lenny sever ,/etc/network/interfaces is modified so that eth1 takes a static IP address then i save it wq! then i restart the networking , /etc/init.d/networking restart . but after reboot ,the file is reset ,note that the interfaces had by defauklt IPv6 address... (5 Replies)
Discussion started by: learn82
5 Replies

10. Android

Problem with wireless network

Good day, everybody! I have a mobile phone (LG Optimus L5) with Android 4.0.3 and a tablet (PocketBook SurfPad 2) with Android 4.1.1 and I have problem with wireless network on these devices. Laptops don't have such problem. My wireless network organisation is a modem connected with an access point... (11 Replies)
Discussion started by: qzxcvbnm
11 Replies
qmail-queue(8)						      System Manager's Manual						    qmail-queue(8)

NAME
qmail-queue - queue a mail message for delivery SYNOPSIS
qmail-queue DESCRIPTION
qmail-queue reads a mail message from descriptor 0. It then reads envelope information from descriptor 1. It places the message into the outgoing queue for future delivery by qmail-send. The envelope information is an envelope sender address followed by a list of envelope recipient addresses. The sender address is preceded by the letter F and terminated by a 0 byte. Each recipient address is preceded by the letter T and terminated by a 0 byte. The list of recipient addresses is terminated by an extra 0 byte. If qmail-queue sees end-of-file before the extra 0 byte, it aborts without placing the message into the queue. Every envelope recipient address should contain a username, an @ sign, and a fully qualified domain name. qmail-queue always adds a Received line to the top of the message. Other than this, qmail-queue does not inspect the message and does not enforce any restrictions on its contents. However, the recipients probably expect to see a proper header, as described in qmail-header(5). Programs included with qmail which invoke qmail-queue will invoke the contents of $QMAILQUEUE instead, if that environment variable is set. FILESYSTEM RESTRICTIONS
qmail-queue imposes two constraints on the queue structure: each mess subdirectory must be in the same filesystem as the pid directory; and each todo subdirectory must be in the same filesystem as the intd directory. EXIT CODES
qmail-queue does not print diagnostics. It exits 0 if it has successfully queued the message. It exits between 1 and 99 if it has failed to queue the message. All qmail-queue error codes between 11 and 40 indicate permanent errors: 11 Address too long. 31 Mail server permanently refuses to send the message to any recipients. (Not used by qmail-queue, but can be used by programs offering the same interface.) All other qmail-queue error codes indicate temporary errors: 51 Out of memory. 52 Timeout. 53 Write error; e.g., disk full. 54 Unable to read the message or envelope. 55 Unable to read a configuration file. (Not used by qmail-queue.) 56 Problem making a network connection from this host. (Not used by qmail-queue.) 61 Problem with the qmail home directory. 62 Problem with the queue directory. 63 Problem with queue/pid. 64 Problem with queue/mess. 65 Problem with queue/intd. 66 Problem with queue/todo. 71 Mail server temporarily refuses to send the message to any recipients. (Not used by qmail-queue.) 72 Connection to mail server timed out. (Not used by qmail-queue.) 73 Connection to mail server rejected. (Not used by qmail-queue.) 74 Connection to mail server succeeded, but communication failed. (Not used by qmail-queue.) 81 Internal bug; e.g., segmentation fault. 91 Envelope format error. SEE ALSO
addresses(5), envelopes(5), qmail-header(5), qmail-inject(8), qmail-qmqpc(8), qmail-send(8), qmail-smtpd(8) qmail-queue(8)
All times are GMT -4. The time now is 06:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy