IP agent to work w/ FORE NIC (ATM LANE) ? - Veritas Cluster Server

This is a discussion on IP agent to work w/ FORE NIC (ATM LANE) ? - Veritas Cluster Server ; Has somebody got a FORE ATM NIC with LAN Emulation successfully to work ? We can take it offline, but onlining with the IP agent fails. We have: VCS 1.3.0, NIC is FORE ATM PCA-200EUX w/ driver 5.2.0.8 We setup ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: IP agent to work w/ FORE NIC (ATM LANE) ?

  1. IP agent to work w/ FORE NIC (ATM LANE) ?


    Has somebody got a FORE ATM NIC with LAN Emulation successfully to work ?

    We can take it offline, but onlining with the IP agent fails.

    We have: VCS 1.3.0, NIC is FORE ATM PCA-200EUX w/ driver 5.2.0.8
    We setup the NIC as a LANE client (LEC) as follows:

    # ifconfig -a
    el5: flags=843 mtu 1500
    inet 194.95.10.240 netmask ffffff00 broadcast 255.255.255.0

    # /etc/fore/elconfig show -all
    ELANs on adapter 0
    ==================
    LECS (current): c5.0079.00.000000.00000000000000a03e000001.00
    ELAN LAN type LES ATM address
    ==== ======== ===============
    => a Ethernet 39.276f.31.000112.0000.0012.0011.19409501001a.02

    /etc/VRTSvcs/conf/config/main.cf lists:

    [...]
    IP alpha_ip (
    Device = el5
    Address = "194.95.10.240"
    NetMask = "255.255.255.0"
    )
    [...]
    NIC alpha_nic (
    Enabled = 0
    Device = el5
    NetworkType = ether
    NetworkHosts = { "194.95.10.240" }
    )
    [...]

    Trying to online the service groups is successful for all dependencies but

    the IP service fails with:

    TAG_E 2001/05/15 18:57:48 VCS:10295:Initiating Online of Resource alpha_ip
    (Owner: unknown Group: alpha_sg) on System alpha2
    TAG_C 2001/05/15 18:57:48 (alpha2) VCS:135004nline:alpha_ipevice name
    (el5) could be a typo or Device (el5) is not configured : Resource will not
    go online
    TAG_C 2001/05/15 18:57:48 (alpha2) VCS:135003nline:alpha_ip:Invalid Device
    Name
    TAG_C 2001/05/15 18:57:48 (alpha2) VCS:135004nline:alpha_ipevice name
    (el5) could be a typo or Device (el5) is not configured : Resource will not
    go online

    Does the bundled agent stumble over "el5" ?
    I have no real clues where to search here.

    I'll post a solution if we find one.

    Thomas-M. Kruel
    05/5/2001

  2. Re: IP agent to work w/ FORE NIC (ATM LANE) ?

    Thomas Kruel wrote:
    >
    > Has somebody got a FORE ATM NIC with LAN Emulation successfully to work ?
    >
    > We can take it offline, but onlining with the IP agent fails.
    >
    > We have: VCS 1.3.0, NIC is FORE ATM PCA-200EUX w/ driver 5.2.0.8
    > We setup the NIC as a LANE client (LEC) as follows:
    >
    > # ifconfig -a
    > el5: flags=843 mtu 1500
    > inet 194.95.10.240 netmask ffffff00 broadcast 255.255.255.0
    >
    > # /etc/fore/elconfig show -all
    > ELANs on adapter 0
    > ==================
    > LECS (current): c5.0079.00.000000.00000000000000a03e000001.00
    > ELAN LAN type LES ATM address
    > ==== ======== ===============
    > => a Ethernet 39.276f.31.000112.0000.0012.0011.19409501001a.02
    >
    > /etc/VRTSvcs/conf/config/main.cf lists:
    >
    > [...]
    > IP alpha_ip (
    > Device = el5
    > Address = "194.95.10.240"
    > NetMask = "255.255.255.0"
    > )
    > [...]
    > NIC alpha_nic (
    > Enabled = 0
    > Device = el5
    > NetworkType = ether
    > NetworkHosts = { "194.95.10.240" }
    > )
    > [...]
    >
    > Trying to online the service groups is successful for all dependencies but
    >
    > the IP service fails with:
    >
    > TAG_E 2001/05/15 18:57:48 VCS:10295:Initiating Online of Resource alpha_ip
    > (Owner: unknown Group: alpha_sg) on System alpha2
    > TAG_C 2001/05/15 18:57:48 (alpha2) VCS:135004nline:alpha_ipevice name
    > (el5) could be a typo or Device (el5) is not configured : Resource will not
    > go online
    > TAG_C 2001/05/15 18:57:48 (alpha2) VCS:135003nline:alpha_ip:Invalid Device
    > Name
    > TAG_C 2001/05/15 18:57:48 (alpha2) VCS:135004nline:alpha_ipevice name
    > (el5) could be a typo or Device (el5) is not configured : Resource will not
    > go online
    >
    > Does the bundled agent stumble over "el5" ?
    > I have no real clues where to search here.
    >
    > I'll post a solution if we find one.
    >
    > Thomas-M. Kruel
    > 05/5/2001


    The network hosts attribute should not be set to the failover IP. Here
    is what the docs say about network host:

    List of hosts on the network that will be pinged to determine if the
    network connection is alive. The IP address of the host should be
    entered instead of the HostName to prevent the monitor from
    timing out (DNS problems can cause the ping to hang); for
    example, 166.96.15.22. If this optional attribute is not specified,
    the monitor will test the NIC by pinging the broadcast address on
    the NIC. If more than one network host is listed, the monitor will
    return online if at least one of the hosts is alive.

    While this is not the problem your having it's not a good
    configuration. The Network host should be set to devices or machines
    which will always be present on the network, it's also recommended you
    use more then one IP.

    Looking at ifconfig -a for an hme card:

    hme0: flags=863 mtu 1500
    inet 10.133.50.100 netmask ff000000 broadcast 10.255.255.255
    ether 8:0:20:b3:4f:c9

    Then looking at the script in /opt/VRTSvcs/bin/IP/online

    ....
    sub TestDeviceUp {
    my(%interfaceTable);
    my($line,$count, $devname, $ret_val);
    my($hash_key);
    $ret_val = 0;
    $devname = $_[0];
    $line = "";
    $count = 0;
    open(IFCONFIG,"$ifconfig -a | $grep -v ether 2> /dev/null |");
    ...

    We can see it's looking for "ether" from the ifconfig, I don't see an
    "ether" in the ifconfig -a with el5. Was the output shorted or is that
    exactly how it is?

    Bill Borsari

    ** any opinions expressed are my own and not of my employer **

  3. Re: IP agent to work w/ FORE NIC (ATM LANE) ?


    Dear Mr.Borsari,

    thanks for the answer.

    >While this is not the problem your having it's not a good
    >configuration. The Network host should be set to devices or machines
    >which will always be present on the network, it's also recommended you
    >use more then one IP.
    >

    Well, this is certainly true in an Ethernet world. Here you have
    multiple IP adresses bound to one interface, while the main IP
    address is typically bound to say hme0. The main IP should not
    be used for service groups.

    In an ATM world, you have principally the same. But if the IP
    addresses are in different IP subnets, one typically has
    different LEC interfaces pointing into different ELANs.

    In our case we have e.g.:

    - el6 -> ELAN core (backbone interface, always up)
    - el5 -> ELAN a (service group A, normally up on this host)
    - el10 -> ELAN b (service group B, normally down on this host)

    You can't have el6:1 pointing to ELAN a.

    That's the reason why it does not work in ATM LANE.



    >Looking at ifconfig -a for an hme card:
    >
    >hme0: flags=863 mtu 1500
    > inet 10.133.50.100 netmask ff000000 broadcast 10.255.255.255
    > ether 8:0:20:b3:4f:c9
    >
    >Then looking at the script in /opt/VRTSvcs/bin/IP/online
    >
    >....
    >sub TestDeviceUp {
    > my(%interfaceTable);
    > my($line,$count, $devname, $ret_val);
    > my($hash_key);
    > $ret_val = 0;
    > $devname = $_[0];
    > $line = "";
    > $count = 0;
    > open(IFCONFIG,"$ifconfig -a | $grep -v ether 2> /dev/null |");
    > ...
    >
    >We can see it's looking for "ether" from the ifconfig, I don't see an
    >"ether" in the ifconfig -a with el5. Was the output shorted or is that
    >exactly how it is?
    >


    The output is shortened. "ether" is the MAC address line only.

    No, the real problem with the online script as shipped per default
    is the following sequence:
    #
    # The address is not set anywhere. Assign it to the first available
    # alias.
    $AliasNum = GetAliasNum($Device);
    $ActiveDevice = sprintf "%s:%s",$Device,$AliasNum;
    # -----
    [...]
    #
    # Do the ifconfig
    #
    system ("$ifconfig $ActiveDevice inet $Address netmask $Netmask $Options
    up");


    Thus ifconfig _always_ operates on $ActiveDevice, which is
    _always_ a subinterface (note the ":").

    From a view of Ethernet the philosophy of using subinterfaces
    _only_ for service groups is perfectly valid.

    From the philosophy of ATM, it does not work in general.

    --

    We're probably going to write a modified agent or try to dig out
    if Veritas consulting sells one (rumors say they do so).

    I'll be back with more info soon.

    Thomas-Martin Kruel
    5/16/2001

    ---

    Max-Born-Institut fuer Nichtlineare Optik und Kurzzeitspektroskopie
    Max-Born-Strasse 2A, D-12489 Berlin, Germany
    Leiter EDV - Thomas-Martin Kruel
    mailto: kruel@mbi-berlin.de Tel. +49 30 / 6392-1540, Fax. -1509
    Tel. +49 170 / 9247 486 (mobile)
    Support: http://www.mbi-berlin.de/edv
    mailto: support@mbi-berlin.de Tel. -1555, Pager: alarm@mbi-berlin.de




    >Bill Borsari
    >
    >** any opinions expressed are my own and not of my employer **



  4. Re: IP agent to work w/ FORE NIC (ATM LANE) (solved)


    In the meanwhile, we digged into the problem a little bit deeper.

    The answer is:

    1. Veritas sales channel claims to have a commercial grade agent, which

    unfortunately not up-to-date with the current version of VCS (1.3.0 at
    the time of this writing).
    ...still checking if it can be made available ...
    Cost: around 5000 EUR / node

    2. In meantime (couldn't afford to wait) we wrote our own.
    It's available as a standard Solaris package suitable for
    pkgadd installation.
    It does not require the use of subinterfaces aka qfe0:1,
    but relies on the existence of LEC interfaces like el1 etc.

    We've tested it on the 4-way-cluster and will go into
    production with it.

    You can get it from ftp://ftp.mbi-berlin.de/pub/mbi/MBIvcsip.tar.gz

    Thomas-Martin Kruel
    ---

    Max-Born-Institut fuer Nichtlineare Optik und Kurzzeitspektroskopie
    Max-Born-Strasse 2A, D-12489 Berlin, Germany
    Thomas-Martin Kruel - Computers & Network
    mailto: kruel@mbi-berlin.de Tel. +49 30 / 6392-1540, Fax. -1509
    Tel. +49 170 / 9247 486 (mobile)
    Support: http://www.mbi-berlin.de/edv
    mailto: support@mbi-berlin.de Tel. -1555, Pager: alarm@mbi-berlin.de


+ Reply to Thread