| 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,
I have installed a GIGASWITCH/ATM version 2.0 (revision code 300)
with a new line card (a modular one)using one optical PMD and two UTP
pmd's.
ON these ports ,I have connected three systems :
_One VNSWITCH EA
_One Sun machine with a Fore ATM module
_One Sun machine with A Sun ATM module
The goal of the play is LANE EMULATION
I have created one Emulated LAN VLAN1 and all the three systems must be
LEC for the gigaswitch where the BUS,LECS and LES are based......
Issuing the commands like: uni -status, lecs -sc, les _sc ,bus -sc
I could check that all lec have joined the VLAN.
But I have two strange points or problems to fight with:
1)I can see all three LEC that have joined the emulated LAN
BUt when I look at the LECS : lecs -sc I just see one CONNECTED client
(One SUn machine with the fore module) but nothing about the other sun
machine and the vnswitch....is it normal? why this behaviour?
2) Sometimes ,the sun machine with the sun module (only this one)
after bootink works ok a certain time then drops suddenly.It is
impossible to get it up back.It goes up and down continuouly.The only
way to stop it is to reboot the machine.
In that case,the uni -status command on the gigaswitch shows that the
port is in the down state .No uni is current.It seems it is the same
with the version 3.0 or 3.1 of uni.........
Any ideas?has somebody at the Engineering side experience of SUNATM
modules? what about interoperability?
How can I troubleshoot easily this problem without ATM analyzer?
3)Another point:
CAn I create different VLANs for each machine?
CAn I use only the same lecs,les or bus ? normally yes...
How the link betwwen Emulated lan and corresponding bus and les is made
on the gigaswitch?
4)Is there a specific order to create and enable the elan,les or bus
because I could use the Elanall command once and after it was
impossible.
I had to create The elan,les and bus separetely and precise the
Addresses of each otherwise it was impossible to enable the les.
netherveless,I was sure to make it before but I could'nt anymore.....
Is it a problem of version?
Any help or ideas appreciated??
Lionel
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 831.1 | Partial answers | AUBER::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Tue Feb 18 1997 11:33 | 36 |
Bonjour Lionel >> 4)Is there a specific order to create and enable the elan,les or bus >> because I could use the Elanall command once and after it was >> impossible. >> I had to create The elan,les and bus separetely and precise the >> Addresses of each otherwise it was impossible to enable the les. >> netherveless,I was sure to make it before but I could'nt anymore..... >> Is it a problem of version? it should be a version problem, i tested in V2.1.1 CMM 1.82 elanall X worked great, from 2.1.1 release notes this command start to be supported in V2.1.1 may be present in v2.0 code but really supported in V2.1.1 3)Another point: >> CAn I create different VLANs for each machine? >> CAn I use only the same lecs,les or bus ? normally yes... >> How the link betwwen Emulated lan and corresponding bus and les is made >> on the gigaswitch? from understanding, you can create Vlans on ethernet side of VnswitchEA and "map them" to ELan on ATM side, i tested with VnswitchEA creating VLANS and mapping them to Elan , you can just create a Elan and bus and les with the same name and give this name to the LEC that it want to join them i tested with VnswitchEA and worked as well. hopes that help you JYP | |||||
| 831.2 | c'est good | SOS6::HOFFMANN | HOFFMANN Lionel/loc=evt/DTN number=858 5647 | Tue Feb 18 1997 12:04 | 14 |
Thank you Jean yves
Ok for the version.I should upgrade but I can't on the customer site
right now.I will do it later when the situation will be quieter...
Ok for the VLAN's mapped to ELAN but my question was about different
ELAN's on the GIGASWITCH associated with different LES and BUS ...
But I will be able to test many points very soon on Anthony site ...
See you may be tomorrow there....
Regards
Lionel
| |||||
| 831.3 | NPSS::NEWTON | Thomas Newton | Tue Feb 18 1997 18:28 | 28 | |
>> 1)I can see all three LEC that have joined the emulated LAN
>> BUt when I look at the LECS : lecs -sc I just see one CONNECTED client
>> (One SUn machine with the fore module) but nothing about the other sun
>> machine and the vnswitch....is it normal? why this behaviour?
The LANE specification allows clients to keep the Configuration Direct
VCC open for as long as they choose. Fore probably just chose to have
their LEC work differently than the ones from the other vendors.
>> 3)Another point:
>> CAn I create different VLANs for each machine?
>> CAn I use only the same lecs,les or bus ? normally yes...
>> How the link betwwen Emulated lan and corresponding bus and les is made
>> on the gigaswitch?
If you are talking about multiple emulated LANs ("ELANs", not "VLANs"),
you can set up several LES/BUS pairs on the GS/ATM.
You can then use the built-in LECS to direct clients to ELANs by either
ELAN name or default ELAN. If your clients don't allow you to enter an
ELAN name, you may need a full-featured external LECS that can assign a
client to an ELAN on the basis of ATM address or MAC address.
The way the GS/ATM associates ELANs, LESes, and BUSes is by ATM address.
The ELAN must have the correct ATM address of the LES, and the LES must
have the ATM address of the BUS.
| |||||
| 831.4 | thanks | SOS6::HOFFMANN | HOFFMANN Lionel/loc=evt/DTN number=858 5647 | Thu Feb 20 1997 03:58 | 3 |
Thank you Thomas.It is clear and interesting to know
regards
Lionel
| |||||