Cisco Switching/Routing :: 5596 - Extending 10Gb/s LAN Between Sites
Dec 14, 2011
For a simple 4x sites design for backup consolidation (3x sites connected to one central site), does the design in the attached JPEG make sense and is the configuration achievable using the specified parts?
- Each site is to have servers with 2x 10Gb/s Ethernet (both teamed/bonded/etc) and one NIC on each of the 2x switches in the site (if possible). Each site will also have 2x Cisco Nexus 5596UP Switch (though the P version may be used instead of the UP).
- Two of the sites are within 10KM of the central site
- The last site is about 35KM from the central site
- It is required to have a minimum bandwidth of 10Gb/s between any site and the central site
- I have specified 10Gb/s LW SFP+ and 10Gb/s LW SFP+ (for the 2x 10KM and 1x 35KM sites)
- are there any special licenses needed?
- as asked before, can such a "simple" design work as-is?
- what sort of single-mode fiber would fit the bill (especially for the 40KM link) - 9nm?
I have 2 Nexus 5596UPs with a layer 3 cards that are exhibiting some very peculiar behavior. The systems are running 5.1(3)N1(1).I have configured 2 VRF contexts each running their own OSPF process. There is a static gateway of last resort configured on each VRF, which is to an upstream pair of 5585X's in Active/Active. Each OSPF process has the "default-information originate always" command configured, however, backbone neighbors are not recieving a gateway of last resort from the 5596UPs. The applicable configurations are show below. All other routing information is passing correctly between devices in the network. This network is not production, it is a proof of concept for a larger implementation.
We have setup a pair of Nexus 5596 L3 switches with 2 x 10Gbps LACP links between them to act as the vpc peer link. We also have another 2 x 10Gbps LACP links between the 5596 switches to carry non VPC VLANs, this is required to provide EIGRP routing between the switches and an upstream router.I have read that it is possible to setup the vpc keep-alive link over an SVI instead of the management interfaces. Is it ok to run the keep-alive SVI over the second LACP non VPC VLAN trunk or is it recommened to keep this seperate?
I am looking to see if Nexus 5596UP & Nexus 2248TP GE compatible with SFP-10G-SR? The reason is because a consultant was hired on to "design" the network layout and has decided to purchase Cisco SFP+ Copper Twinax Cables which have a 10M limit. A small handful of the Data Center racks are 10-15M away... just out of reach of the Twinax. I would prefer NOT to move the LAN row so that it is more centered in the room. Can I use the SFP-10G-SR to connect the 2 switches (5596 & 2248) together? This SFP has a 26M reach on standard 10gig fiber, the small cost increase per connection is of no concern.
I need to implement LACP HP servers mostly DL 380 g7 with Intel based dual port with two types of Cisco equipment first scenario server connected to 3750x stack of 4 switch's .second scenario same server type connected to two Cisco Nexsus 5596 . My question regarding two type of connection.Is it possible to do active active ?Would it give fault tolerance ?With HP LACP implementation is there known issue or should i expect latency with such configuration?What is the maximal lag- channel group that is possible per type?
i have: two nexus 5596 connected each other the mgmt0 is NOT in use SVI for keepalives with IP address and /30 netmask vpc-keepalives running over fiber in e1/1. this works well uplinks to datacenter distribution switch (Cat 6500 VSS) over fiber on port-channel 1 (e1/2 and e1/10), also carrying the management VLAN (vlan 14). SVI with an IP address for management purposes
I can't get this to work. i can ping my whole network from the nexus, but not the nexus from my network. also pinging inside the mgmt vlan is not possible.
we have configured VpC between two Nexus 5596, for Vpc-Keep-alive-link we configured L3 interface with 1G (GLC-T) ,it shows the below status message "L3 not Ready" with interface LED glows in Yellow in color. is this a physical layer problem
Ethernet VLAN Type Mode Status Reason Speed Po Ch Eth1/17 -- eth routed down L3 not ready 1000(D) -- Eth1/18 1 eth access down SFP not inserted 10G(D) -- Eth1/19 1 eth access down SFP not inserted 10G(D) -- Eth1/20 1 eth access down SFP not inserted 10G(D) -- Eth1/21 1 eth access down SFP not inserted 10G(D) --
We have HSRP between NexusA and NexusB with access layer switches connecting to the core using VPC, We are trying to setup a VAM server Voice recording for Siemens phones. We need to span all voice vlan and point it to the VAM server the VAM server connects to a 3750 Stack considering the amount of traffic multiple span session can generate I plan to move the server to the Nexus directly and run a Local Span Session.
1- As we have two Nexus running HSRP and VAM server only connects physically to one NexusA (I can run local span on that nexusA) the Second NexusB is not directly connected to the VAM server I plan to run ERSPAN so if this is the best design and which path will the span traffic take from Nexus B to NexusA will it go through the access layer switches depending on the vlans allowed on the uplinks or will it go through the 20 Gig uplink between the two Nexus allowing all vlans (VPN peer links) ? WE have approximately 10 voice vlans, Do we an example config for ERSPAN session where the source are vlans (As I am for fimilliar with RSPAN) ?
It looks like the deny statement is not working as I can see all routes I am redistributing. I even did a deny on a specific route and I still see it in the routing table on another router in the autonomous system.The same below works fine on IOS platform. [code]
I have a pair of 5596 running in a vPC with Nexus 2248 connected to each N5596. When I do the command "show fex" I get the following output on the 2nd 5596
Number Description State Model Serial ------------------------------------------------------------------------ 101 FEX101 AA Version Mismatch N2K-C2248TP-E-1GE SSI16390705 102 FEX102 AA Version Mismatch N2K-C2248TP-E-1GE SSI163704AD 122 FEX122 Online N2K-C2232PP-10GE SSI16370195
I'm running version 5.1(3)N1(1) on both of the 5K's. I have looked through all the configuration and I am not understanding why I am getting this error. I have tried to look it up on [URL], but not having a ton of luck.
I have 2 datacenters running same equipement (two Nexu 5596 with FEX).I just took a look at the log just to see if everything is ok and I saw that I have the same error message (a lot of times) at both location :
%SYSMGR-FEX100-5-HEARTBEAT_LOSS: Service "satctrl" heartbeat loss 2 ,max 7,I though it was a problem with my peerklink-keepalive connection but I see the word FEX ....so i'm not sure...
Note that at both locations, my Nexus are connected back to back through the management port using transceivers. So it's a copper cable from the first nexus, going into a transceiver, going to another transceiver in fiber and then back to copper to the other nexus.
I currently have Nexus 5596 pair with VPC peer link Po1 between them. My goal is to connect our new Nexus 7Ks to the 5K's using Fabric Path. My question is during this inital setup with the 7K's. Can I use the same port channel number on the 7K's as I did the 5K's? Is the port channel locally significat?
i want to remove the sync-profile on each of two synchronized Nexus 5596UP without loosing the config stored in Switch-Profile. That means without connectivity interruption and re-configuration of interfaces in "conf t mode", for example. Since NX-OS Release 5.2(1)N1(1) there is a new command
switch(config-sync)# no switch-profile abc profile-onlyprofile-only—Deletes the switch profile without the local configuration.
I have pair of 5596 switches in vPC. One host say "HOST A" is connected to the primary vPC peer and other "HOST B" on secondary vPC peer.Both are in same VLAN 10. Both hosts are vpc orphan ports as their NIC is configured in active/standby mode.I have configured span session on both vPC peers with span source as VLAN 10 in rx mode.Span destination is connected to secondary vPC peer. The issue here is that I am not able to capture the traffic originating from HOST A destined to HOST B which is traversing vPC peer-link.Same issue occurs for the traffic in reverse way and span destination on primary vPC peer. In a nutshell, any traffic which crosses vPC peer-link is not getting captured.
What could be the issue and is there any solution for it. Below mentioned is the span config and relevant interfaces. [code]
I'm looking at provisioning a Catalyst 4500 with a WS-X4712-SFP+E module to allow for future 10Gb connectivity via 10Gb SFP+ interfaces. These cards are backwards compatible with standard 1Gb SFP interfaces but I'm wondering about the other way around; ie. can you populate these blades with 10Gb SFP+ interfaces when they connect to Catalysts with only 1Gb SFP interfaces at the other end?
The data sheets don't really explain this. It seems pointless getting 10Gb SFP+ interfaces for the 4500 when it's only 1Gb at the access layer end, but these access switches will be replaced in the near future (~12 months) and if the 10Gb SFP+ interfaces support connections at 1Gb speeds upfront, it would mean I could retain these interfaces when the access switches upgrade to 10Gb connectivity capabilities down the track. Does the 10Gb SFP+ interfaces are compatible with 1Gb SFP's or only other 10Gb SFP+ interfaces?
Created two 6509s as VSS with just one 10gb connection?I know it is recommended to use both the 10gb connections on the sup-720 from below configuration guide
" Information about VSL Topology # A VSS contains two chassis that communicate using the VSL, which is a special port group. Configure both of the 10-Gigabit Ethernet ports on the supervisor engines as VSL ports. "
I have two 3750 stacks that are currently connected using two1GB fiber connections in an etherchannel. I now added new switches to each stack with 10GB modules in them. We would like to bring up the 10GB connection, but still have one of the 1GB lines as a backup, or even the whole etherchannel. Is there a way for us to make the 10GB the main and the 1GB the standby?
the phone connects to the 3750-A access layer switch (VTP mode client) which connects to the nexus 5596 (The nexus is the layer 3 device and set to vtp mode server) and finally we have a Voice recorder that connects to another access layer 3750-B switch.(VTP mode client)
For voice recording I need to setup RSPAN and the nexus5596 does not support RSPAN will the following have any impact on the nexus
IF I move the 3750-B to VTP server mode and run the command remote span on the VLan I need to Rspan its going to update the VTP data base in short it will update the vlan.dat file for all the switch in that VTP domain.
AS the vtp update reaches the nexus saying there is a change (keeping in mind the nexus does not support rspan not sure hows its going to handle that request and how its going to update its vlan.dat file)
Is it going to incremment the VTP revision number? can it crash the vlan.dat file on the nexus ? or do nothing and ignore the update and stop the update from proceeding to the 3750 A switch?
I have configured about 20 of these switches now, and notice in the port listings a TE1/1//1 TE1/1/2 and GI1/1/1 GI1/1/2 uplink port. There are only two uplink SFP+ ports. I now have a reason to install with a 1Gb uplink to the Core. I am using a GLC-LH module at each end. I did configure the TE1/1/1 port for the uplink. Does not work though..Do I need to configure the two GI1/1/1 and 1/1/2 ports for uplink, remove the TE configuration for the uplink to work? Using the UNIVERSAL code with a LANBase license.
I am having trouble updating the epld image on the 10gb Module of Nexus 7k. we have two nexus and two 10gb module. Tried the other one and it worked fine. its jsut the first one that has problems with the epld image. i have tried on both the nexus on two different slots and still the same error.
I get the following error:
Chain connectivity is broken while upgrading the FPGA. (Error Number : 36)
We are trying to connect 2 nexus 5558UP (5.1.(3)N1(1)) with 10G-SFP+-LR interfaces. The interfaces are not genuine cisco's (smartoptics) but as far as we can tell, they are accepted by the hardware. If we take a look at the optical levels, we can see that the switches can see eachother (double-checked by bringing down one interface to see if optical levels really disappears) on optical level, well within limits. I found a notice about changing debounce timers but this doesn't work, setting it to 0 or 1000 doesn't make a difference. Copies of the different show int commands can be found at the end of this text.
Wim Holemans Network Services University of Antwerp
swnxds01-enable# sh int eth1/3 transc details Ethernet1/3(code)