4500-x vss

i am running 4500-x in vss mode. I have set of stackable upstream switches (2960s) that does not support epagp. I cant use fast hello because my ios on 4500x does not support it and dont want to upgrade it. i dont want to use pagp and terminate all links on 1 access switch.
i was wondering if this will work ?
on 4500x i have configured
switch virtual domain 10
switch mode virtual
switch 1 priority 110
mac-address use-virtual
dual-active detection pagp trust channel-group 100
interface Port-channel100
description Test
switchport
switchport mode trunk
interface TenGigabitEthernet1/1/1
switchport mode trunk
channel-protocol lacp
channel-group 100 mode active
interface TenGigabitEthernet2/1/1
switchport mode trunk
channel-protocol lacp
channel-group 100 mode active
Upstream access switches (2960s)
int port-channel 1
switchport mode trunk
spanning-tree guard loop
interface GigabitEthernet1/0/1
switchport mode trunk
spanning-tree guard loop
channel-protocol lacp
channel-group 1 mode active
end
interface GigabitEthernet1/0/2
switchport mode trunk
spanning-tree guard loop
channel-protocol lacp
channel-group 1 mode active
end

yes thats correct but i am not sure if the failover is working correctly. hence i have attached teh config above. do you think this is going to work ?
running
dual-active trust detection pagp port-channel xx
and using lacp on port-channel that connect to 2960s switches ?
I read somewhere trust pagp and using lacp wont work ? please let me know what you thoughts are ?

Similar Messages

4500-x VSS license upgrading

Hi,
We are required to upgrade a 4500-x VSS cluster from IPBASE to ENT SERVICES.
Should we buy two licenses packs? Or a single one? Since VSS forms one logical entity.
Thank you.

Hi,
Even though they are logically one switch but you need one license per chassis. If you put 2 sups in one chassis than you only need one license.
HTH

4500-x vss MEC to 2960-x stack

Building A
(2) 4500-x VSS
(9) closets with 2960-x stacks
(2) Data Center N5K-C5596t
I'm having a difficult time trying to find documentation.
I have the (2) 4500-x configured with VSS and am trying to find info on connecting the 2960-x stacks.

Hi,
some info.
PAgP is supported in all platforms except the Cisco Catalyst 37xx stack configuration in which cross-stack EtherChannel (LACP) is required to have MEC-connectivity with the VSS. Because cross-stack EtherChannel does not support PAgP, it cannot use enhanced PAgP for dual-active detection. A common approach to resolve this gap in support is to use two EtherChannel links from the same stack member. This solution is a non-optimal design choice because it creates a single point-of-failure. If a stack member containing that EtherChannel fails, the whole connectivity from the stack fails. To resolve this single point-of-failure problem, you can put two dual-link EtherChannel group, each on separate stack member connected to VSS; however, it will create a looped topology. The loop-free topology requires a single EtherChannel bundle to be diversified over multiple members which in turn requires LACP.

Catalyst 4500-X, VSS, and SVI

Hello, everybody!
I have a proyect to implement the feature VSS, with two catalyst 4500-X, it will be the layer Core/Distribution.
So, I want integrate in the catalyst 4500X, Inter vlan routing (SVI) and vtp domain, in the layer access, we´ll have SW 3750-X with PoE.
Is possible configure SVI in my catalyst 4500-X. to separate traffic across VLANs. and the routing will be in the 4500X too. ???
My customer does not have sufficient space to mount the serie 4500E in the Rack, so he prefer the 4500-X.
Help me!
Thanks!
Regards

Hi,
Is possible configure SVI in my catalyst 4500-X. to separate traffic across VLANs. and the routing will be in the 4500X too. ???
Yes, there is no different between a VSS pair and non-VSS when it comes to SVI and inter-vlan routing. It works the same way as if the 4500-X ware separate.
HTH

4500-X VSS with different chassis or port counts

Is it possible to run VSS on 2 4500-X switches of different port counts? For example a 24 port 4500-X and a 32 port 4500-X paired into a VSS cluster?

Yes.
See this excerpt from the following link:
Best-in-Class Resiliency
The Cisco Catalyst 4500-X Series is designed for excellent nonstop communications with non-interrupted hardware switching. With Cisco IOS XE Software, customers continue to reap the benefits of this best-in-class resiliency in various ways.
In addition to redundant power supplies and fans, the Cisco Catalyst 4500-X is Virtual Switching System (VSS).
Any two Cisco Catalyst 4500-X Series Switches can be pooled together into a VSS. The two switches are connected with 10 Gigabit Ethernet links called Virtual Switch Links (VSLs). Once a VSS is created, it acts as a single virtual Cisco Catalyst switch delivering the following benefits:
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4500-x-series-switches/data_sheet_c78-696791.html

4500-X VSS and Dual-Active detection PAgP, using 2960-X access stacks

Hi.
I think this may have been asked before but its not clear to me.
I have 2 4500-X configured as a VSS pair, so a VSL link of 2 x 10Gig between them.
I have a number of Access stacks, built from 2600-X's
I have tried to configure dual active detection, which from what I read it is to use ePAgP or Dual-Active Fast hello Packets.
I do not have any additional SFP's to connect the 4500's together using Fast Hello, so ePAgP appears my only option
When I try and configure the access stack with an Etherchannel across 2 switches using PAgP I get the error -
command rejected by the 2960-x stack
%With PAgP enabled, all ports in the Channel should belong to the same switch
Command rejected (Port-channel11, Te1/0/1): Invalid etherchnl mode
From what I have read, PAgP cannot be configured across a stack, and people are recommending LACP as the method to configure the Etherchannnel, but How does that work with Dual-Active detection PAgP?
When I configuring Dual-Active detection PAgP, and made a couple of the MEC's trusted and configure using LACP active, then tried failing the VSL between the 4500's, each stack went into err disable on the trunk connections.
Question is! Does dual active detection PAgP work over an Etherchannel configured as LACP? or what's my options
Thanks for any help.

Hi,
Question is! Does dual active detection PAgP work over an Etherchannel configured as LACP? or what's my options
No, you can't use LACP for ePAGP detection. One option is to break one of the stacks in your access layer and use the switch you want to use for dual active detection individually (not part of a stack) and uplink it to both 4500X switches. This way, you know that the single switch is used for ePAgP detection.
HTH

HP Virtual Connect to 4500-X VSS

Is it possible to create a shared uplink set between 2 HP VC FlexFabric 10Gb/24-Port Module connecting to 2 Cisco 4500-Xs in VSS (total of 4 links)? Traditionally I've been created 1 SUS for each VC going into Cisco Nexus 5Ks. Each SUS is active/active and then within VMware each vSwitch has both SUS links. This works well, but I'd like to know if there's a better way to be doing things.

Hi,
some info.
PAgP is supported in all platforms except the Cisco Catalyst 37xx stack configuration in which cross-stack EtherChannel (LACP) is required to have MEC-connectivity with the VSS. Because cross-stack EtherChannel does not support PAgP, it cannot use enhanced PAgP for dual-active detection. A common approach to resolve this gap in support is to use two EtherChannel links from the same stack member. This solution is a non-optimal design choice because it creates a single point-of-failure. If a stack member containing that EtherChannel fails, the whole connectivity from the stack fails. To resolve this single point-of-failure problem, you can put two dual-link EtherChannel group, each on separate stack member connected to VSS; however, it will create a looped topology. The loop-free topology requires a single EtherChannel bundle to be diversified over multiple members which in turn requires LACP.

4500-E vss MEC

Hi all,
I was reading today that Cisco Release IOS XE 3.4.0SG does not support Layer 3 MEC on the 4500 platform.
I would like to configure my MEC and run OSPF on my UPLINK. I would also like to prioritise 1 uplink over the other.
Would something like this work or can someone recommend a better solution not too sure abut the ospf cost.
thank you
SWITCH-VSS(config)#interface Port-channel 10
SWITCH-VSS(config-if)#switchport
SWITCH-VSS(config-if)#switchport mode trunk
SWITCH-VSS(config-if)#switchport nonegotiate
SWITCH-VSS(config-if)#switchport trunk allowed vlan 100
SWITCH-VSS(config)#interface range gigabitEthernet 1/2/48, gigabitEthernet 2/2/48
SWITCH-VSS(config-if-range)#switchport
SWITCH-VSS(config-if-range)#switchport mode trunk
SWITCH-VSS(config-if-range)#switchport nonegotiate
SWITCH-VSS(config-if-range)#switchport trunk allowed vlan 100
SWITCH-VSS(config-if-range)#channel-group 10 mode desirable
SWITCH-VSS(config)#interface port-channel 15
SWITCH-VSS(config-if)#switchport
SWITCH-VSS(config-if)#switchport mode trunk
SWITCH-VSS(config-if)#switchport nonegotiate
SWITCH-VSS(config-if)#switchport trunk allowed vlan 105
SWITCH-VSS(config-if)#interface range gigabitEthernet 1/3/48, gigabitEthernet 2/3/48
SWITCH-VSS(config-if-range)#switchport mode trunk
SWITCH-VSS(config-if-range)#switchport nonegotiate
SWITCH-VSS(config-if-range)#switchport trunk allowed vlan 105
SWITCH-VSS(config-if-range)#channel-group 15 mode desirable
SWITCH-VSS(config)#interface vlan 100
SWITCH-VSS(config-if)#ip address 10.0.0.1 255.255.255.252
SWITCH-VSS(config-if)#int vlan 105
SWITCH-VSS(config-if)#ip address 10.0.0.5 255.255.255.252
SWITCH-VSS#conf t
Enter configuration commands, one per line. End with CNTL/Z.
SWITCH-VSS(config)#router ospf 100
SWITCH-VSS(config-router)#router-id 10.10.10.10
SWITCH-VSS(config-router)#log-adjacency-changes
SWITCH-VSS(config-router)#nsf
SWITCH-VSS(config-router)auto-cost reference-bandwidth 1000
SWITCH-VSS(config-router)#network 10.0.0.0 0.0.0.3 area 0
SWITCH-VSS(config-router)#network 10.0.0.4 0.0.0.3 area 0
SWITCH-VSS(config-router)#passive-interface default
SWITCH-VSS(config-router)#no passive-interface port-channel 10
SWITCH-VSS(config-router)#no passive-interface port-channel 15
SWITCH-VSS(config-router)#no passive-interface vlan 100
SWITCH-VSS(config-router)#no passive-interface vlan 105
SWITCH-VSS(config-router)#^Z
SWITCH-VSS(config)#int vlan 100
SWITCH-VSS(config-if)#ip ospf cost 10
SWITCH-VSS(config-if)#int vlan 105
SWITCH-VSS(config-if)#ip ospf cost 100
SWITCH-VSS(config-if)#

So you are having two etherchannels to the same device ?
I'm just not sure why you are using two etherchannels as one should give you the redundancy ie. if one of the 4500s goes down you still have the connection from the 3550 to the other 4500.
Again though, like i say it could be due to may lack of knowledge in terms of VSS.
Hopefully Reza can add to this.
Jon

High CPU with error "%ADJ-3-RESOLVE_REQ:" in Catalyst 4500-X VSS after making L3 function (static routing)

We have a VSS based on 2x WS-C4500X-16., The VSS is used as Layer 2 Switch for diffrents Vlan in our DC.
After making the VSS as a Layer 3 gateway for our production VLAN and added 2 routes for routing purposes, we encountered a network down time with high CPU in the VSS and a huges log messages :
.May 14 12:11:25.947: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.22 Vlan100
.May 14 12:11:34.516: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.22 Vlan100
.May 14 12:11:40.072: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
.May 14 12:11:49.682: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:11:55.079: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
.May 14 12:12:00.926: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
.May 14 12:12:06.701: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.8.32 Vlan100
.May 14 12:12:12.624: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
.May 14 12:12:21.627: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.7.40 Vlan100
.May 14 12:12:32.261: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.8.32 Vlan100
.May 14 12:12:41.801: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.2.105 Vlan100
.May 14 12:12:49.633: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:12:54.831: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
.May 14 12:12:59.960: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.1.1.254 Vlan100
.May 14 12:13:08.745: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:13:16.138: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:13:22.393: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
.May 14 12:13:31.415: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.141 Vlan100
.May 14 12:13:38.944: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.2.215 Vlan100
.May 14 12:13:45.972: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.253 Vlan100
Bellow are the show version of our VSS,
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), Version 03.04.00.SG RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Wed 05-Dec-12 04:38 by prod_rel_team
ROM: 15.0(1r)SG10
S_C4500X_01 uptime is 33 weeks, 1 day, 14 minutes
Uptime for this control processor is 33 weeks, 1 day, 16 minutes
System returned to ROM by power-on
System restarted at 11:59:10 UTC Tue Sep 24 2013
Running default software
Jawa Revision 2, Winter Revision 0x0.0x40
Last reload reason: power-on
License Information for 'WS-C4500X-16'
License Level: ipbase Type: Permanent
Next reboot license Level: ipbase
cisco WS-C4500X-16 (MPC8572) processor (revision 9) with 4194304K/20480K bytes of memory.
Processor board ID JAE173303CF
MPC8572 CPU at 1.5GHz, Cisco Catalyst 4500X
Last reset from PowerUp
4 Virtual Ethernet interfaces
32 Ten Gigabit Ethernet interfaces
511K bytes of non-volatile configuration memory.
Configuration register is 0x2101
Can you help please,

Hi,
thanks for your reply, but there is no hsrp configured, just an interface vlan. with 2 static routes and the problem was there for more than an hour before we decided to rollback.
Is there a BugId with this problem in Cisco DataBase.
here is a show ip route
S_C4500X_01# show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is 10.2.1.253 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 10.2.1.253
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.0.0.0/8 is directly connected, Vlan100
L 10.1.1.250/32 is directly connected, Vlan100
172.31.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.31.0.0/16 is directly connected, Vlan120
L 172.31.0.1/32 is directly connected, Vlan120
S 192.1.0.0/16 [1/0] via 10.1.1.254
and the show ip cef:
_C4500X_01# show ip cef
.May 14 12:13:57.859: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 10.2.1.158 Vlan100 f
Prefix Next Hop Interface
0.0.0.0/0 10.2.1.253 Vlan100
0.0.0.0/8 drop
0.0.0.0/32 receive
10.0.0.0/8 attached Vlan100
10.0.0.0/32 receive Vlan100
10.1.1.6/32 attached Vlan100
10.1.1.17/32 attached Vlan100
10.1.1.40/32 attached Vlan100
10.1.1.41/32 attached Vlan100
10.1.1.50/32 attached Vlan100
10.1.1.60/32 attached Vlan100
10.1.1.99/32 attached Vlan100
10.1.1.121/32 attached Vlan100
10.1.1.122/32 attached Vlan100
10.1.1.124/32 attached Vlan100
10.1.1.125/32 attached Vlan100
10.1.1.126/32 attached Vlan100
10.1.1.225/32 attached Vlan100
10.1.1.227/32 attached Vlan100
10.1.1.250/32 receive Vlan100
10.1.1.254/32 10.1.1.254 Vlan100
10.2.1.3/32 attached Vlan100
10.2.1.4/32 attached Vlan100
10.2.1.6/32 attached Vlan100
10.2.1.8/32 attached Vlan100
10.2.1.9/32 attached Vlan100
10.2.1.18/32 attached Vlan100
10.2.1.23/32 attached Vlan100
10.2.1.24/32 attached Vlan100
Prefix Next Hop Interface
10.2.1.26/32 attached Vlan100
10.2.1.28/32 attached Vlan100
10.2.1.29/32 attached Vlan100
10.2.1.31/32 attached Vlan100
10.2.1.103/32 attached Vlan100
10.2.1.108/32 attached Vlan100
10.2.1.109/32 attached Vlan100
10.2.1.124/32 attached Vlan100
10.2.1.129/32 attached Vlan100
10.2.1.137/32 attached Vlan100
10.2.1.139/32 attached Vlan100
10.2.1.143/32 attached Vlan100
10.2.1.144/32 attached Vlan100
10.2.1.159/32 attached Vlan100
10.2.1.167/32 attached Vlan100
10.2.1.174/32 attached Vlan100
10.2.1.175/32 attached Vlan100
10.2.1.176/32 attached Vlan100
10.2.1.181/32 attached Vlan100
10.2.4.38/32 attached Vlan100
10.2.4.39/32 attached Vlan100
10.2.4.43/32 attached Vlan100
10.2.4.47/32 attached Vlan100
10.2.4.51/32 attached Vlan100
10.2.4.63/32 attached Vlan100
10.2.4.65/32 attached Vlan100
10.2.4.69/32 attached Vlan100
10.2.4.71/32 attached Vlan100
10.2.4.73/32 attached Vlan100
10.2.4.102/32 attached Vlan100
10.2.4.106/32 attached Vlan100
10.2.4.107/32 attached Vlan100
10.2.4.113/32 attached Vlan100
10.2.4.116/32 attached Vlan100
10.2.4.119/32 attached Vlan100
10.2.4.120/32 attached Vlan100
10.2.4.122/32 attached Vlan100
10.2.4.141/32 attached Vlan100
10.2.4.148/32 attached Vlan100
10.2.6.7/32 attached Vlan100
Prefix Next Hop Interface
10.2.6.16/32 attached Vlan100
10.2.6.31/32 attached Vlan100
10.2.7.14/32 attached Vlan100
10.2.7.22/32 attached Vlan100
10.2.7.24/32 attached Vlan100
10.2.7.34/32 attached Vlan100
10.2.7.37/32 attached Vlan100
10.2.7.41/32 attached Vlan100
10.2.7.48/32 attached Vlan100
10.2.8.18/32 attached Vlan100
10.2.8.32/32 attached Vlan100
10.2.8.59/32 attached Vlan100
10.2.8.70/32 attached Vlan100
10.2.8.85/32 attached Vlan100
10.2.8.88/32 attached Vlan100
10.2.8.104/32 attached Vlan100
10.2.8.135/32 attached Vlan100
10.2.99.10/32 attached Vlan100
10.2.99.54/32 attached Vlan100
10.255.255.255/32 receive Vlan100
127.0.0.0/8 drop
172.31.0.0/16 attached Vlan120
172.31.0.0/32 receive Vlan120
172.31.0.1/32 receive Vlan120
172.31.0.5/32 attached Vlan120
172.31.0.29/32 attached Vlan120
172.31.255.255/32 receive Vlan120
192.1.0.0/16 10.1.1.254 Vlan100
224.0.0.0/4 drop
224.0.0.0/24 receive
Prefix Next Hop Interface
240.0.0.0/4 drop
and show ip arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.1.1.1 0 aa00.0400.c286 ARPA Vlan100
Internet 10.1.1.6 0 0050.5689.24b8 ARPA Vlan100
Internet 10.1.1.10 0 0050.5694.7d20 ARPA Vlan100
Internet 10.1.1.11 0 0050.5694.7d20 ARPA Vlan100
Internet 10.1.1.12 0 0050.5694.6ae7 ARPA Vlan100
Internet 10.1.1.13 0 0050.5694.6ae7 ARPA Vlan100
Internet 10.1.1.14 0 0050.568a.6321 ARPA Vlan100
Internet 10.1.1.16 0 0050.5694.0ab5 ARPA Vlan100
Internet 10.1.1.17 0 0050.5694.493d ARPA Vlan100
Internet 10.1.1.40 0 0013.19b0.9c40 ARPA Vlan100
Internet 10.1.1.41 0 1c17.d35a.c840 ARPA Vlan100
Internet 10.1.1.50 0 0002.b9b4.a5c0 ARPA Vlan100
Internet 10.1.1.60 0 000a.410f.e500 ARPA Vlan100
Internet 10.1.1.71 - 0008.e3ff.fc28 ARPA Vlan100
Internet 10.1.1.96 0 e02f.6d12.4df3 ARPA Vlan100
Internet 10.1.1.98 0 0050.5696.6d86 ARPA Vlan100
Internet 10.1.1.99 0 0050.5696.6d88 ARPA Vlan100
Internet 10.1.1.121 0 e02f.6d12.4dea ARPA Vlan100
Internet 10.1.1.122 0 e02f.6d12.4e61 ARPA Vlan100
Internet 10.1.1.123 0 e02f.6d5b.c10e ARPA Vlan100
Internet 10.1.1.124 0 e02f.6d17.c869 ARPA Vlan100
Internet 10.1.1.125 0 e02f.6d5b.c217 ARPA Vlan100
Internet 10.1.1.126 0 e02f.6d17.c8ec ARPA Vlan100
Internet 10.1.1.127 0 e02f.6d17.c876 ARPA Vlan100
Internet 10.1.1.128 0 e02f.6d5b.bef3 ARPA Vlan100
Internet 10.1.1.202 0 0000.85b7.9031 ARPA Vlan100
Internet 10.1.1.222 0 000f.f84d.2ca9 ARPA Vlan100
Internet 10.1.1.225 0 000f.f84d.3963 ARPA Vlan100
Internet 10.1.1.227 0 00c0.ee26.9367 ARPA Vlan100
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.1.1.250 - 0008.e3ff.fc28 ARPA Vlan100
Internet 10.1.1.254 0 0000.0c07.ac07 ARPA Vlan100
Internet 10.2.1.2 0 0011.4333.bcda ARPA Vlan100
Internet 10.2.1.3 0 0050.5689.5d38 ARPA Vlan100
Internet 10.2.1.4 0 0050.5689.0404 ARPA Vlan100
Internet 10.2.1.6 0 0050.5689.6d3b ARPA Vlan100
Internet 10.2.1.7 0 1cc1.def4.6940 ARPA Vlan100
Internet 10.2.1.8 0 0050.5689.330e ARPA Vlan100
Internet 10.2.1.9 0 0012.793a.3ccc ARPA Vlan100
Internet 10.2.1.10 0 0012.7990.e5d3 ARPA Vlan100
Internet 10.2.1.13 0 0050.568a.6dcf ARPA Vlan100
Internet 10.2.1.15 0 0050.568a.60ff ARPA Vlan100
Internet 10.2.1.18 0 0050.5689.091b ARPA Vlan100
Internet 10.2.1.20 0 0050.5689.451c ARPA Vlan100
Internet 10.2.1.21 0 0050.568a.0cf4 ARPA Vlan100
Internet 10.2.1.22 0 0050.5689.6c59 ARPA Vlan100
Internet 10.2.1.23 0 0050.5696.6d9e ARPA Vlan100
Internet 10.2.1.24 0 0050.5689.76c4 ARPA Vlan100
Internet 10.2.1.26 0 0050.5689.2f4e ARPA Vlan100
Internet 10.2.1.27 0 0050.5689.0632 ARPA Vlan100
Internet 10.2.1.28 0 0050.5689.1ce9 ARPA Vlan100
Internet 10.2.1.29 0 0050.5689.6aaa ARPA Vlan100
Internet 10.2.1.31 0 0050.5689.0d1a ARPA Vlan100
Internet 10.2.1.37 0 0050.5696.6d81 ARPA Vlan100
Internet 10.2.1.103 0 d4be.d9be.8eef ARPA Vlan100
Internet 10.2.1.106 0 14fe.b5e1.c595 ARPA Vlan100
Internet 10.2.1.107 0 0023.ae7d.a966 ARPA Vlan100
Internet 10.2.1.108 0 d4be.d9c8.6770 ARPA Vlan100
Internet 10.2.1.109 0 14fe.b5e9.c5b5 ARPA Vlan100
Internet 10.2.1.110 0 14fe.b5ea.5f9d ARPA Vlan100
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.2.1.111 0 001e.c959.d4f0 ARPA Vlan100
Internet 10.2.1.114 0 b8ac.6f48.4538 ARPA Vlan100
Internet 10.2.1.115 0 14fe.b5e1.ed89 ARPA Vlan100
Internet 10.2.1.116 0 7845.c409.1959 ARPA Vlan100
Thanks
Lotfi

Prime Infrastructure 2.0 Software Deployment VSS Systems

Good day -
Has anyone used the PI 2.0 Software Deployment with VSS systems like 6500 or 4500? Does it work? Does it upgrade the image in eFSU? Should VSS systems be manually updated?
Finally are there any guides or documentation on using PI 2.0 to deploy / upgrade images for platforms like 6500 / 4500 running VSS mode?
Thanks,
John

there is a Feature Enhancement BUG filed for VSS support
Unable to add or manage a 6500 in VSS in PI:
https://tools.cisco.com/bugsearch/bug/CSCuj09930/?reffering_site=dumpcr
Thanks-
Afroz
[Do rate the useful post]
****Ratings Encourages Contributors ****

EtherChannel between stacked VSS Catalyst 4500X and Stacked 2960X.

I can have only one link in the EhterChannel up but the 2nd one goes in to suspended mode.
I've tried recreating channel group on different ports but with the same results. Am I doing something wrong or pagp cannot be transmitted over stacks on both ends (I have quite a few EtherChannels but all to single/non-stacked switches)?
2960X stack config
Version: 15.0 (2r)EX
interface TenGigabitEthernet2/0/2
description HR-Link1
switchport mode trunk
switchport nonegotiate
channel-group 2 mode on
interface TenGigabitEthernet1/0/2
description HR-Link2
switchport mode trunk
switchport nonegotiate
channel-group 2 mode on
4500X Stack (VSS) config
Version: 03.04.00.SG (fc3)
interface TenGigabitEthernet1/1/12
description MO-Link1
switchport mode trunk
switchport nonegotiate
shutdown
channel-group 12 mode on
interface TenGigabitEthernet2/1/12
description MO-Link2
switchport mode trunk
switchport nonegotiate
shutdown
channel-group 12 mode on
Thank you,
T

Thanks for reply!
I have tried desirable mode as well but no luck. I can work on this only during the weekend as downtime is not an option.
These two 10G links were just installed last weekend and one patch cable I had to replace due to complete lack of connectivity (small shop so we no fiber testing equipment).
I did not do a lot of troubleshooting last weekend but I will dig in to that this weekend. I was hoping to get some insight from people who work with this on daily basis.
Post from about a year ago got me worried: https://supportforums.cisco.com/discussion/12072281/4500-x-vss-mec-2960-x-stack
Thanks again.
T

6500 VSS SNMP issues

We recently converted 2 6506-E chassis to use VSS w/ Quad-Sup and noticed that several SNMP OIDs we used for monitoring have stopped working.
OID 1.3.6.1.4.1.9.9.217.1.3 only provides module statistics for the active chassis, rather than both.
OID 1.3.6.1.4.1.9.5 no longer exists as an object. We monitored numerous items under 1.3.6.1.4.1.9.5.1.3.1.1 which are no longer available.
Has anyone encountered these issues after converting to VSS and/or do you have any suggestions with how to deal with them?
Thanks,
-Kevin

I am having similar issue on 4500-X VSS, ENTITY-MIB only available on active chassis.

How to span vlans across core layer in core/distribution/access campus design?

Hi,
I studied Cisco Borderless Campus Design Guide 1.0 (http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/Borderless_Campus_Network_1-0/Borderless_Campus_1-0_Design_Guide.html) last week because we plan to redesign our campus backbone to a three tier Core/Distribution/Access Design.
Today we use a collapsed backbone where a lot of vlans are spanned across the backbone because they are needed in different buildings.
Could anybody give me a hint how Cisco recommends to deal with that kind of vlans in the multi-tier design?
In my eyes between core and distribution layer there is only routing functionality and no l2 transport of vlans.
So using the same vlan in different buildings seems not to be supported?
Best Regards,
Thorsten

Thorsten
Just to add to Joseph's post.
It is quite common for a vlan to be spanned when it doesn't actually need to be ie. the network has evolved that way.
Most things do not need L2 adjacency, they can happily use L3. Servers sometimes do but in the campus design your servers are usually located in one site so you don't need to extend vlans to other sites in your campus.
Not suggesting this is the case for you but it may be worth checking whether you really do. (apologies if you already have)
As Joseph mentioned you really want to avoid it if at all possible ie. ideally all connections to the core switches are L3 ie. no need for vlans at all in the core.
If you need to extend a few vlans then you can do this but still route for all other vlans ie. you would configure your distribution to core connections as trunks and then allow the vlans you need to extend plus one other vlan, unique per distribution pair, to route all other vlans. So per site your distribution switches route all vlans except the extended vlans and of they need to route to a vlan in another site they use that unique vlan.
But this is not ideal because you then need to extend certain vlans across the core and because you are using L2 connections STP could come into it although that does depend on your core switch selection eg. 4500/6500 VSS etc. would alleviate this.
There are ways to extend vlans across a L3 network but the solutions available are very much dependant on the kit you use and their capabilities so if you do need multiple vlans in multiple sites but still want to keep a L3 core you may want to investigate some of those before purchasing kit (unless of course you have already purchased it).
What you do really depends on just how many vlans you actually need to extend between sites.
Jon

Nexus 5K L3 Design (Best Practice)

Hi All,
I have a few questions regarding the L3 capabilities of the 5548UPs.
We have the enterprise licensing with the L3 Daughter card and want to route from our 4500-X VSS' to our Nexus 5548s running version: 6.0(2)N2(3)
Our design is that our data center traffic is kept isolated in the DC. Our users will route across the 4500Xs to the DC to access the server host.
What we have is 4 physical links from our VSS stack to our Nexus cluster, with 2 cables from VSS1 to N5K-1 and 2 cables from VSS2 to N5K-2. See below:
VSS1 ---------------- 2 x --------------N5K-1
    |                                      |
    |                                    |
VS Link                         PeerLink
    |                                        |
    |                                        |
VSS2 ----------------2 x ---------------N5K-2
What we also have in our topology is an IPS between the VSS and Nexus switches to complicate the design.
Talking to my Sales Engineer he suggested putting the 4 links in a VPC using SVIs at each end and HSRP. Looking further into this it seems that this is a supported design but not a recommended design. I believe this works for Unicast forwarding but doesn't work for multicast according to this doc which is for version 5.1.3.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/interfaces/513_n1_1/ops_interfaces/L3_w_vpc_5500platform.html
From what I read, I believe the recommended way is to use point to Point routed links (/30s) x 4 and use ECMP to load balance the traffic.
The other thing I am looking into is finding out whether the IPS units allow asymmetric routing, eg if it comes in on port 1, and goes out on port 4, will it understand the flows? I'm waiting to hear back on this.
Would this assumption be correct to use the Point to Poink /30s and use ECMP? Is this what I should be doing rather than the SVIs across a vPC?
Do I need to have a separate L3 links between the N5K's?
Is there any other considerations I should be making?

Just had an update on the IPS units - they support asymetric routing, which is good news.

Single or dual 4500e for redundancy

I apologize if this has been asked before, but I haven't been able to find a solid answer when searching.
We're deploying a new datacenter and will have 20 racks of servers, mostly 1u. Given our bandwidth needs which are reasonably modest we're planning on using dual 2960s switches at the top of the racks and aggregating on a single or dual 4500e using 10gig links. The 4500e(s) will also have a bunch of 1gb devices such as firewalls, routers, and load balancers connected to them. Pretty typical network core. Given the need for 40 10gb links to racks and then another 20-or-so 1gb, the 4500e chassis seems to fit the bill.
My question is, do we go with a single 4507e with full redundancy (dual 10gb cards, one link to each from each rack, dual 1gb card, and dual supervisors) or a pair of either 4506e switches each with their own cards. With a virtual chassis the 4506e is appealing, but I'm not up to speed on any limitations that might impose. With IISU and the like does having two physical chassis vs everything in a single actually buy us anything if they're going to be in the same physical proximity anyway? A big reason to go with the single chassis is space - 11 rack units vs 20.
If we do go with a single chasis, other than Cisco's HA docs on the 4500e, is there any documentation or case studies that I could use to sell the idea to management? A number of people, especiailly those in favor of a ton of cheap netgear switches, argue that a single chassis is a single point of failure and we should never do it.
Thanks!

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 you've described, the problem with any single chassis, the chassis itself can become a single point of failure even when loaded with redundant components. Independent chassis (e.g. VSS, StackWise) provide chassis redundancy although it does raise a question on software redundancy, i.e. multiple chassis are running some form of tightly coupled chassis OS vs. standalone chassis. Standalone chassis should be, in theory, the most redundant but they too create issues such as load sharing and asymmetrical path issues (e.g. unicast flooding). If you understand and trust a multi-chassis OS, I personally think it's often the "better" redundancy option.
I don't know if VSS on the 4500s support it, but 6500 VSS supports quad supervisiors, so if you lose a single sup on those you don't lose one of your VSS chassis pair.
Regarding your later post on using a 4500-X VSS pair, yes that might be an idea core for high density 10g. For twenty 10g ports each, you would need either the 16 port with the optional 8 port module or the 32 port model.
Depending on your remote rack setups, you might also consider 3750-Xs, stacked, in lieu of multiple (individual cabinet) ToR 2960S pairs. StackWisePlus is a much better stacking technology then FlexStack. Yes, the 3750-Xs are more expensive, but you might need less if you can bring multiple racks to the same 3750-X stack. (Depending on how many downstream stacks you actually need, you might also reduce your need for 10g ports on the core.) Depending on your feature needs, you might even be able to use the LAN Base models which in the later IOSs also support StackPower.
10g is nice, but it's also expensive. When working with switches within 100m, don't overlook the possibilities of gig copper Etherchannels. For example compare total cost of 8xgig (copper) build-in ports vs. single 10g (fiber) especially if special module is required.

4500-x vss

Similar Messages

Maybe you are looking for