Channel Group Mode Active Vs On

By | 13/10/2022

Configuring Port Channels

This affiliate provides data about port channels and how to configure the port channels.


Finding Feature Information

Your software release might not support all the features documented in this module. For the latest caveats and feature information, run into the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release. To find data about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Characteristic History tabular array below.



Characteristic History for Port Channels

Feature Name

Release

Characteristic Information

Port channels

8.4(two)

The default port channel style was changed from On to Active mode.



Information Well-nigh Port Channels

Port Channels Overview

Port channels refer to the assemblage of multiple physical interfaces into one logical interface to provide higher aggregated bandwidth, load balancing, and link redundancy (see Port Channel Flexibility). Port channels can connect to interfaces across switching modules, and so a failure of a switching module cannot bring downward the port channel link.

Effigy i.

Port Channel Flexibility


Port channels on Cisco MDS 9000 Series Multilayer Switches allow flexibility in configuration. This illustrates three possible port channel configurations:

  • Port channel A aggregates two links on two interfaces on the same switching module at each end of a connection.

  • Port channel B also aggregates two links, but each link is connected to a different switching module. If the switching module goes down, traffic is non afflicted.

  • Port aqueduct C aggregates three links. Two links are on the aforementioned switching module at each cease, while one is connected to a unlike switching module on switch 2.



East Port Channels

An E port channel refers to the assemblage of multiple E ports into one logical interface to provide college aggregated bandwidth, load balancing, and link redundancy. Port channels tin can connect to interfaces beyond switching modules, so a failure of a switching module cannot bring down the port channel link.

A port channel has the following features and restrictions:

  • Provides a signal-to-betoken connectedness over ISL (E ports) or EISL (TE ports). You lot can combine multiple links into a port channel.

  • Increases the aggregate bandwidth on an ISL past distributing traffic among all functional links in the channel.

  • Load balances across multiple links and maintains optimum bandwidth utilization. Load balancing is based on the source ID, destination ID, and exchange ID (OX ID).

  • Provides high availability on an ISL. If one link fails, traffic that is previously carried on this link switches to the remaining links. If a link goes down in a port aqueduct, the upper protocol is not aware of it. To the upper protocol, the link is still there, although the bandwidth is macerated. Link failure does not bear on the routing tables. Port channels may contain upwardly to 16 concrete links and may span multiple modules for added high availability.



F, TF, NP, and TNP Port Channels



Note

We exercise not recommend using interface, fWWN, or domain-ID based zoning for devices that are continued to the edge Cisco N-Port Virtualization (NPV) switches.


F port channels provide fault tolerance and performance benefits on connections to N-Port Virtualization (NPV) switches, including Cisco UCS Material Interconnects (FIs). F port channels present unique challenges to ACL TCAM programming. When F ports are aggregated into a port channel, ACL TCAM programming is repeated on each member interface. Consequently, these types of port channels multiply the corporeality of TCAM entries needed. Considering of this, information technology is imperative that the member interfaces are allocated as optimally every bit possible, and that zoning best practices are also followed. If y’all also consider the fact that these F port channels can contain 100+ host logins, TCAM can hands be exceeded, especially for fabric switches if best practices are not followed.

The post-obit is a sample topology:


This example assumes that the port channel (PC) contains 8 interfaces, fc1/ane-fc1/8.

In add-on, the post-obit ii zones are agile:

            
              zone1 fellow member host (host 0x010001) member target1 (target1 0x010002) zone2 member host (host 0x010001) member target2 (target2 0x010003)
            
          

In such a scenario, the following ACL programming will exist present on each member of the PC:

            
              fc1/1(through fc1/8) (port-channel) Entry#    Source ID     Mask         Destination ID         Mask              Action i         010001       ffffff        010002(target1)       ffffff             Allow 2         010001       ffffff        010003(target2)       ffffff             Permit 3         000000       000000        000000                000000             Drop
            
          

The higher up example shows the ACL TCAM programming that will be duplicated on each fellow member of the F port-aqueduct. Consequently, if a lot of programming is required considering of a large number of FLOGIs on the F port channel, or a large number of devices are zoned with the devices on the F port channel, TCAM can be exhausted on a forwarding engine. The following are the best practices for efficient use of TCAM with respect to F ports and F port-channels:

  • Distribute port-channel member interfaces into unlike forwarding engines, especially on cloth switches.

  • If TCAM usage is even so too high in the example of port-channel with a large number of interfaces, then dissever the port-channel into two split up port-channels each with half the interfaces. This volition still provide redundancy just will reduces the number of FLOGIs per private port-channel and thus reduce TCAM usage.

  • Distribute fellow member interfaces into dissimilar linecards on director-course switches.

  • Distribute member interfaces into forwarding engines with lower TCAM zoning region usage.

  • Utilize unmarried-initiator zones, single-target zones, or Smart Zoning.



Port Channeling and Trunking

Trunking is a commonly used storage industry term. Even so, the Cisco NX-OS software and switches in the Cisco MDS 9000 Serial Multilayer Switches implement trunking and port channeling as follows:

  • Port channeling enables several physical links to be combined into ane aggregated logical link.

  • Trunking enables a link transmitting frames in the EISL format to carry (trunk) multiple VSAN traffic. For instance, when trunking is operational on an Due east port, that Eastward port becomes a TE port. A TE port is specific to switches in the Cisco MDS 9000 Series Multilayer Switches. An industry standard East port can link to other vendor switches and is referred to as a nontrunking interface (see Trunking Only and Port Channeling and Trunking). See Configuring Trunking for information on trunked interfaces.

Figure 2.

Trunking Only


Effigy 3.

Port Channeling and Trunking


Port channeling and trunking are used separately across an ISL.

  • Port channeling—Interfaces tin be channeled between the following sets of ports:

    • E ports and TE ports

    • F ports and NP ports

    • TF ports and TNP ports

  • Trunking—Trunking permits carrying traffic on multiple VSANs betwixt switches.

Run across the
Cisco MDS 9000 Series NX-OS Textile Configuration Guide.

  • Both port channeling and trunking can be used between TE ports over EISLs.



Port Aqueduct Modes



Notation

After changing the port-channel mode, each fellow member interface must be brought down and brought back up via the

shutdown

and

no shutdown

commands for the port-aqueduct mode to be changed. This can be done on an private member-by-fellow member basis such that the port-channel remains upwards and fully functional.


You can configure each port channel with a channel grouping way parameter. Such configuration determines the port aqueduct protocol behavior for all member ports in this channel group. The possible values for a channel group mode are equally follows:

  • On—The fellow member ports only operate as part of a port aqueduct or remain inactive. In this style, the port aqueduct protocol is not initiated. However, if a port channel protocol frame is received from a peer port, the software indicates its nonnegotiable status. This mode is backward compatible with the existing implementation of port channels in releases before Cisco MDS NX-Bone Release ii.0(1b), where the channel group mode is implicitly causeless to be On. In Cisco MDS SAN-Bone Releases 1.3 and earlier, the only bachelor port channel mode was the On manner. Port channels that are configured in the On mode require you to explicitly enable and disable the port channel fellow member ports at either end if you lot add or remove ports from the port aqueduct configuration. Physically verify that the local and remote ports are continued to each other.

    However, from Cisco MDS Release NX-OS Release 8.4(one), the default port channel mode is the Active mode.

  • Active—The member ports initiate port aqueduct protocol negotiation with the peer ports regardless of the channel group fashion of the peer port. If the peer port, while configured in a channel grouping, does not back up the port channel protocol, or responds with nonnegotiable status, it defaults to the On style behavior

    in Cisco MDS Release NX-Bone Release 8.3(one) and earlier releases
    .
    However, from Cisco MDS Release NX-Os Release 8.iv(1), the default port channel mode is the Active mode.
    The Agile port channel mode allows automatic recovery without explicitly enabling and disabling the port channel member ports at either end.



Note

Before Cisco MDS NX-OS Release 8.three(1), the CLI and the Device Director create the port channel in On style on the NPIV cadre switches and Active style on the NPV switches. DCNM-SAN creates all port channels in Active mode. We recommend that you create port channels in Active mode.

From Cisco MDS NX-Bone Release 8.4(1), the CLI and the Device Manager create the port channel in Active mode on the NPIV core switches.


Table 1 compares On and Active modes.

Tabular array one.

Aqueduct Group Configuration Differences

On Mode

Active Fashion

No protocol is exchanged.

A port aqueduct protocol negotiation is performed with the peer ports.

Moves interfaces to the suspended state if its operational values are incompatible with the port channel.

Moves interfaces to the isolated country if its operational values are incompatible with the port channel.

When you add together or alter a port-channel member port configuration, y’all must explicitly disable (shut) and enable (no close) the port channel member ports at either end.

When you add or modify a port channel interface, the port channel automatically recovers.

Port initialization is not synchronized.

At that place is synchronized startup of all ports in a channel across peer switches.

All misconfigurations are non detected every bit no protocol is exchanged.

Consistently observe misconfigurations using a port channel protocol.

Transitions misconfigured ports to the suspended state. You must explicitly disable (shut) and enable (no shut) the member ports at either end.

Transitions misconfigured ports to the isolated state to correct the misconfiguration. Once yous right the misconfiguration, the protocol ensures automatic recovery.



Port Channel Deletion

When you delete the port aqueduct, the corresponding channel membership is likewise deleted. All interfaces in the deleted port channel convert to private concrete links. Afterwards the port channel is removed, regardless of the mode used (Active and On), the ports at either end are gracefully brought downward. The ports going down gracefully indicates that no frames were lost when the interface went downwardly (encounter the Svelte Shutdown).

If you delete the port channel for 1 port, then the individual ports within the deleted port channel retain the compatibility parameter settings (speed, mode, port VSAN, allowed VSAN, and port security). You tin explicitly change those settings every bit required.

  • If you use the default On fashion to avoid inconsistent states across switches and to maintain consistency across switches, then the ports close down. Explicitly enable those ports over again.

  • If you use the Active mode, then the port channel ports automatically recover from the deletion.



Interfaces in a Port Channel

You can add together or remove a physical interface (or range of interfaces) to an existing port channel. The compatible parameters on the configuration are mapped to the port channel. Calculation an interface to a port aqueduct increases the channel size and bandwidth of the port channel. Removing an interface from a port channel decreases the channel size and bandwidth of the port channel.



Note

For information about port channel back up on Generation ii switching modules, encounter the Port Channel Limitations department.



Interface Addition to a Port Channel

You can add together a concrete interface (or range of interfaces) to an existing port aqueduct. The compatible parameters on the configuration are mapped to the port channel. Adding an interface to a port channel increases the channel size and bandwidth of the port channel.

You lot can configure a port as a member of a static port channel simply if the following configurations are the aforementioned in the port and the port channel:

  • Speed

  • Mode

  • Charge per unit mode

  • Port VSAN

  • Trunking mode

  • Allowed VSAN list or VF-ID list

After the members are added, regardless of the way (Active and On) used, the ports at either finish are gracefully brought down. The ports going down gracefully indicates that no frames were lost when the interface went down.


Compatibility Check

A compatibility check ensures that the aforementioned parameter settings are used in all physical ports in the aqueduct. Otherwise, they cannot become part of a port aqueduct. The compatibility check is performed before a port is added to the port channel.

The check ensures that the following parameters and settings match at both ends of a port channel:

  • Capability parameters (type of interface, Gigabit Ethernet at both ends, or Fibre Channel at both ends).

  • Authoritative compatibility parameters (speed, mode, rate manner, port VSAN, allowed VSAN list, and port security).



Note

Ports in shared rate way cannot form a port channel or a trunking port aqueduct.


  • Operational parameters (remote switch WWN and trunking fashion).

A port addition procedure fails if the capability and authoritative parameters on the remote switch are incompatible with the capability and administrative parameters on the local switch. If the compatibility check is successful, the interfaces are operational and the corresponding compatibility parameter settings use to these interfaces.



Suspended and Isolated States

If the operational parameters are incompatible, the compatibility check fails and the interface is placed in a suspended or isolated land based on the configured manner:

  • An interface enters the suspended state if the interface is configured in the On mode.

  • An interface enters the isolated state if the interface is configured in the Active fashion.



Forcing an Interface Addition

You can forcefulness the port configuration to exist overwritten by the port channel. In this instance, the interface is added to a port channel.

  • If you use the On style to avoid inconsistent states across switches and to maintain consistency across switches, then the ports shut down. Explicitly enable those ports again.

  • If yous use the Active way, then the port channel ports automatically recover from the improver.



Annotation

When port channels are created from within an interface, the

strength

option cannot be used.


After the members are forcefully added, regardless of the mode (Active and On) used, the ports at either end are gracefully brought down. The ports going down gracefully indicates that no frames were lost when the interface went downwards (see the Graceful Shutdown) section.



Deleting an Interface from a Port Channel

When a physical interface is deleted from the port aqueduct, the channel membership is automatically updated. If the deleted interface is the last operational interface, and so the port aqueduct status is inverse to a downwardly state. Deleting an interface from a port channel decreases the aqueduct size and bandwidth of the port channel.

  • If you lot apply the On mode to avoid inconsistent states across switches and to maintain consistency across switches, then the ports shut down. Explicitly enable those ports again.

  • If you use the Active mode, then the port channel ports automatically recover from the deletion.

Afterwards the members are deleted, regardless of the mode (Active and On) used, the ports at either finish are gracefully brought down. The ports going downwards gracefully indicates that no frames were lost when the interface went down.



Port Channel Protocols

In earlier Cisco SAN-OS releases, port channels required extra administrative tasks to support synchronization. The Cisco NX-Bone software provides robust error detection and synchronization capabilities. You tin manually configure aqueduct groups or they tin be automatically created. In both cases, the channel groups have the aforementioned adequacy and configurational parameters. Any change in configuration applied to the associated port channel interface is propagated to all members of the channel grouping.

A protocol to exchange port channel configurations is bachelor in all Cisco MDS switches. This addition simplifies port channel management with incompatible ISLs. Extra autocreation mode enables ISLs with uniform 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 MDS switches. It uses the exchange peer parameters (EPP) services to communicate across peer ports in an ISL. Each switch uses the data that is received from the peer ports forth with its local configuration and operational values to decide if it has to be function of a port aqueduct. The protocol ensures that a prepare of ports is eligible to exist part of the same port channel. They are but eligible to be part of the same port channel if all the ports have a compatible partner.

The port aqueduct protocol uses ii subprotocols:

  • Bring-up protocol—Automatically detects misconfigurations then you tin correct them. This protocol synchronizes the port channel at both ends and then 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 brand applications such every bit write acceleration, piece of work for port channels over FCIP links.

  • Autocreation protocol—Automatically aggregates compatible ports into a port channel.


Channel Group Creation



Note

Aqueduct groups are non supported on internal ports in the Cisco Fabric Switch for HP c-Class BladeSystem and the Cisco Fabric Switch for IBM BladeSystem.


Assuming the link A1-B1 comes upwardly showtime (see Autocreating Aqueduct Groups section), that link is operational as an individual link. When the next link comes up, for example, A2-B2, the port channel protocol identifies if this link is compatible with link A1-B1 and automatically creates aqueduct groups ten and 20 in the respective switches. If link A3-B3 can join the channel groups (the port channels), the respective ports have uniform configurations. If link A4-B4 operates equally an individual link, it is because of the incompatible configuration of the two stop ports with the other fellow member ports in this channel group.

Figure iv.

Autocreating Channel Groups


The channel grouping numbers are selected dynamically, and as such, the administrative configuration of the ports forming the aqueduct group at either finish are applicative to the newly created aqueduct group. The channel group number that is chosen dynamically may be different across reboots for the same set of port channels that are based on the gild of ports that are initialized in the switch.

Table 1 identifies the differences between user-configured and auto-configured channel groups.

Tabular array ii.

Channel Group Configuration Differences

User-Configured Channel Group

Autocreated Channel Group

Manually configured by you.

Created automatically when compatible links come up betwixt 2 uniform switches, if the aqueduct group autocreation is enabled in all ports at both ends.

Member ports cannot participate in autocreation of channel groups. You cannot configure the autocreation feature.

None of these ports are members of a user-configured channel grouping.

You tin can form the port aqueduct with a subset of the ports in the aqueduct grouping. Incompatible ports remain in a suspended or isolated state depending on the On or Active mode configuration.

All ports that are included in the channel group participate in the port channel—No member port becomes isolated or suspended. Instead, the fellow member port is removed from the channel group when the link is constitute to be incompatible.

Whatever administrative configuration made to the port aqueduct is applied to all ports in the aqueduct group, and yous can save the configuration for the port channel interface.

Any administrative configuration made to the port channel is applied to all ports in the aqueduct group, but the configurations are saved for the member ports. No configuration is saved for the port aqueduct interface. Y’all tin can explicitly catechumen this channel group, if necessary.

You tin remove any aqueduct grouping and add members to a channel group.

You cannot remove a channel group, or add or remove any of its members. The channel group is removed when no fellow member ports be.



Annotation

Autocreation is not supported every bit of MDS NX-OS Release iv.one(1b) and later.




Autocreation

The autocreation protocol has the following functionality:

  • When you enable the autocreation feature, you lot cannot configure ports every bit function of a port channel. These ii configurations are mutually sectional.

  • Enable the autocreation feature in both the local and peer ports to negotiate a port channel.

  • Assemblage occurs in one of two ways:

    • A port is aggregated into a compatible autocreated port aqueduct.

    • A port is aggregated with some other compatible port to form a new port channel.

  • Newly created port channels are allocated from the maximum port channel in a decreasing society based on availability. If all port channels are used upwardly, aggregation is not allowed.

  • You cannot change the membership or delete an autocreated port aqueduct.

  • When you disable autocreation, all member ports are removed from the autocreated port channel.

  • After you remove the last member from an autocreated port aqueduct, the channel is automatically deleted and the number is released for reuse.

  • An autocreated port channel is not persistent through a reboot. You can configure an autocreated port channel to appear the same every bit a persistent port channel. Later on the port aqueduct is made persistent, the autocreation feature is disabled in all member ports.

  • You tin enable or disable the autocreation feature on a per-port basis or for all ports in the switch. When this you enable this configuration, the channel group mode is assumed to be active. The default for this chore is disabled.

  • If you enable autocreation of channel groups for an interface, y’all must first disable the autocreation feature before downgrading to an earlier software version or before configuring the interface in a manually configured channel group.



Tip

When enabling autocreation in any switch in the Cisco MDS 9000 Series Multilayer Switches, we recommend that you lot retain at least one interconnected port between the switches without any autocreation configuration. If all ports between 2 switches are configured with the autocreation feature at the same time, you may face a possible traffic disruption between these ii switches. The traffic disruption is because the ports are automatically disabled and reenabled when ports are added to an autocreated port aqueduct.




Manually Configured Channel Groups

A user-configured aqueduct group cannot exist converted to an autocreated channel grouping. However, yous can convert an autocreated channel group to a manual channel group. Once performed, this chore is irreversible. The channel group number does not change, but the member ports operate co-ordinate to the properties of the manually configured aqueduct group, and the autocreation of channel grouping is implicitly disabled for all member ports.



Tip

If you enable persistence, be sure to enable it at both ends of the port channel.




Prerequisites for Port Channels

Before configuring a port aqueduct, consider the following guidelines:

  • Configure the port channel across switching modules to implement redundancy on switching module reboots or upgrades.

  • Ensure that you do non connect a port channel to different sets of switches. Port channels crave point-to-point connections between the aforementioned fix of switches.

If you misconfigure port channels, you may receive a misconfiguration message. If you receive this message, the port channel’s physical links are disabled because error was detected.

Port channel error is detected if the following requirements are non met:

  • Connect each switch on either side of a port channel to the same number of interfaces.

  • Connect each interface to a corresponding interface on the other side (come across Misconfigured Configurations for an example of an invalid configuration).

  • You cannot modify the links in a port channel afterwards you configure the port aqueduct. If yous change the links after you configure the port channel, ensure to reconnect the links to interfaces within the port channel and reenable the links.

If all three atmospheric condition are not met, the faulty link is disabled.

Enter the

show
interface

control for that interface to verify that the port channel is functioning every bit required.



Default Settings

Table 1 lists the default settings for port channels.

Table 3.

Default Port Channel Parameters

Parameters

Default

Port channels

FSPF is enabled past default.

Create port aqueduct

Administratively up.

Default port channel style

Cisco MDS NX-Bone Release viii.3(one) and earlier: On style on non-NPV and NPIV core switches.

Cisco MDS NX-Bone Release 8.4(i) and later: Agile fashion on not-NPV and NPIV core switches.

Active mode on NPV switches.

Autocreation

Disabled.



Guidelines and Limitations

General Guidelines and Limitations

Cisco MDS 9000 Serial Multilayer switches support the following number of port channels per switch:

  • A port aqueduct number refers to the unique identifier for each channel group. This number ranges from of 1–256.

The following table describes the results of adding a fellow member to a port channel for various configurations.



F, TF, and NP Port Channel Limitations

The following guidelines and restrictions are applicable for F, TF, and NP port channels:

  • On the switch with

    feature npiv

    configured the ports must exist in F style.

  • On the switch with

    feature npv

    configured the ports must exist in NP mode.

  • Automatic creation is not supported.

  • On fashion is not supported. Merely Active-Active mode is supported. Past default, the manner is Agile on the NPV switches.

  • Devices that are logged in through an F port channel on an MDS switch are not supported in IVR non-NAT configuration. The devices are supported only in IVR NAT configuration.

  • Port security rules are enforced but on concrete pWWNs at the single link level.

  • FC-SP authenticates but the showtime physical FLOGI of every port aqueduct fellow member.

  • Since the FLOGI payload carries just the VF $.25 to trigger the use of a protocol after the FLOGI substitution, those bits are overridden. If the Cisco NPV switches, the core has a Cisco WWN and tries to initiate the PCP protocol.

  • The name server registration of the N ports logging in through an F port channel uses the fWWN of the port channel interface.

  • DPVM configuration is not supported.

  • You cannot configure the port channel port VSAN using DPVM.

  • The Dynamic Port VSAN Management (DPVM) database is queried only for the starting time physical FLOGI of each fellow member, so that the port VSAN tin can be configured automatically.

  • DPVM does not bind FC_IDs to VSANs, but pWWNs to VSANs. It is queried just for the physical FLOGI.



E Port Channel Limitations

The port channel interface must be in Active mode when you configure multiple FCIP interfaces with WA.



Valid and Invalid Port Channel Examples

Port channels are created with default values. You lot can modify the default configuration just like whatsoever other physical interface.

Valid Port Channel Configurations provides examples of valid port aqueduct configurations.

Figure v.

Valid Port Channel Configurations


Misconfigured Configurations provides examples of invalid configurations. Assuming that the links are brought upwardly in the i, two, 3, 4 sequence, links three and 4 will be operationally downwards considering the fabric is misconfigured.

Figure 6.

Misconfigured Configurations




Port Channel Best Practices

Forwarding Engines

A Cisco Multilayer Director Switch (MDS) uses a special kind of memory called Ternary Content Addressable Memory (TCAM) on its Fibre Aqueduct modules. This special retention provides an Access Control Listing (ACL) type of function for Cisco MDS. The procedure that controls this functionality is chosen ACLTCAM. The E or TE ports (ISLs) and F (Textile) ports accept their own programming that is unique to their respective port types.

TCAM is allocated to individual forwarding engines and forwarding engines are assigned a group of ports. Director-class Fibre Channel modules have more TCAM infinite than fabric switches. The number of forwarding engines, the ports assigned to each forwarding engine, and the amount of TCAM allocated to each forwarding engine is hardware dependent.

The following example shows an output from Cisco MDS 9148S:

            
              switch#
              
                show system internal acltcam–soc tcam–usage
              
              TCAM Entries: =============                   Region1   Region2    Region3     Region4   Region5   Region6 Mod Fwd   Dir     Summit SYS  SECURITY    ZONING      BOTTOM    FCC DIS   FCC ENA     Eng          Apply/Total Use/Total  Employ/Full   Use/Total Use/Total Use/Total ––– –––  –––––– –––––––––– ––––––––– –––––––––––– ––––––––– ––––––––– ––––––––– 1   1    INPUT     19/407     1/407      1/2852 *    iv/407     0/0       0/0 1   1    OUTPUT     0/25      0/25       0/140       0/25      0/12      1/25 1   two    INPUT     19/407     ane/407      0/2852 *    4/407     0/0       0/0 i   two    OUTPUT     0/25      0/25       0/140       0/25      0/12      one/25 1   3    INPUT     nineteen/407     1/407      0/2852 *    4/407     0/0       0/0 1   3    OUTPUT     0/25      0/25       0/140       0/25      0/12      ane/25 ––––––––––––––––––––––––––––––––––––––––––––––––––– * 1024 entries are reserved for LUN Zoning purpose.
            
          

The higher up example indicates the post-obit:

  • In that location are iii forwarding engines, 1 through three.

  • Since there are 48 ports on Cisco MDS 9148 switches, each forwarding engine handles 16 ports.

  • Each forwarding engine has 2852 entries in region 3 (the zoning region) for input. This is the main region used, and consequently, has the largest amount of available entries.

  • Forwarding engine three has only one entry that is currently in use out of the total 2852 in the zoning region.

The following example shows the output from Cisco MDS 9710 switch with a 2/4/viii/10/16 Gbps Advanced Fibre Channel Module (DS–X9448–768K9):

            
              F241–15–09–9710–2#
              
                show system internal acl tcam–usage
              
              TCAM Entries: =============                   Region1   Region2    Region3     Region4   Region5   Region6 Modern Fwd   Dir     Top SYS  SECURITY    ZONING      Lesser    FCC DIS   FCC ENA     Eng          Use/Total Use/Total  Use/Total   Utilize/Total Use/Total Use/Total ––– –––  –––––– –––––––––– ––––––––– –––––––––––– ––––––––– ––––––––– ––––––––– 1   0    INPUT     55/19664    0/9840     0/49136*   17/19664    0/0       0/0 1   0    OUTPUT    thirteen/4075    0/1643     0/11467     0/4075    6/1649   21/1664 1   1    INPUT     52/19664    0/9840     2/49136*   xiv/19664    0/0       0/0 ane   one    OUTPUT     7/4078    0/1646     0/11470     0/4078    vi/1652    5/1651 ane   2    INPUT     34/19664    0/9840     0/49136*   10/19664    0/0       0/0 i   ii    OUTPUT     5/4078    0/1646     0/11470     0/4078    6/1652    1/1647 ane   3    INPUT     34/19664    0/9840     0/49136*   x/19664    0/0       0/0 1   iii    OUTPUT     5/4078    0/1646     0/11470     0/4078    6/1652    1/1647 one   4    INPUT     34/19664    0/9840     0/49136*   10/19664    0/0       0/0 i   iv    OUTPUT     5/4078    0/1646     0/11470     0/4078    half dozen/1652    i/1647 1   5    INPUT     34/19664    0/9840     0/49136*   10/19664    0/0       0/0 1   5    OUTPUT     5/4078    0/1646     0/11470     0/4078    6/1652    one/1647 ...
            
          

The above case indicates the following:

  • At that place are vi forwarding engines, 0 through 5.

  • Since there are 48 ports on a Cisco MDS DS–X9448–768K9 module, each forwarding engine handles eight ports.

  • Each forwarding engine has 49136 entries in region 3 (the zoning region) for input. This is the main region that is used, and consequently, has the largest amount of available entries.

  • Forwarding engine two has simply ii entries that are currently in use out of the total 49136 in the zoning region.



Note

The commands that are used to view TCAM usage on fabric switches are different from the ones used for director–class switches. For MDS 9148, MDS 9148S, and MDS 9250i cloth switches, use the

show system internal acltcam-soc tcam-usage
command. For director class switches, MDS 9396S, and 32 Gbps fabric switches, use the

show organisation internal acl tcam-usage

command.


The following tabular array provides information most ports to forwarding engines mapping:

Table iv.

Ports to Forwarding Engines Mapping

Switch or Module

Forwarding Engines

Port Ranges

Forwarding Engine Number

Zoning Region Entries

Bottom Region Entries

MDS 9132T

2

1–16

0

49136

19664

17–32

i

49136

19664

MDS 9148

3

fc1/25–36 and fc1/45–48

1

2852

407

fc1/five–12 and fc1/37–44

2

2852

407

fc1–4 and fc1/13–24

3

2852

407

MDS 9148S

3

fc1/1–16

ane

2852

407

fc1/17–32

2

2852

407

fc1/33–48

3

2852

407

MDS 9148T

3

ane–16

0

49136

19664

17–32

1

49136

19664

33–48

2

49136

19664

MDS 9250i

four

fc1/5–12 and eth1/1–8

1

2852

407

fc1/1–4, fc1/13–twenty, and fc1/37–twoscore

2

2852

407

fc1/21–36

3

2852

407

ips1/ane–2

4

2852

407

MDS 9396S

12

fc1/one–8

0

49136

19664

fc1/9–16

1

49136

19664

fc1/17–24

2

49136

19664

fc1/25–32

3

49136

19664

fc1/33–xl

4

49136

19664

fc1/41–48

v

49136

19664

fc1/49–56

half-dozen

49136

19664

fc1/57–64

7

49136

19664

fc1/65–72

8

49136

19664

fc1/73–80

9

49136

19664

fc1/81–88

10

49136

19664

fc1/89–96

eleven

49136

19664

MDS 9396T

vi

1–16

0

49136

19664

17–32

1

49136

19664

33–48

ii

49136

19664

49–64

3

49136

19664

65-lxxx

4

49136

19664

81-96

v

49136

19664

DS–X9248–48K9

1

one–48

0

27168

2680

DS–X9248–96K9

2

1–24

0

27168

2680

25–48

one

27168

2680

DS–X9224–96K9

2

ane–12

0

27168

2680

xiii–24

ane

27168

2680

DS–X9232–256K9

iv

1–8

0

49136

19664

9–16

1

49136

19664

17–24

2

49136

19664

25–32

3

49136

19664

DS–X9248–256K9

4

1–12

0

49136

19664

13–24

1

49136

19664

25–36

2

49136

19664

37–48

3

49136

19664

DS–X9448–768K9

6

i–8

0

49136

19664

9–xvi

1

49136

19664

17–24

2

49136

19664

25–32

3

49136

19664

33–40

four

49136

19664

41–48

5

49136

19664

DS–X9334–K9

3

ane–viii

0

49136

19664

nine–16

ane

49136

19664

17–24

2

49136

19664

DS–X9648–1536K9

three

1–16

0

49136

19664

17–32

1

49136

19664

33–48

ii

49136

19664



E and TE Port Channels and IVR

Eastward port channels provide Inter Switch Links (ISLs) between fabric switches. Typically, at that place is minimal TCAM programming on these types of interfaces. Therefore, also placing them into unlike linecards, and perhaps port groups on director-course switches, there is a picayune more to be done. However, when the Inter VSAN Routing (IVR) feature is existence deployed, all-encompassing TCAM programming can exist on ISLs because the IVR topology transitions from one VSAN to another. Consequently, most of the considerations that apply on F/TF port channels volition be applicative here too.

The following is an example of a topology:


In this topology:

  • Both Cisco MDS 9148S-ane and MDS 9148S-two are in the IVR VSAN topology:

            
              MDS9148S-one vsan 1 and vsan ii MDS9148S-ii vsan ii and vsan iii
          
  • IVR NAT is configured.

  • VSAN two is the transit VSAN.

            
              FCIDs per VSAN:             VSAN 1  VSAN 2  VSAN three Host     			010001  210001  550002 Target1 			440002  360002  030001
          


Note

Domains 0x44 in VSAN ane, 0x21 and 0x36 in VSAN 2, and 0x55 in VSAN three are virtual domains created by IVR NAT.


  • The following is the IVR zoning topology:

            
              ivr zone zone1 member host vsan 1 fellow member target1 vsan3
          
  • The following is the ACL TCAM programming for the IVR zoning topology:

            
              MDS9148S-1  fc1/1(Host) - VSAN ane Entry# 			Source ID    				Mask      Destination ID  								Mask    Action i      			010001(host) 				ffffff    440002(target1) 								ffffff  Permit            - Forward to fc1/2        - Rewrite the post-obit information:          VSAN to two          Source ID to 210001          Destination ID to 360002 2      			000000     				000000    000000          								000000  Drib MDS9148S-1  fc1/ii(ISL) - VSAN ii Entry# 			Source ID       					Mask      Destination ID  								Mask    Action one      			360002(Target1) 					ffffff    210001(host)    								ffffff  Let        - Forward to fc1/2        - Rewrite the following data:          VSAN to i          Source ID to 440002          Destination ID to 010001 MDS9148S-two fc1/ii(ISL) - VSAN 2 Entry# 			Source ID    				Mask      Destination ID  								Mask    Action one      			210001(host) 				ffffff    360002(target1) 								ffffff  Let        - Forward to fc1/ii        - Rewrite the following data:          VSAN to 3          Source ID to 550002          Destination ID to 030001 MDS9148S-2  fc1/i(Target1) - VSAN 3 Entry# 			Source ID       					Mask      Destination ID  								Mask    Action 1      			030001(Target1) 					ffffff    550002(host)    								ffffff  Permit        - Forrad to fc1/ii        - Rewrite the post-obit information:          VSAN to 2          Source ID to 360002          Destination ID to 210001 2      			000000     					000000    000000          									000000  Drop
          


Annotation

Too the entries in this example, there are other entries that IVR adds to capture important frames such equally PLOGIs, PRILIs, and ABTS.


The programming on the host and target1 ports is similar to the way it is without IVR, except that the FCIDs and VSANs are explicitly forwarded to an egress port and are rewritten to values that are appropriate for the transit VSAN (VSAN 2). These forwarding and rewrite entries are dissever and are not included in the TCAM-usage values.

Withal, now, on the ISLs in both the switches, programming that did not be before is present. When frames from Host to Target1 are received past Cisco MDS 9148S-2 fc1/2, they are rewritten to the values in VSAN three where the target resides. In the reverse direction, when frames from Target1 to the Host are received past Cisco MDS 9148S-1 fc1/two, they are rewritten to the values in VSAN i where the Host resides. Thus, for each VSAN transition on an ISL (that typically occurs across a transit VSAN) there volition be TCAM programming for each device in the IVR zone set.

Consequently, virtually of the all-time practices followed for the F and TF port channels should be followed to ensure that TCAM is utilized every bit efficiently as possible for the following purposes:



Note

Unlike F and TF port-channels, the ACLTCAM programming on ISLs will be the same quantity regardless if the ISLs are part of a port-channel or not. If there are “n” ISLs betwixt two MDS switches, and then it doesn’t thing if they are in 1 port-channel, two port-channels or just individual links. The ACLTCAM programming volition be the aforementioned.


  • Distribute port-channel fellow member interfaces into different forwarding engines, especially on material switches.

  • Distribute fellow member interfaces into different linecards on managing director-class switches.

  • Distribute member interfaces into forwarding engines with lower TCAM zoning region usage.

  • Use single-initiator zones, single-target zones, or Smart Zoning.



Configuring Port Channels

Configuring Port Channels Using the Wizard Creating a Port Channel

To create a port channel, perform these steps:

Procedure


Step one

switch#

configure
terminal

Enters configuration way.

Step ii

switch(config)#

interface
port-channel
1

Configures the specified port channel (one) using the default ON manner.




Configuring the Port Channel Style

Before Cisco MDS NX-Os Release 8.3(1), the CLI and the Device Manager create the port channel in On way on the NPIV core switches and Active mode on the NPV switches. DCNM-SAN creates all port channels in Active mode. We recommend that yous create port channels in Active mode.

From Cisco MDS NX-Os Release 8.4(1), the CLI and the Device Manager create the port channel in Active style on the NPIV core switches.



Note

An F port channel is supported but on Active mode.


To configure Active mode, perform these steps:

Process


Step i

switch#

configure
last

Enters configuration mode.

Step 2

switch(config)#

interface
port-channel
1

Configures the specified port aqueduct (1) using the default On mode in Cisco MDS NX-OS Release viii.3(1) and earlier releases. Configures the specified port channel (1) using the default Active mode from Cisco MDS NX-OS Release 8.4(1).




Deleting Port Channels

To delete a port channel, perform these steps:

Procedure


Step 1

switch#

configure
terminal

Enters configuration mode.

Step 2

switch(config)#

no
interface
port-channel
1

Deletes the specified port channel (one), its associated interface mappings, and the hardware associations for this port channel.




Calculation an Interface to a Port Channel

To add an interface to a port channel, perform these steps:

Process


Step 1

switch#

configure
terminal

Enters configuration mode.

Step 2

switch(config)#

interface
fc1/15

Configures the specified port interface (fc1/15).

Step 3

switch(config-if)#

channel-group
xv

Adds physical Fibre Channel port ane/xv to channel group 15. If the channel-group 15 does not exist, it is created. The port is shut down.




Adding a Range of Ports to a Port Channel

To add range of ports to a port channel, perform these steps:

Procedure


Footstep 1

switch#

configure
terminal

Enters configuration mode.

Step 2

switch(config)#

interface
fc1/1

v

Configures the specified range of interfaces. In this example, interfaces from 1/one to 1/v are configured.

Step three

switch(config-if)#

channel-grouping
2

Adds physical interfaces 1/1, i/2, ane/3, 1/iv, and 1/v to channel group 2. If the channel-group two does non exist, it is created.

If the compatibility check is successful, the interfaces are operational and the corresponding states apply to these interfaces.


What to practise next



Note

By default, the CLI adds an interface normally to a port channel, while DCNM-SAN adds the interface past force, unless specified explicitly.




Forcing an Interface Add-on

To force the addition of a port to a port aqueduct, perform these steps:

Procedure


Step ane

switch#

configure
terminal

Enters configuration fashion.

Step 2

switch(config)#

interface
fc1/one

Specifies the interface fc1/one.

Step iii

switch(config-if)#

channel-group
1
force

Forces the add-on of the physical port for interface fc1/1 to channel group one. The port is shut downwards.




Deleting an Interface from a Port Channel

To delete a physical interface (or range of physical interfaces) from a port aqueduct, perform these steps:

Procedure


Footstep one

switch#

configure terminal

Enters configuration way.

Step 2

switch(config)#

interface
fc1/ane

Enters the selected physical interface level.

Step 3

switch(config)#

interface
fc1/i

5

Enters the selected range of physical interfaces.

Step four

switch(config-if)#

no
aqueduct-group
ii

Deletes the physical Fibre Channel interfaces in channel group 2.




Enabling and Configuring Autocreation

To configure automatic channel groups, perform these steps:

Procedure


Step i

switch#

configure
terminal

Enters configuration manner.

Step 2

switch(config)#

interface
fc8/13

Enters the configuration way for the selected interfaces.

Pace three

switch(config- if)#

channel-group
auto

Automatically creates the aqueduct group for the selected interfaces.

switch(config- if)#
no
channel-group
auto

(Optional) Disables the autocreation of channel groups for this interface, even if the system default configuration may accept enabled autocreation.




Converting to Manually Configured Channel Groups

You can convert an autocreated channel grouping to a user-configured channel group using the
port-channel


channel-grouping-number


persistent

EXEC command. This command does not execute if the port channel does not exist.



Verifying Port Channel Configuration

To brandish the port channel configuration data, perform one of the following tasks:

Command

Purpose


show
port-channel
summary

Displays a summary of port channels within the switch. A ane-line summary of each port channel provides the authoritative state, the operational state, the number of attached and active interfaces (upwardly), and the first operational port (FOP). The FOP is the primary operational interface that is selected in the port aqueduct to bear control-airplane traffic (no load-balancing). The FOP is the first port that comes upward in a port channel and can change if the port goes downwardly. The FOP is besides identified past an asterisk (*).


show
port-aqueduct
database

Cisco MDS NX-Os Release 8.3(1) and earlier: Displays the port aqueduct that is configured in the On mode (default) and Agile mode.

Cisco MDS NX-Bone Release eight.4(2) and later: Displays the port channel that is configured in the On mode and Active manner (default).


show
port-channel
consistency

Displays the consistency status without details.


bear witness port-channel consistency detail

Displays the consistency condition with details.



show port-aqueduct usage

Displays the port channel usage.


show port-channel compatibility-parameters

Displays the port channel compatibility.


show interface fc


slot/port

Displays autocreated port channels.


show port-channel database interface port-aqueduct


number

Displays the specified port aqueduct interface.

For detailed data virtually the fields in the output from these commands, refer to the
Cisco MDS 9000 Serial NX-OS Control Reference.

You tin can view specific data about existing port channels at any time from EXEC style. The following

show

commands provide farther details on existing port channels. You can forcefulness all screen output to go to a printer or relieve information technology to a file. See Examples Displays the Port Channel Summary to Displays the Port Channel Summary.

Examples

              
                switch#
                
                  show port-aqueduct summary
                
                ------------------------------------------------------------------------------ Interface                 Full Ports        Oper Ports        First Oper Port ------------------------------------------------------------------------------ port-channel 77                ii                 0                  -- port-channel 78                2                 0                  -- port-channel 79                2                 two                  fcip200
              
            

Examples



Note

This control output is applicable for Cisco MDS NX-Os Release viii.4(two) and subsequently releases. The control output varies if yous are using Cisco MDS NX-OS Release viii.four(1a) or earlier releases.


              
                switch#
                
                  show port-channel database
                
                port-channel1     Administrative channel style is on     Final membership update succeeded     Beginning operational port is fcip3     2 ports in full, 2 ports up     Ports:   fcip1    [up]              fcip3    [upwards] *  port-channel2     Authoritative channel way is on     Last membership update succeeded     First operational port is fcip5     half dozen ports in full, five ports up     Ports:   fcip5    [upward] *              fcip6    [upward]              fcip7    [up]              fcip11   [up]              fcip12   [down]              fcip13   [up]  port-channel3     Administrative channel mode is on     Concluding membership update succeeded     First operational port is fcip9     3 ports in total, 3 ports up     Ports:   fcip8    [upward]              fcip9    [up] *              fcip10   [up]
              
            

Examples



Note

This command output is applicable for Cisco MDS NX-Os Release viii.4(ii) and later releases. The command output varies if y’all are using Cisco MDS NX-OS Release 8.four(1a) or earlier releases.


              
                switch#
                
                  show port-channel database
                
                port-channel1     Authoritative aqueduct mode is active     Last membership update succeeded     First operational port is fcip3     2 ports in total, 2 ports up     Ports:   fcip1    [up]              fcip3    [up] *  port-channel2     Administrative channel fashion is active     Last membership update succeeded     Commencement operational port is fcip5     6 ports in total, 5 ports up     Ports:   fcip5    [up] *              fcip6    [up]              fcip7    [up]              fcip11   [up]              fcip12   [downwards]              fcip13   [upwards]  port-channel3     Authoritative aqueduct mode is active     Last membership update succeeded     Outset operational port is fcip9     3 ports in total, 3 ports up     Ports:   fcip8    [upward]              fcip9    [up] *              fcip10   [up]
              
            

Examples

The

show port-channel consistency

command has two options: without details and with details.

              
                switch#
                
                  bear witness port-aqueduct consistency
                
                Database is consistent
              
            

Examples

              
                switch#
                
                  show port-channel consistency detail
                
                Administrative port-channel database: ================================================ totally 3 port-channels port-channel 77:     two ports, first operational port is none     fcip1    [downwards]     fcip2    [downwards] port-channel 78:     ii ports, first operational port is none     fc2/i    [down]     fc2/5    [downwards] port-aqueduct 79:     two ports, offset operational port is fcip200     fcip101  [up]     fcip200  [up] ================================================ database i: from module v ================================================ totally iii port-channels port-channel 77:     2 ports, first operational port is none     fcip1    [downwards]     fcip2    [down] port-channel 78:     2 ports, start operational port is none     fc2/1    [down]     fc2/5    [down] port-channel 79:     two ports, first operational port is fcip200     fcip101  [upwards]     fcip200  [up] ================================================ database two: from module 4 ================================================ totally 3 port-channels port-channel 77:     2 ports, commencement operational port is none     fcip1    [down]     fcip2    [down] port-channel 78:     2 ports, outset operational port is none     fc2/i    [down]     fc2/five    [down] port-channel 79:     2 ports, kickoff operational port is fcip200     fcip101  [upwardly]     fcip200  [up] ...
              
            

Examples

The

bear witness port-aqueduct usage

command displays details of the used and unused port channel numbers.

              
                switch#
                
                  show port-channel usage
                  
                
                Totally 3 port-channel numbers used =================================== Used  :   77 - 79 Unused:   i - 76 , 80 - 256
              
            

Examples

Use the existing

show

commands to obtain further details on autocreated channel group attributes. Autocreated port channels are indicated explicitly to aid differentiate them from the manually created port channels.

              
                switch#
                
                  evidence port-channel compatibility-parameters
                
                physical port layer                 fibre channel or ethernet     port fashion                           East/Automobile only     torso way     speed     port VSAN     port allowed VSAN list
              
            

Examples

              
                switch#
                
                  show interface fc1/1
                
                fc1/1 is trunking     Hardware is Fibre Aqueduct, FCOT is curt wave laser     Port WWN is 20:0a:00:0b:5f:3b:iron:80     ...     Receive information field Size is 2112     Beacon is turned off
                
                  Port-channel auto creation is enabled
                
                
                  Belongs to port-channel 123
                
                ...
              
            

Examples

              
                switch#
                
                  testify port-channel database interface port-channel 128
                
                port-aqueduct 128     Administrative channel fashion is active     Operational channel mode is agile     Last membership update succeeded
                
                  Channel is auto created
                
                Showtime operational port is fc1/ane     1 ports in full, 1 ports up     Ports:   fc1/1   [up] *
              
            

Examples

              
                switch#
                
                  show port-channel summary
                
                ------------------------------------------------------------------------------ Interface                 Total Ports        Oper Ports        First Oper Port ------------------------------------------------------------------------------ port-channel 1                 ane                 0                  -- port-channel 2                 1                 ane                  fc8/xiii port-aqueduct three                 0                 0                  -- port-aqueduct 4                 0                 0                  -- port-aqueduct 5                 1                 i                  fc8/iii port-channel 6                 0                 0                  --
              
            



Configuration Examples for F and TF Port Channels

This example shows how to configure an F port channel in shared mode and bring up the link (not supported on the MDS 91×4 switches) between F ports on the Cisco NPIV core switches and NP ports on the Cisco NPV switches:

Procedure


Step 1

Enable the F port trunking and channeling protocol on the MDS core switch.

Example:

                      
                        switch(config)#
                        
                          feature fport-channel-body
                        
                      
                    
Step 2

Enable NPIV on the MDS core switch:

Example:

                      
                        switch(config)#
                        
                          feature npiv
                        
                      
                    
Step 3

Create the port channel on the MDS core switch:

Instance:

                      
                        switch(config)#
                        
                          interface port-channel ane
                        
                        switch(config-if)#
                        
                          switchport manner F
                        
                        switch(config-if)#
                        
                          channel way agile
                        
                        switch(config-if)#
                        
                          switchport trunk mode off
                        
                        switch(config-if)#
                        
                          switchport charge per unit-mode shared
                        
                        switch(config-if)#
                        
                          exit
                        
                      
                    
Stride 4

Configure the port channel member interfaces on the cadre switch:

Example:

                      
                        switch(config)#
                        
                          interface fc2/1-three
                        
                        switch(config-if)#
                        
                          shut
                        
                        switch(config-if)#
                        
                          switchport mode F
                        
                        switch(config-if)#
                        
                          switchport body manner off
                        
                        switch(config-if)#
                        
                          switchport speed 4000
                        
                        switch(config-if)#
                        
                          switchport rate-manner shared
                        
                        switch(config-if)#
                        
                          channel-group 1
                        
                        switch(config-if)#
                        
                          no shut
                        
                        switch(config-if)#
                        
                          exit
                        
                      
                    
Step 5

Create the port aqueduct on the NPV switch:

Example:

                      
                        switch(config)#
                        
                          interface port-aqueduct 1
                        
                        switch(config-if)#
                        
                          switchport mode NP
                        
                        switch(config-if)#
                        
                          switchport charge per unit-fashion shared
                        
                        switch(config-if)#
                        
                          get out
                        
                      
                    
Stride six

Configure the port channel member interfaces on the NPV switch:

Example:

                      
                        switch(config)#
                        
                          interface fc2/one-3
                        
                        switch(config-if)#
                        
                          shut
                        
                        switch(config-if)#
                        
                          switchport way NP
                        
                        switch(config-if)#
                        
                          switchport speed 4000
                        
                        switch(config-if)#
                        
                          switchport rate-way shared
                        
                        switch(config-if)#
                        
                          switchport trunk mode off
                        
                        switch(config-if)#
                        
                          channel-group 1
                        
                        switch(config-if)#
                        
                          no shut
                        
                        switch(config-if)#
                        
                          exit
                        
                      
                    
Footstep 7

Fix the administrative state of all the port-channel member interfaces in both NPIV cadre switch and the NPV switch to ON:

Instance:

                      
                        switch(config)#
                        
                          interface fc1/i-three
                        
                        switch(config-if)#
                        
                          shut
                        
                        switch(config-if)#
                        
                          >no shut
                        
                        switch(config)#
                        
                          interface fc2/1-three
                        
                        switch(config-if)#
                        
                          close
                        
                        switch(config-if)#
                        
                          >no shut
                        
                      
                    



Configuration Examples for F and TF Port Channels (Dedicated Mode)



Note

The speed configuration must exist the same for all member interfaces in a port channel. While configuring the channel in dedicated fashion, ensure that required bandwidth is available to the ports.


This example shows how to configure channeling in dedicated mode and bring up the TF-TNP port channel link between TF ports in the NPIV core switch, and TNP ports in the Cisco NPV switch:

Procedure


Step one

Enable the F port trunking and channeling protocol on the MDS cadre switch:

Example:

                      
                        switch(config)#
                        
                          characteristic fport-channel-trunk
                        
                      
                    
Pace 2

Enable NPIV on the MDS cadre switch:

Example:

                      
                        switch(config)#
                        
                          feature npiv
                        
                      
                    
Pace iii

Create the port channel on the MDS core switch:

Example:

                      
                        switch(config)#
                        
                          interface port-channel 2
                        
                        switch(config-if)#
                        
                          switchport style F
                        
                        switch(config-if)#
                        
                          switchport rate-mode defended
                        
                        switch(config-if)#
                        
                          channel mode agile
                        
                        switch(config-if)#
                        
                          exit
                        
                      
                    
Footstep iv

Configure the port channel member interfaces on the MDS cadre switch in defended style:

Case:

                      
                        switch(config)#
                        
                          interface fc1/4-half dozen
                        
                        switch(config-if)#
                        
                          shut
                        
                        switch(config-if)#
                        
                          switchport mode F
                        
                        switch(config-if)#
                        
                          switchport speed 4000
                        
                        switch(config-if)#
                        
                          switchport rate-mode dedicated
                        
                        switch(config-if)#
                        
                          switchport torso fashion on
                        
                        switch(config-if)#
                        
                          aqueduct-group 2
                        
                        switch(config-if)#
                        
                          no shut
                        
                        switch(config-if)#
                        
                          exit
                        
                      
                    
Step v

Create the port channel in dedicated style on the Cisco NPV switch:

Example:

                      
                        switch(config)#
                        
                          interface port-channel 2
                        
                        switch(config-if)#
                        
                          switchport charge per unit-style dedicated
                        
                        switch(config-if)#
                        
                          switchport mode NP
                        
                        switch(config-if)#
                        
                          no shut
                        
                        switch(config-if)#
                        
                          exit
                        
                      
                    
Step half dozen

Configure the port aqueduct member interfaces on the Cisco NPV switch in dedicated mode:

Example:

                      
                        switch(config)#
                        
                          interface fc3/i-3
                        
                        switch(config-if)#
                        
                          shut
                        
                        switch(config-if)#
                        
                          switchport way NP
                        
                        switch(config-if)#
                        
                          switchport speed 4000
                        
                        switch(config-if)#
                        
                          switchport rate-style dedicated
                        
                        switch(config-if)#
                        
                          switchport trunk mode on
                        
                        switch(config-if)#
                        
                          channel-group ii
                        
                        switch(config-if)#
                        
                          no shut
                        
                        switch(config-if)#
                        
                          exit
                        
                      
                    
Footstep 7

Set the administrative state of all the port channel member interfaces in both NPIV core switch and the Cisco NPV switch to ON:

Example:

                      
                        switch(config)#
                        
                          interface fc1/four-6
                        
                        switch(config-if)#
                        
                          shut
                        
                        switch(config-if)#
                        
                          no close
                        
                        switch(config)#
                        
                          interface fc3/i-3
                        
                        switch(config-if)#
                        
                          close
                        
                        switch(config-if)#
                        
                          no shut
                        
                      
                    



Source: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/8_x/config/interfaces/cisco_mds9000_interfaces_config_guide_8x/configuring_portchannels.html