Guest

Cisco 7000 Series Routers

vPC Peer Link Migration from a Nexus 7000 F1 Module to an M1 Module Configuration Example

Techzone Article content

Document ID: 116153

Updated: Jun 13, 2013

Contributed by Rajeshkumar Gatti, Cisco TAC Engineer.

   Print

Introduction

The document defines the steps needed to migrate a virtual PortChannel (vPC) peer link from the Nexus 7000 F1 Module to the M1 Module. This scenario might occur when the F1 Module needs to be upgraded for scalability or other reasons.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

  • Nexus operating system CLI
  • vPC rules

Components Used

The information in this document is based on these software and hardware versions:

  • Nexus 7000 Release 6.1.x and later
  • M1/F1 series line card

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Configure

Network Diagram

For this test, a blue line maps the data path of two hosts that communicate with each other.

 116153-configure-VPC-01.png

Configuration Steps

Module 3 and Module 4 are N7K-F132XP-15 line cards. This is the current configuration from a vPC point of view.

N7K1# show run vpc
version 6.1(2)feature vpc
vpc domain 10
  role priority 100
  peer-keepalive destination 10.201.254.254 source 10.201.254.253 vrf VPC
  peer-gateway
  auto-recovery

interface port-channel1
  vpc peer-link

interface port-channel20
  vpc 20

interface port-channel30
  vpc 30
N7K2# show run vpc
version 6.1(2)
feature vpc
vpc domain 10
  role priority 200
  peer-keepalive destination 10.201.254.253 source 10.201.254.254 vrf VPC
  peer-gateway
  auto-recovery

interface port-channel1
  vpc peer-link

interface port-channel20
  vpc 20

interface port-channel30
  vpc 30

interface port-channel50
  vpc 50

Migration Steps

 

  1. Shut down the vPC peer link port channel 1.
    Int po1
    Shut

    This action suspends the vPC links on the secondary side. The vPC link will be on the primary side.
  2. Shut down ports e3/1 and e4/1 and remove the channel group configuration from both Nexus modules.
    Int e3/1,e4/1
    Shut
    No channel-group 1

    N7K1# show port-c sum
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
            M - Not in use. Min-links not met
    --------------------------------------------------------------------------------
    Group Port-       Type     Protocol  Member Ports
         Channel
    --------------------------------------------------------------------------------
    1     Po1(SD)     Eth      NONE      --
    20    Po20(SU)    Eth      LACP      Eth3/4(P)    
    30    Po30(SU)    Eth      LACP      Eth4/4(P)   
    50    Po50(SD)    Eth      LACP      Eth2/12(D)  
    100   Po100(RU)   Eth      LACP      Eth2/48(P) 
  3. Use the M1 port and bundle it into the vPC port channel. Use the port on Module 7, which is a N7K-M108X2-12L line card. Configure e7/7 to have the same configuration as e3/1 or e4/1 on both sides. For this example, a single port is used. In a real world situation, there will be more than one port. However, the same steps apply.

    interface Ethernet7/7
      switchport
      switchport mode trunk
      channel-group 1 mode active
      no shutdown

    N7K1# show port-c sum
    Flags:  D - Down        P - Up in port-channel (members)
           I - Individual  H - Hot-standby (LACP only)
           s - Suspended   r - Module-removed
           S - Switched    R - Routed
           U - Up (port-channel)
           M - Not in use. Min-links not met
    --------------------------------------------------------------------------------
    Group Port-       Type     Protocol  Member Ports
        Channel
    --------------------------------------------------------------------------------
    1     Po1(SD)     Eth      LACP      Eth7/7(D)   
    20    Po20(SU)    Eth      LACP      Eth3/4(P)   
    30    Po30(SU)    Eth      LACP      Eth4/4(P)   
    50    Po50(SD)    Eth      LACP      Eth2/12(D)  
    100   Po100(RU)   Eth      LACP      Eth2/48(P) 
  4. Bring up the port channel 1 on both sides.
    Int po1
    No shut

    This brings up the vPC links on the secondary side. Now your peer link is on the M1 line card.
    116153-configure-VPC-02.png
    In this test, there will be a small interruption in traffic that uses the secondary path when it fails over to the primary path. A change window is always recomended for these types of changes to accomodate for any unwanted suprises.

Verify

There is currently no verification procedure available for this configuration.

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

Frequently Asked Question

Q. Is it possible to add new members from the M card to the vPC peer link but leave a current F1 member in the bundle and then remove it after the new member is added?

A. Peer link can not be formed with ports from different card types such as M1 and F1.

Updated: Jun 13, 2013
Document ID: 116153