|
Size: 456
Comment:
|
Size: 7932
Comment: Add link to configSync
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| * [[Nexus/Logging]] * [[Nexus/ConfigSync]] == Nexus 4000 == * MTBF [[http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps10596/ps10642/data_sheet_c78-560881_ps10596_Products_Data_Sheet.html|187,265 hours]] = 21years. * == vPC == * [[http://bradhedlund.com/2010/12/16/routing-over-nexus-7000-vpc-peer-link-yes-and-no/|Rules and diagrams]] * Check witch link in a port channel will be used. * show port-channel load-balance forwarding-path interface port-channel 2 vlan 902 dst-ip 192.168.110.212 src-ip 192.168.110.200 # sh hardware internal carmel port e 1/1 * QOS http://alleasysetup.blogspot.com/2011/10/qos-on-cisco-nexus-5k.html * FlowControll to VMware http://www.boche.net/blog/index.php/2010/11/29/flow-control/ * vPC virtual port channel, let port's on 2 vPC peers look like they are from one switch, eliminating blocked ports on ethertrunk. * Step1 enable features needed on switches. {{{ feature lacp feature vpc }}} * peer-gateway - only for dumb hosts that do not use arp for gw discovery, but incoming packet. * pinning max-links 1 * Before the peer link will come up, you also have to set up VPC keepalives to detect dual active peers {{{ vpc domain 1 peer-keepalive destination 10.10.10.14 source 10.10.10.13 }}} * VPC Rule 101 * VPC peers are expected to forward a frame received on a member link out any other member link that needs to be used. Only if they cannot do so due to a link failure, is forwarding across the VPC peer link and then out a member link allowed, and even then, the cross-peer-link traffic can only go out the member link that is paired with the member link that is down. * Restatement of VPC Rule 101 * To put it another way, VPC peers are expected to forward a frame received on a member link out any other member link that needs to be used. Only if they cannot do so due to a link failure, is forwarding across the VPC peer link and then out a member link allowed, and even then, the cross-peer-link traffic can only go out the member link that is paired with the member link that is down. * With VPC, one should always put keepalives on a different link than the VPC peer link, since their purpose is to detect a situation with the peer still up but VPC peer link down. You just can't do that if they're running over the peer link. Instead, you can use the management port. Or, if you put a separate point-to-point routed link between the peers, in parallel with the VPC peer-link, you can use that for the keepalives. * The L3 decision determines the outbound interface. If that outbound link is a VPC member link, the same forwarding rule is applied as for L2: the frame (packet) came in the peer-link, the member interface that is VPC-paired to the chosen outbound link is up, therefore drop the packet. * Check fiber signal strength. {{{ sh interface transceiver details }}} * Other options * [[http://www.aristanetworks.com/|Arista]] Networks * [[http://www.cisco.com/en/US/products/ps11541/index.html|Nexus 3000]] Ultra Low Latency * 3064 48 x 10G + 4 x 40G - 1RU - L2 & L3 10Gbit/s on 64 ports 48-SFP+ + 4 x QSFP+ (40Gbit or 4 x 10Gbit ) * 3016 16 x 40G quad sfp ports. |
|
| Line 5: | Line 49: |
| * L3 capable. [[http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html|additional hardware]] * Nexus2k Fabric extender * 2148T * 2248TP GE * 2231PP 10GE * [[http://www.cisco.com/en/US/docs/switches/datacenter/nexus2000/sw/configuration/guide/rel_4_1/Cisco_Nexus_2000_Series_Fabric_Extender_Software_Configuration_Guide_chapter3.html|Nexus 2000]] config, upgrade, dual-home |
|
| Line 6: | Line 56: |
| * [[http://www.cisco.com/en/US/docs/switches/datacenter/nexus2000/sw/configuration/guide/rel_4_1/Cisco_Nexus_2000_Series_Fabric_Extender_Software_Configuration_Guide_chapter3.html|Nexus 2000]] config, upgrade, dualhome * |
== List price estimates == * 2012 * '''2x CoreB Total: R831,708.00''' = 2x R415,854.00 * R355,774.00 N3K-C3064-E-FA-L3 : Nexus 3064-E, Std Airflow (port side exhaust), LAN Ent Lic B * R60,080.00 8x 1GSX-MM, 4x 10Gbase-Cu, 4x 10Gbase-Sr * '''ADD''' 2x R147,000.00 N3K-C3048-FA-L3 + 2x10Guplink + 4 x SFP-10G-SR : 10Gbase-Sr Sfp Module * '''R294,000.00''' ---- * ADD 2x N2K-C2248TP-1GE (48x100/1000-T+4x10GE) + 2x10Guplink + 4 x SFP-10G-SR : 10Gbase-Sr Sfp Module * '''R166,342.00''' * R49,970.73 N2K-C2248TP : N2K-C2248TP-1GE (48x100/1000-T+4x10GE) * R8,300.00 SFP-10G-SR : 10Gbase-Sr Sfp Module * '''2x CoreA Total: R460,160.00''' = 2x 230,080.00 * 1x R170,000.00 2 x N5K-C5548P-FA +L3: Cisco Nexus 5548P 1Ru Chassis 2 Ps 2 Fan 32 Fixed 10Ge Ports * 8x R2,776.15 GLC-SX-MM : Ge Sfp Lc Connector Sx Transceiver * 1G Fiber uplinks - DWDM + Wan + 4Floors * 4x R1,166.00 SFP-H10GB-CU3M : 10Gbase-Cu Sfp+ Cable 3 Meter * 10G to DWDM, + Link to 2nd switch * 4x R8,300.00 SFP-10G-SR : 10Gbase-Sr Sfp Module * 10G fiber 10G links. ---- * Cisco switch details * Perf 1-year limited hardware warranty * 176 Gbps or 131 mpps, 40°C, 95W, * Cisco Nexus 2232TM Coper 1/10G-RJ45 [Cisco Nexus 2232PP - SFP/SFP+] 4:1 560 Gbps or 595 mpps * Cisco Nexus 2248TP Coper 100M/1G * Cisco Nexus 2248TP-E Coper 100M/1G (32MB shared buffers.) * Cisco Nexus B22HP Fabric Extender * '''Core''' 5548's * (8 fabric extenders for L3 configurations) * Cisco Nexus 5548P Switch 160 Gbps of Layer 3 forwarding capability (240 million packets per second [mpps]) * Cisco Nexus 5548UP Switch * Nexus 3064 provides Layer 2 and 3 switching of up to 1.2 terabits per second (Tbps) and more than 950 million packets per second (mpps) * '''Modules''' * Cisco Fabric Extender Transceiver (FET-10G) FO-SR OM3 0.1uS * NXA-AIRFLOW-SLV Nexus2k Airflow Extension Sleeve * N2K-C2148T-FAN= Cisco Nexus 2148T FEX Fan Module (Std airflow, port side exhaust), spare * N2K-C2248-FAN= Cisco Nexus 2224TP, 2248TP, and 2248TP-E FEX Fan Module (Std airflow, port side exhaust), spare * N2200-PAC-400W= Cisco Nexus 2200 AC Power supply (Std airflow, port side exhaust), spare * N2200-P-BLNK= Cisco Nexus 2200 Power supply Blank, spare * SFP-10G-SR(=) 10GBASE-SR SFP+ Module * SFP-H10GB-CU1M(=) 10GBASE-CU SFP+ Passive Cable 1 Meter * CAB-C13-CBN(=) Cabinet Jumper Power Cord, 250 VAC 16A, C14-C13 Connectors ---- * HQ R1.5M * R461k(2Core) x1pair * R167k(2Switch) x6pairs [2xNewServRack + 0xIBM +1xCore + 2xProduction + 1xDev] * DR R1.2M * R461k(2Core) x1pair N5K-C5548P-FA +L3 * R167k(2Switch) x4pairs N2K-C2248TP-1GE [1xCore, 1xRack1 , 1xRack2, 1xSpare] ---- * Option B * Using WS-C3750X-48P-S -> WS-C3750X-48P-S IPBase, poe + stack, 160Gbit Fabric, Max Forwarding 101.2 mpps, * 3750X-48P-MTBF-139,913 C3KX-PWR-715WAC-MTBF-664,055 * Operating Temperature 40C * 2 x 10G MM fiber ports. * Problem: The airflow on the Cisco Catalyst 3750-X and 3560-X Series is "front and sides" to back airflow. * Spares * C3KX-PWR-715WAC= 715W AC power supply * C3KX-FAN-23CFM= Fan module spare * C3KX-4PT-KIT= Extension rails and brackets for four-point mounting for Cisco Catalyst 3750-X and 3560-X Series * HQ * Core 10Gig fiber concentration switch. * Pairs of WS-C3750X-48P-S IPBase(48x1G , 715W - PoE future, 2 can power-stack for redundant power in Datacenter, 10G uplink) * '''Q''' Air flow for WS-C3750X-48P-S ??? Want port side exhaust. * DR * Core 10Gig fiber concentration switch. == Nexus 5548 Questions ? == * Max 2k switches supported in L3 mode ? * 8 * Max span sessions ? * 4 * Max vPC, LACP bundles ? * Max HSRP sessions ? |
Cisco Nexus
Nexus 4000
MTBF 187,265 hours = 21years.
vPC
- Check witch link in a port channel will be used.
- show port-channel load-balance forwarding-path interface port-channel 2 vlan 902 dst-ip 192.168.110.212 src-ip 192.168.110.200
# sh hardware internal carmel port e 1/1
QOS http://alleasysetup.blogspot.com/2011/10/qos-on-cisco-nexus-5k.html
FlowControll to VMware http://www.boche.net/blog/index.php/2010/11/29/flow-control/
- vPC virtual port channel, let port's on 2 vPC peers look like they are from one switch, eliminating blocked ports on ethertrunk.
- Step1 enable features needed on switches.
feature lacp feature vpc
- peer-gateway - only for dumb hosts that do not use arp for gw discovery, but incoming packet.
- pinning max-links 1
- Before the peer link will come up, you also have to set up VPC keepalives to detect dual active peers
vpc domain 1 peer-keepalive destination 10.10.10.14 source 10.10.10.13
- VPC Rule 101
- VPC peers are expected to forward a frame received on a member link out any other member link that needs to be used. Only if they cannot do so due to a link failure, is forwarding across the VPC peer link and then out a member link allowed, and even then, the cross-peer-link traffic can only go out the member link that is paired with the member link that is down.
- Restatement of VPC Rule 101
- To put it another way, VPC peers are expected to forward a frame received on a member link out any other member link that needs to be used. Only if they cannot do so due to a link failure, is forwarding across the VPC peer link and then out a member link allowed, and even then, the cross-peer-link traffic can only go out the member link that is paired with the member link that is down.
- With VPC, one should always put keepalives on a different link than the VPC peer link, since their purpose is to detect a situation with the peer still up but VPC peer link down. You just can't do that if they're running over the peer link. Instead, you can use the management port. Or, if you put a separate point-to-point routed link between the peers, in parallel with the VPC peer-link, you can use that for the keepalives.
- The L3 decision determines the outbound interface. If that outbound link is a VPC member link, the same forwarding rule is applied as for L2: the frame (packet) came in the peer-link, the member interface that is VPC-paired to the chosen outbound link is up, therefore drop the packet.
- Check fiber signal strength.
sh interface transceiver details
- Other options
Arista Networks
Nexus 3000 Ultra Low Latency
3064 48 x 10G + 4 x 40G - 1RU - L2 & L3 10Gbit/s on 64 ports 48-SFP+ + 4 x QSFP+ (40Gbit or 4 x 10Gbit )
- 3016 16 x 40G quad sfp ports.
Cisco Nexus 5548P Switch Oct 2010
- Need SPS license for FC.
L3 capable. additional hardware
- Nexus2k Fabric extender
- 2148T
- 2248TP GE
- 2231PP 10GE
Nexus 2000 config, upgrade, dual-home
List price estimates
- 2012
2x CoreB Total: R831,708.00 = 2x R415,854.00
- R355,774.00 N3K-C3064-E-FA-L3 : Nexus 3064-E, Std Airflow (port side exhaust), LAN Ent Lic B
- R60,080.00 8x 1GSX-MM, 4x 10Gbase-Cu, 4x 10Gbase-Sr
- R355,774.00 N3K-C3064-E-FA-L3 : Nexus 3064-E, Std Airflow (port side exhaust), LAN Ent Lic B
ADD 2x R147,000.00 N3K-C3048-FA-L3 + 2x10Guplink + 4 x SFP-10G-SR : 10Gbase-Sr Sfp Module
R294,000.00
- ADD 2x N2K-C2248TP-1GE (48x100/1000-T+4x10GE) + 2x10Guplink + 4 x SFP-10G-SR : 10Gbase-Sr Sfp Module
R166,342.00
- R49,970.73 N2K-C2248TP : N2K-C2248TP-1GE (48x100/1000-T+4x10GE)
- R8,300.00 SFP-10G-SR : 10Gbase-Sr Sfp Module
2x CoreA Total: R460,160.00 = 2x 230,080.00
- 1x R170,000.00 2 x N5K-C5548P-FA +L3: Cisco Nexus 5548P 1Ru Chassis 2 Ps 2 Fan 32 Fixed 10Ge Ports
- 8x R2,776.15 GLC-SX-MM : Ge Sfp Lc Connector Sx Transceiver
- 1G Fiber uplinks - DWDM + Wan + 4Floors
- 4x R1,166.00 SFP-H10GB-CU3M : 10Gbase-Cu Sfp+ Cable 3 Meter
- 10G to DWDM, + Link to 2nd switch
- 4x R8,300.00 SFP-10G-SR : 10Gbase-Sr Sfp Module
- 10G fiber 10G links.
- Cisco switch details
- Perf 1-year limited hardware warranty
- 176 Gbps or 131 mpps, 40°C, 95W,
- Cisco Nexus 2232TM Coper 1/10G-RJ45 [Cisco Nexus 2232PP - SFP/SFP+] 4:1 560 Gbps or 595 mpps
- Cisco Nexus 2248TP Coper 100M/1G
- Cisco Nexus 2248TP-E Coper 100M/1G (32MB shared buffers.)
- Cisco Nexus B22HP Fabric Extender
Core 5548's
- (8 fabric extenders for L3 configurations)
- Cisco Nexus 5548P Switch 160 Gbps of Layer 3 forwarding capability (240 million packets per second [mpps])
- Cisco Nexus 5548UP Switch
- Nexus 3064 provides Layer 2 and 3 switching of up to 1.2 terabits per second (Tbps) and more than 950 million packets per second (mpps)
Modules
- Cisco Fabric Extender Transceiver (FET-10G) FO-SR OM3 0.1uS
- NXA-AIRFLOW-SLV Nexus2k Airflow Extension Sleeve
- N2K-C2148T-FAN= Cisco Nexus 2148T FEX Fan Module (Std airflow, port side exhaust), spare
- N2K-C2248-FAN= Cisco Nexus 2224TP, 2248TP, and 2248TP-E FEX Fan Module (Std airflow, port side exhaust), spare
- N2200-PAC-400W= Cisco Nexus 2200 AC Power supply (Std airflow, port side exhaust), spare
- N2200-P-BLNK= Cisco Nexus 2200 Power supply Blank, spare
- SFP-10G-SR(=) 10GBASE-SR SFP+ Module
- SFP-H10GB-CU1M(=) 10GBASE-CU SFP+ Passive Cable 1 Meter
- CAB-C13-CBN(=) Cabinet Jumper Power Cord, 250 VAC 16A, C14-C13 Connectors
- Perf 1-year limited hardware warranty
- HQ R1.5M
- R461k(2Core) x1pair
- R167k(2Switch) x6pairs [2xNewServRack + 0xIBM +1xCore + 2xProduction + 1xDev]
- DR R1.2M
- R461k(2Core) x1pair N5K-C5548P-FA +L3
- R167k(2Switch) x4pairs N2K-C2248TP-1GE [1xCore, 1xRack1 , 1xRack2, 1xSpare]
- Option B
Using WS-C3750X-48P-S -> WS-C3750X-48P-S IPBase, poe + stack, 160Gbit Fabric, Max Forwarding 101.2 mpps,
- 3750X-48P-MTBF-139,913 C3KX-PWR-715WAC-MTBF-664,055
- Operating Temperature 40C
- 2 x 10G MM fiber ports.
- Problem: The airflow on the Cisco Catalyst 3750-X and 3560-X Series is "front and sides" to back airflow.
- Spares
- C3KX-PWR-715WAC= 715W AC power supply
- C3KX-FAN-23CFM= Fan module spare
- C3KX-4PT-KIT= Extension rails and brackets for four-point mounting for Cisco Catalyst 3750-X and 3560-X Series
- HQ
- Core 10Gig fiber concentration switch.
- Pairs of WS-C3750X-48P-S IPBase(48x1G , 715W - PoE future, 2 can power-stack for redundant power in Datacenter, 10G uplink)
Q Air flow for WS-C3750X-48P-S ??? Want port side exhaust.
- DR
- Core 10Gig fiber concentration switch.
Nexus 5548 Questions ?
- Max 2k switches supported in L3 mode ?
- 8
- Max span sessions ?
- 4
- Max vPC, LACP bundles ?
- Max HSRP sessions ?