| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 906.1 | No luck here. | SMURF::GREBUS | DTN 381-1426 - Digital Unix | Wed Apr 16 1997 13:59 | 6 |
| I was unable to make the ATMworks 351 work reliably on an AS 500 5/333.
The version of the driver I was using did not list the AS 500 as a
supported system.
/gary
|
| 906.2 | More question. | TKTVFS::NAGANO_T | | Thu Apr 17 1997 02:48 | 13 |
|
Hi gary,Thank you for your quick response.
It is confirmation for a careful.
Is the configuration of ASt500 and DIGITAL UNIX V4.0A
formal support?
It is decause our customer uses the configuration.
Regards.
Takeharu Nagano/MCS-J
|
| 906.3 | V4.0A and AS 500 is ok | SMURF::GREBUS | DTN 381-1426 - Digital Unix | Thu Apr 17 1997 14:08 | 7 |
| DIGITAL UNIX V4.0A on an AlphaStation 500 is supported. The ATMworks
350 works fine in that configuration. It was only with the ATMWorks
351 that I saw a problem.
/gary
|
| 906.4 | supported? | DAIVC::IVAN | | Fri Apr 18 1997 02:48 | 4 |
| Is ATMworks 315 officially supported in DIGITAL UNIX V4.0A ???
regards
ivan
|
| 906.5 | Check with the product manager | SMURF::GREBUS | DTN 381-1426 - Digital Unix | Mon Apr 21 1997 13:59 | 8 |
| Check with the product manager for ATM adapters. Last I heard, that
was Ranjeet Sudan.
Note that support for the ATMworks 351 comes from the Network PBU, not
from DIGITAL UNIX engineering.
/gary
|
| 906.6 | DUNIX ATM config questions | DAIVC::IVAN | | Tue May 13 1997 12:16 | 14 |
| Hi!
I have two questions regarding the configuration of ATMworks 350
in D UNIX:
- Where should I put all those atm commands?
(atm.conf? Is this a file a kind of batch/script file that
is executed when the machine is up?)
- Can I use different ESI than those that are stored in
ATMworks ROM?
thanks & regards
ivan
|
| 906.7 | Startup questions | SMURF::GREBUS | DTN 381-1426 - Digital Unix | Tue May 13 1997 15:52 | 42 |
| The default place to put atm commands is /etc/atm.conf. Replace the
example commands with the ones needed for your environment. You can
execute the contents of atm.conf with the:
atmconfig source
command. Refer to the atmconfig(8) reference page for more
information.
atm.conf is not executed automatically, because currently the ATM
subsystem must wait for ATM layer and signalling connectivity before
the protocols over ATM (Classical IP, LANE, etc) can be started.
Running this as part of normal booting will cause the boot process to
"hang" until the connection with the switch completes. If that's not
a problem, you can add a script to /sbin/rc3.d to run atmconfig.
In V4.0D, ATM startup will be part of normal system startup. There
will be a new command "atmsetup" which will manage most of the boot
time configuration of ATM. The logical interfaces (lis's and elan's)
will be created independently of the switch connection. You will be
able to configure these interfaces like a normal network interface
using netsetup, rather than having ifconfig commands in /etc/atm.conf.
For V4.0D, configuration of PVC's and IP switching will still happen
through atm.conf.
In the Steel release, atmsetup will get a GUI interface and be
integrated with the rest of the SysMan configuration tools. It will
also handle PVC's and IP switching. atm.conf will still be supported
for user-written convergence modules and a few non-standard things that
won't be supported in the GUI.
You can manually register ESI's using the "atmconfig +esi" command, and
you can suppress registration of one or more ROM ESI's via "atmconfig up
numesis=xxxx".
The Classical IP convergence module normally creates its own ESI.
You can supply your own ESI on an "atmarp -c" command, although I've
never tried that option.
I believe LAN Emulation picks the next available PPA (and therefore
ESI).
/gary
|