VLAN Aggregation

VLAN Aggregation

NewsGroups | Search | Tools
 comp.dcom.lans.ethernet  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
VLAN Aggregation vicky 07-04-2008
Posted by vicky on July 5, 2008, 5:54 am
If you were  Registered and logged in, you could reply and use other advanced thread options
>
> > Hello
>
> > I 've a query related on the topic VLAN Aggregation is in my
> > shared web file folder
>
> > named as : VLAN Aggregator.txt
>
> > I m giving u my web shared file link
>
> > http://vikrantpandey.diinoweb.com/files/
>
> > please give some of your time for watching my query and
> > plz reply .
>
> In RFC 3069, Table 2, followed by Section 6, are what really matters.
>
> It's obvious that you can aggregate IP addressed among LANs. You do
> this anytime you connect two Ethernet hosts to an Ethernet layer 2
> switch (i.e. bridge), and assign those two to the same IP subnet. So
> it should be clear that the same can be done between VLANs.
>
> RFC 3069 says that implementation details are not considered in the
> RFC. Seems to me, you can create a single spanning tree, then use IP
> addresses to determine who the various members are in each VLAN. This
> is a valid way to create VLANs.
>
> Also, pay attention to this text in Section 6:
>
> "That is, when an address or range of addresses is allocated to a
> given sub-VLAN, reception of IP or ARP packets on a sub-VLAN with a
> source IP address that isn't allocated to the sub-VLAN should be
> discarded, ..."
>
> So, the way I'd set this up, a single broadcast domain, and only IP
> addresses used to differentiate between VLANs.
>
> Bert

----------------------------------------------------

Hello Sir

i 've one more question related to promiscuous port
as i know the defination of this promiscuous port .. it can talk to
all other types of ports

But my question is how we make a port promiscuous
means becaming a port promiscuous is only done by when the switch
controller gives the capability for promiscuous
or making a port promiscuous is done by something else

please clearify this .....

Thanks in advance


Vikrant


Pure Networks
Posted by Walter Roberson on July 5, 2008, 10:52 am
If you were  Registered and logged in, you could reply and use other advanced thread options

>But my question is how we make a port promiscuous
>means becaming a port promiscuous is only done by when the switch
>controller gives the capability for promiscuous
>or making a port promiscuous is done by something else

>please clearify this .....

Whether a port is promiscuous or not is controlled on the switch.
That control may be by switch software or by switch hardware.

Making a port promiscuous is *not* done by the contents of any
data packet. You cannot, for example, set a particular bit in the
layer 2 headers to signal to the switch that it needs to switch
into promiscuous mode.

There is no requirement that any switch (of any Layer of operation)
support promiscuous ports.

Posted by vicky on July 6, 2008, 11:40 am
If you were  Registered and logged in, you could reply and use other advanced thread options
On Jul 5, 7:52=A0pm, rober...@hushmail.com (Walter Roberson) wrote:
> In article <8ffa1849-f3a7-47bb-8fd0-ec53c52fc...@j22g2000hsf.googlegroups=
.com>,
>
> >But my question is how we make a port promiscuous
> >means becaming a port promiscuous is only done by =A0when the switch
> >controller gives the capability for promiscuous
> >or making a port promiscuous is done by something else
> >please clearify this .....
>
> Whether a port is promiscuous or not is controlled on the switch.
> That control may be by switch software or by switch hardware.
>
> Making a port promiscuous is *not* done by the contents of any
> data packet. You cannot, for example, set a particular bit in the
> layer 2 headers to signal to the switch that it needs to switch
> into promiscuous mode.
>
> There is no requirement that any switch (of any Layer of operation)
> support promiscuous ports.

------------------------------------------------------------------

Ok Sir,

I m thinking some about a promiscuous port .... i m writing it you
please tell me is it correct or not

I think when we set some ports or any one port to primary vlan
(default vlan 1) and allocate a l3 device to this port then this port
or ports are termed as promiscuous port....

Is it correct................


regards

Vikrant

Posted by Albert Manfredi on July 6, 2008, 7:20 pm
If you were  Registered and logged in, you could reply and use other advanced thread options

> I think when we set some ports or any one port to primary vlan
> (default vlan 1) and allocate a l3 device to this port =A0then this port
> or ports =A0are termed as promiscuous port....
>
> Is it correct................

What are you asking?

Are you asking what a promiscuous port is, or are you asking how the
existence of VLANs in a given L2 network affects the definition of
promiscuous port?

Bert

Posted by Albert Manfredi on July 6, 2008, 7:34 pm
If you were  Registered and logged in, you could reply and use other advanced thread options

> =A0I m thinking some about a promiscuous port .... i m writing it =A0you
> please tell me is it correct or not
>
> I think when we set some ports or any one port to primary vlan
> (default vlan 1) and allocate a l3 device to this port =A0then this port
> or ports =A0are termed as promiscuous port....

I just did a quick search under "promiscuous port," as opposed to the
more general "promiscuous mode," and came up with this definition:

---------------------------------------
http://www.examguides.com/ccnp-switching-7.htm

39.0 The following are true about PVLANs:

1. There are three types of private VLAN ports: promiscuous, isolated,
and community.

1.1 Promiscuous port: A promiscuous port communicates with all other
PVLAN ports, and is the port typically used to communicate with
external routers, servers, administrative workstations, etc.

[ ... ]

4. In a PVLAN, promiscuous ports are called the primary VLAN, while
community and isolated ports are called secondary VLANs.

5. A PVLAN will only have one primary VLAN, but may have several
secondary VLANS.
----------------------------------------------------------

Bert

Similar ThreadsPosted
Efficiency of link aggregation August 1, 2008, 8:13 pm
Testing Link aggregation without LACP January 25, 2007, 3:45 am
Port trunking / link aggregation problem October 8, 2006, 9:11 am
VLAN Help (for a Vlan newbie) November 6, 2006, 12:09 pm
port-based vlan and tag-based vlan October 21, 2008, 2:03 pm
port-based vlan and tag-based vlan October 21, 2008, 2:03 pm
VLAN December 13, 2005, 10:23 am
VLAN and VPN January 17, 2007, 1:05 pm
VPN Vs VLAN December 21, 2007, 3:54 pm
VLAN May 24, 2008, 2:08 am

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map