| 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 |
hello,
a customer wants to setup LAT over ATM on a Digital-UNIX.
But he doesn't fail.
When he does a #latcp -e elan0 he gets the error
"Invalid network adapter elan0 specified"
The configuration:
Digital Unix V4.0B
Alphaserver 2100 Modell 4/233 (firmware V3.8)
ATM-Adapter : ATMWORKS 350
ATM-Switch : FORE
The customer has LANEmulation und IP is working properly with ATM.
Only LAT makes trouble.
Can someone give me some hints about setting up LAT over ATM ?
And is this supported ?
(Sorry, but I'm a novice in ATM)
In the following are further details of the customers configuration.
Many thanks in advance
Norbert Woerle, CSC Munich
# ifconfig -a
tu0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 193.24.81.118 netmask ffffff00 broadcast 193.24.81.255 ipmtu
1500
sl0: flags=10<POINTOPOINT>
lo0: flags=c89<UP,LOOPBACK,NOARP,MULTICAST,SIMPLEX>
inet 127.0.0.1 netmask ff000000 ipmtu 1536
# atmconfig up driver=lta0
# atmsig up driver=lta0
Enabled signalling on lta0.
# atmsig ilmi driver=lta0
ILMI on lta0 (vpi = 0 vci = 16) : Enabled.
ILMI State : Address registered.
# atmelan create driver=lta0 les=vl-archiv
# ifconfig elan0 172.18.4.55
# ifconfig -a
tu0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 193.24.81.118 netmask ffffff00 broadcast 193.24.81.255 ipmtu
1500
sl0: flags=10<POINTOPOINT>
lo0: flags=c89<UP,LOOPBACK,NOARP,MULTICAST,SIMPLEX>
inet 127.0.0.1 netmask ff000000 ipmtu 1536
elan0:
flags=e63<UP,BROADCAST,NOTRAILERS,RUNNING,ALLMULTI,MULTICAST,SIMPLEX>
inet 172.18.4.55 netmask ffff0000 broadcast 172.18.255.255 ipmtu 1500
# atmelan show
Local LEC ATM Address: 47000580ffe1000000f21a018f.08002b804a20.00
LES ATM Address: 47000580ffe1000000f21a1c34.0020481a1c34.05
BUS ATM Address: 47000580ffe1000000f21a1c34.0020481a1c34.06
Lan Type: Ethernet/802.3
Max frame Size: 1516
Proxy Flag: FALSE
Elan Name: vl-archiv
LEC ID: 22788 (0x5904)
Registered MAC Addresses: 08-00-2b-80-4a-20
Control Timeout: 10
Max Unknown Frame Count: 0
Max Unknown Frame Time: 1
VCC Timeout: 1200
Max Retry Count: 2
Aging Time: 300
Forward Delay Time: 15
Topology Change Flag: FALSE
LE-ARP Response Time: 1
Flush Timeout: 4
Path Switching Delay: 6
Control State: S_OPERATIONAL
Illegal Control Frames Rcvd: 0
Control Transmit Failures: 0
Unicast Frames Sent Direct: 0
Unicast Frames Flooded: 0
Unicast Frames Discarded: 0
Non-Unicast Frames Sent: 1
Frames Received from BUS: 84
Frames Received Data Direct: 0
Receive Frames Discarded: 6
Echo Frames Suppressed: 1
Control Frames Sent: 2
Control Frames Received: 53
LE-ARP Requests Sent: 1
LE-ARP Requests Received: 0
# learp -a
le-arp cache contains 2 entries.
MAC Address State ATM Address Flags
VPI/VCI
08-00-2b-80-4a-10 (FD) 47000580ffe1000000f21a1fe4.08002b804a10.00
0/7
00-20-48-10-2a-32 (FD) 47000580ffe1000000f21a1fe4.002048102a32.00
0/9
# ping 172.18.4.54
PING 172.18.4.54 (172.18.4.54): 56 data bytes
64 bytes from 172.18.4.54: icmp_seq=1 ttl=128 time=0 ms
64 bytes from 172.18.4.54: icmp_seq=2 ttl=128 time=0 ms
64 bytes from 172.18.4.54: icmp_seq=3 ttl=128 time=0 ms
----172.18.4.54 PING Statistics----
4 packets transmitted, 3 packets received, 25% packet loss
round-trip (ms) min/avg/max = 0/0/0 ms
LAT-Services
=============
# latcp -d
Node name: SEPTIMA
Multicast timer: 60 seconds
LAT version: 5 ECO: 2
Outgoing Port Groups: 0
Selected Interface Name(s): tu0
LAT Protocol is active
Agent Status: Disabled
Maximum Number of Learned Services: 100
Service information
Service name: SEPTIMA
Service ID: Digital UNIX Version V4.0 LAT SERVICE
Rating: Dynamic 254
Groups: 0
====================
error
====================
# latcp -e elan0
Invalid network adapter elan0 specified
===============================
further Config Files
===============================
# more /etc/atmhosts
#
# This file contains the mapping between ATM addresses and host names.
# ATM addresses are 20 byte values represented here by a string of fourty
# hexidecimal digits. No separators or non-hex characters are allowed.
# ESI's can also be specified as a string of twelve hexidecimal digits.
# Each address has one or more associated host name.
#
# 1 2 3 4
#234567890123456789012345678901234567890
#
0000000000000000000000000000000000000000 PVC
47000580ffe1000000f21a1c340020481a1c3405 vl-archiv
Nachfolgend noch die ausf�hrbaren Eintr�ge in /etc/atm.conf,
die aber meines Erachtens bisher nicht ausgef�hrt wird:
# The commands in this file are run by running
# atmconfig source
#
print Starting ATM Network
up driver=lta0
wait state=up driver=lta0
# wait till address registration is complete
run /usr/sbin/atmsig up driver=lta0 wait
run /usr/sbin/atmarp -c lis=0 driver=lta0
# allow dynamic ESI time to register with switch
sleep 3
# For setting flow control
+vfc driver=lta0
run ifconfig lis0 atmipaddr netmask 255.255.255.0 up
# For setting a PVC
+pvc driver=lta0 converge=atmip vpi=0 vci=50
# For making this a client on a LIS
run /usr/sbin/atmarp -h lis=0 client atmserver serverip
print ATM network started
In the kernel are only the ATM-Options
Uni3.x Signalling and
LAN-Emulation
(Classical IP was not chosen)
uerf -r 300 gibt dann f�r die letzte Meldung folgendes:
********************************* ENTRY 13.
*********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 300. SYSTEM STARTUP
SEQUENCE NUMBER 0.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Wed Feb 19 13:01:05 1997
OCCURRED ON SYSTEM septima
SYSTEM ID x00060009 CPU TYPE: DEC 2100
SYSTYPE x00000000
MESSAGE Alpha boot: available memory from
_0x91a000 to 0x7fee000
Digital UNIX V4.0B (Rev. 564);
Tue
_Feb 18 11:58:21 MET 1997
physical memory = 128.00
megabytes.
available memory = 118.82
megabytes.
using 483 buffers containing 3.77
_megabytes of memory
Firmware revision: 4.7
PALcode: OSF version 1.45
ibus0 at nexus
AlphaServer 2100 4/233
cpu 0 EV-45 1mb b-cache
gpc0 at ibus0
pci0 at ibus0 slot 0
tu0: DECchip 21040-AA: Revision:
2.3
tu0 at pci0 slot 0
tu0: DEC TULIP Ethernet Interface,
_hardware address:
08-00-2B-E6-27-BC
tu0: console mode: selecting
10BaseT
_(UTP) port: half duplex
psiop0 at pci0 slot 1
Loading SIOP: script 1000d00, reg
_81511000, data 40654c10
scsi0 at psiop0 slot 0
rz0 at scsi0 target 0 lun 0
(LID=0)
_(DEC RZ28M (C) DEC 0568)
rz1 at scsi0 target 1 lun 0
(LID=1)
_(DEC RZ29B (C) DEC 0014)
tz5 at scsi0 target 5 lun 0
(LID=2)
_(DEC TLZ07 (C)DEC 4BE0)
rz6 at scsi0 target 6 lun 0
(LID=3)
_(DEC RRD43 (C) DEC 1084)
eisa0 at pci0
ace0 at eisa0
ace1 at eisa0
lp0 at eisa0
fdi0 at eisa0
fd0 at fdi0 unit 0
qvision0 at eisa0
qvision0: CMPQ Qvision 1024/E SVGA
pci2000 at pci0 slot 6
lta0: Microcode Version: 1.11,
_Hardware Rev: 0.04
lta0 at pci2000 slot 0
lta0: DEC DGLPB ATM Interface,
_hardware addresses:
08-00-2B-80-4A-20
08-00-2B-80-4A-21
08-00-2B-80-4A-22
08-00-2B-80-4A-23
08-00-2B-80-4A-24
08-00-2B-80-4A-25
08-00-2B-80-4A-26
08-00-2B-80-4A-27
ATM Subsystem configured with 1
_restart threads
ltaregister: registered unit 0
with
_CMM
pza0 at pci0 slot 8
pza0 firmware version: DEC L01
A10
_
scsi1 at pza0 slot 0
kernel console: qvision0
dli: configured
ATM UNI 3.x signalling: configured
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 840.1 | BERN02::DEY | Walter Dey, Berne Switzerland | Wed Feb 26 1997 04:21 | 33 | |
Hi
I don't think that LAT (and DECnet, ...) over LANE is supported
(see below). However, on OpenVMS it works.
Gruss Walter.
From: NPSS::SNAY 5-SEP-1996 09:54:19.02
To: SUDAN
CC: CASADAY,RENDA,BURRILL,WASTED::"rtm",BRADSHAW,[email protected],[email protected],NETCAD::HOPKINS,NETCAD::FISCH,NETCAD::COOPER,WOOF::BUCELL,RICHESSON,SNAY
Subj: Digital Unix 4.O? and MULTICAST/ MULTIPROTOCOL SUPPORT
Hi
Digital Unix Engineering is attempting to deliver Multicast support
for support of Decnet,Lat,IPX etc.. using Lane on Digital Unix. However
they need to identify real customers that have been requesting this
need.
Ranjeet we are asking that you send this out to all SE'S, WIZARDS etc..
If they have a customer with this requirement please ask them to send
me mail with the customer name address and contact. And a brief writeup
of there requirements:
They can send the reply to [email protected]
or mts$::"lkg::jim snay"
or NPSS::SNAY
ThankYou
Jim Snay
| |||||
| 840.2 | Not officially supported | SMURF::GREBUS | DTN 381-1426 - Digital Unix | Wed Feb 26 1997 11:44 | 8 |
Digital UNIX has never claimed support for LAT over LANE. It has never
been formally qualified by the group responsible for the LAT code. In
some informal testing here, it appeared to work and got further than
this latcp command error. I'm not sure what might be different in this
case.
/gary
| |||||
| 840.3 | SMURF::MENNER | it's just a box of Pax.. | Wed Feb 26 1997 15:57 | 1 | |
i plan on looking into this tonight (feb. 26) | |||||
| 840.4 | not really an ATM problem pre se | SMURF::MENNER | it's just a box of Pax.. | Thu Feb 27 1997 20:09 | 3 |
Found this problem to be caused by a new version of the DLB (Data Link
Bridge) which was merged into V4.0B very late in the game. Hope to
have a patch availible soon.
| |||||
| 840.5 | Thanks to all | MUNICH::WOERLE | Fri Feb 28 1997 01:47 | 12 | |
hi ,
many many thanks for your great help.
.-3 "Hope to have a patch available soon"
If you have this patch, please can you inform me with the location
of this patch (MUNICH::woerle)
Kind regards
Norbert
| |||||
| 840.6 | SMURF::MENNER | it's just a box of Pax.. | Fri Feb 28 1997 10:00 | 3 | |
RE: -.1
Soon should be sometime next week.
| |||||
| 840.7 | Yes/No supported/unsupported | KERNEL::FREKES | Like a thief in the night | Fri Feb 28 1997 10:37 | 4 |
So just to clarify, LAT is still officially/unofficially
supported/unsupported?
Steven
| |||||
| 840.8 | SMURF::MENNER | it's just a box of Pax.. | Fri Feb 28 1997 11:39 | 10 | |
LAT still is unsupported over ATM but since this is not a LAT (or
even an ATM) problem per se, the DLB will be fixed. Ofcourse the fix
will go into a development pool. To get a patch will require an
IPMT. The IPMT should state something to the effect that the V4.0B
DLB does not support dynamic interfaces.
i have tried to get the owner engineering groups to verify their
products over LANE but have had NO success.
/ron_who_is_still_trying_to_working_around_thre_system
| |||||
| 840.9 | exit | MUNICH::WOERLE | Tue Mar 11 1997 07:23 | 26 | |
hello,
many thanks for all your replies.
The customer now wants a patch.
If I have understood the last reply correctly I must open an IPMT
.-1"Ofcourse the fix will go into a development pool. To get a
patch will require an IPMT."
Okay but to whom should I send the IPMT ? To ATM Engineering or to
Digital UNIX ?
The customer wants to do LAT over LANE.
If I have the last replies understood correctly the LAT over LANE is
*NOT* supported.
When the customer wants this functionality should he send mail like
described in .1 :
" [email protected]
or mts$::"lkg::jim snay"
or NPSS::SNAY "
Many thanks in advance
Norbert
| |||||
| 840.10 | Handle through Digital UNIX | SMURF::GREBUS | DTN 381-1426 - Digital Unix | Tue Mar 11 1997 13:19 | 10 |
IPMT cases for problems with Digital UNIX software should go through
the Digital UNIX support process.
LAT over LANE is not officially supported. Since this is a request for
a new supported feature, it should go to Digital UNIX product
management. I believe Steve LeBlanc is the product manager responsible
for the network area.
/gary
| |||||
| 840.11 | SMURF::MENNER | it's just a box of Pax.. | Wed Mar 12 1997 22:58 | 4 | |
But if you enter an IPMT which states that the Data Link Bridge (the
DLB), does not support dynamicly added interfaces - then a patch
could be generated which will allow LAT to work (offical support
is another issue...)
| |||||