Nexus 3548 Switch doesn't recognize command " vtp mode Server / Client"

Hi Community.
I have a brand new Nexus 3548 switch. And I did the vtp setup:
vtp version 2
vtp password ******
vtp domain *****
Every thing is ok, but If I use the command "vtp mode server" the switch doesn't know that command. Even it doesn't know the "vtp mode" subcommand?
What's the problem ?
Best regards patrick

The Nexus 3548 supports only Transparent mode:
Step 5 vtp mode {transparent| off} Sets the VTP mode to transparent or off.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3548/sw/layer_2_switching/b_Cisco_N3548_Layer_2_Switching_Config_503A1.pdf
I have no clue why.
Patrick

Similar Messages

  • Vtp mode server operational question

                       Hi,
    So I would think if a vlan is added to a switch whose vtp mode is server and that vlan is then in turn propogated to a switch in either client or server mode, if said added vlan is not saved to the start-up config on the switch is was added to and that switch is rebooted then the added vlan should in turn be removed from the other client and server mode switches.
    Is this correct?
    Thank you.
    Basically I am trying to find out if a add a vlan to a switch in server mode and is messes everything up will a reboot fix it ( ie remove it from any other switches that have now added the new vlan to their vlan database even if one of the switches that learned the new vlan is a switch in server mode.)

    Yes By Right When your VTP server comes up after a Reboot it will readvertise all Vlans and all switches will sync up its Vlan database .
    If you dont save the vlan in the VTP server and VTP server gets rebooted ,Then as it comes up all swiches in the domain will also delete that unsaved Vlan from its Databse as well ,
    This is True if you have only one VTP server for that VTP domain.If you have more than one VTP servers  than situation is more complicated .then configuration revision number plays the deciding factor here

  • Hardware failure on Nexus 3548 switch

    Suddenly my Nexus switch was unreachable and when i logged in through console i found all the ports are in faulty state with the below error message. Any known solution for this case.
    Device Model:3548P-10G
    Version : version 6.0(2)A1(1b)
    2014 Nov 16 23:12:23 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/43 
    2014 Nov 16 23:12:23 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/44 
    2014 Nov 16 23:12:23 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/29 
    2014 Nov 16 23:12:23 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/30 
    2014 Nov 16 23:12:23 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/31 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/32 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/13 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/14 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/15 
    2014 Nov 16 23:12:24 SW1 %ETHPORT-5-IF_DOWN_HW_FAILURE: Interface Ethernet1/47 is down (Hardware Failure)
    2014 Nov 16 23:12:24 SW1 last message repeated 1 time
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/16 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/37 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/38 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/39 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/40 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/25 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/26 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/27 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/28 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/1 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/2 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/3 
    2014 Nov 16 23:12:24 SW1 %NOHMS-2-NOHMS_DIAG_ERROR: Module 1: Runtime diag detected major event: Port failure: Ethernet1/4 
    2014 Nov 16 23:12:24 SW1 %ETH_PORT_CHANNEL-5-PORT_INDIVIDUAL_DOWN: individual port Ethernet1/47 is down
    2014 Nov 16 23:12:25 SW1 %ETHPORT-5-IF_DOWN_HW_FAILURE: Interface Ethernet1/48 is down (Hardware Failure)
    2014 Nov 16 23:12:25 SW1 last message repeated 1 time
    2014 Nov 16 23:12:25 SW1 %ETH_PORT_CHANNEL-5-PORT_INDIVIDUAL_DOWN: individual port Ethernet1/48 is down
    2014 Nov 16 23:12:25 SW1 %ETHPORT-5-IF_DOWN_HW_FAILURE: Interface Ethernet1/17 is down (Hardware Failure)
    2014 Nov 16 23:12:25 SW1 last message repeated 1 time
    2014 Nov 16 23:12:25 SW1 %ETHPORT-5-IF_DOWN_HW_FAILURE: Interface Ethernet1/18 is down (Hardware Failure)
    2014 Nov 16 23:12:26 SW1 last message repeated 1 time
    2014 Nov 16 23:12:26 SW1 %ETHPORT-5-IF_DOWN_HW_FAILURE: Interface Ethernet1/7 is down (Hardware Failure)

    I would highly recommend that you contact Cisco TAC, they will gladly assist you with your trouble, and if its damage, replace it if you a SmartNET contract with Cisco :)
    You can e-mail them directly: [email protected]
    Just a heads up, provide in your e-mail your Cisco.com user ID, Serial of device and Contract number(s) since they will ask it :D
    Rate or mark as correct helpful post! :)

  • Cisco catalyst 3850 switch won't take command: "switchport mode trunk encapsulation dot 1q"

    Hi all,
        I'am working on this switch's configuration. when I typed "switchport mode trunk encapsulation dot 1q", I got an error " invavid input". I'm guessing that this model already set encapsulation type to dot 1q, and that's why the switch won't take it, right? 
       Please help!

    According to the documents it supports both.
    You are however using the wrong command, it should be -
    "switchport trunk encapsulation dot1q"
    ie. no "mode" keyword.
    If it doesn't take that then do a "sh int <x> capabilities" and it should show you which encapsulation methods are supported.
    Jon

  • Change VTP mode from Client to Server in a production VTP Domain

    Dear all,
    we have a production VTP Domain with some switches acting as VTP Client and 1 as a VTP Server. now the master is dead, and we would like to change the mode of one of the remaining switches from VTP Client to VTP Master. IMHO this change should not have any impact on the current configuration of the switches (and on the VLAN database), but we would like to have your opinion about this.
     Any help/feedback will be greatly appreciated
    thank you

    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
    That should be fine.  The real difference between a VTP server vs. VTP client, the former allows (manual) VLAN configuration changes and the latter doesn't.

  • Thoughs on interconnecting Nexus 3548 and 3750 switches

    Hi,
    I have two nexus 3548 switches.
    I have created port-group 1  on both switches to group eth1/47 with eth1/48.
    I have 4 sfps, 2 per switch. to connect to a single 3750 that I want to group together as well.
    So I have gi1/0/31 going to eth1/1 on nexus1 and gi1/0/32 going to eth1/2 on nexus1
    I have gi1/0/33 goin to eth1/1 on nexus2 and gi1/0/32 goin to eth1/2 on nexus2
    When I create the port group on the 3750 do I create one group with all 4 ports or will I have to create 2, one per nexus switch?
    Thanks

    Thanks for the replies. I finally got to test the hardware and config yesterday.
    Just so I am clear. the vpc and peer to peer links are only for interconnecting the two Nexus switches. I think I got that right. sho VPC br seems to say it is up. I am using Po5
    vPC domain id : 1
    Peer status : peer adjacency formed ok
    vPC keep-alive status : peer is alive
    Configuration consistency status : success
    Per-vlan consistency status : success
    Type-2 consistency status : success
    vPC role : secondary
    Number of vPCs configured : 0
    Peer Gateway : Disabled
    Dual-active excluded VLANs : -
    Graceful Consistency Check : Enabled
    Auto-recovery status : Disabled
    vPC Peer-link status
    id Port Status Active vlans
    1 Po5 up 1
    Next do I create a port channel on Nex1 and Nex2 for the two ports that connect to the 3750 (Po6 for example) or do I add the two links to the 3750s to Po5 ? I thought I add them to Po 5 but since I am mixing 1000 and 10G ports it doesnt seem to like it.

  • Unable to enable sflow feature on Nexus 3548

    When I try to enable sflow via "feature sflow" command on the nexus 3548 switches running 6.0(2)A1(1C) I receive:
    Error: while enabling/disabling service: sflow, err: service not found (0x401e0005)
    Any input would be greatly appreciated.
    Thank you

    Ryan,
    Thanks for the reply... it appears to be supported on the 3000, but not the 3524, which, in my opinion is fairly stupid... I know, I know, "its an architecture thing!", but really, Cisco, you couldn't have considered that customers would want this type of visibility in this switch?? Really?!?!
    Anyway, thanks for the info... have you found a work-around or similar product that provides you similar visibility?

  • Nexus 3548 temperature alarm

    Hi all,
        My name is Harry from China shanghai and  I have a trouble in Cisco Nexus 3548 switch  the system reload at 2 min after shutdown .
        How can i do it please help me.
    System info
    N3548# sh inventory 
    NAME: "Chassis", DESCR: "Nexus 3548 Chassis"
    PID: N3K-C3548P-10G    , VID: V00 , SN: FOC1625R004
    NAME: "Module 1", DESCR: "48x10GE Supervisor"
    PID: N3K-C3548P-10G    , VID: V00 , SN: FOC16245CPU
    NAME: "Fan 1", DESCR: "Chassis fan module"
    PID: NXA-FAN-30CFM-F   , VID: N/A , SN: N/A
    NAME: "Fan 2", DESCR: "Chassis fan module"
    PID: NXA-FAN-30CFM-F   , VID: N/A , SN: N/A
    NAME: "Fan 3", DESCR: "Chassis fan module"
    PID: NXA-FAN-30CFM-F   , VID: N/A , SN: N/A
    NAME: "Fan 4", DESCR: "Chassis fan module"
    PID: NXA-FAN-30CFM-F   , VID: N/A , SN: N/A
    NAME: "Power supply 1", DESCR: "AC power supply"
    PID: N2200-PAC-400W    , VID: V04 , SN: DTN1707P1VV
    NAME: "Power supply 2", DESCR: "AC power supply"
    PID: N2200-PAC-400W    , VID: V04 , SN: DTN1707P1VS
    N3548#               
    N3548# 
    N3548# sh ser
               ^
    % Invalid command at '^' marker.
    N3548# sh version 
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie
    s_home.html
    Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
    The copyrights to certain works contained herein are owned by
    other third parties and are used and distributed under license.
    Some parts of this software are covered under the GNU Public
    License. A copy of the license is available at
    http://www.gnu.org/licenses/gpl.html.
    Software
      BIOS:      version 1.9.0
      loader:    version N/A
      kickstart: version 6.0(2)A4(3)
      system:    version 6.0(2)A4(3)
      Power Sequencer Firmware: 
                 Module 1: version v2.1
      BIOS compile time:       10/13/2012
      kickstart image file is: bootflash:///n3500-uk9-kickstart.6.0.2.A4.3.bin
      kickstart compile time:  11/21/2014 9:00:00 [11/21/2014 19:29:20]
      system image file is:    bootflash:///n3500-uk9.6.0.2.A4.3.bin
      system compile time:     11/21/2014 9:00:00 [11/21/2014 21:09:06]
    Hardware
      cisco Nexus 3548 Chassis ("48x10GE Supervisor")
      Intel(R) Pentium(R) CPU  @ 1.50GHz
     with 3805876 kB of memory.
      Processor Board ID FOC16245CPU
      Device name: N3548
      bootflash:    2007040 kB
    Kernel uptime is 0 day(s), 0 hour(s), 3 minute(s), 4 second(s)
    Last reset at 30232 usecs after  Fri Dec 19 21:29:56 2014
      Reason: Power down due to temperature sensor policy trigger
      System version: 6.0(2)A4(3)
      Service: 
    plugin
      Core Plugin, Ethernet Plugin
    --More--2014 Dec 19 21:28:11 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 105 seconds due to major temperature alarm
    2014 Dec 19 21:28:16 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 100 seconds due to major temperature alarm
    2014 Dec 19 21:28:21 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 95 seconds due to major temperature alarm
    2014 Dec 19 21:28:26 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 90 seconds due to major temperature alarm
    2014 Dec 19 21:28:31 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 85 seconds due to major temperature alarm
    2014 Dec 19 21:28:36 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 80 seconds due to major temperature alarm
    2014 Dec 19 21:28:41 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 75 seconds due to major temperature alarm
    2014 Dec 19 21:28:46 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 70 seconds due to major temperature alarm
    2014 Dec 19 21:28:51 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 65 seconds due to major temperature alarm
    2014 Dec 19 21:28:56 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 60 seconds due to major temperature alarm
    2014 Dec 19 21:29:01 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 55 seconds due to major temperature alarm
    2014 Dec 19 21:29:06 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 50 seconds due to major temperature alarm
    2014 Dec 19 21:29:11 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 45 seconds due to major temperature alarm
    2014 Dec 19 21:29:16 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 40 seconds due to major temperature alarm
    2014 Dec 19 21:29:21 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 35 seconds due to major temperature alarm
    2014 Dec 19 21:29:26 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 30 seconds due to major temperature alarm
    2014 Dec 19 21:29:31 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 25 seconds due to major temperature alarm
    2014 Dec 19 21:29:36 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 20 seconds due to major temperature alarm
    2014 Dec 19 21:29:41 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 15 seconds due to major temperature alarm
    2014 Dec 19 21:29:46 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 10 seconds due to major temperature alarm
    2014 Dec 19 21:29:51 N3548 %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN: System shutdown in 5 seconds due to major temperature alarm

    Sangeeth,
    The first thing that you will want to verify is the physical condition of 
    the switch. The Nexus 7010 chassis used a front-to-back airflow model. see 
    the diagram below for a reference: 
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/hw/nexus7000/installation/guide/n
    7k_hig_book/n7k_sys_specs.html#wp1039713 
    You will want to ensure that there is nothing blocking the intake or 
    exhaust vent of the switch. Also look at the front intake fan to see if 
    there is dust, or some other material that has accumulated that could be 
    impeding air intake. 
    Also verify if there is a device that is exhausting hot air towards the 
    intake of the switch. 
    2)
    In case if you already checked the colling you can give the below try:-
    Please remove and thoroughly clean the air filter located on the front of the Nexus 7010. 
    Find below the instructions for cleaning the Nexus 7010 air filter:
    Cleaning or Replacing the Air Filter for the Cisco Nexus 7010 Chassis
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/hw/nexus7000/installation/guide/n
    7k_hig_book/n7k_replacing.html#wp1454429
    HTH
    Regards
    Inayat
    ***********Please rate if this info is helpfull.*********

  • Nexus 3548 couldn`t enable vPC feature

    Hello All,
    I have to implement to 2 Nexus 3548 switches for a customer. The customer like to use it as core-switch (small LAN) and also like to run VPC feature. Now I have tried to active it, but I got the follow error message:
    Enter configuration commands, one per line.  End with CNTL/Z.
    chefan-swi01(config)# feature vpc
    Error: vPC feature is not supported
    Is their a way to get VPC working on these plattform?
    Software
      BIOS:      version 1.9.0
      loader:    version N/A
      kickstart: version 5.0(3)A1(1)
      system:    version 5.0(3)A1(1)
      power-seq: Module 1: version v2.1
      BIOS compile time:       10/13/2012
      kickstart image file is: bootflash:/n3500-uk9-kickstart.5.0.3.A1.1.bin
      kickstart compile time:  11/2/2012 1:00:00 [11/02/2012 09:53:29]
      system image file is:    bootflash:/n3500-uk9.5.0.3.A1.1.bin
      system compile time:     11/2/2012 1:00:00 [11/02/2012 10:27:12]
    Hardware
      cisco Nexus 3548 Chassis ("48x10GE Supervisor")
      Intel(R) Pentium(R) CPU  @ 1 with 4140896 kB of memory.
      Processor Board ID FOC17480ZHN
      Device name: chefan-swi01
      bootflash:    2007040 kB
    Thx a lot for any suggestions.
    Kind Regards, Ferdi

    Seems to be an error on the Nexus 3k product page.  We had a customer who purchased these for VPC support.
    http://www.cisco.com/en/US/products/ps11541/index.html
    Nexus 3500 Features
    Ultra-Low Latency
    Line-rate layer 2 and 3 switching at ultra-low latencies
    Ideal for high-performance trading workloads
    Mission-Critical Features
    Network Address Translation (NAT)
    Virtual Port Channel
    IEEE-1588 PTP

  • How many BGP peers does the 3548 switch support?

    Is it possible to run more than 40 peers on a single switch? What is the limitation if not?

    Hi ,
     You can have 40 BGP peers , IPV4 unicast routes handled by hardware is only 24000 .Enusre all your BGP peering routing updates is within this limits . 
    http://www.cisco.com/c/en/us/products/collateral/switches/nexus-3548-switch/data_sheet_c78-707001.html
    Table 7. Hardware Specifications Common to Both Switches
    Mode
    Normal Mode
    Warp Mode
    Hardware tables and scalability
    Number of MAC addresses
    64,000
    8000
    Number of IPv4 unicast routes
    24,000
    4000
    Number of IPv4 hosts
    64,000
    8000
    Number of IPv4 multicast routes
    8000
    8000
    Number of VLANS
    4096
    Number of ACL entries
    4096
    Number of spanning-tree instances
    Rapid Spanning Tree Protocol (RSTP): 512
    Multiple Spanning Tree (MST) Protocol: 64
    Number of EtherChannels
    24
    Number of ports per EtherChannel
    24
    Buffer size
    6 MB shared among 16 ports; 18 MB total
    Boot flash memory
    2 GB
    HTH
    Sandy

  • FCP doesn't recognize VTR mode on HVX camera

    I'm new to FCP7 and can't figure out why log and capture doesn't recognize the VTR mode on my Panasonic HVX. I turn on the camera, switch it to VTR (by pressing the MCR/VCR button) and the launch FCP with my MBP connected to the camera by FireWire. When I launch L&amp;C and the click on the now button, I get a black screen that says the camera must be in VTR mode. Yet when I launch iMovie, the capture window will play and record the video on the camera just fine. The video is on a miniDV tape. I don't have a P2 card so can't try that method.

    L&C!  Did that work?
    Works for you & I can do it from my MBP, but evidently not from my iPad.  Weird.
    OK...the thing you need to do first in FCP is choose the DV/NTSC Easy Setup. THEN try to capture from tape.
    Yeah, did that first.  I'll try again when I get home tonight.

  • Question about Nexus 3548 vPC setup

    Hi.
    We have just installed our two first Nexus 3548 switches in our Catalyst environment. We want to set up a vPC domain between the Nexuses, to use for connections to storage and other equipment.
    I have read the guide at http://www.cisco.com/c/en/us/products/collateral/switches/nexus-3000-series-switches/white_paper_c11-685753.html and tried setting it up. I created a vPC domain on both switches like this:
    nexus1:
    vpc domain 1
      role priority 2000
      system-priority 4000
      peer-keepalive destination 192.168.105.40 source 192.168.105.39 vrf default
    nexus2:
    vpc domain 1
      system-priority 4000
      peer-keepalive destination 192.168.105.39 source 192.168.105.40 vrf default
    The switches are connected with a port-channel consisting of 2x 10GE. The IP addresses above are the ones we use for managing the switches. When I configure the port-channel as "vpc peer-link", the vpc status looks OK:
    vPC domain id                     : 1
    Peer status                       : peer adjacency formed ok
    vPC keep-alive status             : peer is alive
    Configuration consistency status  : success
    Per-vlan consistency status       : success
    Type-2 consistency status         : success
    vPC role                          : primary
    Number of vPCs configured         : 0
    Peer Gateway                      : Disabled
    Dual-active excluded VLANs        : -
    Graceful Consistency Check        : Enabled
    Auto-recovery status              : Disabled
    vPC Peer-link status
    id   Port   Status Active vlans
    1    Po2    up     1,6,100,102,106
    The problem I have is that I lose connection to nexus2 when I bring up the vPC. I can no longer access it on its IP (192.168.105.40). I cannot ping it from nexus1 either. The Nexus switches are connected to our core switches, which are Catalyst 6509. nexus1 is connected to coreswitch1 using a portchannel of 2xGE and nexus2 is connected to coreswitch2 the same way. A spanning-tree cost has been set on the uplink from nexus2, to make spanning tree block that uplink, and allow traffic between the nexuses to go over the 2x 10GE portchannel instead of over the core switches. I have attached a drawing of this.
    Maybe I shouldn't use the management IP:s for peer keepalive? Does the peer keepalive need to be on a different physical link than the peer-link?
    Regards,
    Johan

    We are not using the management ports for management, but an ordinary Vlan Interface in the default vrf, as seen below. We can of course change that and instead use the mgmt0 port if that is the best approach.
    vrf context management
    vlan configuration 1,100
    vlan 1
    vlan 100
      name DMMgmtPriv
    vpc domain 1
      role priority 2000
      system-priority 4000
      peer-keepalive destination 192.168.105.40 source 192.168.105.39 vrf default
    interface Vlan1
    interface Vlan100
      no shutdown
      no ip redirects
      ip address 192.168.105.39/23

  • What is the advantage of setting VTP mode to transparent?

    I have a Cat 6509 and eighteen 3524 and/or 3548's. Obviously I want my 6509 to be in VTP server mode. But is there any advantage/disadvantage to having the 3500's in client or transparent. I would think client, but is transparent use less resources, both internal to the switch, and , external, i.e., network resources. I've seen some CCIE's insist that the 3500's must be in transparent mode and configure the VLAN info on them manually. What is preferred?

    Configuring VTP in transparent mode requires manual configuration, a VTP-transparent switch does not advertise VLAN information to other switches and will ignore VTP updates from VTP clients and servers.
    VTP propagates information about the VLAN configuration throughout the switched network. A Catalyst 6000 family switch can operate in any one of these three VTP modes:
    Server—VTP servers advertise their VLAN configuration to other switches in the same VTP domain and synchronize their VLAN configuration with other switches based on advertisements received over trunk links. VTP server is the default mode.
    Client—VTP clients are similar to VTP servers, except that you cannot create, change, or delete VLANs on a VTP client.
    Transparent—VTP transparent switches do not participate in VTP. A VTP transparent switch does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements.

  • VTP Mode not staying set?

    I was configuring a C3560-48PS for deployment in my new job and I asked my boss if he wanted to review my config before I setup a swap time. He did and came back to me stating I needed to set the switch to be a VTP client on suchandsuch domain. Hmm.. I thought I did that. So I con'd the switch, conf t, vtp mode client, vtp domain ABC123, ctrl-z. did a status on vtp, in client mode. great! So did a copy ru star and reloaded. Switch came up, just for grins did a vtp status. It's back in server mode (the switch is not currently on the network). Hmm.. So I inquired to my boss, he was puzzled and suggested an IOS upgrade. I loaded up the 12.2(25)SEE version. reloaded. attempt to set vtp to client again, saved, reloaded. and it's STILL saying it's in server mode. What the heck? This should be a fairly simple process. Any idea?

    Hello,
    The default is VTP Server with a NULL domain. VLAN and VTP data is stored within the flash:vlan.dat file. If you change the VTP mode to client first, client's can't change VTP attributes per se. If you don't have a vlan.dat file in flash and you change vtp to client and then save - these changes will not be applied. However, while in default server mode, simply set the domain name, then save the config, verify you have a vlan.dat file - then you can make any changes you like (see attachment).
    Hope this helps.
    Regards,
    James

  • Vtp mode transparent and DTP negotiation

    I don't have any equipment at home to make the following test :
    - Assuming that 2 catalysts are connected through a GigatbitEthernet interfaces
    - Assuming that both interfaces are configured with "sw mode dynamic desirable" and no other command.
    - Assuming that vtp domain name is the same
    - Assuming that both catalysts are configured with "vtp mode transparent"
    Question: Would those Catalyst able to negotiate the trunking mode ?
    (with "vtp mode server" or "client" it would work, but with "vtp mode transparent"...)
    Thanks for your help

    Bonjour,
    the trunk would be formed regardless of the VTP mode or the VTP domain name. DTP packets are sent when the port is configured as 'dynamic desirable', and the trunk will be established.
    Saluts,
    Nethelper

Maybe you are looking for