Deleting An Interface From A San Port Channel; Port Channel Protocol - Cisco AJ732A - MDS 9134 Fabric Switch Configuration Manual
Cisco nexus 5000 series switch cli software configuration guide, nx-os 4.0(1a)n1 (ol-16597-01, january 2009)
Hide thumbs
Also See for AJ732A - Cisco MDS 9134 Fabric Switch:
- Command reference manual (1640 pages) ,
- Messages manual (518 pages) ,
- Installation manual (288 pages)
Table of Contents
Advertisement
Chapter 36
Configuring SAN Port Channels
S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
After the members are deleted, regardless of the mode (Active and On) used, the ports at either end are
gracefully brought down, indicating that no frames are lost when the interface is going down.
Deleting an Interface from a SAN Port Channel
To delete a physical interface (or a range of physical interfaces) from a SAN port channel, perform this
task:
Command
Step 1
switch(config)# interface type slot/port
Step 2
switch(config-if)# no channel-group
channel-number
The following example deletes an interface from a SAN port channel:
switch(config)# interface fc2/3
switch(config-if)# no channel-group 15
fc2/1 removed from san-port-channel 2 and disabled. Please do the same operation on the
switch at the other end of the san-port-channel
Port Channel Protocol
The switch software provides robust error detection and synchronization capabilities. You can manually
configure channel groups, or they can be automatically created. In both cases, the channel groups have
the same capability and configurational parameters. Any change in configuration applied to the
associated port channel interface is propagated to all members of the channel group.
Cisco SAN switches support a protocol to exchange port channel configurations, which simplifies port
channel management with incompatible ISLs. An additional autocreation mode enables ISLs with
compatible parameters to automatically form channel groups without manual intervention.
The port channel protocol is enabled by default.
The port channel protocol expands the port channel functional model in Cisco SAN switches. It uses the
exchange peer parameters (EPP) services to communicate across peer ports in an ISL. Each switch uses
the information received from the peer ports along with its local configuration and operational values to
decide if it should be part of a SAN port channel. The protocol ensures that a set of ports are eligible to
be part of the same SAN port channel. They are only eligible to be part of the same port channel if all
the ports have a compatible partner.
The port channel protocol uses two subprotocols:
•
•
This section describes how to configure the port channel protocol and includes the following sections:
•
OL-16597-01
Bringup protocol—Automatically detects misconfigurations so you can correct them. This protocol
synchronizes the SAN port channel at both ends so that all frames for a given flow (as identified by
the source FC ID, destination FC ID and OX_ID) are carried over the same physical link in both
directions. This helps make applications such as write acceleration work for SAN port channels over
FCIP links.
Autocreation protocol—Automatically aggregates compatible ports into a SAN port channel.
About Channel Group Creation, page 36-12
Purpose
Enters configuration mode for the specified
interface.
Deletes the physical Fibre Channel interface from
the specified channel group.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
Port Channel Protocol
36-11
Hide quick links:
Advertisement
Chapters
Table of Contents
Troubleshooting
