WiSM-2 in 6500 running VSS (Virtual Switching System)

Hi,
Is this SM supported in VSS chassis?  I couldn't find information about it. I found only about WiSM-1.
Thanks.

Sup2T 15.0SY VSS config guide add WiSM2 support.
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/15.0SY/configuration/guide/virtual_switching_systems.html
Service Module Support
•Application Control Engine (ACE):
–ACE20-MOD-K9
–ACE30-MOD-K9
•Firewall Services Module (FWSM): WS-SVC-FWM-1-K9
•Network Analysis Module (NAM):
–WS-SVC-NAM-1
–WS-SVC-NAM-2
•Wireless Services Module (WiSM):
–WS-SVC-WISM-1-K9
–WS-SVC-WISM2

Similar Messages

  • How to mornitor VSS (Virtual Switching System) & Stack (Switch) By Cisco Prime Infrastructure

    Dear all,
    I have 02 C6504-E with VSS (Virtual Switching System)
       and 02 C3750X-24T-L used Stack
    How to you Cisco Prime Infrastructure to monitor VSS & Stack tatus?
    Thanks.

    Virtual Switching technology is  the process of combining two standalone distribution switches found in  the local distribution layer into a single management point.
    The Virtual  Switching System functions and appears as a single switch to the wiring  closet and the core layer. You can also create Virtual Switching Systems  with a pair of standalone switches available in the core layer.
    For configuration please check  the below link:
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/user/guide/configuration/configvss.html#wp1042960

  • IPS 4270 and VSS (Virtual Switch System)

    HI,
    I would like to know whether it is possible to connect just One IPS 4270 to a VSS in etherchannel mode (two IPS interfaces per each 6500 Switch).
    Thanks in advance

    You can re-use the virtual domain ID as long as the the two VSS chassis are not directly connecting to each other. Take a look at this link:
    VVirtual Domain
    Defining the domain identifier (ID) is the first step in creating a VSS from two physical chassis. A unique domain ID identifies two switches that are intended to be part of the same VSS pair that defines the VSS domain. Assignment of a domain ID allows multiple virtual switch pairs to be connected in a hierarchical manner. Only one VSS pair can participate in a particular domain. The domain ID can have a value ranging from 1 to 255 and must be unique when multiple VSS pairs are connected together. See Figure 2-2.
    Figure 2-2 VSS Domain IDs
    http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/VSS30dg/campusVSS_DG/VSS-dg_ch2.html
    Hope this helps!
    Thanks you for rating useful posts! 

  • Configuring and Troubleshooting Virtual Switching System (VSS)

    With Anand Ganesan
    Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about how to monitor, configure, and troubleshoot the Virtual Switching System (VSS) in Cisco Catalyst 6500 Series Switches with expert Anand Ganesan.
    VSS is network system virtualization technology that pools multiple Cisco Catalyst 6500 Series Switches into one virtual switch, increasing operational efficiency, boosting nonstop communications, and scaling system bandwidth capacity to 1.4 Tbps. At the initial phase, a VSS will allow two physical Cisco Catalyst 6500 Series Switches to operate as a single logical virtual switch called a virtual switching system 1440 (VSS1440). 
    For more information, visit:  www.cisco.com/en/US/prod/collateral/switches/ps5718/ps9336/prod_qas0900aecd806ed74b.html
    The VSS simplifies network configuration and operation by reducing the number of Layer 3 routing neighbors and by providing a loop-free Layer 2 topology.
    Anand Ganesan is a customer support engineer in the High-Touch Technical Service team at Cisco specializing in switching protocols. He has been supporting major service providers and enterprise customers in switching and all other switching technologies for more than two years with Cisco. He has a total of eight years of experience in the IT industry. He holds a bachelor of engineering degree from Bharathiyar University, Coimbatore.
    Remember to use the rating system to let Anand know if you have received an adequate response. 
    Because of the volume expected during this event, Anand might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure subcommunity, LAN Switching & Routing shortly after the event. This event lasts through September 6, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Okay..they are two different /30 networks.
    my BFD interfaces are GigabitEthernet1/3/48 and GigabitEthernet2/3/48 and they work fine.
    interface GigabitEthernet1/3/48
    description Switch 1 BFD Interface
    no switchport
    ip address 10.48.0.17 255.255.255.252
    bfd interval 100 min_rx 100 multiplier 3
    end
    interface GigabitEthernet2/3/48
    description Switch 2 BFD Interface
    no switchport
    ip address 10.48.0.21 255.255.255.252
    bfd interval 100 min_rx 100 multiplier 3
    end
    switch virtual domain 1
    switch mode virtual
    switch 1 priority 110
    dual-active pair interface GigabitEthernet1/3/48 interface GigabitEthernet2/3/48 bfd
    show switch virtual dual-active bfd
    Bfd dual-active detection enabled: Yes
    Bfd dual-active interface pairs configured:
    interface-1 Gi1/3/48 interface-2 Gi2/3/48
    router eigrp 1
    network 10.0.0.0
    network 10.1.201.0 0.0.0.255
    network 10.48.0.12 0.0.0.3
    network 10.48.177.0 0.0.0.255
    network 97.0.0.0
    network 99.0.0.0
    network 100.0.0.0
    network 100.7.7.0 0.0.0.255
    network 192.34.145.0
    network 192.168.15.0
    show ip ei in
    EIGRP-IPv4 Interfaces for AS(1)
                           Xmit Queue   Mean   Pacing Time   Multicast   Pending
    Interface       Peers Un/Reliable SRTT   Un/Reliable   Flow Timer   Routes
    Gi1/2/40           1       0/0         1       0/1           50           0
    Gi1/2/41           0       0/0         0       0/1           0           0
    Vl1               1       0/0         1       0/1           50           0
    Vl7               0       0/0         0       0/1           0           0
    Vl13               0       0/0         0       0/1           0           0
    Vl15               0       0/0         0       0/1           0           0
    Vl21               0       0/0         0       0/1           0           0
    Vl25               0       0/0         0       0/1            0           0
    Vl26               0       0/0         0       0/1           0           0
    Vl134             0       0/0         0       0/1           0           0
    Vl135             0       0/0         0       0/1           0           0
    Vl140             0       0/0         0       0/1           0           0
    Vl300             0       0/0         0       0/1           0           0
    Vl400             0       0/0         0       0/1           0           0
    Vl199             0       0/0         0       0/1           0           0
    Vl6               0       0/0         0       0/1           0           0
    Vl20               0       0/0         0       0/1           0           0
    Vl24               0        0/0         0       0/1           0           0
    Vl30               0       0/0         0       0/1           0           0
    Vl31               0       0/0         0       0/1           0           0
    Vl37               0       0/0         0       0/1           0           0
    Vl2               0       0/0         0       0/1           0           0
    Gi1/3/48           0       0/0         0       0/1           0           0
    Gi2/3/48           0       0/0         0       0/1           0           0
    Vl17               0       0/0         0       0/1           0           0
    Gi2/6/40           0       0/0         0       0/1           0           0
    Gi2/6/41           0       0/0         0       0/1           0           0
    Gi2/1/45           1        0/0         1       0/1           50           0
    Gi1/1/33           1       0/0         1       0/1           50           0
    My questions revolve around the same point.
    Are there any significance in running eigrp or any other routing protocol over this BFD link?
    Is the Dual active scenario detected by BFD or BFD notifies a routing protocol like eigrp and in turn dual active is detected?
    Should I suppress the eigrp HELLOs on these interfaces to get rid of the log message?
    Regards
    Vinayak

  • VSS - Virtual Switch Domain Uniqueness Doubt

    Hi everyone,
    In the Cisco documentation, says that
    You must configure the same virtual switch domain number on both switches of the VSS. The virtual switch domain is a number between 1 and 255, and must be unique for each VSS in your network.
    My doubt is how can I understand the word network ?
    I cannot use the same Virtual Switch Domain in a L2 Network, in a L3 Network, in a same customer Network ?
    For example, if a customer has a lot of sites connected by a MPLS Wan, can I reuse the Virtual Switch Domain in each site ?
    Thanks for Advanced
    Andre Gustavo

    You can re-use the virtual domain ID as long as the the two VSS chassis are not directly connecting to each other. Take a look at this link:
    VVirtual Domain
    Defining the domain identifier (ID) is the first step in creating a VSS from two physical chassis. A unique domain ID identifies two switches that are intended to be part of the same VSS pair that defines the VSS domain. Assignment of a domain ID allows multiple virtual switch pairs to be connected in a hierarchical manner. Only one VSS pair can participate in a particular domain. The domain ID can have a value ranging from 1 to 255 and must be unique when multiple VSS pairs are connected together. See Figure 2-2.
    Figure 2-2 VSS Domain IDs
    http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/VSS30dg/campusVSS_DG/VSS-dg_ch2.html
    Hope this helps!
    Thanks you for rating useful posts! 

  • 6500 Virtual Switching System (VSS) design in MPLS PE PoP

    ...

    Hello,
    The VSS is not designed to function as a PE , its best fit in a DataCenter Environment where I have Multiple Links from Core/Access to the Distribution layer.
    Although VSS provides Higher backblane Throughput, Ease and Single Administartion Managment, and Redundancy SSO between SUP engines at the Control Plane, These features wont help at the MPLS edge, why? because Both Chasis have identical configuration, So I cant have two links from the CE or from the P router to the same VSS Chasis, So I have No redundancy here.
    what if a VSL link fails between the Two Chasis, Each chasis will revert to be as a standlone chasis with Identical Configuration, So I dont have redundancy here.
    The VSS would be an ideal option as a PE router  if the CE and P routers can form a direct Layer-3 Eitherchannel to each of the VSS chasis in order to benefit from a redundancy, in this case we can say we have (Intra Chasis Redundancy).
    Since this Type of Scenario is not an option, then its normaly Service Providers prefer (Inter Chasis Redundancy) by having Two Different PE routers with two different Configuration to have resilency.
    Other than that, it could quitely fit.
    Regards,
    Mohamed

  • Proper sizing of VSS virtual switch link

    I am considering using VSS in my collapsed core/distribution on a pair of 6509/Sup2T switches with 6904-40G-2T modules. My closets are 4506/Sup7E, and I have one high-density, mission critical IDF with two fully populated 4510R+E/Sup7E switches. The interlinks will be either 2x or 4x10GE depending on customer decisions to be made. I am trying to find information that would suggest best practice for sizing the VSL. From what I can find, it would appear that not a significant amount of traffic goes across this link if everything in the environment is equally connected to both members of the VSS pairs. So, 2x10GE would be just as good as 4x, or even 2x40GE. However, I haven't found anything definitive yet. Is there a rule of thumb for sizing this link?
    Thanks for any guidance.

    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
    The VSL can be the Achilles Heel of a VSS setup.
    As you note, if everything is configured optimally, very little traffic should cross this link.
    However, suppose a line card fails.  As the sup2t supports 80Gbps slot, in theory, that 80Gbps might need to transit the VSL.  (NB: Hopefully, VSL also wasn't on the failed card.)
    So, to size your VSL, consider bandwidth needs if a line card fails.
    Also keep in mind, VSL (at least on 6500s) doesn't allow custom QoS, so you also lose some control on traffic management if VSL congests.

  • NAC OOB and 6500 in Virtual Switch Mode

    Is there any issue or special care to implement NAC OOB in Central Deploy, VGW, using AD SSO for wired clients where the Core Switch is a pair of 6500 in Virtual Switch Mode?
    The customer uses Radius IAS for authentication. How does it fit with the AD SSO?

    Hi Bruce,
    I am afraid there are some arguments missing in your db command.
    To manually add the OID of  Cat4507R+E to CAM's database here is the  procedure to do this.
    [root@cca-3140-cam ~]# psql -h localhost -U postgres controlsmartdb -c "INSERT INTO supported_switch VALUES ('1.3.6.1.4.1.9.1.1286', '4', 'Cisco Catalyst 4507 R+E')" INSERT 0 1
    psql: warning: extra command-line argument "INSERT" ignored
    psql: warning: extra command-line argument "0" ignored
    psql: warning: extra command-line argument "1" ignored
    INSERT 0 1
    Then to make sure it is there:
    [root@cca-3140-cam ~]# psql -h localhost -U postgres controlsmartdb -c "SELECT * FROM supported_switch" | grep 1286
    The output should be:
    1.3.6.1.4.1.9.1.1286      |     4 | Cisco Catalyst 4507 R+E
    Restart perfigo service on NAC Manager and try to manage the switch  using the model used by the above command.
    HTH,
    Tiago
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • 2012 R2 Hyper-V Virtual Switch Refuses to Be Created -- Error Messages Not Especially Helpful

    Windows Servers 2012 R2 Standard
    4 NICs 
    Windows 8.1 is guest of the host 
    Hyper-V
    Virtual Switch Manager
    External
    Create Virtual Switch
    External network
    Choose a NIC that is connected to the physical Ethernet switch but otherwise unused
    Tick Allow management operating system to share this network adapter
    Untick everything else
    Click Apply
    "Error applying Virtual Switch Properties changes"
    "Failed while adding virtual Ethernet switch connections."
    "External Ethernet adapter "<name-of-adapter>" is already bound to the Microsoft Virtual Switch protocol."
    Close
    Cancel
    Control Panel\Network and Internet\Network Connections
    Change Properties of NIC to untick Virtual Switch protocol
    Repeat steps as above
    "Virtual Switch Manager for <name-of-server>"
    "Error applying Virtual Switch Properties changes"
    "An internal error occurred while processing the results of creating a new virtual switch."
    "To refresh the results, close and then reopen this window."
    Close
    Dead in the Water
    An internal error occurred while processing the results of creating a new virtual switch.  To refresh the results, close and then reopen this window.
    The first one is to use a tool called “nvspscrub.js”. Download nvspscrub.js then from cmd run: “cscript nvspscrub.js”, this will delete all vswitches, virtual NICs in the parent partition and will unbind the switch protocol from all physical NICs.
    This script aborts when a class turns up undefined.  Maybe this old script applies solely to Windows Server 2008.  Dunno.
    NVSPbind
    What I do now?
    It is an internal error.  Internal to what? 
    MARK D ROCKMAN

    Hi Mark,
    I just came across the same issue!
    After troubleshooting, I deleted all my Virtual Switches and reinstalled my WiFi and Ethernet NIC drivers.
    I'm now able to create the Virtual Switches without error.
    Hope this helps.
    Regards
    Lee

  • SCVMM Virtual Switch Provisioning ignores "Inherit settings from the physical management adapter" setting

    When provisioning a new Hyper-V hosting into SCVMM I have a situation occur that causes loss of management to the server, which really should not be happening. When I add a new host, I set the 'Virtual Switch' adding a new 'Logical Switch' as well as a 'Virtual
    Network Adapter' for the management OS traffic. 
    The first NIC in the team is active and configured with correct static IP information, which is allowing VMM access to the server to perform these steps.  The 'Virtual Network Adapter' has a checkbox in the 'This virtual network adapter inherits settings
    from the physical management adapter.' option box. 
    From my understanding what should happen is when the virtual adapter is created on the host the IP information should move to the virtual adapter from the physical adapter that is now part of the NIC Team. What is actually happening is the NIC Team seems
    to create OK, but it picks up a DHCP IP address instead of assuming the first physical NIC's IP information. I tried this with only one NIC as well as both NICs in the team to see what happens. Either case the same problem presents. 
    To get around this, what I did was sit on the console after I started the provisioning process. As soon as I saw Teamed NIC create I applied the static IP address via PowerShell manually to that Teamed NIC virtual adapter and then VMM just continued along
    normally. It then moving the IP from the NIC Team adapter to the Hyper-V virtual adapter properly. I did get a warning back from the creation (below) which hints me to the problem. 
    The Error code details as 2147942465 which is a "Network Access Denied" code followed by "Error while applying physical adapter network settings to teamed adapter". So, this is telling me there was a permission issue of some sort during
    the step of adding the original physical NIC IP settings to the virtual NIC. 
    The VMM Run As user 'HVAdmin' is a Local Administrator on the Hyper-V host, this has been verified. It has also been temporarily granted Administrator access on the domain to see if it helps. No go.
    Searching around the net has now revealed this problem so far, has anyone else seen this? It makes provisioning a bit of a chore because I have to be at the Hyper-V console and on VMM at the exact same time to add a new host. 

    It's a workaround but this works best.
    When initially configuring the host use a dedicated Nic.
    Configure the new team with a management Vnic and assign the Vnic an IP.
    Now disable the dedicated nic and you can start working the the team and the Vnic.
    Gil Gross | Technical Lead | G-Net Network Solutions | www.g-net.co.il | plz visit my blog - gilgrossblog.wordpress.com

  • Removal of Virtual Switch Logical Networks

    Hi,
    I've recently managed to get SCVMM 2012 R2 up and running and it's currently managing 2 hosts in a cluster. I've migrated both hosts onto a logical switch, and I'm now at the stage where I'm ready to delete the LN's created for the per-host switches. I've
    deleted the Virtual Switches and deleted the VM Networks associated with the switches successfully, but when I go to delete the LN's associated with the Virtual Switches, I get a 25100 error.
    In dependencies, it shows that each LN has one of the hosts as a dependency but when I log into the hosts, there's nothing to indicate that they're in use. Is there any way to fix this or do I need to manually delete them from the database?
    Cheers,
    Ed

    Hi Sir,
    >>In dependencies, it shows that each LN has one of the hosts as a dependency
    If you mean this :
    Please open the hosts' properties then check the hardware option and uncheck the "logical network connectivity":
    Best Regards,
    Elton Ji
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • Virtual switch internet connection sharing problem

    Greetings,
    I am having a problem with sharing internet connection to virtual machine. I tried to create external virtual switch but without success. From time to time I got an error:
    Error applying Virtual Switch Properties changes
    An internal error occurred while processing the results of creating a new virtual switch. To refresh the results, close and then reopen this window.
    but mostly the creation goes fine but after new virtual network device is created I can no longer access internet from Windows 8.1 nor VM as authentication fails (802.1x Secure W2 EAP-TTLS with certificate, username and password). The new device created
    by virtual switch manager has authentication changed to Windows Protected EAP(PEAP) instead of original Secure W2 - even if I change it to original Secure W2 nothing happens - authentication still fails.
    Sometimes when I try to change authentication settings of new or old NIC I got an error:
    The changes to Authentication settings could not be saved
    The virtual switch seems to have the same authentication settings as I have had on my NIC but from some reason it doesn't work.
    If I am persistent enough I convince to install virtual switch by several attempts but it doesn't work - neither my server (windows 8.1) nor VM can connect to internet.
    I hope it is not this:
    http://social.technet.microsoft.com/Forums/windows/en-US/341cbe70-3fa7-4991-a7e4-4f1af63df4d0/windows-8-hyperv-8021x-eapol-request-missing?forum=w8itpronetworking
    unsolved problem. If it is I am screwed :-/
    Any advice how to fix this mess much appreciated...

    1.Go to network connection, and find the Wireless network, right click at it.
    I am connected by wire (RJ-45) not by WIFI. The cerificate is valid (trusted root certificate used by Secure W2 authentization - not the authentication type you have described).
    The problem is in creation of external virtual switch - removed it also with the driver from device manager I installed (and removed) subsequently both motherboard manufacturer latest drivers for my integrated network card and also let windows detect it. 
    Finally I removed Hyper-V and did a clean installation of network adapter drivers. Then I enabled again Hyper-V role. 
    After several restarts I tried to create external switch and I was again in the same problems. Then I redid everything and tried to install virtual switch again but 
    I installed INTERNAL virtual switch instead of external.
    External simply doesn't work for me and also destroys functional connections... 
    To be able to access internet from virtual machine a tried to create a bridge between the connections but then it simply didn't work again (neither could I access internet from host on which was Hyper-V running). 
    So what has after several trial and errors worked for me eventually - if you would like to have internet connection functional in Hyper-V VM you have to
    create INTERNAL VIRTUAL SWITCH and share the original connection and it should then somehow work...

  • Windows 8.1 - Hyper-V Virtual Switch fails to create

    I'm running into a problem with creating a new virtual switch on my Windows 8.1 RTM box. Frist time attempt at Hyper-V on this system.
    The error I get is as follows:
    Error applying Virtual Switch Properties changes
    Failed while creating virtual Ethernet switch.
    switch create failed, name= 'B57B7B7B-64314AF5-AB8F-4521CBAA9FFBA', friendly name = 'New Virtual Switch': The system cannot find the file specified. (0x80070002)
    The steps I have taken to try and resolve this issue.
    1. Uninstall and reinstall Hyper-V...numerous times - no change.
    2. Uninstall Hyper-V, reboot, uninstall NIC, reboot, reinstall NIC, reboot, reinstall Hyper, reboot - no change.
    3. Uninstall it all again. Get new NIC drivers, for ASUS Sabertooth 990FX, first gen.  Reinstall it all again - no change.
    4. Updated BIOS, and check for virtualization, and DEP are enabled. - no change.
    5. User powershell to create virtual switch - no change.
    6. Tried resetting Hyper-V networking using the netcfg commands posted
    here, failed, file not found.
    Any help to resolving this would be greatly appreciated.
    Thank you,
    Sean

    Hi Dw3xx,
    Unusual problem,my suggestion is  :
                 uninstall any anti-virus software then try to create the virtual switch
                 insert Win8 media and fix OS
    Hope this helps.
    Elton Ji

  • Virtual Switches doesn't appear in the metro connection panel

    Network Connections before creating the External Virtual Switch:
    ...and after creating the External Virtual Switch:
    ...probably because 8.1 don't recognize the new Network Adapter?

    Hi Luigi,
    “Network connections ethernet properties panel disappear”
    Do you mean the properties of the physical NIC cannot be opened or there is nothing in it or something else ?The screenshot seems not to make it clear .
    I have checked my own machine .I can open the properties both the physical NIC and the virtual NIC (the virtual NIC on a bridge network adapter)
    Will the network work correctly both the virtual machine and the host machine ?Have you tried to restart the machine and then have a check ?
    We can run “ncpa.cpl” to get the network connections interface quickly .
    Best regards  

  • WLC 4402 LAG connection to 2 different chassis of 6509 VSS switch system

    Hi,
    I have inherited a 6509 VSS switch system as the network core and have the task of ensuring proper redundancy and redesign of the directly connected data center devices.  One of the connected devices (WLC 4402) physically appears to be connected to both switches - the WLC is in the same rack as VSS-Chassis1 so I can trace the fiber from WLC port 1 to gi1/1/22, the other fiber from the WLC port 2 goes into the floor and presumably over to VSS-Chassis2 gi2/1/22 (there is fiber connected there, I have link lights on both sides, and the port channel, Po200, on the VSS switch which is configured on gi1/1/22 is also configured on gi2/1/22).  My question pertains to the CDP neighbor output I get on the VSS switch: (truncated to include just the WLC)
    NCMECHQWiFi1     Gig 1/1/22        137               H    AIR-WLC44 Gig 0/0/2
    NCMECHQWiFi1     Gig 1/1/22        137               H    AIR-WLC44 LAGInterface0/3/1
    NCMECHQWiFi1     Gig 1/1/22        137               H    AIR-WLC44 Gig 0/0/1
    It looks like both WLC ports are physically connected to Gi1/1/22, which they are quite obviously not.
    This is confirmed on the WLC's sho cdp entry all output:
    (Cisco Controller) >show cdp entry all
    Device ID: ncmec-vsscoresw1.ncmec.org
    Entry address(es): 100.1.0.254
    Platform: cisco WS-C6509-E,  Capabilities: Router Switch IGMP
    Interface: LAGInterface0/3/1,  Port ID (outgoing port): GigabitEthernet1/1/22
    Holdtime : 160 sec
    I believe that the multi chassis etherchannel is set up correctly on the VSS:
    vsscoresw1#sho run int gi1/1/22             
    interface GigabitEthernet1/1/22
    description WLC-Management
    switchport
    switchport trunk encapsulation dot1q
    switchport mode trunk
    switchport nonegotiate
    channel-group 200 mode on
    end
    vsscoresw1#sho run int gi2/1/22
    interface GigabitEthernet2/1/22
    description WLC-Management
    switchport
    switchport trunk encapsulation dot1q
    switchport mode trunk
    switchport nonegotiate
    channel-group 200 mode on
    end
    vsscoresw1#sho run int po200
    interface Port-channel200
    description WLC-Management
    switchport
    switchport trunk encapsulation dot1q
    switchport mode trunk
    switchport nonegotiate
    end
    And yet when I show the details of port channel 200, I expect to see "mode on" but get instead see LACP which is unsupported on the WLC:
    vsscoresw1#sho etherchannel 200 detail
    Group state = L2
    Ports: 2   Maxports = 8
    Port-channels: 1 Max Port-channels = 1
    Protocol:    -
    Minimum Links: 0
                    Ports in the group:
    Port: Gi1/1/22
    Port state    = Up Mstr In-Bndl
    Channel group = 200         Mode = On      Gcchange = -
    Port-channel  = Po200       GC   =   -         Pseudo port-channel = Po200
    Port index    = 0           Load = 0xFF        Protocol =    -
    Mode = LACP
    Age of the port in the current state: 180d:19h:47m:01s
    Port: Gi2/1/22
    Port state    = Up Mstr In-Bndl
    Channel group = 200         Mode = On      Gcchange = -
    Port-channel  = Po200       GC   =   -         Pseudo port-channel = Po200
    Port index    = 1           Load = 0xFF        Protocol =    -
    Mode = LACP
    Age of the port in the current state: 180d:19h:47m:02s
                    Port-channels in the group:
    Port-channel: Po200
    Age of the Port-channel   = 354d:12h:47m:27s
    Logical slot/port   = 46/19          Number of ports = 2
    GC                  = 0x00000000      HotStandBy port = null
    Port state          = Port-channel Ag-Inuse
    Protocol            =    -
    Fast-switchover     = disabled
    Load share deferral = disabled  
    Ports in the Port-channel:
    Index   Load      Port          EC state       No of bits
    ------+------+------------+------------------+-----------
    0      FF       Gi1/1/22                 On   8
    1      FF       Gi2/1/22                 On   8
    Time since last port bundled:    173d:17h:06m:34s    Gi2/1/22
    Time since last port Un-bundled: 173d:17h:06m:34s    Gi2/1/22
    Last applied Hash Distribution Algorithm: Fixed
    >>>  So my question, arising at least partly from the apparently misleading CDP information, is this:  How can I confirm that the WLC is correctly dual homed to both core switches? (short of tracing the cable)  I ask because there are several other devices (not WLCs) that need to have the dual homed connections confirmed.
    I tried a layer 2 trace route but for all macs associated with the WLC, the trace abborts with the error "Device has Multiple CDP neighbours on destination port."
    Thanks in advance!
    Sue

    PS:  It is critical that I confirm the redundancy, since as a part of the data center redesign we will be moving the second VSS chassis to the same rack with the first to simplify the dual connections.  I need to verify all the redundant connections before I take it offline and move it.  Thanks!

Maybe you are looking for