|
> I can configure (netsetup) the card and can ping itself.
You'll always be able to ping you're local interfaces if they're UP
because those packets are "looped back" through the loopback driver.
More interesting info would be the ping of a remote node on that
Ethernet segment (which obviously fails, hence the note). Just a note:
bringing up the interface won't necessarily update you're routing
tables to use it, this is why scripts like netsetup always ask if you
want to restart network services (recommended).
For example, I just brought up my 100MB Ethernet here, but didn't restart
the network, it's using the old route.
--> traceroute fastcondor
traceroute to fastcondor.zk3.dec.com (16.141.160.8), 30 hops max, 40 byte
packets
1 albacorefddi (16.141.128.1) 1 ms 1 ms 1 ms
2 fastcondor (16.141.160.8) 2 ms 1 ms 1 ms
And after restarting the network, the new route is used.
--> traceroute fastcondor
traceroute to fastcondor.zk3.dec.com (16.141.160.8), 30 hops max, 40 byte
packets
1 fastcondor (16.141.160.8) 1 ms 1 ms 0 ms
If you're using the "old" routed, you might also have to flush you're routing
tables (this was fixed in a patch). rcinet stop/route flush/rcinet start
About you're DE-500 problem, I'd start with checking the cables and
configuration,
or maybe trying another machine you know works in it's place. Also try
searching
this conference for more info, I know there's been a lot of similar questions,
and some might have better answers.
-Brian
[Posted by WWW Notes gateway]
|