Cisco Switching/Routing :: Nexus 5500 Support Auto Negotiation On 1gig Sfp Port?
Jul 28, 2012
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.
We are facing to an annoying issue. We have a 6509 running in Catos 8.3(4) with WS-X6548-GE-TX, WS-X6348-RJ-45 and WS-X6148-RJ-45. When we configure the mode in auto negotiation, it comes up in half duplex. We need to configure the speed mode at 100Mbit/Full to make it work. But if the chassis or port restarts (not the server), the link becomes half duplex. This happens only on module in Gigabyte like WS-X6548-GE-TX.
Cable have been replaced but does not work. It is not happened on another chassis running on IOS 12.2(18)SXF17b with WS-X6548-GE-TX.
confirm if "negotiation auto" is supported gigabit port for C3925E router.
Router(config-if)#Interface gi0/2 Router(config-if)#description test link Router(config-if)# no ip address Router(config-if)# negotiation auto ^ % Invalid input detected at '^' marker.
I've a D-Link DFE-520TX PCI Fast Ethernet card, which is/was excellent until this first problem. 2 nights ago there was some good lightning/thunders activity, resulting in burning of ISP network switches. This morning they replaced the switches and brought up the network, but here's the problem:1) Under the default card setting with Auto-negotiation, PC looks for DCHP Server address resolution and ends up with YELLOW triangle in the system tray.2) Whereas, when I CHANGE the card setting to 10Base in FullDuplex, then PC gets connected to the ISP network.ISP support said that either the card could be damaged due to lightning strike or it could be due to damaged cable running from port box to the PC (RJ-45). I'm wondering, could lightning strike damage a Network card in such a partial manner (just one feature, i.e., Auto-negotiation)? But that person warned, there will be deterioration in ISP speeds when I use 10Base in Full Duplex (for now) compared to Auto-negotiation speeds. Speeds really came down badly, that's understood.
How to you setup ip routing on a Nexus 5500 I want to do vlan routing between an Nexus 5500 and Catalyst 3750. Nothing clever just have the 2 switches talk and vlans route between the two.
Is there an official Cisco-Page with the always-up-to-date recommended NX-OS-Releases for the Nexus 5000, just as there is URL
If there is no such page: What Release can be recommended?
We got new N596 & N2232 this week, and are using L2-LAN only, no L3,no FCoE- or FC-Ports. The command 'vPC orphan-ports suspend' is the newest feature used, so 5.0(3)N2(1) would be the oldest possible release.
Before I install 5.1(3)N1(1a) and then have to do a distruptive downgrade to 5.0(3)N2(2b), I'd like to be assured that the new one is already recommended as mature enough.
How many VMs can a pair of 5548s support? Remember, for each VM, I will have an ARP entry in the 5500 ARP Table (assume 5500 is the L3 default gateway).
IOS we used for limiting access for a group we used configuration of snmp-server views like following
snmp-server group backupgroup v3 priv read backupview write backupview access 20 snmp-server view backupview ccCopyTable included could not find out how to achive this config in NX-OS on Nexus5500
Are there any dependencies on VTP on the Nexus platforms like the 5500 or 7000? In IOS P V LAN required VTP Transparent mode however I cannot find any reference to this for the Nexus platform. Are there any other features that would require the use of VTP? By default VTP is turned off on nexus and has to be enabled with the feature command so is there any benefit to running VTP in transparent mode vs off?
There is very little and quite diverse Information regarding the if, where and how of a Nexus 5000 or 5500 series Switch and support for IEEE 802.1AE Link Layer Encryption (also called MACsec).
For example: the official FAQ denies that the Nexus 5500-series supports 802.1AE at all, while the data sheet says that only "downlink ports" are supported (host access).
On the Nexus 7000 platform the 802.1AE link layer encryption is part of TrustSec (feature cts) and much better documented.
The Question is: If and under which circumstances (configuration, L3 modules, license, NX/OS version) does a Nexus 5k or 5500 series Switch support 802.1AE on 1G or 10G interfaces that are directly connected to a Nexus 7000 (with the necessary cts feature licensed/configured)?
I am experiencing inconsistent echo-replay from devices connected via VPC to Nexus 5500s while pinging from the Nexus exec prompt.
In some cases I receive normal response when pinging from one Nexus, but no response when pinging from the other switch. In other instance I receive normal response to one Nexus, and duplicate replays to the other. It looks like a VPC related bug. NXOS is 5.1.3.N2.1
5501# ping 10.12.12.232 PING 10.12.12.232 (10.12.12.232): 56 data bytes 64 bytes from 10.12.12.232: icmp_seq=0 ttl=253 time=8.585 ms 64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=9.227 ms (DUP!) 64 bytes from 10.12.12.232: icmp_seq=1 ttl=253 time=1.011 ms 64 bytes from 10.12.12.232: icmp_seq=2 ttl=253 time=8.097 ms 64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=9.429 ms (DUP!) 64 bytes from 10.12.12.232: icmp_seq=3 ttl=253 time=18.195 ms 64 bytes from 10.12.12.232: icmp_seq=4 ttl=253 time=8.807 ms(code)
I have a Nexus 5500 which is the core of our network and we have access layer switches uplinked to it. I know by default the qos markings will be trusted.
1. On a trunk uplink from an access layer switch to the Nexus, I have "mls qos trust dscp". Will the DSCP marking be preserved when it reaches the Nexus?
2. How do I do prioritization of voice traffic on an uplink on Nexus based on DSCP EF?
We have a switch that, when configuring auto qos on and edge port facing video equipment, the upstream port channel drops. I was wondering if no auto qos would have to be configured on the member ports of the port channel prior to enabling auto qos on any other ports.
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 are having two sites seperated by half a mile and we are using dedicated 100 Meg link at the moment for intranet traffic, and now we got new 1 gig link and I am working to set it up, Service Provider came on site installed two circuits on both sites and fiber connectivity is tested succesfully betweeen sites, now I need to connect the circuits to our network and make the 1 gig link active to make traffic flow between sites and as well bring 100 meg as standby.
So to brief the issue:
Connectivity at the moment SiteA: Switch1(3560)------100Meg--------.SiteB: Switch 2(3560)
I Want to configure SiteA: Switch 3(4507)------1gig (Active)--------.SiteB: Switch 4(3560) SiteA: Switch1(3560)------100Meg(Standby)--------.SiteB: Switch 2(3560)
simple as connecting a fiber or ethernet link from external circuit on both sites to respective switches on their interfaces and configuring hsrp to enable redundancy. A
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 configured a SVI in my 4500 ( Sup 7-E 10GE,,,,,,and,,,,,cat4500e-universalk9.SPA.03.02.00.SG.150-2.SG.bin) switch and it is showing Down Down, because there were no active switch port in the vlan, I added one switch port to this vlan but this port also in the down state, so i added the SWITCH PORT AUTO STATE EXCLUDE command under this port, even after this also the SVI never came up, So i added one systen to the port so both the switch port and the SVI came up...So why SWITCH PORT AUTO STATE EXCLUDE command have no effect in this model of the switch..
I have a 4510R-E chassis with SUP7-E running IOS XE version 3.01.01.SG. I am unable to create a port-channel and apply auto-qos for VOIP.If I configure auto-qos on the physical interfaces, I get this message when I try adding them to the port channel:
"The attached policymap is not suitable for member either due to non-queuing actions or due to type of classmap filters."
Auto-qos is not an available command in the port-channel interface configuration, but if I try adding the service policies that were created by auto-qos to the port channel manually, it lets me apply the input policy but on the output policy I get this message:
"A service-policy with queuing actions can be attached in output direction only on physical ports."
With the input policy applied to the port-channel interface, I tried addign the output policy to the physical ports and I got this message:
"A service-policy with non-queuing actions should be attached to the port-channel associated with this physical port."
Is there a way to get the auot-qos policies applied to the port-channel properly?
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?