Re: lo0 network interface

From: Miller, Dave (I.S.) (Dave.Miller_at_BHS.ORG)
Date: 05/11/05

  • Next message: Steve Stamper: "Re: lo0 network interface"
    Date:         Wed, 11 May 2005 14:32:54 -0400
    To: aix-l@Princeton.EDU
    
    

    Its not, but that might be a clue. Thanks. -----Original Message----- From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of Justin Bleistein Sent: Wednesday, May 11, 2005 2:25 PM To: aix-l@Princeton.EDU Subject: Re: lo0 network interface Is this a TSM client by any chance running on the same physical server as the tsm server? I do a way to configure that in the "dsm.sys" client config file, is to have the backup traffic go through the loopback interface, if they're on the same server, rather then using shared memory. Thanks. --Justin Richard Bleistein AIX Systems Administrator "Miller, Dave (I.S.)" <Dave.Miller@BHS.ORG> Sent by: IBM AIX Discussion List <aix-l@Princeton.EDU> 05/11/2005 02:03 PM Please respond to IBM AIX Discussion List <aix-l@Princeton.EDU> To aix-l@Princeton.EDU cc Subject lo0 network interface Can anyone give me some insight as to where all of the lo0 activity would be coming from in the nmon stats below? Thanks. Network I/O I/F Name Recv=KB/s Trans=KB/s packin packout insize outsize Peak->Recv Trans en0 1638.4 760.1 2396.3 1520.7 700.1 511.8 2344.2 2728.7 en1 0.2 0.1 2.7 0.9 64.4 118.0 0.9 0.5 en2 279.0 528.5 942.5 1073.2 303.2 504.2 661.6 696.1 en3 71.0 0.0 1578.6 1148.6 46.0 0.0 154.2 42299.8 lo0 21587.4 21583.2 2405.9 2405.6 9187.9 9187.4 51129.7 51123.5 _____ CONFIDENTIALITY NOTICE: This email communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at (413) 794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health System's privacy policy, please visit our Internet web site at http://www.baystatehealth.com. NOTICE: This communication may contain confidential, proprietary or legally privileged information. It is intended only for the person(s) to whom it is addressed. If you are not an intended recipient, you may not use, read, retransmit, disseminate or take any action in reliance upon it. Please notify the sender that you have received it in error and immediately delete the entire communication, including any attachments. Towers Perrin does not encrypt and cannot ensure the confidentiality or integrity of external e-mail communications and, therefore, cannot be responsible for any unauthorized access, disclosure, use or tampering that may occur during transmission. This communication is not intended to create or modify any obligation, contract or warranty of Towers Perrin, unless the firm clearly expresses such an intent. ----------------------------------------- CONFIDENTIALITY NOTICE: This email communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at (413) 794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health System's privacy policy, please visit our Internet web site at http://www.baystatehealth.com.


  • Next message: Steve Stamper: "Re: lo0 network interface"

    Relevant Pages

    • Re: TSO region size
      ... NOTICE OF CONFIDENTIALITY ... This communication including any information transmitted with it is ... If you are not an intended recipient or responsible for delivering ... Ce courriel, ainsi que tout renseignement ci-inclus, destiné ...
      (bit.listserv.ibm-main)
    • SUMMARY: Cant boot a V440 from Solaris 9 cd kit
      ... This communication may contain privileged and/or confidential ... It is intended solely for the use of the addressee. ... not the intended recipient, you are strictly prohibited from disclosing, ... receipt and/or confidentiality. ...
      (SunManagers)
    • please help
      ... CONFIDENTIALITY NOTICE: This message is intended for only the use of the ... applicable law. ... If the reader of this message is not the intended recipient, ... copying of this communication is strictly prohibited. ...
      (alt.games.warcraft)
    • RE: Web bots - blocking the bad
      ... > robots scanning our site. ... > CONFIDENTIALITY NOTICE: This message is intended only for the ... > delivering the message to the intended recipient, ... > copying this communication, or admitting to take any action ...
      (Security-Basics)
    • Re: System crash
      ... immediately by replying "Received in error" and immediately delete ... to its intended recipient, you are hereby notified that any ... distribution or copying of this communication is strictly prohibited. ... message and all its attachments. ...
      (RedHat)