Cisco Cisco Nexus 5010 Switch デザインガイド
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 89 of 119
●
Use pathcost method long.
●
Configure the spanning-tree port type edge or port type edge trunk.
QoS Checklist
QoS best practices include the following steps:
●
If you are using FCoE at the access layer, be sure to map FCoE service policies with the no-drop class.
●
Add fabric extender uplinks to achieve the greatest buffer size and lower oversubscription.
●
Spread server ports over different port ASICs on the fabric extender if you want more buffer space.
●
Tune the queue limits for fabric extender ports.
●
Consider using the Cisco Nexus 2248TP-E for particular applications such as video editing and Panasas
storage.
Multicast Checklist
Multicast best practices include the following steps:
●
Do not disable IGMP snooping.
●
If necessary, you can configure multicast ports manually, or you can define a querier.
●
Prune multicast traffic from the peer link (configure no ip igmp snooping mrouter vpc-peer-link).
Manageability Considerations
Using Port Profiles
Port profiles provide a template configuration that can then be applied identically to multiple interfaces. The
Ethernet port profile by default is Layer 2 on the Cisco Nexus 5000 Series.
This sample configuration illustrates the configuration template provided by port profiles:
port-profile type ethernet accessvlan
switchport access vlan 50
spanning-tree port type edge
state enabled
Whenever you configure shut or no shut from the port profile, this setting is propagated to the port. Also, state
enabled must be configured for the port profile configuration to take effect.
Note: For more information about port profiles, please refer to the following link:
Using Configuration Synchronization
Starting from Cisco NX-OS 5.0(2)N1(1), vPC-based configurations can be replicated among Cisco Nexus 5000
Series vPC peers by using the configuration synchronization (config-sync) feature. Config-sync provides a
mechanism for synchronizing configurations. It does so by using the concept of a switch profile; the switch profile is
used to create the configuration file that is then applied to the local vPC peer and the remote vPC peer.