Netgear XSM4324FS M4300 FAQs - Page 3

•Cisco 40GBASE-LR4 QSFP 40G transceiver module for Single Mode Fiber, 4 CWDM lanes in 1310nm window Muxed inside module, Duplex LC connector, 10km, 40G Ethernet rate only (QSFP-40G-LR4-S) •Cisco 40GBASE-CSR4 QSFP+ transceiver module for MMF, 4-lanes, 850-nm wavelength, 12-fiber MPO/MTP connector, 300 m reach with OM3 fiber (QSFP-40G-CSR4) •Cisco 40G QSFP Bi-Directional transceiver module, Duplex Multi-mode Fiber, LC Duplex connector, 100m reach with OM3 fiber (QSFP-40G-SR-BD) •Cisco 40GBASE-CR4 QSFP+ direct-attach copper cable, 1 meter passive (QSFP-H40G-CU1M) •Cisco 40GBASE-CR4 QSFP+ direct-attach copper cable, 3 meter passive (QSFP-H40G-CU3M) •Cisco 40GBASE-CR4 QSFP+ direct-attach copper cable, 5 meter passive (QSFP-H40G-CU5M) •Cisco 40GBASE-CR4 QSFP+ direct-attach copper cable, 7 meter active (QSFP-H40G-ACU7M) Cisco is a registered trademark of Cisco Technology, Inc. HPE® Modules: • HPE X140 40G QSFP+ MPO SR4 Transceiver (JG325A) • HPE X140 40G QSFP+ LC LR4 SM 10km 1310nm Transceiver (JG661A) •HPE X140 40G QSFP+ LC BiDi 100m MM Transceiver (JL251A) •HPE X240 40G QSFP+ to QSFP+ 1m Direct Attach Copper Cable (JG326A) •HPE X240 40G QSFP+ to QSFP+ 3m Direct Attach Copper Cable (JG327A) •HPE X240 40G QSFP+ to QSFP+ 5m Direct Attach Copper Cable (JG328A) HPE is registered trademark of Hewlett-Packard Enterprise Company. 10. The M4300 offers PoE+, spine and leaf resiliency and 10G stacking in a virtual chassis footprint. What are the primary reasons to select the M4300 over the M6100 Chassis? M4300 is cost effective solution for PoE+ edge deployment, midsize server/storage top-of-rack and SMB dependable core. While M4300 nonstop forwarding and master hitless failover offers unique high availability for stack architectures, the M6100 chassis provides the following, unmatched benefits: • High speed fabric with 80G half-duplex 160G full duplex access to the backplane for each M6100 blade (1G blades line-rate to the fabric and 10G blades 3:1 oversubscription) which is must faster than comparable M4300 stack topologies. This would correspond to eight 10G ports used for any switch to switch interconnect in M4300 stack. • Centralized power management system with N+1 power redundancy at the chassis level (one redundant PSU for the entire chassis, when M4300 switches require one redundant PSU per switch) • Modular and redundant architecture with everlasting passive backplane and highly reliable fabric-based design • Modular PoE+ (30 watts per port) and UPOE (60 watts per ports) allow to turn PoE on, with easy upgrade, easy downgrade (M4300 switches are fixed PoE+ or non-PoE switches) • Advanced software features with BGP and DCB (including DCBX 802.1Qaz; Priority Flow Control PFC; Enhanced Transmission Selection ETS and FCoE FIP Snooping) 11. What are ring topologies and associated benefits? Common for intermediate distribution frames (IDF) in K-12, horizontal or vertical ring stacking topologies, or dual ring topologies greatly simplify deployments at the edge and bring network resiliency with distributed uplinks in aggregation to the core. While reducing the number of logical units to manage, stacking also brings network resiliency with distributed uplinks in aggregation to the core: •Horizontal or vertical ring topologies makes sense with Gigabit models when inter-switch links oversubscription requirements aren't critical •Up to (8) M4300 switches can be aggregated using a virtual backplane and a single console or web management interface •M4300 PoE and non-PoE versions are highly cost-effective at the edge, with built-in 10GBASE-T and SFP+ fiber uplinks and no hidden costs •While any 10 Gigabit port can be used for stacking, SFP+ ports can be reserved for fiber uplinks to the core •10 Gigabit copper ports can be used for local stacking ring topology and unused 10 Gigabit fiber ports can connect remote switches to the stack •Ideally the two top switches connecting back to the core should have priority settings forcing their roles as "management unit" and "backup unit" respectively •This way, management unit hitless failover and nonstop forwarding ensures no single point of failure: - Nonstop Forwarding (NSF) enables the stack to secure forwarding end-user traffic on all other switches when the management unit fails - Instant failover from management unit to backup management unit is hitless for the rest of the stack - Since both the management unit and the backup unit connect to the core using distributed link aggregation (LACP), there is no possible service interruption while the backup management unit takes over - All other switches in the stack keep forwarding L2 and L3 traffic in and out, while backup unit guarantees connectivity to the core •Other lower end solutions are causing service interruptions across the entire stack without NSF and hitless failover