The Cisco Nexus 7000 F3-Series 48-Port 1 and 10 Gigabit Ethernet Module is a high-density modular line card for Cisco Nexus 7000 Series chassis. It provides 48 SFP/SFP+ interfaces, supports both 1 Gigabit Ethernet and 10 Gigabit Ethernet connectivity, and delivers wire-rate Layer 2 and Layer 3 forwarding for IPv4 and IPv6 traffic. The module is intended for data center access, aggregation, core, unified fabric, virtualization, cloud, and data center interconnect deployments that require dense fiber connectivity with low forwarding latency.
Product role and architecture
The module uses the Cisco Nexus F3-Series switch-on-a-chip ASIC. The ASIC combines forwarding, queuing, and packet-processing functions in a design intended to provide high performance while reducing module power and cooling requirements compared with more distributed architectures.
Each module provides:
- 48 SFP and SFP+ ports
- 1 Gigabit Ethernet and 10 Gigabit Ethernet operation
- Up to 720 million packets per second of Layer 2 and Layer 3 forwarding
- Up to 480 Gbps of data throughput
- Four ingress queues and four egress queues per port
- 72 MB of virtual output queue buffer per module
- Jumbo frames up to 9216 bytes
- Hardware forwarding for IPv4 and IPv6
- Support for Layer 2 and Layer 3 data center functions
- Hardware support for VXLAN and LISP
- MACsec support on ports 41 through 48
- Optional FCoE capability through the applicable ordering item
A Cisco Nexus 7000 18-Slot chassis populated with F3-Series modules can deliver up to 11.5 billion packets per second and 15.4 Tbps of switching performance. These figures describe chassis-level capacity under the stated fully populated configuration and should not be interpreted as a guaranteed application throughput for every traffic profile.
The module requires a Cisco Nexus 7000 supervisor module identified as N7K-SUP2 or N7K-SUP2E. Compatibility also depends on the installed NX-OS software release and the specific optic or copper assembly selected.
Chassis compatibility and density planning
The module is supported in Cisco Nexus 7000 4-, 9-, 10-, and 18-slot chassis. The maximum native 10 Gigabit Ethernet density depends on chassis size:
| Chassis | Maximum wire-rate 10 Gigabit Ethernet density | Presales interpretation |
|---|---|---|
| Cisco Nexus 7000 18-Slot Switch | 768 ports | Highest-density deployment and large aggregation or core environments |
| Cisco Nexus 7000 10-Slot Switch | 384 ports | Medium-to-large modular data center deployments |
| Cisco Nexus 7000 9-Slot Switch | 336 ports | Dense deployments where a smaller chassis footprint is required |
| Cisco Nexus 7000 4-Slot Switch | 96 ports | Smaller data center, aggregation, or dedicated service environments |
The module occupies one I/O module slot in a Cisco Nexus 7700 platform chassis, as stated in the physical specifications. When preparing a chassis design, the line-card count must be evaluated together with supervisor, fabric, power, cooling, and slot requirements. The 48-port module count alone does not establish the final chassis capacity or redundancy model.
A practical port-density calculation is:
Installed module count x 48 = physical ports before reserving ports for uplinks, maintenance, redundancy, or growth
For a 10 Gigabit Ethernet-only design, the chassis maximums in the table above should be used rather than assuming that every physical port can be populated without regard to chassis architecture or fabric capacity.
Forwarding, scale, and buffering
The forwarding engine provides 720 mpps for Layer 2 and Layer 3 forwarding of both IPv4 and IPv6 packets. The module supports up to 480 Gbps of data throughput. Forwarding scale includes:
| Resource | Capacity |
|---|---|
| MAC address entries | 64,000 |
| Simultaneous VLANs per VDC | 4,096 |
| IPv4 entries | 64,000 |
| IPv6 entries | 32,000 |
| Adjacency entries | 64,000 |
| ACL entries | 16,000 |
| Virtual output queue buffer | 72 MB per module |
| Ingress queues | 4 per port |
| Egress queues | 4 per port |
| Maximum jumbo frame size | 9,216 bytes |
These values are hardware scale limits presented for the module. Actual usable scale can be affected by NX-OS release, feature combinations, table allocation, VDC configuration, and the traffic features enabled on the system. Presales designs should reserve capacity for control-plane, routing, security, and virtualization requirements instead of sizing exactly to the published maximum.
The 72 MB VOQ buffer is relevant to designs with oversubscription, bursty east-west traffic, storage traffic, and multi-tenant aggregation. It does not eliminate the need to validate congestion behavior, queue configuration, traffic-class design, and fabric-level contention.
Network and virtualization capabilities
The module supports the core Layer 2 and Layer 3 functions required for data center switching. It is also designed for environments using network virtualization, fabric overlays, and data center interconnection.
Supported technologies include:
- Cisco FabricPath
- VXLAN with wire-rate hardware support
- Locator/ID Separation Protocol
- Overlay Transport Virtualization
- Multiprotocol Label Switching
- Virtual Private LAN Service
- Cisco Nexus 2000 Series Fabric Extenders
- Fibre Channel over Ethernet
- Virtual Device Contexts
- Cisco TrustSec
- MACsec on ports 41 through 48
FabricPath is applicable where a resilient and scalable Layer 2 fabric is required while maintaining connectivity with existing spanning-tree-based deployments. VXLAN supports Layer 2 overlay extension across Layer 3 infrastructure and can support virtual machine mobility between Layer 2 domains when the surrounding architecture is designed for that purpose.
OTV, MPLS, and VPLS provide options for data center interconnection and service-provider-style transport designs. These capabilities should be mapped to the required control-plane, encapsulation, transport, and operational model before selecting the module for a production architecture.
FEX support allows Nexus 2000 Series fabric extenders to be connected through the module. This can reduce the number of independently managed switch points, but the resulting design remains dependent on the parent Nexus 7000 chassis, supervisor, fabric, and software architecture.
VDCs allow one physical switch to be provisioned as multiple logical devices. Each logical device is configured and managed as if it were a separate physical device. VDC planning must account for the published limit of 4,096 simultaneous VLANs per VDC and for the separate resource requirements of routing, ACLs, adjacencies, and management.
Security and control-plane functions
The module provides several hardware-assisted security functions:
- Configurable Control-Plane Policing
- ACL counters and logging
- Layer 2 through Layer 4 ACL processing
- IPv4 and IPv6 ACL support
- Cisco TrustSec security group tag processing
- IEEE 802.1AE MACsec on ports 41 through 48
CoPP is used to protect the supervisor CPU from excessive or hostile control-plane traffic. Presales designs should include a defined control-plane policy rather than treating CoPP as an automatic substitute for routing protocol protection, management-plane controls, or infrastructure ACLs.
ACL counters and logging improve operational visibility. The published ACL scale is 16,000 entries, but the effective limit depends on how entries are consumed by IPv4, IPv6, Layer 2, Layer 3, Layer 4, VDC, and feature-specific policies.
MACsec is limited to ports 41 through 48 according to the supplied specifications. This restriction must be checked during port assignment. If encrypted links are required, the design should reserve these ports for the applicable connections and confirm transceiver and software compatibility.
Optics and cabling selection
The module requires separate SFP or SFP+ modules. Optic selection must match the port speed, fiber type, wavelength, distance, connector plant, and feature requirements. The following matrix lists the supported interface options and stated distances.
10 Gigabit Ethernet SFP+ options
| Part number | Medium and wavelength | Published distance | Best For |
|---|---|---|---|
| SFP-10G-SR | 850 nm MMF | 26 m to 400 m, depending on fiber | Short-reach intra-rack and data center links |
| SFP-10G-SR-S | 850 nm MMF | 26 m to 400 m, depending on fiber | Short-reach multimode deployments |
| SFP-10G-LRM | 1310 nm MMF or SMF | 100 m to 300 m | Multimode links requiring longer reach than SR |
| SFP-10G-LR | 1310 nm SMF | 10 km | Standard single-mode campus or data center interconnect |
| SFP-10G-LR-S | 1310 nm SMF | 10 km | Single-mode links using the -S variant |
| FET-10G | 850 nm MMF | 25 m or 100 m | Supported short-reach fabric extender connectivity |
| SFP-10G-ER | 1550 nm SMF | 40 km | Long-distance single-mode links |
| SFP-10G-ER-S | 1550 nm SMF | 40 km | Long-distance links using the -S variant |
| SFP-10G-ZR | 1550 nm SMF | 80 km | Extended-reach single-mode interconnection |
| SFP-10G-ZR-S | 1550 nm SMF | 80 km | Extended-reach links using the -S variant |
| DWDM-SFP10G-xx.xx= | DWDM SMF | Wavelength-specific | Dense wavelength-division multiplexing designs |
| SFP-H10GB-CUxM | Passive twinax | 1 m, 3 m, or 5 m | Short equipment-rack connections |
| SFP-H10GB-ACUxM | Active twinax | 7 m or 10 m | Longer copper rack connections |
| SFP-10G-AOCxM | Active optical cable | 1 m, 2 m, 3 m, 5 m, 7 m, or 10 m | Preterminated short optical rack links |
For SFP-10G-SR, the stated distances range from 26 meters on FDDI-grade multimode fiber to 400 meters on OM4. SFP-10G-LRM supports specific multimode distances and 300 meters over G.652 single-mode fiber. Multimode use with LRM is limited to ports 41 through 48, while 300-meter single-mode support applies to all ports.
The -ER option requires a 5 dB 1550 nm fixed-loss attenuator for links shorter than 20 km. The -ZR option requires attenuation based on link length: 15 dB below 5 km, 10 dB from 5 km to 25 km, and 5 dB from 25 km to 45 km. Links longer than 30 km using ER are considered engineered links.
Gigabit Ethernet SFP options
| Part number | Medium and wavelength | Published distance | Best For |
|---|---|---|---|
| GLC-SX-MMD | 850 nm MMF | 220 m to 1,000 m | Short and medium Gigabit Ethernet fiber links |
| GLC-LH-SMD | 1310 nm MMF or SMF | 550 m over MMF or 10 km over SMF | Mixed multimode and single-mode connectivity |
| GLC-EX-SMD | 1310 nm SMF | 40 km | Extended Gigabit Ethernet single-mode links |
| GLC-ZX-SMD | 1550 nm SMF | 70 km to 100 km | Long-distance engineered links |
| GLC-TE | Category 5 copper | 100 m | Short Gigabit Ethernet copper connections |
| GLC-BX-U | 1310 nm SMF | 10 km | Bidirectional single-mode links |
| GLC-BX-D | 1490 nm SMF | 10 km | Paired bidirectional single-mode links |
| CWDM-SFP-1xxx= | CWDM SMF | Wavelength-specific | Coarse wavelength-division multiplexing |
| DWDM-SFP-xxxx= | DWDM SMF | Wavelength-specific | Dense wavelength-division multiplexing |
Mode-conditioning patches are required for certain traditional multimode fiber types, including FDDI-grade, OM1, and OM2, where identified by the optic requirements. Fiber attenuation, splice count, connector loss, dispersion, and plant quality must be validated for long-reach optics.
Ordering matrix
| Description | Part number | Best For |
|---|---|---|
| Nexus 7000 F3-Series 48-Port Fiber 1 and 10G Ethernet Module | N7K-F348XP-25 | Primary line card with 48 SFP/SFP+ ports |
| Nexus 7000 F3-Series 48-Port Fiber 1 and 10G Ethernet Module, spare | N7K-F348XP-25= | Spare inventory and replacement planning |
| FCoE for Nexus 7000 F3-Series 48-port 10 Gigabit Ethernet SFP+ module | N7K-FCOE-F348XP | Environments consolidating Ethernet and Fibre Channel traffic |
| FCoE for Nexus 7000 F3-Series module, spare | N7K-FCOE-F348XP= | Spare FCoE licensing or entitlement item |
The base module requires separately selected SFP or SFP+ modules. Optics, twinax assemblies, and active optical cables are not included in the line-card part number.
Environmental and physical requirements
The module occupies one I/O module slot and has the following physical characteristics:
| Attribute | Specification |
|---|---|
| Height | 1.733 inches, 4.4 cm |
| Width | 15.3 inches, 38.9 cm |
| Depth | 21.9 inches, 55.6 cm |
| Weight | 15 lb, 6.8 kg |
| Operating temperature | 32 to 104 degrees F, 0 to 40 degrees C |
| Operating humidity | 5 to 90 percent, noncondensing |
| Storage temperature | -40 to 158 degrees F, -40 to 70 degrees C |
| Storage humidity | 5 to 95 percent, noncondensing |
The supplied specifications do not publish a module MTBF value, acoustic noise level, module-specific power draw, or module-specific heat dissipation figure. These values must therefore be obtained from the applicable chassis installation and power documentation before completing rack power, thermal, or facilities calculations. The module’s use of the F3-Series SoC is described as reducing power and cooling requirements, but no numerical power or acoustic value is provided.
Listed compliance includes Class A EMC requirements, FCC Part 15, ICES-003, EN55022, CISPR22, CISPR24, EN55024, EN50082-1, EN61000-3-2, EN61000-3-3, EN61000-6-1, EN300 386, and related regional standards. The module also lists NEBS, Verizon, CenturyLink, AT&T, and ETSI environmental requirements, with validation in progress identified for the relevant entries. Safety compliance includes UL/CSA/IEC/EN 60950-1 and AS/NZS 60950.
Software and management prerequisites
The stated software compatibility is Cisco NX-OS Software Release 6.2.12 or later. The datasheet identifies hardware support for multiple functions but directs that the required NX-OS release be confirmed for individual features.
Available programming and management interfaces include:
- XML
- Scriptable CLI
- Cisco Data Center Network Manager web services
- Python
- Tool Command Language interpreter
- Cisco Embedded Event Manager
- Cisco ONE Platform Kit
- OpenFlow
Front-panel indicators provide operational and troubleshooting status:
- Status LED: green for operational, red for faulty, orange during module boot
- Link LED: green for enabled and connected, orange for disabled, off for enabled but not connected
- Link and ID beacon behavior: blinking green and orange with blue ID indication when the port is flagged
- ID LED: blue when identified by an operator, off when not flagged
Warranty and service
The Cisco Nexus 7000 Series switches include a standard Cisco one-year limited hardware warranty.
Available service offerings include Cisco Advanced Services and Cisco SMARTnet Service. Advanced Services uses an architecture-led approach covering data center planning, deployment, optimization, migration, and operational improvement. SMARTnet Service provides access to Cisco network experts and support resources for mission-critical issues. The service description also identifies Smart Call Home capability for proactive diagnostics and real-time alerts on the Nexus 7000 Series switch.
For a production proposal, the hardware warranty should be separated from the selected support contract. The support design should identify response requirements, replacement logistics, software access, escalation procedures, monitoring ownership, and whether proactive alerting is required. Spare line cards and optic reserves should be sized according to the business impact of a failed module, the number of deployed chassis, and the required restoration time.