- 201210 - Bug in Nexus design reports normal frames over trunk link as jumbo due to vlan header.
HowTo enable jumbo frames.
Done through policy. 3 Layers, qos -> queuing -> network-qos
system qos service-policy type queuing output policyQueuing service-policy type queuing input policyQueuing service-policy type network-qos policyNetwork-qos service-policy type qos input policyQos
switch(config)# policy-map type network-qos jumbo switch(config-pmap-nq)# class type network-qos class-default switch(config-pmap-c-nq)# mtu 9216 switch(config-pmap-c-nq)# exit switch(config-pmap-nq)# exit switch(config)# system qos switch(config-sys-qos)# service-policy type network-qos jumbo
MTBF 187,265 hours = 21years.
- 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
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.
There are some definite requirements for using an EtherChannel for FEXs, such as the FEX parameter pinning max-links must be set to 1.
- Check fiber signal strength.
sh interface transceiver details
- Other options
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
- 2248TP GE
- 2231PP 10GE
Nexus 2000 config, upgrade, dual-home