[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::atm

Title:atm
Moderator:NPSS::WATERS
Created:Mon Oct 05 1992
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:970
Total number of notes:3630

814.0. "ATMworks 351 NT4.0 and LANE" by LEMAN::PAIVA (Hawkeye - Network Support @GEO) Fri Jan 31 1997 11:27

    Hi!
    
    I'm having trouble using an ATMworks 351 with LANE under Windows NT 4.0
    (Intel).
    The two LEDs on the board are steady green (the one that has a circle -
    I suppose it means power) and steady orange (the one that has a #) and
    on the 8260 IBM switch where it is connected there is activity.
    However, I can not connect to the network. There was an ATMworks 350L
    on the same machine before and it was working correctly.
    
    Any hint (does anybody know the meaning of the orange LED)?
    
    BTW, why can't we configure a LECS address as we could with the 350L?
    
    Thanks.
    
    Pedro
    
T.RTitleUserPersonal
Name
DateLines
814.1Need more infoWASNT::"[email protected]"Born to be MildFri Jan 31 1997 16:209
Please run the web management tool to give us more information.
We are particularly interested in the address registration state
and the link state and the signalling state.

What model of PC are you using?

The web tool is available on www.networks.digital.com

doug
814.2No web mgmt toolLEMAN::PAIVAHawkeye - Network Support @GEOFri Jan 31 1997 17:0311
    Doug,
    
    I already had the web management tool with me but did not manage to get
    it running (when I lauched web_mgt it ended up immediatly...).
    The PC is a Prioris ZX 6200 (the same in which I didn't manage to
    configure a ATMw350 because he didn't catch an IRQ!).
    
    What about the orange LED?
    
    Pedro
    
814.3Someone else is having a similiar bugWASNT::"[email protected]"Born to be MildMon Feb 03 1997 11:4014
We've had someone else report that the can't get the prioris running.
We are trying to get our hands on one of these machines to
reproduce the bug.

By the way, the reason the web management probably did not run is
because you started with the default port, which might have been used
by another process (do you have the IIS server running?).
Try starting it with port 81 or something.

Also, if you could run journal, and use set mask to get address
registration information, this would be helpful.  I suspect that the
problem is that address registration is not running.

doug
814.4LEMAN::PAIVAHawkeye - Network Support @GEOMon Feb 03 1997 12:319
    Doug,
    
    What's IIS server? I'll try using some port other than the default.
    
    journal? do you mean the one that was given with the ATMworks 350?
    
    Cheers,
    
    Pedro
814.5webWASNT::"[email protected]"Born to be MildWed Feb 05 1997 12:316
Microsoft has a WEB server that they sell, which competes with 
Netscape's WEB server.

Try starting the web server like this: web_mgt 81

doug
814.6No DHCPLEMAN::PAIVAHawkeye - Network Support @GEOFri Feb 14 1997 09:4017
    Doug,
    
    There Web Server from MS was effectively running and after stopping it
    I could lauch web_mgt (the help file says it doesn't support port
    numbers so that's why I preferred to test it with the default port).
    However when I do what's suggested, ie. http://ip_address/atm I get the
    atm.htm that is in the web mgt directory but no card info.
    The actual situation is that the card is working when its IP config is
    fixed and doesn't when trying to use DHCP. When tracing comparatively
    with a working config (on another PC) we saw the 351 was only sending
    DHCP discover packets as opposed to the other one that sent DHCP
    discover followed by DHCP request.
    
    Any hint?
    
    Pedro
    
814.7update...WASNT::"[email protected]"Born to be MildTue Feb 25 1997 15:5718
We have found a "situation" with the ATMworks 351 NIC that prevents
it from running with certain PCI bridges.  Some models of this 
server have the faulty PCI bridges, some do not.  We will be posting
more information on the NPB web server as it becomes available:

From Paul Ely:
The PC server, Prioris Loudon, does not compute parity correctly and 
will never compute parity correctly unless the PCI chipset on the 
motherboard is updated.  Our PCI-based ASIC on the ATMworks 351 must 
be tolerant of this condition existing in earlier PCI devices.  This 
is the bug in the ATMworks 351, and we will fix this in a future 
release.

For now, the Prioris Limerock is the Digital PC server of choice
when using the ATMworks 351.

doug