Classification: NATO UNCLASSIFIED - RELEASABLE FOR INTERNET TRANSMISSION We've got forty E7s as edge switches. We've been replacing our 6xxxx.xx cards with 7H4284-49s. The FTM1 backplanes are across the entire switch, but they are only five slots in length. A 6xxxx.xx card in slots 6 and 7 cannot connect to slot 1 unless there is another 6xxxx.xx card in slots 2-5 The FTM2 backplane is 7 slots long.
We front-panel uplink between the 3rd and 4th gen cards using the 1GB VHSIMs in our 6H25x.17 cards (the former uplinks to the core) to GBICs in a NEM in one of the DFEs. RSTP works as normal. VLANs also work as normal. You just have to make sure the front-panel uplinks are on the proper egress lists for the VLAN you want to transport. This is very easy in the CLI of the DFE, but you have to pick through the menu on the 3rd gen cards to do it there. Regards, Jesse W. Ohlsson Engineer, Information Systems Administration NCSA Sector Mons, Customer Services Squadron B7010 SHAPE Belgium tel: +32-65-44-8518; NCN 254-8518 -----Original Message----- From: Stephen Faulkner [mailto:[email protected]] Sent: Thursday, January 08, 2009 15:49 To: Enterasys Customer Mailing List Subject: RE: [enterasys] Howto use DFE and 3rd generation cards in E7 chassis We have 3 years experience with this. Our distribution switches are E7s. The first 1-5 slots are used for 2nd and 3rd generation modules (SmartSwitch) in our 'old' LAN, while slots 6 and 7 are used for DFEs in the 'new' LAN. The old modules use the FTM1 backplane while the DFEs use the FTM2 backplane. This allows us to have 2 totally isolated LANs in one chassis which saves space, cost etc. The following is what I recall and I hope it is still correct: Certain modules like the 7H you mentioned below do have a bridging function between FTM1 and FTM2. However if you put in a NEM (uplink daughter card) then the bridging function is disabled. We use 12 port giga DFE modules in the distribution E7s, so this isn't an issue for us. We certainly don't want to bridge between the old and new LANs. We have an E7 server switch chassis in both LANs. This contains 3x 7G4282-41 modules, 2 of which have 7G-6MGBIC-A uplink cards installed. All of these work completely independently of the older modules in the lower-numbered slots. We even had a 1st generation blade until recently (10FX fiber!). Now if you must have communication between the 6H and 7H then I guess it will work OK but I think there are some restrictions regarding which slots to use. I think the 6H will not work in slot 6 or 7 as FTM1 isn't there, but someone else must confirm that. Regards Stephen Oslo University Hospital (previously Rikshospital) In compliance with the Security Policy of Rikshospitalet HF , the content of this message (including any attachments) is of a non-sensitive nature > -----Original Message----- > From: Thorsten Steffen [mailto:[email protected]] > Sent: Thursday, January 08, 2009 3:19 PM > To: Enterasys Customer Mailing List > Subject: [enterasys] Howto use DFE and 3rd generation cards in E7 chassis > > Hello, > does anybody know if enterasys offers online documentation about using > dfes and 3rd generation cards in an E7 chassis? > > I just tested this with a 7H4382-49 and a 6H352-25 in an E7 chassis and > two pcs each connected to one of the modules could ping each other > successfully. > I also found out that the two modules don't see each other which means > that there are two administration domains where each domain manages only > it's own ports. > Because of this I'm wondering if there are any configuration guidelines > concerning > - the backplane connection > - layer 2 protocols like stp (rstp) > - vlan configuration > - ...? > > Does anybody have experience with dfes and 3rd gen cards in E7 > chassis? > > > Many thanks in advance, > Thorsten Steffen > > > > ============================ > Thorsten Steffen > > Westdeutscher Rundfunk Köln > IT- und Netz-Services / Netze und Telekommunikation > Appellhofplatz 1 > 50667 Köln > > Tel.: +49 (0) 221-220-1057 > Fax: +49 (0) 221-220-4999 > e-mail: [email protected] > ============================ > > --- > To unsubscribe from enterasys, send email to [email protected] with the > body: unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
