Re: PVLAN on 3750

From: Sadiq Yakasai <sadiqtanko_at_gmail.com>
Date: Wed, 22 Jun 2011 13:45:09 +0100

I think you are right there! I have not seen anywhere, an indication of a
promiscuous port also capable of being a trunk port.

On Wed, Jun 22, 2011 at 1:19 PM, Persio Pucci <persio_at_gmail.com> wrote:

> Sadiq,
>
> I have tried that while troubleshooting what was wrong during the
> maintenance window, but that did not help.
>
> I suspect this have something to do with the trunk port acting as
> promiscuous and not working fine as trunk, but can't find anything on it.
>
>
> On Wed, Jun 22, 2011 at 8:57 AM, Sadiq Yakasai <sadiqtanko_at_gmail.com>wrote:
>
>> Hmmm, sounds very strange, as the configuration is pretty straight forward
>> as you have mentioned.
>>
>> One quick test to verify this: how about if you created an SVI for the
>> primary VLAN and added the mapping on there. Does the problem persist?
>>
>> I understand this might conflict with your network design but this is
>> strictly for troubleshooting sake.
>>
>> HTH,
>> Sadiq
>>
>> On Wed, Jun 22, 2011 at 12:06 PM, Persio Pucci <persio_at_gmail.com> wrote:
>>
>>> Hi fellows,
>>>
>>> I just tried to implement a fairly standard PVLAN configration on a 3750,
>>> however it did not work as intended. Configs as follows:
>>>
>>> vlan 501
>>> > private-vlan isolated
>>> > !
>>> > vlan 500
>>> > private-vlan primary
>>> > private-vlan association add 501
>>> > !
>>> > int g1/0/3
>>> > switchport mode private-vlan host
>>> > switchport private-vlan host-association 500 501
>>> > !
>>> > int g2/0/5
>>> > switchport mode private-vlan promiscuous
>>> > switchport private-vlan mapping 500 add 501
>>>
>>>
>>> Configuration is pretty straight-forward but could not identify what went
>>> wrong. Command "*show interface g1/0/3 private-vlan mapping*" would
>>> produce
>>> a "*Private vlan mapping information is not available*" response,
>>> although "
>>> *show vlan private-vlan*" would show them correctly configured.
>>>
>>> As a result, I was unable to reach IP addresses on the 500/501 subnet
>>> that
>>> were located on the isolated vlan/ports
>>>
>>> Another question I have (and I could not find much information on the
>>> documentation) is regarding making promiscuous a trunk port (as port
>>> g2/0/5
>>> in the above example). How does it work for VLANs out of the PVLAN config
>>> that are supposed to be received on this trunk? They also did not seem to
>>> be
>>> working at the time.
>>>
>>> Any help is appreciated.
>>>
>>> Persio
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> CCIEx2 (R&S|Sec) #19963
>>
>
>

-- 
CCIEx2 (R&S|Sec) #19963
Blogs and organic groups at http://www.ccie.net
Received on Wed Jun 22 2011 - 13:45:09 ART

This archive was generated by hypermail 2.2.0 : Fri Jul 01 2011 - 06:24:28 ART