Thanks George, that's what I was thinking. Have to wait to get my hands on this switch again... just getting my head around the new Bridging concept commands that were introduced with this IOS. Nothing like the other 2900 series or ever the 5500 or 6500's Will let you know how it goes.
Thanks again for your help Hartnell, George wrote: > > Well, I think that you could have two seperate VLANs with some > modifications > of the below. As far as I know, there is no dictate to assign > an IP to > those VLANs. While I don't have the need, or lack of need, for > the L3 part, > I'm not sure if the IRB command would be required for this > seemingly unusual > setup for a L3 switch. I'd just eliminate the IP parts below, > set up a > couple of bridge-groups, add the members, and see how that > works. > > Best, G. > VP OGC > > > -----Original Message----- > > From: 416South [mailto:[EMAIL PROTECTED]] > > Sent: Friday, January 18, 2002 6:12 AM > > To: [EMAIL PROTECTED] > > Subject: RE: VLAN's [7:32351] > > > > > > Thanks all, > > > > in George's description mentions that that your doing > > intervlan routing, > > would this BVI work without a IP address and if not is there > > a command to > > just provide L2 separate VLANS? > > > > thanksHartnell, George wrote: > > > > > > Well, I have one of those GL3's, and it's a pretty good > piece > > > of work. I > > > would agree that the documentation accompanying that switch > is > > > somewhat > > > sparse. It took me quite a while to 'figure it out' on my > > > first setup. The > > > below assumes an IP network. > > > > > > If I remember correctly, those docs talked about irb > enabling. > > > Syntax: > > > bridge irb > > > > > > Then the bridge: > > > bridge (xx) protocol ieee ; for example for subnet > > > 10.0.11.0/24; bridge 11 > > > protocol ieee > > > > > > Then pop the interface config: > > > int BVIxx ;Bridge Virtual > > Interface > > > ip address xx.xx.xx.xx (netmask) ; example "int BVI11, ip > > > address 10.0.11.1 > > > 255.255.255.0" > > > > > > If I were to route these VLANS, internally, I'd have to add > a > > > statement > > > whilst creating the bridge. This is where the routing > happens, > > > or, as you > > > require, doesn't happen: > > > > > > bridge xx protocol ieee > > > bridge xx route ip > > > > > > Without the "route" statement, routing doesn't occur between > > > other VLANs. > > > > > > Finally, each interface needs to have VLAN membership. At > the > > > interface > > > config: > > > > > > bridge group xx > > > > > > > > > Took me a while to get all that right.... > > > > > > Best, G. > > > > > > > > > ject: VLAN's [7:32351] > > > > > > > > > > > > Have a 2948GL 3 and want to set up a vlan but it docs > state > > > > that you have to > > > > set up ISL . I don't want ISL enabled. is there a way > to > > > > just create VLANS > > > > like in other L3 switches? I don't want to make these > > > > routeable or anything > > > > just L2 VLANS simple VLANS > > > > > > > > ie. when I do a "int vlan 400" this would normally create > a > > > > new vlan and put > > > > me into interface mode > > > > > > > > when i do a "int vlan ?" the options are to put in the > vlan > > > > # but when I do > > > > all i get is a wrong command with the famous ^ at the > vlan > > > > point in the > > > > command > > > > > > > > docs doc's dont seem to give enough info > > > > > > > > any Ideas???? > > > > > > > > thanks > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=32527&t=32351 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
