SUMMARY: rc.config

From: Urey, Dawn (UreyD_at_pginw.com)
Date: 02/19/04

  • Next message: Joe Evans: "SUMMARY: Stale paths"
    Date: Thu, 19 Feb 2004 10:39:37 -0500
    To: 'Tru64 Managers' <tru64-unix-managers@ornl.gov>
    
    

    Thanks for all of the responses.

    The general consensus is, "if it's not broken, don't fix it".

    Apparently, when the cluster is established, it assigns NETDEV_0="tu0".
    When you run clu_add_member, it sets NETDEV_0="ics0".

    Thanks to Dr. Blinn for this answer:

    If I were changing it, I'd list the physical hardware interface (in this
    case, "tu0" on both systems) first, not the logical name used by TruCluster
    (the "ics0" on both systems). But I checked my V5.1B cluster, and it's the
    same way, the node that was installed first has NETDEV_0="tu0" and the node
    that was added with clu_add_member has NETDEV_1="tu0" (and reflexively for
    the "ics0"), and it works just fine.

    So my advice is, it isn't broken, don't try to fix it.

    -----Original Message-----
    From: Urey, Dawn
    Sent: Thursday, February 19, 2004 10:12 AM
    To: 'Tru64 Managers'
    Subject: rc.config

    All:
     
    I have 2 separate Truclusters. Both are running 5.1A patchkit 5. On one of
    the clusters, the rc.config lists
     
    NETDEV_0="isc0'"
    NETDEV_1="tu0"
     
    On the other cluster, rc.config lists
     
    NETDEV_0="tu0"
    NETDEV_1="ics0"
     
     
    Does the way the network devices are defined cause any performance issues?
    Should ics0 be NETDEV_0?
     
    Thanks,
     
    Dawn
     
    Dawn Urey
    PGI
    Systems and Site Support Manager
    (919)874-9512
     

    ------------ PGI Internet E-mail Confidentiality ------------ Please note:
    This message may contain information which is privileged and confidential.
    If you are not the intended recipient, you are hereby notified that any
    dissemination, distribution or copying of this communication is strictly
    prohibited. If you believe you have received this message in error, please
    forward to Postmaster@pginw.com.

    ------------ Confidencialidad de Correo Electronico de PGI ------------
    Nota: Este mensaje puede contener informacion privilegiada y confidencial.
    Si usted no es el destinatario, esta notificado que cualquier diseminacion,
    distribucion o copia de esta comunicacion esta estrictamente prohibida. Si
    usted cree que ha recibido este mensaje por error, por favor reenvielo a
    Postmaster@pginw.com. (Informacion intencionalmente sin acentos)


  • Next message: Joe Evans: "SUMMARY: Stale paths"

    Relevant Pages

    • rc.config
      ... the clusters, the rc.config lists ... On the other cluster, rc.config lists ... Este mensaje puede contener informacion privilegiada y confidencial. ... Si usted no es el destinatario, esta notificado que cualquier diseminacion, ...
      (Tru64-UNIX-Managers)
    • Re: Xorg-6.8.1 +glib +i810 +FreeBSD4.11-STABLE
      ... or switching back to Xfree. ... have bitten the bullet and am downgrading to 6.7.0. ... I intend to keep an eye on the lists and see what happens - I'm sure ... the port maintainers will work their magic and fix the ...
      (freebsd-questions)
    • Re: 2.6.4-mm1
      ... > with is in getting a really reliable fsyncacross the page lists while ... > - Various little fixes as usual. ... > iSeries device number fix ... > nfs: Remove an unnecessary spinlock from XID generation... ...
      (Linux-Kernel)
    • RE: Cannot Add To Library
      ... It still only lists ... > posting my fix here for anyone who may need it. ... > in folders with that attribute. ... > then type in cd "music" and hit Enter. ...
      (microsoft.public.windowsmedia.player)
    • Re: FreeBSD 5.3-BETA6 available
      ... me on all replies, I'm not on all lists. ... >>information about migrating to BIND9. ... FIX IS AVAILABLE, bug has been open for many months, has ... NIS is still faulty in pretending users aren't there when in fact NIS ...
      (freebsd-current)