Very Computer

I have 2 indigo-2 on my network running 4.05H. "rup" does not 'see'
any other machines on the network nor do any other machines 'see'
the 2 indigos when executing the same command. Also , the 2 indigos
can only see the global location broker on thier own machine , not
across the network. Is this an indication of a low level ethernet
problem or an application level bug on the indigos running 4.05H ?

--
------------------------------------------------------------------
- Fletcher Karl Robinson       |            Phone : 310 332 0489 -
- Computer Engineer Specialist |                                 -
- Department T213/85           |              Fax : 310 332 5962 -
- Aircraft Division            |                                 -
- Northrop Corporation         |            Email :              -
- One Northrop Avenue          |                                 -

------------------------------------------------------------------

| I have 2 indigo-2 on my network running 4.05H. "rup" does not 'see'
| any other machines on the network nor do any other machines 'see'
| the 2 indigos when executing the same command. Also , the 2 indigos
| can only see the global location broker on thier own machine , not
| across the network. Is this an indication of a low level ethernet
| problem or an application level bug on the indigos running 4.05H ?

405H is the IOP with all the ethernet fixes for Indigo, so I doubt
that is your problem.  Does everything else seem to work
(network-wise)?  I don't know enough about glb to know if running
it locally keeps products from seeing other brokers or not.

Could you have somehow configured your systems to have non-standard
broadcast addresses?  What does 'ifconfig ec0' show on all of
them?
--

The most beautiful things in the world are              |   Dave Olson
those from which all excess weight has been             |   Silicon Graphics

|>
|> | I have 2 indigo-2 on my network running 4.05H. "rup" does not 'see'
|> | any other machines on the network nor do any other machines 'see'
|> | the 2 indigos when executing the same command. Also , the 2 indigos
|> | can only see the global location broker on thier own machine , not
|> | across the network. Is this an indication of a low level ethernet
|> | problem or an application level bug on the indigos running 4.05H ?
|>
|> 405H is the IOP with all the ethernet fixes for Indigo, so I doubt
|> that is your problem.  Does everything else seem to work
|> (network-wise)?  I don't know enough about glb to know if running
|> it locally keeps products from seeing other brokers or not.
|>
|> Could you have somehow configured your systems to have non-standard
|> broadcast addresses?  What does 'ifconfig ec0' show on all of
|> them?
|> --
|>
|> The most beautiful things in the world are              |   Dave Olson
|> those from which all excess weight has been             |   Silicon Graphics

...There is another problem with the ethernet , 'pinging' to or
from either of the indigo-2 from or to any other machine reveals
random timing responses in the range of 0msec to over 2000msec.

ifconfig ec0 shows : inet 128.99.27.23 netmask 0xffffff00
                     broadcast 128.99.27.255.

--
------------------------------------------------------------------
- Fletcher Karl Robinson       |            Phone : 310 332 0489 -
- Computer Engineer Specialist |                                 -
- Department T213/85           |              Fax : 310 332 5962 -
- Aircraft Division            |                                 -
- Northrop Corporation         |            Email :              -
- One Northrop Avenue          |                                 -

------------------------------------------------------------------

| ...There is another problem with the ethernet , 'pinging' to or
| from either of the indigo-2 from or to any other machine reveals
| random timing responses in the range of 0msec to over 2000msec.

Sounds like you have a broken bridge or router in the path then.
You might want to try ping -R to see if strange routes are being
used.  traceroute might also be interesting, if you installed it.

| ifconfig ec0 shows : inet 128.99.27.23 netmask 0xffffff00
|                      broadcast 128.99.27.255.

Looks reasonable, assuming that you have subnet'ed your class B net.
--

The most beautiful things in the world are              |   Dave Olson
those from which all excess weight has been             |   Silicon Graphics