{"id":1278,"date":"2018-09-06T13:48:24","date_gmt":"2018-09-06T06:48:24","guid":{"rendered":"https:\/\/lagonet.vn\/?p=1278"},"modified":"2018-09-06T13:48:24","modified_gmt":"2018-09-06T06:48:24","slug":"cisco-6500-vss-configuration","status":"publish","type":"post","link":"https:\/\/kb.lagonet.vn\/?p=1278","title":{"rendered":"Cisco 6500 VSS configuration"},"content":{"rendered":"<p>The Cisco Catalyst 6500 Series Virtual Switching System (<strong>VSS<\/strong>) allows the\u00a0<strong>clustering of two chassis together into a single<\/strong>, logical entity. This technology allows for enhancements in all areas of network\u00a0design, including high availability, scalability, management, and maintenance.<\/p>\n<p>The Virtual Switching System is created by\u00a0<strong>converting two standalone<\/strong>\u00a0Catalyst 6500 systems\u00a0<strong>to a Virtual Switching\u00a0System<\/strong>. The conversion is a one-time process that requires a few simple configuration steps and a system reload.\u00a0Once the individual chassis reload, they are converted into the Virtual Switching System.<\/p>\n<p>All\u00a0<strong>control plane<\/strong>\u00a0functions are centrally\u00a0<strong>managed by the active supervisor<\/strong>\u00a0engine of the active virtual switch chassis,\u00a0<strong>including<\/strong>:<\/p>\n<ul>\n<li><strong>Management<\/strong>\u00a0(Simple Network Management Protocol [SNMP], Telnet, Secure Shell [SSH] Protocol, etc.)<\/li>\n<li>Layer 2 Protocols (bridge protocol data units [<strong>BPDUs<\/strong>], protocol data units [<strong>PDUs<\/strong>], Link Aggregation Control<br \/>\nProtocol [<strong>LACP<\/strong>], etc.)<\/li>\n<li><strong>Layer 3<\/strong>\u00a0Protocols (routing protocols, etc.)<\/li>\n<li><strong>Software data path<\/strong><\/li>\n<\/ul>\n<p><span id=\"more-1192\"><\/span>The\u00a0<strong>requirements<\/strong>\u00a0to convert the\u00a06500 into a Virtual Switching System are:<\/p>\n<ul>\n<li>The VSS requires\u00a0<strong>Supervisor Engine 720 with 10-Gigabit<\/strong>\u00a0Ethernet ports. You must use either two VS-S720-10G-3C or two VS-S720-10G-3CXL supervisor engine modules.<\/li>\n<li>The VSS requires\u00a0<strong>67xx series<\/strong>\u00a0switching\u00a0<strong>modules<\/strong>.<\/li>\n<li>The\u00a0<strong>VSL<\/strong>\u00a0EtherChannel supports\u00a0<strong>only 10-Gigabit<\/strong>\u00a0Ethernet ports.<\/li>\n<\/ul>\n<p>To convert two standalone chassis into a VSS, perform the following activities:<\/p>\n<ol>\n<li>Configure each chassis as a VSS<\/li>\n<li>Convert to a VSS<\/li>\n<li>Configure the dual-active detection (optional)<\/li>\n<li>Configure the switch priority (optional)<\/li>\n<\/ol>\n<p>&nbsp;<\/p>\n<p><strong>1.\u00a0Configure each chassis<\/strong>\u00a0as a VSS<\/p>\n<p><strong>Define<\/strong>\u00a0a switch\u00a0<strong>virtual domain ID<\/strong>\u00a0to identify the VSS. The ID must be the same on each 6500; in this example\u00a0the ID\u00a0\u2018100\u2019 is used:<\/p>\n<pre>CiscozineA(config)#switch virtual domain 100\nDomain ID 100 config will take effect only\nafter the exec command 'switch convert mode virtual' is issued\n\nCiscozineA(config-vs-domain)#switch 1\nCiscozineA#<\/pre>\n<pre>CiscozineB(config)#switch virtual domain 100\nDomain ID 100 config will take effect only\nafter the exec command 'switch convert mode virtual' is issued\n\nCiscozineB(config-vs-domain)#switch 2\nCiscozineB#<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>Configure<\/strong>\u00a0the\u00a0<strong>VSL<\/strong>\u00a0port channel and member ports<\/p>\n<p>The Virtual Switch Link (<strong>VSL<\/strong>), like\u00a0the VPC peer-link in VPC, is clearly a vital part of the VSS. It\u00a0<strong>provides<\/strong>\u00a0the\u00a0<strong>signaling<\/strong>\u00a0path used for\u00a0<strong>synchronizing<\/strong>\u00a0the\u00a0<strong>two supervisor engines\u2019<\/strong>\u00a0control planes, as well as providing the data path for any user data traffic needing to pass between the two chassis.<\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1284\" src=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-Configuration-conversation.png\" sizes=\"auto, (max-width: 331px) 100vw, 331px\" srcset=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-Configuration-conversation.png 331w, http:\/\/www.ciscozine.com\/wp-content\/uploads\/Cisco-6500-VSS-Configuration-conversation-300x158.png 300w\" alt=\"Cisco-6500-VSS-Configuration-conversation\" width=\"331\" height=\"175\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Choose unique port-channel IDs for each chassis to form the VSL and configure them with the corresponding switch ID:<\/p>\n<pre>CiscozineA(config)#interface port-channel 1\nCiscozineA(config-if)#switch virtual link 1\nCiscozineA(config-if)#no shut\nCiscozineA(config-if)#exit\nCiscozineA(config)#interface range tenGigabitEthernet 5\/4 -5\nCiscozineA(config-if-range)#channel-group 1 mode on\nCiscozineA(config-if-range)#no shutdown\nCiscozineA#<\/pre>\n<pre>CiscozineB(config)#interface port-channel 2\nCiscozineB(config-if)#switch virtual link 2\nCiscozineB(config-if)#no shut\nCiscozineB(config-if)#exit\nCiscozineB(config)#interface range tenGigabitEthernet 5\/4 -5\nCiscozineB(config-if-range)#channel-group 2 mode on\nCiscozineB(config-if-range)#no shutdown\nCiscozineB#<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>2.\u00a0Convert to a VSS<\/strong><\/p>\n<p>Convert both switches to virtual switch mode. During these phases:<\/p>\n<ul>\n<li>The running configuration of the individual switch is converted into a three-level virtual switch interface notation. Two-level interface configurations (such as 10 GigabitEthernet 5\/4) are converted into three-level interfaces (such as 10 GigabitEthernet 1\/5\/4 in Switch 1 and 10 GigabitEthernet 2\/5\/4 in Switch 2) like in a stack.<\/li>\n<li>The startup configuration is updated with the three-number notation.<\/li>\n<li>A copy of the original startup configuration converted to three-number notation is written to the\u00a0bootflash of the respective switch.<\/li>\n<li>Both switches reload.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1287 aligncenter\" src=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-Configuration-VSS.png\" sizes=\"auto, (max-width: 336px) 100vw, 336px\" srcset=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-Configuration-VSS.png 336w, http:\/\/www.ciscozine.com\/wp-content\/uploads\/Cisco-6500-VSS-Configuration-VSS-217x300.png 217w\" alt=\"Cisco-6500-VSS-Configuration-VSS\" width=\"336\" height=\"464\" \/><\/p>\n<p>&nbsp;<\/p>\n<pre>CiscozineA#switch convert mode virtual\n\nThis command will convert all interface names\nto naming convention \"interface-type switch-number\/slot\/port\",\nsave the running config to startup-config and\nreload the switch.\n\nNOTE: Make sure to configure one or more dual-active detection methods\nonce the conversion is complete and the switches have come up in VSS mode.\n\nDo you want to proceed? [yes\/no]: yes\nConverting interface names\nBuilding configuration...\n[OK]\nSaving converted configuration to bootflash: ...\nDestination filename [startup-config.converted_vs-20140915-123802]?\n8243 bytes copied in 0.048 secs (171729 bytes\/sec)\n*Sep 15 12:38:06.395: %SYS-5-RELOAD: Reload requested by Exec. Reload Reason: Conversion.\n*Sep 15 12:38:09.406: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.\n\n*Sep 15 12:38:09.406: %OIR-SP-6-CONSOLE: Changing console ownership to switch processor\n\n\n\n*Sep 15 12:38:09.610: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.\n\n\n\n***\n*** --- SHUTDOWN NOW ---\n***\n\n*Sep 15 12:38:13.152: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.<\/pre>\n<p>&nbsp;<\/p>\n<p>Wait more\u00a0or less five minutes, then convert the second switch.<\/p>\n<pre>CiscozineB#switch convert mode virtual\n\nThis command will convert all interface names\nto naming convention \"interface-type switch-number\/slot\/port\",\nsave the running config to startup-config and\nreload the switch.\n\nNOTE: Make sure to configure one or more dual-active detection methods\nonce the conversion is complete and the switches have come up in VSS mode.\n\nDo you want to proceed? [yes\/no]: yes\nConverting interface names\nBuilding configuration...\n[OK]\nSaving converted configuration to bootflash: ...\nDestination filename [startup-config.converted_vs-20140915-123819]?\n8243 bytes copied in 0.049 secs (171729 bytes\/sec)\n*Sep 15 12:38:16.795: %SYS-5-RELOAD: Reload requested by Exec. Reload Reason: Conversion.\n*Sep 15 12:38:19.106: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.\n\n*Sep 15 12:38:19.436: %OIR-SP-6-CONSOLE: Changing console ownership to switch processor\n\n\n\n*Sep 15 12:38:19.619: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.\n\n\n\n***\n*** --- SHUTDOWN NOW ---\n***\n\n*Sep 15 12:38:19.152: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.<\/pre>\n<p>&nbsp;<\/p>\n<p>After the conversion,\u00a0you will notice three\u00a0things:<\/p>\n<ul>\n<li>The name of the VSS\u00a0is CiscozineA; rename it to \u201cCiscozineVSS\u201d.<\/li>\n<li>The interface name is\u00a0converted into three-level interface. The first number (one or two) identify the switch.<\/li>\n<li>By default, the console port on the standby switch is locked; if you try to use it, this message will be displayed:<\/li>\n<\/ul>\n<pre>Standby console disabled<\/pre>\n<p>If needed, enable the standby console:<\/p>\n<pre>CiscozineVSS#conf t\nCiscozineVSS#(config)#redundancy\nCiscozineVSS#(config-red)#\nCiscozineVSS#(config-red)#main-cpu\nCiscozineVSS#(config-r-mc)#standby console enable\n<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>3. Configure the dual-active detection (optional)<\/strong><\/p>\n<p>The VSLs can be configured with up to eight links between the two switches across any combination of line cards or supervisor ports to provide a high level of redundancy.\u00a0<strong>If<\/strong>for some rare reason all\u00a0<strong>VSL connections are lost<\/strong>\u00a0between the virtual switch members leaving\u00a0<strong>each virtual switch<\/strong>\u00a0assumes the role as the\u00a0<strong>active virtual switch<\/strong>, and each virtual switch controls only its local ports. Duplication of this configuration can possibly have adverse effects to the network topology and traffic.<\/p>\n<p>To avoid this disruptive scenario, Cisco has implemented\u00a0<strong>different mechanisms<\/strong>\u00a0<strong>to address<\/strong>\u00a0this\u00a0<strong>dual-active<\/strong>\u00a0scenario:<\/p>\n<ul>\n<li><strong>Enhancement to PAgP<\/strong>\u00a0used in MEC with connecting Cisco switches<\/li>\n<li>L3 Bidirectional Forwarding Detection (<strong>BFD<\/strong>) configuration on a directly connected link (besides VSL) between virtual switch members or through an L2 link through an access layer switch<\/li>\n<li>L2\u00a0<strong>Fast-Hello<\/strong>\u00a0Dual-Active Detection configuration on a directly connected link (besides VSL) between virtual switch members (supported with 12.2(33)SXI)<\/li>\n<\/ul>\n<p>In this tutorial, \u201cfast-hello\u201d is implemented.<\/p>\n<p><strong>Note:<\/strong>\u00a0If\u00a0the dual-active detection is not configured, the system will suggest\u00a0to implement it!<\/p>\n<pre>%DUAL_ACTIVE-SW1_SP-4-CONFIG: No dual-active detection methods configured - it is recommended to have at least one configured<\/pre>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1288\" src=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-fast-hello.png\" sizes=\"auto, (max-width: 361px) 100vw, 361px\" srcset=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-fast-hello.png 361w, http:\/\/www.ciscozine.com\/wp-content\/uploads\/Cisco-6500-VSS-fast-hello-300x193.png 300w\" alt=\"Cisco-6500-VSS-fast-hello\" width=\"361\" height=\"233\" \/><\/p>\n<p>&nbsp;<\/p>\n<pre>CiscozineVSS(config)#int gi1\/2\/1\nCiscozineVSS(config-if)#dual-active fast-hello\nCiscozineVSS(config-if)#no shut\nCiscozineVSS(config-if)#int gi2\/2\/1\nCiscozineVSS(config-if)#dual-active fast-hello\nCiscozineVSS(config-if)#no shut\nCiscozineVSS(config-if)#\n*Sep 15 13:01:20.747: %VSDA-SW2_SPSTBY-5-LINK_UP: Interface Gi2\/2\/1 is now dual-active detection capable\n*Sep 15 13:01:21.759: %VSDA-SW1_SP-5-LINK_UP: Interface Gi1\/2\/1 is now dual-active detection capable<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>4. Configure the switch priority (optional)<\/strong><\/p>\n<p>My suggestion is to statically define the switch priority\u00a0(an\u00a0higher-priority value assumes the active virtual switch role):<\/p>\n<pre>CiscozineVSS(config)#switch virtual domain 100\nCiscozineVSS(config-vs-domain)#switch 1 priority 110\nCiscozineVSS(config-vs-domain)#switch 2 priority 90<\/pre>\n<p>Changing\u00a0the priority, a log message is generated:<\/p>\n<pre>%VSLP-SW1_SP-5-RRP_RT_CFG_CHG: Configured priority value is different from operational value.\nChange will take effect after config is saved and switch 1 is reloaded.\n%VSLP-SW2_SPSTBY-5-RRP_RT_CFG_CHG: Configured priority value is different from operational value.\b \b\b \b\b \b\b \b\b \b\nChange will take effect after config is saved and switch 1 is reloaded.<\/pre>\n<p><strong>Note:<\/strong>\u00a0the switch\u00a0<strong>priorities<\/strong>\u00a0<strong>affect<\/strong>\u00a0<strong>role<\/strong>\u00a0determination\u00a0<strong>if both<\/strong>\u00a0virtual\u00a0<strong>switches<\/strong>\u00a0<strong>are<\/strong><strong>initiated<\/strong>\u00a0<strong>simultaneously<\/strong>\u00a0. If either switch (regardless of priority) is initiated prior to the subsequent switch, it always assumes the role of the active virtual switch.<\/p>\n<p>After these steps, the\u00a0<strong>VSS configuration is completed<\/strong>!<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Multichassis EtherChannel<\/strong><\/p>\n<p>The multichassis EtherChannel (MEC) is another term\u00a0to identify an etherchannel that\u00a0allows a connected node to terminate the EtherChannel across the two physical Cisco Catalyst 6500 Series. In this example the \u201cCiscozine-L2\u201d switch is\u00a0connected to the CiscozineVSS using a MEC.<\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1286\" src=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-Configuration-MEC-Physical.png\" sizes=\"auto, (max-width: 361px) 100vw, 361px\" srcset=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-Configuration-MEC-Physical.png 361w, http:\/\/www.ciscozine.com\/wp-content\/uploads\/Cisco-6500-VSS-Configuration-MEC-Physical-150x150.png 150w, http:\/\/www.ciscozine.com\/wp-content\/uploads\/Cisco-6500-VSS-Configuration-MEC-Physical-300x300.png 300w\" alt=\"Cisco-6500-VSS-Configuration-MEC-Physical\" width=\"361\" height=\"360\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>From the point of view of the Ciscozine-L2, the CiscozineVSS\u00a0is a single device (like a stack):<\/p>\n<pre>Ciscozine-L2#show cdp neighbors\nCapability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge\n                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,\n                  D - Remote, C - CVTA, M - Two-port Mac Relay\n\nDevice ID        Local Intrfce     Holdtme    Capability  Platform  Port ID\nCiscozineVSS     Gig 0\/1           145             R S I  WS-C6509- Gig 1\/1\/1\nCiscozineVSS     Gig 0\/2           173             R S I  WS-C6509- Gig 2\/1\/1\nCiscozine-L2#<\/pre>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1285\" src=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-Configuration-MEC-logical.png\" sizes=\"auto, (max-width: 126px) 100vw, 126px\" srcset=\"https:\/\/lagonet.vn\/wp-content\/uploads\/2018\/09\/Cisco-6500-VSS-Configuration-MEC-logical.png 126w, http:\/\/www.ciscozine.com\/wp-content\/uploads\/Cisco-6500-VSS-Configuration-MEC-logical-94x300.png 94w\" alt=\"Cisco-6500-VSS-Configuration-MEC-logical\" width=\"126\" height=\"402\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>For these reasons, on the Ciscozine-L2 is possible define the port-channel10 with the interfaces Gi0\/1 and Gi0\/2.\u00a0To find more informations about etherchannel read this\u00a0<a href=\"http:\/\/www.ciscozine.com\/configuring-link-aggregation-with-etherchannel\/\">article<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Useful show commands<\/strong><\/p>\n<p>To show basic VSS informations:<\/p>\n<pre>CiscozineVSS#show switch virtual\nSwitch mode : Virtual Switch\nVirtual switch domain number : 100\nLocal switch number : 1\nLocal switch operational role: Virtual Switch Active\nPeer switch number : 2\nPeer switch operational role : Virtual Switch Standby\nCiscozineVSS#<\/pre>\n<p>&nbsp;<\/p>\n<p>To find\u00a0informations about fast-hello detection:<\/p>\n<pre>CiscozineVSS#show switch virtual dual-active fast-hello\nFast-hello dual-active detection enabled: Yes\n\nFast-hello dual-active interfaces:\nPort       Local State    Peer Port    Remote State\n---------------------------------------------------\nGi1\/2\/1    Link up        Gi2\/2\/1      Link up\n\nCiscozineVSS#<\/pre>\n<p>&nbsp;<\/p>\n<p>To identify the role\/priority of the two switches:<\/p>\n<pre>CiscozineVSS#show switch virtual role\nRRP information for Instance 1\n\n--------------------------------------------------------------------\nValid  Flags   Peer      Preferred  Reserved\n               Count     Peer       Peer\n\n--------------------------------------------------------------------\nTRUE    V        1           1          1\n\nSwitch  Switch   Status      Priority     Role     Local   Remote\n        Number               Oper(Conf)            SID     SID\n--------------------------------------------------------------------\nLOCAL   1         UP         110(110)     ACTIVE    0       0\nREMOTE  2         UP         90 (90 )     STANDBY   8934    7925\n\nPeer 0 represents the local switch\n\nFlags : V - Valid\n\n\nIn dual-active recovery mode: No\n\nCiscozineVSS#\n<\/pre>\n<p>&nbsp;<\/p>\n<p>To find\u00a0more informations about the VSS status:<\/p>\n<pre>CiscozineVSS#show switch virtual redundancy\nMy Switch Id = 1\nPeer Switch Id = 2\nLast switchover reason = none\nConfigured Redundancy Mode = sso\nOperating Redundancy Mode = sso\n\nSwitch 1 Slot 5 Processor Information :\n-----------------------------------------------\nCurrent Software state = ACTIVE\nUptime in current state = 26 weeks, 4 days, 10 hours, 57 minutes\nImage Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9-M), Version 15.1(2)SY, RELEASE SOFTWARE (fc4)\nTechnical Support: http:\/\/www.cisco.com\/techsupport\nCopyright (c) 1986-2013 by Cisco Systems, Inc.\nCompiled Wed 04-Sep-13 13:05 by prod_rel_team\nBOOT = bootdisk:s72033-adventerprisek9-mz.151-2.SY.bin,12;\nConfiguration register = 0x2102\nFabric State = ACTIVE\nControl Plane State = ACTIVE\n\nSwitch 2 Slot 5 Processor Information :\n-----------------------------------------------\nCurrent Software state = STANDBY HOT (switchover target)\nUptime in current state = 2 weeks, 3 days, 3 hours, 51 minutes\nImage Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9-M), Version 15.1(2)SY, RELEASE SOFTWARE (fc4)\nTechnical Support: http:\/\/www.cisco.com\/techsupport\nCopyright (c) 1986-2013 by Cisco Systems, Inc.\nCompiled Wed 04-Sep-13 13:05 by prod_rel_team\nBOOT = bootdisk:s72033-adventerprisek9-mz.151-2.SY.bin,12;\nConfiguration register = 0x2102\nFabric State = ACTIVE\nControl Plane State = STANDBY\n\nCiscozineVSS#<\/pre>\n<p><strong>Note:<\/strong>\u00a0After the VSS conversation, some \u201cshow\u201d commands have the feature to view the output of\u00a0individual switch! For instance, to see the modules of the second switch\u00a0use \u201cshow module switch 2\u201d.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Reload commands:<\/strong><\/p>\n<p>To reload a single unit:<\/p>\n<pre>redundancy reload shelf<\/pre>\n<p>where\u00a0either Switch 1 or Switch 2 can be specified.<\/p>\n<p>&nbsp;<\/p>\n<p>To force a switchover:<\/p>\n<pre>redundancy force-switchover<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>References:<\/strong><\/p>\n<ul>\n<li><a href=\"http:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/lan\/catalyst6500\/ios\/12-2SX\/configuration\/guide\/book\/vss.html\" target=\"_blank\" rel=\"nofollow noopener\">http:\/\/www.cisco.com\/\u2026\/configuration\/guide\/book\/vss.html<\/a><\/li>\n<li><a href=\"http:\/\/www.cisco.com\/c\/dam\/en\/us\/products\/collateral\/interfaces-modules\/network-modules\/white_paper_c11_429338.pdf\" target=\"_blank\" rel=\"nofollow noopener\">http:\/\/www.cisco.com\/\u2026\/network-modules\/white_paper_c11_429338.pdf<\/a><\/li>\n<\/ul>\n<p>Details:\u00a0<a href=\"http:\/\/www.ciscozine.com\/cisco-vss-configuration\/\">http:\/\/www.ciscozine.com\/cisco-vss-configuration\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Cisco Catalyst 6500 Series Virtual Switching System (VSS) allows the\u00a0clustering of two chassis together into a single, logical entity. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[29,30,31,25,16,19,6],"tags":[],"class_list":["post-1278","post","type-post","status-publish","format-standard","hentry","category-ccie-rs","category-ccna","category-ccnp-route","category-cisco","category-courses","category-issues","category-networking"],"_links":{"self":[{"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=\/wp\/v2\/posts\/1278","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1278"}],"version-history":[{"count":0,"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=\/wp\/v2\/posts\/1278\/revisions"}],"wp:attachment":[{"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1278"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1278"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kb.lagonet.vn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1278"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}