From: David Murray (AU) (David.Murray3@didata.com.au)
Date: Fri Feb 27 2009 - 22:06:27 ARST
Also I should mention that I have tried the private vlan in question in isolated and community.
And on the second 3560 I have tried the port as a promiscuous port and still it stays in non connect.
The vlans are created and seem to be fine...
VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/1, Fa0/3, Fa0/6, Fa0/7
                                                Fa0/8, Fa0/9, Fa0/10, Fa0/11
                                                Fa0/12, Fa0/13, Fa0/14, Fa0/15
                                                Fa0/16, Fa0/17, Fa0/18, Fa0/20
                                                Fa0/23, Fa0/24, Gi0/1, Gi0/2
100  VLAN0100                         active
101  VLAN0101                         active
102  VLAN0102                         active
1002 fddi-default                     act/unsup
1003 token-ring-default               act/unsup
1004 fddinet-default                  act/unsup
1005 trnet-default                    act/unsup
VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1    enet  100001     1500  -      -      -        -    -        0      0
100  enet  100100     1500  -      -      -        -    -        0      0
101  enet  100101     1500  -      -      -        -    -        0      0
102  enet  100102     1500  -      -      -        -    -        0      0
1002 fddi  101002     1500  -      -      -        -    -        0      0
VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1003 tr    101003     1500  -      -      -        -    -        0      0
1004 fdnet 101004     1500  -      -      -        ieee -        0      0
1005 trnet 101005     1500  -      -      -        ibm  -        0      0
Remote SPAN VLANs
------------------------------------------------------------------------------
Primary Secondary Type              Ports
------- --------- ----------------- ------------------------------------------
100     102       non-operational
        101       isolated
-----Original Message-----
From: David Murray (AU)
Sent: Saturday, 28 February 2009 10:04 AM
To: ccielab@groupstudy.com
Subject: Private VLANs
Hi Group,
Just a couple of quick questions (well quick if anyone knows the answer!!) I am just working on the private vlan section of the switching and bridging IE workbook.
What is the difference between
A. switchport private-vlan association host 100 102
and
B. switchport private-vlan host-association 100 102
I have a 3560 ((C3560-ADVIPSERVICESK9-M), Version 12.2(25)SEE2) connected to 2 identical 2811s ((C2800NM-ADVENTERPRISEK9-M), Version 12.4(3a)).
When I configure them both with (A) one works and one doesn't as per below...
switchport mode private-vlan host
switchport private-vlan association host 100 102
Logs:
SW3-3560#sh int fast 0/1
FastEthernet0/4 is up, line protocol is down (notconnect)
Name: Fa0/1
Switchport: Enabled
Administrative Mode: private-vlan host
Operational Mode: down
Administrative Trunking Encapsulation: negotiate
Negotiation of Trunking: Off
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: 100 (VLAN0100) 101 (VLAN0101)
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
When I configure them both with (B) they both work!!!!!
switchport mode private-vlan host
switchport private-vlan host-association 100 102
FastEthernet0/2 is up, line protocol is up (connected)
Switchport: Enabled
Administrative Mode: private-vlan host
Operational Mode: private-vlan host
Administrative Trunking Encapsulation: negotiate
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: 100 (VLAN0100) 101 (VLAN0101)
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan:
  100 (VLAN0100) 101 (VLAN0101)
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Then to make matters worse (for me!!) I have a dot1q trunk connection from one 3560 to an identical 3560. Fast 0/4 is configured exactly as fast 0/1 in the above (I have tried scenario A & B) and still the interface stays in a non operational mode (3560 interface is up, line protocol is down (not connect)
I should mention that there is no other config on the ports of the 3560 and the 2811 ports simply have an ip address and are not shutdown.
Has anyone seen this before or recognise it as a bug? I had a very quick bug scrub, will have a more detailed look later, just thought I would throw it out and see what you guys think.
Thanks
******************************************************************************
 - NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally privileged information.  If you have received this email in error, please notify the sender and delete it immediately.
Internet communications are not secure. You should scan this message and any attachments for viruses.  Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments.
******************************************************************************
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:13 ARST