Moving Other Port Channels Into A Vpc - Cisco Nexus 3548 Configuration Manual

Nx-os interfaces release 9x
Hide thumbs Also See for Nexus 3548:
Table of Contents

Advertisement

Moving Other Port Channels into a vPC

DETAILED STEPS
Command or Action
Step 1
switch# ping ipaddress vrf vrf-name
Example
This example shows how to specifiy the VRF named vpc_keepalive:
switch# ping 123.1.1.1 vrf vpc_keepalive
PING 123.1.1.1 (123.1.1.1): 56 data bytes
64 bytes from 123.1.1.1: icmp_seq=0 ttl=254 time=3.234 ms
64 bytes from 123.1.1.1: icmp_seq=1 ttl=254 time=4.931 ms
64 bytes from 123.1.1.1: icmp_seq=2 ttl=254 time=4.965 ms
64 bytes from 123.1.1.1: icmp_seq=3 ttl=254 time=4.971 ms
64 bytes from 123.1.1.1: icmp_seq=4 ttl=254 time=4.915 ms
--- 123.1.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 3.234/4.603/4.971 ms
Moving Other Port Channels into a vPC
Before you begin
Ensure that you have enabled the vPC feature.
You must configure both switches on either side of the vPC peer link with the following procedure.
SUMMARY STEPS
1. switch# configure terminal
2. switch(config)# interface port-channel channel-number
3. switch(config-if)# vpc number
4. (Optional) switch# show vpc brief
5. (Optional) switch# copy running-config startup-config
DETAILED STEPS
Command or Action
Step 1
switch# configure terminal
Step 2
switch(config)# interface port-channel channel-number
Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x
84
Purpose
Specifies the virtual routing and forwarding (VRF) name
to use. The VRF name is case sensitive and can be a
maximum of 32 characters..
Purpose
Enters global configuration mode.
Selects the port channel that you want to put into the vPC
to connect to the downstream switch, and enters interface
configuration mode.
Configuring Virtual Port Channels

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents