10Gig Copper SFP for Nexus F Series module (N7K-F248XP-25E)

Does Cisco have 10Gig Copper SFP which can be supported on Nexus platform in the F Series module (N7K-F248XP-25E)

Leo,
Thank you for the answer, you mentioned 10Gig Copper module in your reply (Part# N7K-F248XT-25E) but I already have Fiber Module (Part# N7K-F248XP-25E), I just need 2 10Gig copper ports for my storage and cant afford to buy a whole new Copper module. My question was if there is any 10Gig Copper SFP supported on F Series Fiber Module (Part# N7K-F248XP-25E), (not a twinax/DAC cable since my distance is longer and Twinax wont work)

Similar Messages

How to do routing on N7K-F248XP-25E (Nexus 7010) ?

Hi all,
Please educate me the following scenario : I have Nexus 7010 with 2 L3 modules, N7K-M132XP-12L and N7K-M148GT-11L. Now to increase more ports for end devices, I add in the module N7K-F248XP-25E and believe it's for Layer 2 switching only. Is there a way to do routing on these L2 modules without having to go to the L3 modules ? Thanks for all help.

Is there a way to do routing on these L2 modules without having to go to the L3 modules ?
No. If you have an M1/M2 card and routing is enabled, the F2E card will "step down" and do Layer 2 work. All Layer 3 work will be done by the M1/M2 card.

Nexus 7009 does not show the N7K-F248XP-25 modules ethernet ports n sh run

Hi everyone,
I have a question...
I going to install two Nexus 7009 with three N7K-F248XP-25 modules on each one, I am planning to create 3 VDC, but at the initial configuration the system does not show the Ethernet ports of these modules, even with the show inventory and show module I can see that the modules are recognized and its status is OK. There is something that I have to do before start to configure these modules...? enable some feature or license in order to see the ports with show running CLI...?

You can enable F1, F2, M1, M1XL and M2XL Series modules. There are no restrictions on the type of mix allowed for the system module-type command. The system module-type command allows a mix of F1, F2, M1, M1XL, and M2XL Series modules in the VDC.
Note The limit-resource module-type command controls the restrictions on the module-types that can be mixed in the VDC.
Note Use the system module-type f2 command to allow F2E Series modules into a VDC. The ports from F2 and F2E Series modules can be allocated like any other ports.
Note The modules that you do not enable must not be powered on after you configure this feature and enter yes. An error message will force you to manually disable these modules before proceeding. This prevents major disruption and service issues within a VDC.
The no form of this command resets the configuration mode to allow all modules.
hope this helps

Nexus 7K F2 modules Multicast support

I have some questions related to F2 multicast support:
Cisco multicast configuration guide says that “F2 modules do not support any form of IPv4 or IPv6 tunnels” what dose it means? Are they referring to MDF and GRE tunnels?
I know PIM-BiDir is not supported, so what is the support multicast protocols?
What is max number of (*,G) and (S,G) entries the line card can allow?
Dose both ingress and egress replication supported?
Can I enable multicast on VRF-lite on F2 module? Especially is the SVI VRF is associated to vPC
Could you please list all multicast limitations on F2 module?
Can anyone provides a configuration template for SVI VRF is associated to vPC with multicast enabled on F2 cards?
Fady Boules

Hi,
Please refer to the below for vPC peer link on the mixed module:
vPC Peer Link and I/O Modules Support In Cisco NX-OS Release 6.2
Beginning with Cisco NX-OS Release 6.2(2), mixing I/O modules on the same side of a port channel is supported when there is an F2 Series module and an F2e Series module, or when there is an F2e Series module and an M Series Module. You can configure F2E VDCs. The VDC type for two vPC peer devices must match when the F2 Series module and the F2e Series module are used in the same VDC or system. For an F2 Series module and an F2e Series module in the same topology, the features related to the F2 Series module will only apply. After ISSU to Cisco NX-OS Release 6.2(2), F2 VDCs will automatically change to F2 F2E VDCs, regardless of the existence of an F2e Series module.
Table displays the I/O modules that are supported on both sides of a vPC peer link in Cisco NX-OS Release 6.2.
vPC Primary
vPC Secondary
M Series I/O module
M Series I/O module
F2 I/O module
F2 I/O module
F2 I/O module
F2e I/O module
F2e I/O module
F2e I/O module
F2e I/O module
F2 I/O module
vPC Peer Link and I/O Modules Support In Cisco NX-OS Release 6.1 and Earlier Releases
In Cisco NX-OS Release 6.1 and earlier releases, only identical I/O modules on either side of a vPC peer link are supported. Using different I/O modules on either side of a vPC peer link is not supported. Mixing I/O modules on the same side of a port channel is also not supported.
Table 7-2 I/O Module Combinations Supported on Both Sides of a vPC Peer Link, Cisco NX-OS Release 6.1 and Earlier Releases.
vPC Primary
vPC Secondary
F1 I/O module
F1 I/O module
M1 I/O module
M1 I/O module
F2 I/O module
F2 I/O module

Does the F2 linecard (N7k-F248XP-25) on Nexus 7010 support Layer 3?

Hi All,
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?
Regards,
Mayank

Hi, Im know that this is resolved but i have a f2e Card
Model:                 N7K-F248XP-25E
Type (SFP capable):    1000base-SX
and i can not configure an interface as l3
NX7K-1-VDC-3T-S1-L3FP(config)# interface ethernet 7/2
NX7K-1-VDC-3T-S1-L3FP(config-if)# no switchport
ERROR: Ethernet7/2: requested config change not allowed
whats the problem??
Software
BIOS:      version 2.12.0
kickstart: version 6.2(2)
system:    version 6.2(2)
BIOS compile time:       05/29/2013
kickstart image file is: bootflash:///n7000-s2-kickstart-npe.6.2.2.bin
kickstart compile time: 7/9/2013 20:00:00 [08/22/2013 04:51:27]
system image file is:    bootflash:///n7000-s2-dk9.6.2.2.bin
system compile time:     7/9/2013 20:00:00 [08/22/2013 08:07:03]
Hardware
cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor Module-2")
Intel(R) Xeon(R) CPU         with 12224956 kB of memory.

Using SNMP to monitor Nexus 7000 Series Supervisor Module

Hello,
I got a Nexus 7000 supervisor module recently, I met a SNMP problem for this module
I would like to know which specific OIDs to use to monitor the following using SNMP on a Nexus 7000 supervisor module:
- Port status
- CPU total utilization
- Power Supply status
- Chassis Fan status
etc.
The Nexus is quite different from other Cisco devices - any help will be appreciated!

hope help, and
port status OID is ifOperStatus
CPU total utilization OID is 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifDescr.83886080
.1.3.6.1.2.1.2.2.1.2.83886080 = STRING: mgmt0
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifOperStatus.83886080
.1.3.6.1.2.1.2.2.1.8.83886080 = INTEGER: up(1)
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
.1.3.6.1.4.1.9.9.109.1.1.1.1.6.1 = Gauge32: 21
[root@NET-MONITOR-1 ~]#

10Gig SFP for 7 Meters

Not sure if you take other vendors and then “ciscolize” it (ie HP or IBM to MCS Callmanager) but do anyone know if Cisco also ciscolize the SFP cables?
I see 7meter cables available below via other vendors. All the vendors (including Cisco) uses the same Madison 24AWG cable. However, with the transceivers themselves, I couldn’t tell if they all come same vendor or not.
http://www.tmcscsi.com/SFP+_cables.shtml
Anyways, does anyone know why is the 7M available in other vendors but not via Cisco?
Also, is the transceiver really Cisco or some other vendor

To answer this question:
"... does anyone know why is the 7M available in other vendors but not via Cisco?"
As of right now Cisco is the only vendor supporting FCoE on SFP+ copper cables, and Cisco will not certify the 7m passive copper cable for FCoE. With FCoE, there are bit error rate tolerances that the vendor must be mindful of, and the bit error rate on the 7m cable is not meeting Cisco's strict quality tolerances.
Other vendors that are not currently supporting FCoE, such as HP, do not need to worry about this (yet).
So, if you plan to run FCoE traffic on these cables anytime now or in the future, you might want to stick to 5m or less cables regardless of which vendor you choose, because any other vendor will likely come to the same conclusion as Cisco has already done with support for FCoE on 7m passive SFP copper cables.
Cheers,
Brad

ME 3800 output drops with Copper SFP

We have installed a copper SFP (GCL-T) in a access port on an ME-3800 running 12.2(52r)EY2. The port connects to an ONS-CE-100 copper line card on an FE Port. Both ports are set to auto-negotiate. We see output drops on the interface. We tried hard setting the speed on both sides, but the drops persisted. We tried hard setting the duplex to full, but that made things worse. On ports where we use the optical SFPs we do not see these issues.
Has anybody else run into this issue? Does the ME 3800 support auto-negotiation with the copper SFPs? Any thoughts on this would be appreciated.

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
I'm not familiar with the ME series, but if you can "tune" interface egress buffer/queue sizes, increasing resources for bursts can often mitigate and/or eliminate egress drops. Of course, this also can increase latency.

SAN-OS 3.3.1a Copper SFP Support.

hi guys,
beginning with SAN-OS Rel. 3.3.1a, are Copper SFP Supported for the MSM-18/4 and 9222i. My question, are Copper SFP Supported into the MDS 9000 4 Port IP Storage Service Module ? If yes, which exactely Cisco Part Number of SFP are Supported ?
Thanks.

howdy,
They are supported...
DS-SFP-GE-T
I am using 16x of these in some IPS-8's
Cheers

10Gb SFP for UTP?

I need to build a new 3850 switch which requires some server to be connected to a few 10Gb ports which i need to buy the 3580-nm-4-10Gb module for the first time. Was tying to build up a BOM and finding the correct SFP to buy together with the module from this site
http://www.cisco.com/c/en/us/products/collateral/interfaces-modules/transceiver-modules/data_sheet_c78-455693.html
I didn't see any 10Gb SFP for copper, something similar to the GLC-T sfp for the 1Gb slot, the most relevant one would be the Twinax copper cable which comes with both ends of the sfp with the cable attached together. Now is this something that we buy to inter connect to server's 10Gb port?
Not too sure about the 10Gb SFP to connect to a server but if you guys and give me some of the example of the model that people would use that would be great!
Cheers,
Ben

Hi Benny,
That's interesting. I thinkg the Twinax active copper cable (with SFPs at both ends) is the way to go. But it depends on the interface on the other end - the server. The 10G server interfaces I've seen are normally having an SFP port, but... your have to check what the situation is at your end.
In this case though, I guess the only factor to go for the copper cable would be the price. If you have SFPs at both ends of the connection, you can go optical. It's more robust and reliable, and it's cheeper these days.
Regards,
Boyan

Why do I keep getting error -65581 when trying to use a cRIO 9024 and c series modules

I am simply trying to send out a digital high on DIO0 of a 9401 c series module and I get the following error every time.
Error -65581 occurred at Shared Variable in Send True Value Out.vi
Possible reason(s):
CompactRIO: (Hex 0xFFFEFFD3) The FPGA personality currently running on the CompactRIO chassis does not support the RIO Scan Interface in this slot.
This error or warning occurred while writing the following Shared Variable:
\\NRL-CMG-cRIO\NI 9401-1\DIO0
\\170.126.209.52\NI 9401-1\DIO0
Any help would be greatly appreciated.
Nate
Solved!
Go to Solution.

NMAYO,
In your project view can you right click on the chassis in the cRIO and make sure that it is set for Scan Mode and not FPGA mode? Also, In the measurement and automation explorer you can check the cRIO and verify that it has Scan Engine Support installed on it. The tutorial below shows how to reformat a cRIO and install software on it, the later steps on software will allow you to check your cRIO.
Reformatting a CompactRIO Real-Time Embedded Controller
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco® NX-OS.
The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response.
Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Gustavo
Please see my responses to your questions:
Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
Now for Data Plane we have two types of traffic – Unicast and Multicast.
The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
Similarity: For both products, loop avoidance is possible due to VSL bit
The VSL bit is set in the DBUS header internal to the Nexus.
It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
This mechanism is used for loop prevention within the chassis.
The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
Differences: In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
For more details please see below presentation:
https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
DCI Scenario: If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
Let us know if you have further questions.
Thanks,
Vishal

Which c-series modules are compatible with Scan Mode?

OK, so I just wasted 4 hours.
I started a new Project with a need to use a 9220 analogue input card on a cRIO 9030, but immediately became stuck when I was unable to add the module using the right click Add New C-Series Module wizard to the 9030 chassis.
My first (and only) assumption was that this was a new card and I needed the latest Device Drivers. So I installed those.
When that failed I upgraded my LV2014 to LV2014 SP1, and also upgraded the Real-Time and FPGA modules too.
4 hours later, when that failed, I realised that maybe this isn't a card compatible with Scan Mode so began searching ni.com for information. I've searched a whole raft of terms and I just cannot find information on which modules are supported by Scan Mode (which is presumably nearly all of them). I know it exists somewhere because I one referred to it when I had an RS485 module that was only compatible in FPGA mode, about four years ago.
So:
1. Is there an easy way to determine if a C-Series module is compatible with Scan Mode? I still don't know!
2. Can we please have Scan Mode compatibility shown in the Add C-Seris Module Wizard. When attempting to add a module to a cRIO chassis, the wizard can hint to us that a particular module is not compatible. By not showing the 9220 in the drop down list I was led to believe the module was not a known device (and hence I attempted to upgrade my drivers). It would be better if the module was listed but disabled and not selectable, with some informational text to explain why. It's a fair assumption that a module will be compatible, so we don't expect it to not be listed when we attempt to add it. In fact, the possibility that some modules aren't compatible can evade your consciousness temporarily and make you do stupid things (like upgrade your installation!).
3. Can we please have Scan Mode compatability information put on each module's description page. That would have made this whole process much quicker.
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Well, I definitely agree that finding info about RSI module support is not as easy as it should be. Since I know where to look, I will refer you to this document, which I found linked from this page.
That's the best document I know of on the topic.
Cheers!
TJ G

Can I create a task that includes 2 C series modules?

I am trying to create a single task that includes 2 NI-9425 C series modules but when I wire the physical channel constant "Mod3/port0, Mod4/port0" into the DAQmx Create Virtual Channel.vi I receive error -200086 which states physical channel range syntax in the input string is invalid because multiple devices were listed in the string. It is my understanding from LabView help that multidevice tasks are allowed. Also according to this KB article http://digital.ni.com/public.nsf/allkb/CF85114C6025C84C862571C000722DDA multi-device tasks are supported for S Series devices, C Series, and DSA devices, and according to this KB article http://digital.ni.com/public.nsf/websearch/78E44565FD87E7D686257108007F94F8?OpenDocument I have formatted my physical channel constant correctly.
Can someone please explain why I am getting this error when all indications are that this should be a simple thing to do?
My C series modules are in slots 3 and 4 in a cDAQ-9188 chassis, I am currently running LabView 8.5.1, with Windows XP
Thank you,
Eric
Solved!
Go to Solution.

Hi Eric,
I'm afraid that you can't configure hardware timing with the NI 9425 in CompactDAQ. The NI 9425 data sheet explains: "The NI 9425 is a static digital module, so you can use it to perform software-timed or static operations only when installed in an NI CompactDAQ chassis."
For AI, AO, and counters, daisy chaining multiple calls to DAQmx Create Channel is equivalent to specifying a list of physical channels, but for DIO it's different. A single DIO virtual channel can contain multiple physical channels (lines). It would be completely reasonable to assume that specifying a list of lines with "one channel for all lines" would cause DAQmx to put all of the lines in a single virtual channel, but due to how it's implemented in the DAQmx framework, this is not possible when the lines are on multiple devices. It would also be reasonable to assume that if DAQmx couldn't put all of the lines in a single virtual channel, then it would create one virtual channel per device, but that's also not how it's implemented--it returns the error that you received.
Instead, here are two approaches to putting all 64 lines in one task. Either one should work.
Approach A: Create a single task, containing two virtual channels (MyChan0 and MyChan1). MyChan0 contains cDAQ1Mod3/port0/line0:31 and MyChan1 contains cDAQ1Mod4/port0/line0:31. The Digital 2D Bool NChan 1Samp read VI returns a 2x32 array of Booleans. To flatten this into a 1D 64-element array, you need to use Reshape Array or some other method.
The DAQmx Task >> Channels property is there to show that there are two virtual channels named MyChan0 and MyChan1. Also, I used a for-loop to show that you don't have to hardcode multiple calls to DAQmx Create Channel. The "one channel for all lines" constant is redundant because that is the default.
Approach B: Create a single task, containing 64 virtual channels (MyChan0 through MyChan63). This uses the "one channel for each line" constant, which is not the default. MyChan0 contains cDAQ1Mod3/port0/line0, MyChan1 contains cDAQ1Mod3/port0/line1, etc. The Digital 1D Bool NChan 1Samp read VI returns a 1D 64-element array of Booleans. If you used the Digital 2D Bool NChan 1Samp VI instead, you would get a 64x1 array because there are 64 virtual channels containing 1 line each.
Brad
Brad Keryan
NI R&D

CompactRIO, CVI, and C series modules

Being used to LabVIEW, not sure how to interface to the C-series modules on my cRIO using CVI. The project I'm on needs to use CVI, and I have no idea how to interface to my cards -- e.g. writing to my DIO card or reading from an AI channel, etc.
In LV, it was easy and each I/O channel was simply a variable I could drop over to my block diagram and either read to write from/to. Any pointers in the right direction for this? I have the CVI real-time module and I know C, but never messed with CVI much.. I've searched and searched, but maybe I'm not searching right or something :/
How can I read from my NI-9221 card on, say, channel 0 and get a double back representing the voltage that's on that line?? That's the kind of stuff I'm looking for... in CVI?
Thanks.

Hi there,
LabWindows/CVi actually cannot be used to program cRIO. CVI uses Pharlap, while cRIO uses VxWorks. See CVI + RT FAQ and here's another more in-depth document regarding CVI in Real-Time.
Best,
Ryan C.
Applications Engineer
National Instruments

10Gig Copper SFP for Nexus F Series module (N7K-F248XP-25E)

Similar Messages

Maybe you are looking for