HOW TO CONFIGURE NEXUS 3000

CARA CONFIGURE NEXUS 3064

Perbedaan IOS dan NX-OS SWITCH layer 3:

NX-OS  untuk mengaktifkan beberap feature kita harus ketik command "NX-OS(config)# feature interface-vlan "

Command untuk interface range di NX-OS

NX_OS(config)# interface eth1/1 - 48
NX-OS(config-if-range)# ?
  bandwidth              Set bandwidth informational parameter
  beacon                 Disable/enable the beacon for an interface
  cdp                    Configure CDP interface parameters

berikut adalah syarat Port chanel nexus 3064 ,

untuk lebi detail bisa cek link cisco berikutklik disini

CISCO-NX-OS# show port compatibility-parameters
* port mode
Members must have the same port mode configured.
* port mode
Members must have the same port mode configured, either E,F or AUTO. If
they are configured in AUTO port mode, they have to negotiate E or F mode
when they come up. If a member negotiates a different mode, it will be
suspended.
* speed
Members must have the same speed configured. If they are configured in AUTO
speed, they have to negotiate the same speed when they come up. If a member
negotiates a different speed, it will be suspended.
* MTU
Members have to have the same MTU configured. This only applies to ethernet
port-channel.
* shut lan
Members have to have the same shut lan configured. This only applies to
ethernet port-channel.
* MEDIUM
Members have to have the same medium type configured. This only applies to
ethernet port-channel.
* Span mode
Members must have the same span mode.
* load interval
Member must have same load interval configured.
* negotiate
Member must have same negotiation configured.
* sub interfaces
Members must not have sub-interfaces.
* Duplex Mode
Members must have same Duplex Mode configured.
* Ethernet Layer
Members must have same Ethernet Layer (switchport/no-switchport) configured.
* Span Port
Members cannot be SPAN ports.
* Storm Control
Members must have same storm-control configured.
* Flow Control
Members must have same flowctrl configured.
* Capabilities
Members must have common capabilities.
* Capabilities speed
Members must have common speed capabilities.
* Capabilities duplex
Members must have common speed duplex capabilities.
* rate mode
Members must have the same rate mode configured.
* Capabilities FabricPath
Members must have common fabricpath capability.
* Port is PVLAN host
Port Channel cannot be created for PVLAN host
* 1G port is not capable of acting as peer-link
Members must be 10G to become part of a vPC peer-link.
* EthType
Members must have same EthType configured.
* shared interface
Members can not be shared-interfaces.
* Capabilities SpanDest
Members must be capable of span destination configuration
* Sflow enabled port
Members cannot be Sflow enabled ports
* port
Members port VLAN info.
* port
Members port does not exist.
* switching port
Members must be switching port, Layer 2.
* port access VLAN
Members must have the same port access VLAN.
* port native VLAN
Members must have the same port native VLAN.
* port allowed VLAN list
Members must have the same port allowed VLAN list.
* port Voice VLAN
Members must not have voice vlan configured.
* All HIF member ports not in same pinning group
All HIF member ports not in same pinning group
* Members in multiple FEX
Members must belong to same FEX.
* Members are of different type
Members must of same interface type.
* vPC cannot be defined across more than 2 FEXes
vPC cannot be defined across more than 2 FEXes
* Max members on FEX exceeded
Max members on FEX exceeded
* vPC cannot be defined across ST and AA FEX
vPC cannot be defined across ST and AA FEX
* Untagged Cos Params
Members must have the same untagged cos.
* Priority Flow Control Params
Members must have the same priority flow control parameters.
* Untagged Cos Params
Members must have the same untagged cos.
* Priority Flow Control Params
Members must have the same priority flow control parameters.
* queuing policy configured on port-channel
queuing service-policy not allowed on RW HIF-ports and RW HIF-Po.
* Port priority-flow-control
PFC config should be the same for all the members
* Port-channel with STP configuration, not compatible with HIF
HIF ports cannot be bound to port-channel with STP configuration
* Port Security policy
Members must have the same port-security enable status as port-channel
* Dot1x policy
Members must have host mode as multi-host with no mab configuration. Dot1X
cannot be enabled on members when Port Security is configured on port
channel
* PC Queuing policy
Queuing policy for the PC should be same as system queuing policy
* PVLAN port config
Members must have same PVLAN port configuration.
* Emulated switch port type policy
vPC ports in emulated switch complex should be L2MP capable.
* VFC bound to FCoE capable port channel
Port Channels that have VFCs bound to them cannot have non fcoe capable
member
* VFC bound to member port of port channel.
 Fail to add additional interface to port channel
* VFC bound to FCoE capable port channel
Port Channels that have VFCs bound to them cannot have non fcoe licensed
member
* vfc bound to member port of hif po, Two members cannot be on the same fex
 Fail to add additional interface to port channel
* VFCs bound to both port channel and new member port(s).
 Fail to add additional interface to port channel
* Flexlink config
Features configured on member interface must be supportable by Flexlink.
* Fex ports for span
Port-Channel is already a SPAN source. Cannot add FEX ports connected
through                         Ricard to this PC