Switch Port Trunk allowed Vlan

Hi Guys
Request your help on my query :
I have a distribution switch  and access switch and port channel between them.
Dist switch is the VTP server
lets assum I have 25 vlan
when I do show vlan brief on the access switch I can see all 25 vlans listed now
no when I configure switch port trunk allowed vlan (ex : permitting 10 vlans )on the link connecting to access switch at Dist switch
Dist switch po1 -- connecting to - po Access switch
Dist switch #
int po1
switch port trunk alllowed vlan x,x,x,x,x,x,x,x,x,
After permitting 10 vlan through trunk allowed vlan and then when I do show vlan brief on the access switch , I should see only the 10 vlan whcih I have permiited right ?
Thanks in advance  

Hi,
John is absolutely correct - even if you do not permit a VLAN on a trunk, it can still provide communication among local ports on a switch that are all assigned to the same VLAN.
I have a feeling that your original question was focused on a different aspect, though: You probably expected that if you exclude some VLANs from trunks, these VLANs will not be propagated via VTP to surrounding switches. Sadly, this is not the case. The switchport trunk allowed vlan command only affects data traffic in individual VLANs but it has no impact on the operation of VTP protocol. The VTP still advertises all VLANs, regardless of which VLANs are allowed on a trunk. To put it plainly, in a VTP domain, all server/client switches will know about all VLANs. THere is no legal possibility of having a single VTP domain consisting of server/client switch and yet have the switches differ in their VLAN database contents. It's as easy as that: one VTP domain = one big common VLAN database.
Best regards,
Peter

Similar Messages

  • VTP Pruning vs Allowing VLANs on Trunk ports

    We would like to know best approach to reduce VLAN traffic on our network. We are currently trunking all fiber ports 802.1q.
    We have about 73 VLANs across the network. We have done a lot of research and there seem to be a lot of theoretical answers but no one who uses it in practice.
    Here is our current configs for fiber ports between closets:
    Cisco WMH6509
    interface GigabitEthernet2/8
     description Fiber To STB Lab 3850
     switchport
     switchport trunk encapsulation dot1q
     switchport mode trunk
     no ip address
     no snmp trap link-status
    end
    Cisco STB Lab 3850
    interface GigabitEthernet1/1/1
     description Fiber To WMH6509
     switchport mode trunk
    end
    We are considering:
    VTP Pruning Enable
               or
     switchport
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 26,99,109,188
     switchport mode trunk
    Thanks,
    Tom

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of   the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    As I have some years (cough - decades) software development experience, I lean toward automation solutions, so, for example, I often prefer dynamic routing over static routing, and so likewise, I prefer VTP over manual configuration on multiple devices.
    However, VTP does have some "quirks".  For example, this year I ran into an issue where an edge switch had a new VLAN defined to a port which wasn't in use on a transit switch, so VTP auto pruning, pruned it off the transit's uplink trunk.  (I was a bit of a pain to find the cause as VTP doesn't prune right away - edge worked for a bit and then it stopped working.  One fix would have been to stop using VTP auto-pruning, across the whole VTP domain, but instead, configured VTP to not auto-prune the needed VLAN across the needed trunk.)
    So, as Paul notes, VTP auto pruning might be easier to get going, but be prepared for unexpected incidents (again, not saying you'll have any, just be prepared).  So, if you're prepared, I would go with VTP auto pruning, but if you want to "play safe", go with Paul's recommendation.

  • Unable to add allowed VLANs to TenGig trunk port

    Hi,
    I've got a ten gig interface on a 6509 running 12.2(33) configured as a trunk, but I've not been able to add any allowed VLANs as I've done before on other ten gig ports on different 6509 chassis. Am I missing something obvious?
    I'm assuming that the reason I'm unable to set the encapsulation to dot1q is because the new hardware doens't support ISL, hence no need. The command to add the VLANs however doesn't get rejected, it just doesn't appear to do anything.
    I've tried adding single VLANs and multiples, but no joy. Any ideas?
    Here's what I've done:
    SWITCH_1631(config)#default int t4/1
    Interface TenGigabitEthernet4/1 set to default configuration
    SWITCH_1631#sh ru int t4/12
    Building configuration...
    Current configuration : 65 bytes
    interface TenGigabitEthernet4/12
     no ip address
     shutdown
    end
    SWITCH_1631(config)#int t4/1
    SWITCH_1631(config-if)#switchport
    SWITCH_1631(config-if)#switchport mode trunk
    SWITCH_1631(config-if)#switchport trunk allowed vlan ?
      WORD    VLAN IDs of the allowed VLANs when this port is in trunking mode
      add     add VLANs to the current list
      all     all VLANs
      except  all VLANs except the following
      none    no VLANs
      remove  remove VLANs from the current list
    SWITCH_1631(config-if)#switchport trunk allowed vlan add 700
    SWITCH_1631(config-if)#
    SWITCH_1631#sh vlan id 700
    VLAN Name                             Status    Ports
    700  VLAN_NAME                        active    <snip>
    SWITCH_1631#sh ru int t4/1
    Building configuration...
    Current configuration : 74 bytes
    interface TenGigabitEthernet4/1
     switchport
     switchport mode trunk
    end

    Steve,
    Thanks for getting back to me. You're right that it is by default a dot1q trunk allowing all VLANs, therefore it should work for what I want to do.
    Port                Mode         Encapsulation  Status        Native vlan
    Gi3/39              on           802.1q         trunking      1
    Te4/1               on           802.1q         trunking      1
    Po1                 on           802.1q         trunking      50
    Po2                 on           802.1q         trunking      50
    Po3                 on           802.1q         trunking      50
    Po4                 on           802.1q         trunking      50
    Po5                 on           802.1q         trunking      50
    Port                Vlans allowed on trunk
    Gi3/39              15-16,20-23,30,401,608
    Te4/1               1-4094
    Po1                 10,13,20-21,25,30,50,52,61,70,600,700-701,950
    Po2                 10,20,30,50,52,61,70,600,700-701,950
    Po3                 10,20,30,50,61,70,600,700-701,950
    Po4                 10,20,30,50,61,70,600,700-701,950
    Po5                 2-3,10-23,25-26,30,35-36,40,50-53,56,58,61,65,70,77,101-102,145-146,155-158,401-402,600-602,608,700-701,800,950
    The problem was that I've always been advised that best practise is to only allow the VLANs that are actually required on a trunk to avoid broadcasting traffic unnecessarily. I worked out what the issue was though, and it was a pretty simple one!
    Once I saw that 1-4094 was allowed I tried "switchport trunk allowed vlan remove 700" which worked and left me with 1-699,701-4094.
    Then I realised what the problem was  trying to use the "add" command when all possible VLANs had already been added. As soon as I got rid of it and used "switchport trunk allowed vlan 700" followed by "switchport trunk allowed vlan add 701" I was back in business.
    So it was a very simple issue, but thank you Steve for pointing me in the right direction and confirming that all the VLANs were already allowed!

  • How to configure a port channel with VLAN trunking (and make it work..)

    We're trying to configure a port channel group with trunked ports to connect a NetApp HA pair. We want to create two data LIFs and connect them to the switch stack.  We are trying to create 2 data lifs, one for cifs and one for nfs that are on different vlans.
    We want the same ports to be able to allow multiple vlans to communicate. (trunked)
    These data lifs should be able to fail over to different nodes in the HA pair and still be able to communicate on the network.
    What this means is that we have to connect 4 ports each for each node in the NetApp HA Pair to the switches and create a port channel of some type that allows for trunked vlans. When we configure the ports, the configuration is as follows (below):
    We are only able to configure an IP on one of the vlans.
    When we configure an IP from another vlan for the data lif, it does not respond to a ping.
    Does anyone have any idea what I'm doing wrong on the Cisco switch?
    interface GigabitEthernet4/0/12
    description Netapp2-e0a
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet4/0/13
    description Netapp2-e0c
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet6/0/12
    description Netapp2-e0b
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet6/0/13
    description Netapp2-e0d
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface Port-channel20
    description Netapp2-NFS
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    spanning-tree portfast
    spanning-tree bpduguard enable
    end

    Our problem was fixed by the storage people.  They changed the server end to trunk, and the encapsulation / etherchannel.
    I like all the suggestions, and they probably helped out with the configuration getting this to work.
    Thanks!
    interface Port-channel20
    description Netapp2-NFS
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    interface GigabitEthernet4/0/12
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet4/0/13
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet6/0/12
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet6/0/13
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active

  • AP-1131AG: 2 VLANs/SSIDs, switch port configuration?

    We're setting up a (seemingly) simple deployment of some APs, and want 2 SSIDs...one will have Pre-Shared WEP and one will be open and broadcast (with access-lists on the router). My question is how to set up the switch port to match my AP, in order for it to pass both VLANs (in this case I've setup WLAN100=VLAN100 and WLAN101=VLAN101)...Do I have to configure trunking on that switchport? Thanks for any links or answers on this!!!

    Hi Vince,
    Here is a great doc that goes over this concept in detail. You will need to configure Trunking on the switchport. Have a look at what yours might look like;
    switchport mode trunk
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 1
    switchport trunk allowed vlan 1,100,101
    From this excellent doc;
    Using VLANs with Cisco Aironet Wireless Equipment
    http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801d0815.shtml#clic2935xl
    Hope this helps!
    Rob

  • Switch trunk native and switchport trunk allowed commands

      Hello,
    What will be the result of having these two commands defined on trunk
    Switch(Config-if)# switchport trunk native vlan 500
    Switch(Config-if)# switchport trunk allowed vlan remove 500
    Thanks        

    The first command would send traffic untagged over vlan 500, but the second command removes vlan 500 from the trunk, so I think you would lose traffic for anything using vlan 500....
    HTH,
    John
    *** Please rate all useful posts ***

  • Missing Allowed vlans on trunk on Standby ACE.

    Guys,
    I would like to know if allowing vlans under portchannel will replicate on standby unit.Somehow I see all configuration is sync except  switchport trunk allowed vlan under Portchannel.             
    Thanks
    Ajay

    Hi Siva,
    I remove 3rd port from port channel but still vlans are not getting sync.
    ACE1/Admin# sh vlan
    Vlans configured on physical port(s)
    vlan3001  vlan3060  vlan3200-3201  vlan3208  vlan3260-3262  vlan3264-3265  vlan3270-3272  vlan3274-3275  vlan3280  vlan3300-3302  vlan3650-3652  vlan3661-3663  vlan3668-3669  vlan4090
    ACE1/Admin#
    ACE2/Admin# sh vlan
    Vlans configured on physical port(s)
    vlan3001  vlan3200-3201  vlan3208  vlan3260-3262  vlan3264-3265  vlan3270-3272  vlan3274-3275  vlan3300-3302  vlan3650-3652  vlan3661  vlan3668-3669  vlan4090
    ACE2/Admin#
    ACE1/Admin# sh ft group status
    FT Group                     : 1
    Configured Status            : in-service
    Maintenance mode             : MAINT_MODE_OFF
    My State                     : FSM_FT_STATE_ACTIVE
    Peer State                   : FSM_FT_STATE_STANDBY_HOT
    Peer Id                      : 1
    No. of Contexts              : 1
    Running cfg sync status      : Running configuration sync has completed
    Startup cfg sync status      : Startup configuration sync has completed
    ft peer 1
      heartbeat interval 300
      heartbeat count 10
      ft-interface vlan 4090
      query-interface vlan 3001
    ft group 1
      peer 1
      no preempt
      priority 150
      associate-context Admin
      inservice
    any suggestion/ next steps to troubleshoot ?
    Thanks
    Ajay

  • CSCur53506 - broadcast flood when allowed vlan add/remove on protected port

    Does not this Bug occur in IOS 15.XX ?

    Thanks for the reply - yes I did save it.  All the other ports have the command.  But when the phone boots up - it ends up disappearing after the above occurs:
    When the phone boots up - it seems to encounter a broadcast storm (???) the port goes from this:
    interface gigabitethernet36
    switchport trunk allowed vlan add 10
    to this:
    interface gigabitethernet36
    storm-control broadcast enable
    storm-control broadcast level 10
    storm-control include-multicast
    port security max 10
    port security mode max-addresses
    port security discard trap 60
    spanning-tree portfast
    switchport trunk allowed vlan add 10
    macro description ip_phone
    !next command is internal.
    macro auto smartport dynamic_type ip_phone
    Then in a minute or two I'm no longer able to ping the voicelan - and when I do a show run - gi36 isn't even visible.  However, the PC that is also on gi36 works fine.
    If I then reissue the 'switchport trunk allowed vlan add 10' to gi36 - the phone is pingable - and works continuously until the phone is rebooted.
    So I'm not really sure what happens during the bootup that causes this to happen, or a way to try and prevent it from occuring.

  • Port Channel and VLAN trunking

    When configuring trunking of VLANS accross a Port Channel, do we need to configure vlan pruning on both the port-Channel port and the physical ports ???
    E.g. do I need to apply the "switchport trunk allowed vlan add " command under each physical port and the port channel port ? Or only under the port channel port ?
    Thanks

    In short, yes. Configure the port channel interface exactly as you do the physical interfaces and both ends should be an exact match. otherwise you will have problems getting the channel to come up or stay up.
    -Mark

  • 897VAW: Cannot add Allowed vlans to Trunk on WLAN-GigabitEthernet interface

    Hi,
    I am trying to configure the Access Point module on my Cisco Router (897AVW), however I am unable to route / ping between the router and the AP.
    In a few examples I've seen, the wlan-GigabitEthernet interface has the command:
    switchport trunk allowed vlan 1-3,1002-1005
    or
    switchport trunk native vlan 2
    I have tried both and although the router doesn't error, show-ing the config, neither commands have taken.
    Is there something I am doing wrong or is this a bug in the IOS?
    To save making this post long, my latest running configs are on my blog:
    Router: http://www.thingsgeeky.walker.uk.com/?p=3781
    AP: http://www.thingsgeeky.walker.uk.com/?p=3781
    Many Thanks
    W.

    Hi,
    I am trying to configure the Access Point module on my Cisco Router (897AVW), however I am unable to route / ping between the router and the AP.
    In a few examples I've seen, the wlan-GigabitEthernet interface has the command:
    switchport trunk allowed vlan 1-3,1002-1005
    or
    switchport trunk native vlan 2
    I have tried both and although the router doesn't error, show-ing the config, neither commands have taken.
    Is there something I am doing wrong or is this a bug in the IOS?
    To save making this post long, my latest running configs are on my blog:
    Router: http://www.thingsgeeky.walker.uk.com/?p=3781
    AP: http://www.thingsgeeky.walker.uk.com/?p=3781
    Many Thanks
    W.

  • Template(best practice) for Switch ports

    Hi,
    Looking for best practice advice on switchport config for client facing ports.
    We recently had an incident where an access port turned into a trunk(trunk mode desirable), which we obviously do not want to happen again!
    For Access Ports(First two should stop DTP I'm hoping?):
    switchport mode access
    switchport nonegotiate
    storm-control broadcast level 20.00
    storm-control action trap
    no cdp enable
    spanning-tree portfast
    spanning-tree bpdufilter enable
    spanning-tree guard root
    switchport port-security maximum 10
    switchport port-security
    switchport port-security aging time 10
    And for trunk ports to clients:
    switchport trunk encapsulation dot1q
    switchport mode trunk
    switchport trunk allowed vlan xxx,xxx
    switchport nonegotiate
    storm-control broadcast level 20.00
    storm-control action trap
    no cdp enable
    spanning-tree bpdufilter enable
    spanning-tree guard root
    Thanks in advance.

    Look here: http://www.cisco.com/en/US/docs/solutions/Enterprise/Branch/E_B_SDC1.html#wp68930
    That's Cisco's branch design doc from Design Zone.
    For those that want a fast answer:
    For VoIP phones and PC:
    interface GigabitEthernet1/0/6 - interface GigabitEthernet1/0/23
    description phone with PC connected to phone
    switchport access vlan 102
    switchport mode access
    switchport voice vlan 101
    switchport port-security maximum 2
    switchport port-security
    switchport port-security aging time 2
    switchport port-security violation restrict
    switchport port-security aging type inactivity
    ip arp inspection limit rate 100
    load-interval 30
    srr-queue bandwidth share 1 70 25 5
    srr-queue bandwidth shape 3 0 0 0
    priority-queue out
    mls qos trust device cisco-phone
    spanning-tree portfast
    spanning-tree bpduguard enable
    ip verify source
    ip dhcp snooping limit rate 100
    For data only:
    interface GigabitEthernet1/0/24- interface GigabitEthernet1/0/28
    description DATA only ports
    switchport access vlan 102
    switchport mode access
    switchport port-security maximum 3
    switchport port-security
    switchport port-security aging time 2
    switchport port-security violation restrict
    switchport port-security aging type inactivity
    ip arp inspection limit rate 100
    load-interval 30
    srr-queue bandwidth share 1 70 25 5
    srr-queue bandwidth shape 3 0 0 0
    priority-queue out
    spanning-tree portfast
    spanning-tree bpduguard enable
    ip verify source
    ip dhcp snooping limit rate 100
    That's Cisco's recommendation.
    And just my opinion is that I'd much rather shut a port down that receives a BPDU than just filter it. Reason being that you can't trust users not to do something stupid, like hook two switch ports to the same switch they're using at their desk in an effort to "make the network faster". For two, if someone malicious plugs in a switch into your environment, shut the port down. . .that makes it hard for them to do anything malicious.

  • Does it need add the native vlan to allowed vlan list ?

    If I confiured the port like this "
    switchport trunk native vlan 10
    switchport trunk allowed vlan 11,12"
    does the vlan 10 allowed passing ? or it still need add vlan 10 to the allowed vlan list like "
    switchport trunk native vlan 10
    switchport trunk allowed vlan 10,11,12"
    Thanks

    Yes you can remove the native VLAN from the list, and it does prevent the native VLAN from traversing the trunk. That is, if you look at the Spanning Tree for the native VLAN, the trunk will be absent from the list of ports on the VLAN.
    The question of untagged frames is a different one. There are some control protocols, particularly link-local ones, that are sent untagged, and these will traverse the trunk regardless. However, they are not considered as part of the native VLAN Spanning Tree as such.
    But beware: there is a bug in earlier IOS and in all CatOS switches! If you use a non-1 VLAN as your trunk native VLAN, and you disallow it from the trunks, and there are no other ports carrying that native VLAN, then the Spanning Tree for that VLAN shut down. That is fair enough. But the bug is that the Spanning Tree for VLAN 1 also breaks down, sending your network into meltdown.
    Kevin Dorrell
    Luxembourg

  • Server Port - Trunk Mode

    Hi,
    One of the Server ports (pointing towards a UCS Chassis) on my fabric interconnect is currently showing as down as it is Trunk mode not Fabric Mode as per all the other server ports.
    For some reason when I look under the LAN tab this one interface is showing under "internal LAN". I have tried disabling and/or deleting the interface from under "internal LAN" however every time I re-configure the port as a Server Port it is showing back under and the mode remains in Trunk.
    Does anyone have some advice how I can get this port out of Trunk Mode and into Fabric Mode?
    Many Thanks, Paul

    Hi Cristian,
    As requested please see outputs below:
    UCS1-A(nxos)# sh run int e1/22
    interface Ethernet1/22
      description S: Server
      no pinning server sticky
      switchport mode trunk
      switchport trunk native vlan xxx4
      switchport trunk allowed vlan xxx4,xxx7
      no shutdown
    UCS1-A(nxos)# show int fex-fabric
         Fabric      Fabric       Fex                FEX
    Fex  Port      Port State    Uplink    Model         Serial
      1    Eth1/1        Active     1         N20-C6508  xx
      1    Eth1/2        Active     2         N20-C6508  xx
      2    Eth1/3        Active     1         N20-C6508  xx
      2    Eth1/4        Active     2         N20-C6508  xx
      3    Eth1/5        Active     1         N20-C6508  xx
      3    Eth1/6        Active     2         N20-C6508  xx
      4    Eth1/7        Active     1         N20-C6508  xx
      4    Eth1/8        Active     2         N20-C6508  xx
      5    Eth1/9        Active     1         N20-C6508  xx
      5   Eth1/10        Active     2         N20-C6508  xx
      6   Eth1/11        Active     1         N20-C6508  xx
      6   Eth1/12        Active     2         N20-C6508  xx
      7   Eth1/13        Active     1         N20-C6508  xx
      7   Eth1/14        Active     2         N20-C6508  xx
      8   Eth1/15        Active     1         N20-C6508  xx
      8   Eth1/16        Active     2         N20-C6508  xx
      9   Eth1/17        Active     1         N20-C6508  xx
      9   Eth1/18        Active     2         N20-C6508  xx
    10   Eth1/19        Active     1         N20-C6508  xx
    10   Eth1/20        Active     2         N20-C6508  xx
    11   Eth1/21        Active     1         N20-C6508  xx
    12   Eth1/23        Active     1         N20-C6508  xx
    12   Eth1/24        Active     2         N20-C6508  xx
    13   Eth1/25        Active     1         N20-C6508  xx
    13   Eth1/26        Active     2         N20-C6508  xx
    14   Eth1/27        Active     1         N20-C6508  xx
    14   Eth1/28        Active     2         N20-C6508  xx
    UCS1-A(nxos)# show fex 1 detail
    FEX: 1 Description: FEX0001   state: Online
      FEX version: 5.0(3)N2(2.11.3a) [Switch version: 5.0(3)N2(2.11.3a)]
      FEX Interim version: 5.0(3)N2(2.11.3a)
      Switch Interim version: 5.0(3)N2(2.11.3a)
      Chassis Model: N20-C6508,  Chassis Serial: XXX
      Extender Model: UCS-IOM-2204XP,  Extender Serial: XXX
      Part No: 73-14488-03
      Card Id: 184, Mac Addr: c0:67:af:84:a6:5a, Num Macs: 38
      Module Sw Gen: 21  [Switch Sw Gen: 21]
      post level: complete
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth1/1
      Fabric interface state:
        Po1025 - Interface Up. State: Active
        Eth1/1 - Interface Up. State: Active
        Eth1/2 - Interface Up. State: Active
      Fex Port        State  Fabric Port
             Eth1/1/1  Down      Po1025
             Eth1/1/2  Down      Po1025
             Eth1/1/3  Down        None
             Eth1/1/4  Down        None
             Eth1/1/5  Down        None
                    Eth1/1/6  Down        None
             Eth1/1/7  Down        None
             Eth1/1/8  Down        None
             Eth1/1/9  Down      Po1025
            Eth1/1/10  Down      Po1025
            Eth1/1/11  Down        None
            Eth1/1/12  Down        None
            Eth1/1/13  Down        None
            Eth1/1/14  Down        None
            Eth1/1/15  Down        None
            Eth1/1/16  Down        None
            Eth1/1/17    Up      Po1025
    Logs:
    01/03/2014 11:23:14.295257: Module register received
    01/03/2014 11:23:14.296133: Registration response sent
    01/03/2014 11:23:14.580311: Module Online Sequence
    01/03/2014 11:23:17.47105: Module Online
    If possible would you be free to discuss this on a WebEx?
    Kind Regards, Paul

  • Switchport trunk allowed - Cisco / HP

    Hi, I have a simple query and just seeking some clarification....
    I have a Cisco 3750X with various vlans configured. One interface has the command: "Switchport Trunk allowed vlan 100, 200". I understand it will ONLY forward packets for vlan 100 & 200 on this interface - certainly the case if connected to another Cisco device.
    On the other end of the interface is a HP1810 switch. The ports are configured for vlan 100, 200 and 300. I have looked at the config of the Cisco stack and there is no mention of vlan 300 at all. Is it safe to assume the Cisco switch is not doing any forwarding for vlan 300 to the HP if it is not defined in its config or the allowed command?
    Thanks, Harv

    yes, you can assume that the Cisco switch is not forwarding anything from itself to towards HP for vlan 300 but the HP will be sending the traffic for VLAN300 on the Tagged ports. 
    I think you can remove the Tagged PORTNAME on HP under the VLAN 300 configuration as well. Removing the Tagged PortXX under the vlan 300 configuration on HP where XX is the trunk port connecting to the Cisco will stop HP for forwarding any traffic towards the Cisco as well.
    Manish

  • Switchport trunk native vlan & switchport access vlan dual configuration

    I've discovered this dual configuration on a 3500xl switch while troubleshooting an incrementing runts issue. Could the config of this port be related to the issue at hand?
    port configuration:
    interface FastEthernet0/3
    duplex full
    speed 100
    switchport access vlan 203
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 203
    switchport trunk allowed vlan 1,203,204,220,1002-1005
    switchport mode trunk
    spanning-tree portfast

    Hi,
    The 'switchport access vlan' command will have no effect on the configuration you have on this port. The port will operate as a trunk and will dis-regard any config that pertains to an access port.
    Hope that helps ...
    Paresh

Maybe you are looking for

  • PI on IDOC to CIDX

    Dear All, I just managed my configuration of PI for B2B (IDOC - CIDX). I am using "Business System without party for SAP ERP IDOC" and  "Communication component with Party for CIDX Adapter". I managed to send the idoc to SAP PI. I can see the message

  • Problem with more than one item in a track

    DVDSP 4.0.2 / OSX.4.2 I've built a DVD with several tracks. In each track I've placed several .m2v files, one after another. Finished build plays fine on my Mac and on one of my stand alone DVD players. But on another stand alone (Sony DVP-S360) some

  • Need Help in Smartforms - multiple pages

    Hi all, I have developed a Smartform in which i have 2 PAGES. in the First Page : there are many windows .                            Due to space crunch , i can only print a single line / first record alone in the Main       Window. the size of the

  • Iphoto '08 won't open

    Iphoto '08 won't open.  I tried removing the battery and putting it back in.  I have 18,000 pictures.  Hope I haven't lost them.  Do have a separate hard drive for back-up.  didn't do anything unusual.  ????

  • Mail For Exchange - Interesting and Challenging Pr...

    Hi all, We've been running Mail For Exchange in our organisation for around 6 months now without a problem. And now we have a problem I cannot seem to father out. Searched forums, checked and double checked things and no further, so I post on here ho