See:
http://www.3com.com/nsc/200374.html
-Original Message-From: Asad Jafari
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, October 17, 2000 4:05
PMTo: [EMAIL PROTECTED]Subject:
VLAN's
Hello All,
I have some questions about VLAN. Can someone
send me a good resource for VLAN
No, You only need one PDC, the systems can log on to the network acfross a
router hop if they have lmhosts files. Alternately, you can use a 802.10
Capable Nic, and connect your PDC to a trunk port. Then you can give the
PDc an iP in every VLAN/Subnet.
"Cisco Ios Switching Services" and the
Probably one of the best books on Vlans is, Cisco LAN Switching, by Clark
and Hamilton.
""Ejay Hire"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> No, You only need one PDC, the systems can log on to the network acfross a
> router hop if they have lmhosts fi
You can use lmhosts files to contact the PDC in a separate VLAN
You can use a WINS server to contact the PDC in a separate VLAN
You can use BDC in each VLAN which is the most expensive of all
The WINS is the easiest to configure...
""Asad Jafari"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROT
This is called 'routing on a stick'. Send us your sanitized config. What
router are you using?
>From: "sujar khmar" <[EMAIL PROTECTED]>
>Reply-To: "sujar khmar" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: VLAN's
>Date: Tue, 29 Aug 2000 14:56:29 -0400
>
>Group,
> I have a catalyst
You can't just make a switch port a member of all the VLAN's and hang a
router off it to route traffic between VLAN's.
The router and switch must have a way to exchange VLAN information in order
for you to route between VLAN's. You need to connect the router on a trunk
link. This link must be
My understanding is... If you're going to have multiple vlan's, you will
typically have different subnets. In order for one vlan to talk to another,
a router has to be involved. You can use a Catalyst 5000, 6000, etc. with
an RSM or a router with multiple ethernet ports, each configured for its
You need VLAN trunking between the switch and the router. It requires a
FastEthernet port. (Won't work on a 10Mbs Ethernet.)
http://www.cisco.com/warp/public/473/24.html
http://www.cisco.com/warp/public/473/#cat
> -Original Message-
> From: sujar khmar [mailto:[EMAIL PROTECTED]]
> Sent:
9:27 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: VLAN's
You can't just make a switch port a member of all the VLAN's and hang a
router off it to route traffic between VLAN's.
The router and switch must have a way to exchange VLAN information in order
for you to
I have the same switch but haven't VLAN'd it yet. I will soon. This document
has great examples and should be what you need to get the idea and set it
up.
http://www.cisco.com/warp/public/473/29.html
"" 416South"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Have a 2948GL 3 a
Configure bridge groups on the switch, and assign ports to the bridge groups
as required.
CM
- Original Message -
From: " 416South"
To:
Sent: Thursday, January 17, 2002 9:03 PM
Subject: VLAN's [7:32351]
> Have a 2948GL 3 and want to set up a vlan but it docs state that you have
to
> s
thanks sam but this doesn't let you do it unless ISL is implemented ... this
is a tough one plus there is not vlan database with this version of IOS it's
12.07 .. any other ideas??
sam sneed wrote:
>
> I have the same switch but haven't VLAN'd it yet. I will soon.
> This document
> has great exa
VLAN in 2848L3 works like that
!
interface FastEthernet2
duplex half
speed 10
bridge-group 20 -> VLAN 20
bridge-group 20 spanning-disabled
!
interface FastEthernet3
duplex half
speed 10
bridge-group 20 -> VLAN 20
bridge-group 20 spanning-disabled
!
!
interface
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 ab
In your original post as seen below, you said that you didn't want to make
this
routeable between the vlans. But are you wanting to route the traffic
anywhere
else, cause if you aren't, then just put the following in under the port
config.
"switchport access vlan 1", and you can then put what eve
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 w
s
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32476&t=32351
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
M
> 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
> 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
l
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32531&t=32351
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Hi Sammi,
You can create
10.200.1.x/24 as VLAN 1
10.200.2.x/24 as VLAN 2
this will isolate the broadcast within the VLAN.
You can't create
10.200.1.x/16 as VLAN 1
10.200.2.x/16 or /24 as VLAN 2
because VLAN 2 will become part of VLAN 1, does not serve the purpose of
having VLAN configuration
Just think of VLANs as normal broadcast domains. One routes between
broadcast domains. Your config does not create an overlap between the
VLANs, but rather between the IP subnets. To properly route between
broadcast domains, you must have unique IP subnets that do not overlap.
Pete
*
Sammi,
You can always create VLANs without a router, you just can't move traffic
between them. If you have a situation where you have two networks that exist
in the same location but need to be kept strictly seperate (such as a
production and a test network) then it isn't necessarily a bad thing
Thanks all, that clarifies somewhat.
On 30 Apr 2001 14:06:09 -0400, [EMAIL PROTECTED] ("Karen E Young")
wrote:
> Usually there needs to be some form of communication
>between VLANS though, so practically speaking you do need a router.
What I would like to do is create broadcast domains for diff
>Thanks all, that clarifies somewhat.
>
>On 30 Apr 2001 14:06:09 -0400, [EMAIL PROTECTED] ("Karen E Young")
>wrote:
>
>> Usually there needs to be some form of communication
>>between VLANS though, so practically speaking you do need a router.
>
>What I would like to do is create broadcast domain
On 30 Apr 2001 15:06:15 -0400, [EMAIL PROTECTED] ("Howard C. Berkowitz")
wrote:
>>Thanks all, that clarifies somewhat.
>>
>>On 30 Apr 2001 14:06:09 -0400, [EMAIL PROTECTED] ("Karen E Young")
>>wrote:
>>
>>> Usually there needs to be some form of communication
>>>between VLANS though, so practica
You could buy a special NIC card for your server that can handle ISL
encapsulated frames. It might be cheaper to buy a router though since I
don't think the lower end switches support ISL anyway.
At 12:25 PM 4/30/01, you wrote:
>Thanks all, that clarifies somewhat.
>
>On 30 Apr 2001 14:06:09 -
Are dual NIC's feasible? Seems on the surface to be cheaper and more
straightforward but haven't seen it mentioned so I may be missing
something.
I can actually give each department their own server but accessing the
email server would present problems.
On 1 May 2001 10:47:35 -0400, [EMAIL PROTEC
Personally I think you'd be better off getting a router.
At 09:35 AM 5/1/01, you wrote:
>Are dual NIC's feasible? Seems on the surface to be cheaper and more
>straightforward but haven't seen it mentioned so I may be missing
>something.
>I can actually give each department their own server but ac
ll gather round and face the facts:
This is a Cisco type email list. There IS a Cisco answer.
TTFN,
Bill 'layer 4 and up is for end users' Pearch, Anchorage AK
-Original Message-
From: Sammi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 7:35 AM
To: [EMAIL PROTECTED]
S
why Cisco, why not use Extreme's summit switches? it's very cheap!!
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=2898&t=2891
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report miscondu
On 2 May 2001 02:45:45 -0400, [EMAIL PROTECTED] ("Bill Pearch")
wrote:
>This is a Cisco type email list. There IS a Cisco answer.
And that's what I'm after, was just exploring other possibilities.
Now I need to decide what type of router to purchase; ~150 users split
between 4-6 VLAN's.
Thanks
x27;t be killing the
CPU with route lookups in any case.
HTH
Chuck
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 02, 2001 12:02 PM
To: [EMAIL PROTECTED]
Subject: Re: VLAN's and Routers [7:2534]
On 2 May 2001 02:45:45 -04
Sammi,
At my last position I was called in to redesign a smallish corporate
network. They had 23 VLANs running on a 2621 router. The average CPU
utilization was in the range of 30% to 40%. When I dropped it to 4 VLANs the
utilization dropped to between 1% and 3%. While I'm sure that the 3600 coul
I would suggest the 2621 - don't forget you'll need the IP plus software
""Sammi"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Thanks all, for the advice.
> Looks like I should go with a router, am looking at 2600 and 3600
> series.
> I will have no more than 6 VLAN's, more li
35 matches
Mail list logo
