Misplaced Pages

#959040

32-483: All switches in the Nexus range run the modular NX-OS firmware/operating system on the fabric. NX-OS has some high-availability features compared to the well-known Cisco IOS . This platform is optimized for high-density 10 Gigabit Ethernet . Cisco Nexus OS Software Defined Networking (SDN) allows the same policies that govern Identity and Access Management (IAM) to dictate levels of access to applications and data through

64-532: A 'client' or Virtual Ethernet Module (VEM) a vSwitch which replaces the standard vSwitch. The VEM uses the vDS API , which was developed by VMware and Cisco together VMware announced in May 2017, vDS API support will be removed from vSphere 6.5 Update 2 and later. Therefore Nexus 1000v can no longer be used. VMware KB https://kb.vmware.com/s/article/2149722 https://www.theregister.co.uk/2017/03/31/vmware_to_end_support_for_thirdparty_virtual_switches/ Besides offering

96-412: A Network Analysis Module to be run. The Nexus 2000 series are fabric extenders (FEX): 'top of rack' 1 U high system that can be used in combination with higher end Nexus switches like the 5000 , 6000 or 7000 series: the 2000 series is not a 'stand-alone' switch but needs to be connected to a parent and should be seen as a 'module' or 'remote line card' but then installed in a 19" rack instead of in

128-464: A description of its "system". This is far more detailed and comprehensive than SAS 70's description of "controls". Other data center compliance standards include Health Insurance Portability and Accountability Act (HIPAA) audit and PCI DSS Standards. Colocation facilities generally have generators that start automatically when utility power fails, usually running on diesel fuel . These generators may have varying levels of redundancy, depending on how

160-554: A disagreement between Dell and Cisco, Cisco stopped development of the FEX for the M1000e in 2010 The Nexus B22FEX offer 16 x 10 Gbase-KR internal 10 Gbit/s link to each blade-server interface and up to 8 SFP+ ports for uplink with a Nexus 5010, 5548 or 5596 switch. The maximum distance between the FEX and the mother-switch is 3 kilometer when it is only used for TCP/IP traffic and 300 meter when carrying also FCoE traffic. The model 3064

192-406: A main switch-enclosure. The interconnection between this 'remote line card' and the 5000 or 7000 parent switch uses either proprietary interfaces (CX-1 for copper or the short or long range Cisco Fabric Extender Transceiver (FET) interfaces), or standard interfaces (Cisco SFP+ SR and LR fibre interface modules or SFP+ Twinax cables). In combination with the 5000/6000/7000 mother-switch you can create

224-609: A modified Nexus operating system (Nexus OS ACI). The Nexus 9000 has many models: NX-OS Too Many Requests If you report this error to the Wikimedia System Administrators, please include the details below. Request from 172.68.168.226 via cp1108 cp1108, Varnish XID 217767815 Upstream caches: cp1108 int Error: 429, Too Many Requests at Thu, 28 Nov 2024 07:42:06 GMT Colocation centre A colocation centre (also spelled co-location , or shortened to colo ) or " carrier hotel ",

256-449: A so-called Distributed Modular System. The 2000 series consists of 4 different models. Three models offer 24 or 48 Gbit/s only or Gigabit or Fast Ethernet copper interfaces and up to four 10 Gigabit uplink interfaces on copper or fibre. The Nexus 2232PP offers thirty-two 1/10 Gbit/s Ethernet and Fibre Channel over Ethernet (FCoE) interfaces. The Nexus 2248PQ offers forty-eight 1/10 Gbit/s Ethernet and FCoE interfaces. For

288-427: A totally converged infrastructure not possible with legacy network and system access methods. The Nexus 9000 is the high-end model in the Nexus range of datacenter switches. Other models are: The 1000v is a virtual switch for use in virtual environments including both VMware vSphere and Microsoft Hyper-V It is as such not a physical box but a software application that interacts with the hypervisor so you can virtualize

320-448: A wide range of customers, ranging from large enterprises to small companies. Typically, the customer owns the information technology (IT) equipment and the facility provides power and cooling. Customers retain control over the design and usage of their equipment, but daily management of the data centre and facility are overseen by the multi-tenant colocation provider. Buildings with data centres inside them are often easy to recognize by

352-489: Is a range of 5 models 1U or 2U rack-switches offering 20 to 96 interfaces running on 1 or 10 Gbit/s Ethernet and 10 Gbit/s FCoE interfaces. They can be used with the above-mentioned Nexus 2000 series fabric extender. The 5000-series offer carrier-grade layer2 and layer3 switching as well as FCoE capabilities The Nexus 5000 has 5 models: A two rack-unit high switch with 40 fixed 10 Gbit/s supporting Ethernet, FCoE and DCB and two expansion ports each offering one of

SECTION 10

#1732779725960

384-424: Is a type of data centre where equipment, space, and bandwidth are available for rental to retail customers. Colocation facilities provide space, power, cooling, and physical security for the server , storage , and networking equipment of other firms and also connect them to a variety of telecommunications and network service providers with a minimum of cost and complexity. Many colocation providers sell to

416-503: Is capable of building a route-table with up to 16000 prefixes, 8000 host-entries and 4000 multicast routes and up to 4096 VLANs are supported. On top of that a high number of ingress or egress ACLs can be configured. The 3064 has a single fan tray, two replaceable power-supplies on board and two separate out of band management interfaces. To connect the 3064 to the rest of the network the use of proprietary EtherChannel or Link aggregation using industry-standard LACP or IEEE 802.3ad

448-488: Is currently the only Nexus switch in the 3000-series utilizing merchant silicon. The 1U rack-switch with 1, 10 and 40 Gbit/s Ethernet interfaces is designed for use in colo center . Offers layer 2 and layer 3 capabilities at wire-speed for all 64 interfaces running in 10 Gbit/s. Layer3 routing protocols supported include static routes, RIP v2 , OSPF and BGP-4 . The switch-fabric can switch 2.28 Tbit/s and forward up to 950 million packets per second. The switch

480-727: Is supported with up to 32 port-channels with each up to 16 physical interfaces. The switch holds of 48 SFP+ for 1 Gbit/s or 10 Gbit/s Ethernet interfaces and four QSFP+ each handling 4 x 10 Gbit/s interfaces allowing for 40 Gbit/s over a single fibre-pair The Nexus 4000 series consists of only the model 4001: a blade -switch module for IBM BladeCenter that has all 10 Gbit FCoE interfaces. This blade switch had 14 server-facing downlinks running on 1 Gbit/s or 10 Gbit/s and six uplinks using 10 Gbit/s SFP+ modules. For out-of-band management, three Ethernet interfaces are available: one external 10/100/1000 bit/s copper interface, one internal management interface for

512-561: Is wire-speed at layer2 and 1.28 Tbit/s for layer3 operation. The 2nd model in the Nexus 6000 series is a modular chassis, 4 Rack units high. The basic chassis offers 48 fixed QSFP+ ports at 40 Gbit/s each, each can be split in 4 x 10 Gbit/s SFP+ ports. Besides the 48 QSFP+ ports the chassis can hold up to 4 expansion modules - each offering 12 additional 40 Gbit/s QSFP+ ports - thus in total up to 96 QSFP+ ports or 384 SFP+/10 Gbit/s ports and when aggregating FEX up to 1536 (blade)server ports at 1 or 10 Gbit/s. As with

544-699: The AMM or Advanced Management Module and one in-band interface using the VLAN interface option. And this blade-switch also has a serial console cable for direct access to the CLI At present only switches for the IBM blade systems are available. When the Nexus 4000 series were announced in 2009 it was expected that there would be Nexus 4001 series for IBM and Dell (and not HP) but in February 2010 it became clear that Cisco canceled

576-564: The 6001 layer 2/layer 3 operation is at line-rate and total switching capacity of a chassis is 7,68 Tbit/s. The Nexus 6004-EF switch is a modular device which provides the same features as the 6004 but with the use of expansion modules in all slots of the switch. The base configuration of the 6004-EF must have 2 x 12 port 40GbE expansion modules, delivering 24 ports of 40GbE or 96 ports of 10GbE. Additional capacity can be provided by installing further expansion modules. For layer3 and FCoE operation additional licences are required Cisco released

608-703: The Fabric Extenders (FEX) for different blade-server systems. Both models support either front to back or back to front airflow and they do support Fibre Channel over Ethernet in combination with a 'full' FCoE switch (e.g. Nexus 5500 or Brocade 8000 switch (which is same as Dell PowerConnect 8000e or blade version PCM 8428-k )). The Nexus 6001 is a fixed 1 RU switch with 48 x 10 Gbit/s and 4 x 40 Gbit/s interfaces for uplinks. It can operate as both layer2 and as layer3 switch and in combination with FEX (fabric extenders) you can aggregate up to 1152 ports at 1 Gbit/s or 10 Gbit/s. System speed

640-775: The HP BladeSystem C3000 and C7000 server blade chassis, the Cisco Nexus B22HP fabric extender exists. (October 2011) The Fujitsu PRIMERGY BX400 and BX900 blade server chassis uses the B22F fabric extender. (July 2012) For the Dell M1000e blade server chassis, the Cisco Nexus B22Dell fabric extender was released in January 2013, which is 2.5 years after the initially planned release. Due to

672-592: The NX-OS interface to configure, manage and monitor the virtual switch it also supports LACP link aggregation where the standard virtual switches only support static LAGs The configuration of VEMs is done via the VSM NX-OS Command-line interface . The Virtual Supervisor Module or VSM would normally run as a virtual appliance in an ESX/ESXi cluster but it is possible to run the VSM on dedicated hardware:

SECTION 20

#1732779725960

704-507: The Nexus 1010, 1010x and 1100. For organisations where there is a very strict boundary between network management and server management, network administrators can avoid the dependency on the VSM running as virtual machine within the ESX cluster. The capabilities and limitations of a VSM running on a Nexus1010 are the same as a VSM running as virtual appliance under ESX. A Nexus 1100 can host up to 14 VSMs and it also allows additional services such as

736-622: The Nexus 2000 Fabric Extenders can act as a remote line card on the 7000 series. 70xx and 77xx linecards and supervisor modules are not compatible. The Nexus 9000 series is a range of many models 2U to 21U rack-switches offering 60 to 2304 interfaces running on 100Mb , 1Gb , 10Gb , 25Gb , 40Gb , 100Gb , 400Gb Ethernet, 10/25/40 Gb FCoE interfaces. They can be used with the above-mentioned Nexus 2000 series fabric extender. The 9000 series provides converged Active Directory (AD), Network Standard Execution, (NSX) and Application Centric Infrastructure (ACI) using Software Defined Networking (SDN) in

768-414: The Nexus 2000 fabric extender to the 5500 range, the Nexus 7000 is the real modular switch in the Nexus family with six versions: one 4 slot, one 9 slot, two 10 slot and two 18 slot switches. Unlike the other Nexus models, the 7000 series switches are the modular switches for campus core and data center access, aggregation and core. Some details on the models are detailed below. As with the Nexus 5000 series

800-619: The Nexus 4001d for the Dell M1000e For the HP blade system Cisco released a Fabric Extender, which compares with the Nexus 2000 top of rack devices, but then in a blade-form factor. The FEX that was developed for the Dell blade system, which was due to be released in the summer of 2010 was dropped at the same time as the Nexus 4001d in February of that year The Nexus 5000 series, a.k.a. N5K,

832-484: The Nexus 6004X switch and renamed it to the Nexus 5696Q. Previously, the Nexus 6000 series was meant to be focused on the Cisco 40G aggregation products, and the 5500 and 5600 series on 10G. However, these switches mostly shared common hardware components, ASICs, and the same software images, so recently the Cisco decided to merge the product portfolios. Although the Nexus 5000 had some modular capabilities and you can attach

864-523: The amount of cooling equipment located outside or on the roof. Colocation facilities have many other special characteristics: Colocation data centres are often audited to prove that they attain certain standards and levels of reliability; the most commonly seen systems are SSAE 16 SOC 1 Type I and Type II (formerly SAS 70 Type I and Type II) and the tier system by the Uptime Institute or TIA. For service organizations today, SSAE 16 calls for

896-473: The facility is built. Generators do not start instantaneously, so colocation facilities usually have battery backup systems. In many facilities, the operator of the facility provides large inverters to provide AC power from the batteries. In other cases, customers may install smaller UPSes in their racks. Some customers choose to use equipment that is powered directly by 48 VDC (nominal) battery banks. This may provide better energy efficiency, and may reduce

928-586: The modules The 5548 comes in two sub-models: the 5548P and 5548UP The 5596 comes in two sub-models the UP and the T: Next to the expansion modules all three Nexus 55xx switches offer the capability to insert a 160 Gbit/s layer-3 routing engine The 5672UP comes in two variants, with 16 or 24 unified ports: The Cisco Nexus 6000 range contains two models, the 6001 model and the 6004 model. They can be used as layer2 and layer3 switches and can aggregate traffic from

960-436: The networking environment and be able to configure your system as if all virtual servers have connections to a physical switch and include the capabilities that a switch offers such as multiple VLANs per virtual interface, layer-3 options, security features etc. Per infrastructure/cluster you have one VM running the Nexus 1000v as virtual appliance , this is the VSM or Virtual Supervisor Module and then on each node you would have

992-515: The number of parts that can fail, though the reduced voltage greatly increases necessary current, and thus the size (and cost) of power delivery wiring. An alternative to batteries is a motor–generator connected to a flywheel and diesel engine. Many colocation facilities can provide redundant, A and B power feeds to customer equipment, and high end servers and telecommunications equipment often can have two power supplies installed. Colocation facilities are sometimes connected to multiple sections of

Cisco Nexus switches - Misplaced Pages Continue

1024-436: The utility power grid for additional reliability. Colocation facility owners have differing rules regarding cross-connects between their customers, some of whom may be carriers. These rules may allow customers to run such connections at no charge, or allow customers to order such connections for a monthly fee. They may allow customers to order cross-connects to carriers, but not to other customers. Some colocation centres feature

#959040