| Hi Terry,
After changing some switch configurations to force it to use UNI 3.1 on
the
alpha interface I have had some greater success. Your engineer was
correct
as regards the UNI version, and both switch and alpha had to be
changed, as
the switch failed to recognize the change in UNI on the alpha. I did as
follows:
-Used the suggested command set on the alpha:
atmconfig up driver=lta0
atmsig version driver=lta0 uni=3.1
atmsig up driver=lta0
which was the command set supplied by the engineer, followed by:
atmarp -c lis=0 driver=lta0
ifconfig lis0 134.153.189.77 netmask 255.255.255.0 up
atmelan create driver=lta0 type=ethernet
in order to create interface, configure it, and set up an Emulated LAN.
This left ATM is basically the same state as before, but switch still
listed
the UNI interface as 3.0. I changed it to 3.1 without any alterations
on the
alpha.
The console log on the alpha then stopped spewing the disconnect
messages
and yielded:
ATM LANE: cm_sap_xmt_vc - null conn_handle
ATM LANE - Connection Released, cause = 0
ATM LANE - SVC PPA Deleted, associated ELAN disconnected
ATM LANE - New PPA Bound to waiting ELAN. ELAN coming up...
ATM LANE - Connection Released, cause = 16
VC released on interface lta0:Source Address:
"470918100006083c521802b8033f0"
Destination Address: "4707900000000000a03e0010"
Call Duration: 0 seconds
the first few lines seem to relate to the transition from 3.0 --> 3.1
The tail of this message is the results of:
atmelan show
atmconfig vclist driver=lta0
atmsig stats driver=lta0
and in particular for "atmelan show" the "Control State" is now
"S_OPERATIONAL"
and the BUS ATM address is now correct. I havn't achieved IP success,
but
believe it to be the state of my routing tables, etc. I will mail
results.
Many thanks for your assistance, and pass on same to the engineer
please. I
can produce a detailed log with revs, IOS, etc, etc for the engineers
if
they'd want that. In particular the Cisco auto_configuration does seem
to
work in this example. The results of the above commands follow. Rod.
# atmelan show
Local LEC ATM Address:
47009181000000006083c50201.08002b80330f.00
LES ATM Address:
47009181000000006083c50201.00400b685c41.01
BUS ATM Address:
47009181000000006083c50201.00400b685c42.01
Lan Type: Ethernet/802.3
Max frame Size: 1516
Proxy Flag: FALSE
Elan Name: vltest
LEC ID: 3 (0x0003)
Registered MAC Addresses: 08-00-2b-80-33-0f
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: 0
Frames Received from BUS: 114
Frames Received Data Direct: 0
Receive Frames Discarded: 114
Echo Frames Suppressed: 0
Control Frames Sent: 183
Control Frames Received: 171
LE-ARP Requests Sent: 1
LE-ARP Requests Received: 0
# atmconfig vclist driver=lta0
Driver VPI/VCI VCID Call Ref flags BindID
PPA_ID Sel
lta0 0/16 1 0 active 1
1 0
No Addresses - PVC
lta0 0/5 2 0 active 1
1 0
No Addresses - PVC
lta0 0/174 129 127 active 7
20 0
remote 0x47009181000000006083c5020100400b685c4101
lta0 0/175 130 128 active 7
20 0
remote 0x47009181000000006083c5020100400b685c4101
lta0 0/176 131 129 active 7
20 0
remote 0x47009181000000006083c5020100400b685c4201
lta0 0/177 132 130 active 7
20 0
remote 0x47009181000000006083c5020100400b685c4201
# atmsig stats driver=lta0
Q.SAAL statistics on lta0 (vpi = 0 vci = 5) :
RECEIVE TRANSMIT
------- --------
Begin PDUs : 0 7
Begin Acknowledge PDUs : 3 0
Begin Reject PDUs : 0 0
Poll PDUs : 81 896
End PDUs : 0 3
End Acknowledge PDUs : 0 0
Resyncronization PDUs : 0 0
Resyncronization Acknowledge PDUs : 0 0
Sequenced Data PDUs : 431 429
Solicited State PDUs : 890 0
Unsolicited State PDUs : 0 0
Unnumbered Data PDUs : 0 0
Unnumbered Management Data PDUs : 0 0
Recovery PDUs : 0 0
Recovery acknowledgements PDUs : 0 0
Q.93b statistics on lta0 (vpi = 0 vci = 5) :
RECEIVE TRANSMIT
------- --------
Call Proceeding messages : 123 0
Connect messages : 123 2
Connect Acknowledge messages : 2 123
Setup messages : 2 123
Release messages : 60 61
Release Complete messages : 61 120
Restart messages : 0 0
Restart Acknowledge messages : 0 0
Status messages : 0 0
Status Enquiry messages : 0 0
Add Party messages : 0 0
Add Party Acknowledge messages : 0 0
Add Party Reject messages : 0 0
Drop Party messages : 0 0
Drop Party Acknowledge messages : 0 0
Last Cause code : 16 16
Last Diagnostic code : 0 92
Counters were reset to zero.
Roderick Campbell
Computing and Communications
Memorial University of Newfoundland
[email protected]
|
| Hi Terry. It works. That is, I can ping the switch and catalyst from
the
alpha through it's ATM interface. What I was missing was an "ifconfig
elan0
..." line after the atmelan configuration. The commands atmarp and the
previous ifconfig command were likely just for classical IP over ATM
and not
needed for LANE (not confirmed). There seems to be an IP over ATM
interface,
and a separate elan type interface that shows up after atmelan is done.
In
conclusion, it's seems to be done. I'm going to try and clean up the
command
set and write a little document. Please let me know what feedback
Digital
would like if any. Also, I don't know of a way to shut the interface
down
and bring it back up gracefully (to say the least!). I can shut the
interface down, reversing most commands, but every time I've tried to
re-enable ATM it instantly crashes the system. It's happened twice
recently
and I'm a little gun-shy. Thanks again. Rod.
Roderick Campbell
Computing and Communications
Memorial University of Newfoundland
[email protected]
|
| The atmarp command (and the lis<n> interfaces that it creates) are only for
Classical IP (RFC1577). LAN Emulation creates elan<n> devices, which
then must be ifconfig'ed just like any other LAN device.
There is no way to remove a network interface once it has been
configured, other than by rebooting. You can use ifconfig to down the
interface, and you can disable all ATM activity on a physical ATM
interface with "atmconfig down".
There is a known problem with restarting ATM ("atmconfig down" followed
by "atmconfig up") when ELANs are active. I'll have to check whether a
patch has been released yet.
If you are using LANE with V4.0A, you should install patch
OSF405-400102 which will fix various other ATM and LANE related
problems.
|