Cisco Switching/Routing :: Nexus 5020 Support Of HP Passive Twinax Cable?
Mar 3, 2013
I have a customer who is having some issues with 5m passive HP twinax cables, 537965-001, with a Chelsio 10G NIC. Aside from NIC driver issue, if NX-OS recognizes this SFP+, should it be expected to work in a 5020 running 4.2(1)N1(1)? Whether Cisco has certified passive HP twinax cables? I have included output to 'transceiver details' to a Cisco twinax and the HP (WL GORE) cables.
Nexus5020# show interface eth 1/7 transceiver details
Ethernet1/7
sfp is present
name is CISCO-MOLEX
type is SFP-H10GB-CU3M
We are facing issue of continous packet discards On nexus4001L link (int po2) to Nexus5020 switch. Nexus4001L is installed in IBM blade center server and we have FCOE enabled in this setup. [code]
The below nexus 5020 nx-os version and type/revision of my GLC-T is compatible with each other? I noticed also the "Transceiver calibration is invalid" when i do show int e1/8 transceiver details , what does it mean?
I have an alert from monitoring system about: “ fan for this system is not in the NORMAL state”. In the switch I found that the problem is with fex 3, see below:
Nexus5020# sh env fex 3 fan Fan Fex: 3: ------------------------------------------------------ Fan Model Hw Status ------------------------------------------------------ Chassis N2K-C2148-FAN -- failure PS-1 N2K-PAC-200W -- OK PS-2 N2K-PAC-200W -- OK
Technician said: fans appear to be operational, BUT the only thing that appears abnormal is STAT light is amber (not sure what it means).
Also, if I compare the temperature from module 3 with module 2 (which doesn’t have an alert) is almost the same, this is why I think the fan is working fine, since module 3 is not hotter that module 2.
I have two N5K (5020) switches with NX-OS - 5.0(3)N2(1). These two switches form VPC domain: peer-link = 2*10Gb ports (1/17-18) and peer-keepalive link over managements ports.Also I have two HP servers with two 10 Gb ports on each server.Each server conected by one link to each N5K switch (1/9-10). N5K downlinks configured as access ports with LACP Active mode.There is only one VLAN (1).When "no shut" command entered on N5K access ports - ports going in "not connected" status, begin flap and then going in "linkFlapErrDisabled" state.In attach - "sh run" from N5K.
We have two Nexus switches in our network, one of them is Nexus5020 other Nexus5596UP. System image is identical on both switches 5.2(1)N1(4). When we try to setup VPC between these switches we see that all configured vlans on VPC peer link between Nexus switches are blocked by spanning tree protocol with message "Bridge Assurance Inconsistent, VPC Peer-link Inconsistent". We still can't solve this problem.
Topology:
NEXUS_5020---Peer_link(Po2)---NEXUS_5596UP
/
/
Member_link (Po100) Member_link (Po100)
/
/
SERVER
Configuration:
NEXUS_5020: speed 1000 interface Vlan2000 no shutdown description VPC_keepalive_link vrf member VPC_kepalive ip address 10.55.55.2/30
specifying Cisco devices and I've made an error.I have 2 Catalyst 2960S switches (C2960S-24PS-L).Based on this snippet of web copy from the Cisco website:What's new for the Cisco Catalyst 2960-S Series Switches with LAN Base Software: # 10 and 1 Gigabit Ethernet uplink flexibility with Small Form-Factor Pluggable Plus (SFP+), providing business continuity and fast transition to 10 Gigabit Ethernet I bought a cable assembly "SFP-H10GB-CU3M" (3 meter copper twinax cable with 10GB SFPs on each end). Unfortunately, it appears after more careful reasearch that my specific model 2960S's are not directly compatible. , can I force these 10GB SFPs down to 1GB and get them to work with my switches or do I need to return and repurchase?
I'm trying to create a vpc between a Nexus 5010 and Nexus 5020 switch. I recently upgraded the software so they are running the same version. I connect get a vpc link. Is there something wrong with my setup? Is a vpc between a 5010 and 5020 even possible? They are connected using a pair of Intel X520's in 802.3AD teaming mode. [code]
Our customer is willing to have a Cisco Nexus 5020 to provide server connectivity and this Nexus would go connected to their core switch 6509. They are concern about Spanning tree compatibility between the Nexus and the 6509. Are they fully compatible for Spanning tree?
I'm currently working on a plan to migrate our 6500's over to our new 7010's. At the time of the migration I want to tighten up our OSPF design and configure OSPF for "passive-interface default" then allow only those interfaces that should have OSPF neighbors to send the hellos. The issue is that the command is not showing up under the OSPF process. What's even more interesting is that the Nexus 5.x Unicast Routing Configuration Guide shows that the "passive-interface default" command should be an option to enter.
I'm currently running version 5.1(4) (though looking to upgrade to 5.2 during my migration testing). I would rather configure the passive-interface via the routing process versus having to enter it on every interface.
Does the nexus 7010 support virtual switching yet? All of the posts I have found from about a year ago say that it is going to be supported, but there were no dates listed. I heard the same thing from Cisco a while back, but haven't followed up with it.If it is supported finally are there any configuration guides available for it?
We recently purchased a pair of 2232TM Fabric eXtenders just to find out that our Nexus 7000 does not support it. Will there be support for the 2232TM FeX in Nexus 7000 any time soon?
if vPC is supported between a single 2232PP FEX and two 7000 switches running 6.0(1)? I have been researching this for an implementation I am doing for a client and was able to determine it was not supported with earlier versions of 5.0 when the FEX is connected via vPC as I described above, but I can't find anything related to version 6.0(1). I have done this for other clients with 5000 and 2000 switches, but I don't have too much experience with 7000 switches.
Iam having some issue trying to configure snmp-server context vrf XXX.From some reason even if i put my VRF name i cant see anything about this vrfthis is the command i add:
future support for IP Sla on the nexus 7000. The latest info that I've seen is that it will/could be supported in release 6.2, scheduled for mid 2012. Does this still accurate?
I am trying to install SFP-GE-T module on Nexus 5548UP Switch, but is giving the ‘SFP validation Failed’ error. The details of the switch is given below
Model : N5K-C5548UP-FA
The interface is configured with speed 1000 before inserting the module, still we are getting the same error. PFA logs for more details We have 8 Nos of SFP-GE-T modules , all are giving same error. We tried to insert the module on onboard as well as expansion module.
The same module is working fine on Cisco 3750X-24T-L Switch As per the Hardware installation guide , SFP-GE-T transciever is supported on N5K platform. Please extend your support in configuring SFP-GE-T module on N5K platform? We tried with SFP-GE-S module on the same switch , and the same is found working fine.
I have two different model's of GLC-T SFP's. One is PN 30-1410-02 the other is PN 30-1410-03. The -02 will not work in Nexus 5020 or an ASR-1000 router that I have, but works fine in my Cisco Wireless Controller. The -03 works fine in any device. My problem is when ordering, you can not specify the -03 they get ordered as GLC-T and none of my suppliers can assure me that I would get the -03.What is the difference between these two?
currently nexus 2000 and nexus 7000 does not support dual connection. you can not connect to 1 nexus 2000 to 2 nexus 7000 chasis. But for the nexus 5000, you can. what is the problem to to support this feature on Nexus 7000s? 5000s and 7000s run same software.
The data sheet for the 2232PP says you can use a SFP-GE-T, but there is no mention of 100Mbps. I want to recommend to a customer that they use 2232PP for an upcoming core upgrade, but it may need to support some existing 100Mbps devices which are currently connected to 3750s.
I am deploying a pair of Nexus 5596's with 3750 POE switches in the closets. I'm looking for a best practice as how to configure the Nexus 5596 to support proper QoS for EF at the core.
I am sure that F1 linecards on Nexus weren’t able to support L3 functionality, so my query is does the F2 linecard (N7k-F248XP-25) on Nexus 7010 support Layer 3?
I have a problem with the switches Nexus, is impossible authenticate from tac_plus. In other company, I configured ACS for authenticate the Nexus Switches and OK The configuration of my tac_plus is:
user = gian { login = cleartext prueba member = nexus group = nexus { default service = permit service = shell { #double-quote-values = yes #shell:roles=""network-admin"" cisco-av-pair*shell:roles="network-admin"
The configuration of switch is:
tacacs-server host xx.xx.xx.xx key 7 "xxxxx"aaa group server tacacs+ AAA_TACACS_SERVER server xx.xx.xx.xx source-interface mgmt0 aaa authentication login default group AAA_TACACS_SERVERaaa authorization commands default group AAA_TACACS_SERVER localaaa accounting default group AAA_TACACS_SERVER
Nexus 5500 support auto negotiation on 1gig sfp port? There is an end device that only support auto negotiation and cannot be manually set speed/duplex.
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?
