From: Nate Cielieska (ncielieska@advanticom.com)
Date: Wed Dec 12 2007 - 10:56:36 ART
Begin forwarded message:
> From: Cielieska Nathan <ncielieska@gmail.com>
> Date: December 12, 2007 8:55:31 AM EST
> To: Nambi Appachigounder <nambi_gct@yahoo.co.in>
> Subject: Re: PVLAN Question.
>
> Nambi,
>
> In my testing, the private-vlan mapping command is only valid if
> preparing your port as a promiscuous one. I see it simliar
> to a frame map statement where you can bind 2 or more private-vlans
> to an interface, which is indicative of a promiscuous port.
> The switchport mode trunk basically makes your private-vlan mapping
> command irrelevant. Similar to:
>
> switchport mode trunk
> switchport access vlan 20
>
> Your switchport access command would be irrelevant (yet exists)
> here until you did a "switchport mode access"
>
> The thought process behind it is that you can either have 2 types
> of ports.. a promiscuous access port or an isolated/community
> access port. You
> would configure another trunk port on the switch to carry the vlan
> information and is outside the scope of private-vlans
>
> To make an interface private-vlan "active" on an interface
>
> For edge isolated/community config
> switchport private-vlan mode host
> switchport private-vlan host-association <primary vlan><secondary
> vlan>
>
> or
>
> For edge promiscuous config
> switchport private-vlan mode prom
> switchport private-vlan mapping <primary vlan><secondary vlan>
>
> Thats how i know it to be true
>
> Regards,
> Nate
>
> On Dec 12, 2007, at 1:07 AM, Nambi Appachigounder wrote:
>
>> Thank you all for the responses.
>>
>> Nate,
>>
>> My switch allows this configuration.Here gi1/48 is a
>> trunk.In which scenario I need to add private VLAN
>> configs on the trunk?
>>
>> 6k#show runn int gi1/48
>> Building configuration...
>>
>> Current configuration : 112 bytes
>> !
>> interface GigabitEthernet1/48
>> switchport
>> switchport private-vlan mapping 20 200
>> switchport mode trunk
>> end
>>
>> 6k#
>>
>> 6k#show runn int gi1/48
>> Building configuration...
>>
>> Current configuration : 161 bytes
>> !
>> interface GigabitEthernet1/48
>> switchport
>> switchport private-vlan host-association 20 200
>> switchport mode trunk
>> end
>>
>> 6k#
>>
>> Thanks
>> Nambi
>>
>> --- Cielieska Nathan <ncielieska@gmail.com> wrote:
>>
>>> Nambi,
>>>
>>> 1) No. Your trunks will care your vlan information
>>> unless explicit
>>> disallowed.
>>>
>>> 2) I have seen 2 configurations on an interface
>>> basis.
>>>
>>> for putting an interface into an isolated or
>>> community vlan
>>> switchport mode private-vlan host
>>> switchport private-vlan host association <primary
>>> vlan><sub-vlan>
>>>
>>> for putting an interface into a prom mode
>>> switchport mode private-vlan prom
>>> switchport private-vlan mapping <primary vlan> add
>>> <subvlan>
>>>
>>> Regards,
>>> Nate
>>> On Dec 12, 2007, at 12:31 AM, Nambi Appachigounder
>>> wrote:
>>>
>>>> Hi Friends,
>>>>
>>>> I have a question on PVLAN configuration.
>>>>
>>>> My topology is as follows.
>>>>
>>>>
>>>> Sw1<---------->Sw2<-------->R1
>>>> | |
>>>> | |
>>>> H1 H2
>>>>
>>>> Sw1 and Sw2 are connected via a trunk link.H1 and
>>> H2
>>>> are in isolated ports.Port that connects to R1
>>> should
>>>> be promiscuous.
>>>>
>>>> My question is,
>>>> 1) Do we need any PVLAN configurations for the
>>> trunk
>>>> link?
>>>>
>>>> 2) In the trunk port I could see options for PVLAN
>>>> configuration.When should I use them.
>>>>
>>>> Can someone please help me understand this.
>>>>
>>>> Thanks,
>>>> Nambi
>>>>
>>>>
>>>> 5, 50, 500, 5000 - Store N number of mails
>>> in your inbox. Go
>>>> to
>>>
>> http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html
>>>>
>>>>
>>>
>> _____________________________________________________________________
>> _
>>>
>>>> _
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>
>>
>>
>> Bring your gang together - do your thing. Go to http://
>> in.promos.yahoo.com/groups
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:30 ARST