Book Image

Cisco ACI Cookbook

By : Stuart Fordham
Book Image

Cisco ACI Cookbook

By: Stuart Fordham

Overview of this book

Cisco Application Centric Infrastructure (ACI) is a tough architecture that automates IT tasks and accelerates data-center application deployments. This book focuses on practical recipes to help you quickly build, manage, and customize hybrid environment for your organization using Cisco ACI. You will begin by understanding the Cisco ACI architecture and its major components. You will then configure Cisco ACI policies and tenants. Next you will connect to hypervisors and other third-party devices. Moving on, you will configure routing to external networks and within ACI tenants and also learn to secure ACI through RBAC. Furthermore, you will understand how to set up quality of service and network programming with REST, XML, Python and so on. Finally you will learn to monitor and troubleshoot ACI in the event of any issues that arise. By the end of the book, you will gain have mastered automating your IT tasks and accelerating the deployment of your applications.
Table of Contents (17 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Using IPv6 within ACI


Implementing IPv6 is very simple compared to traditional IOS routers. It is so simple that Cisco has not even made any distinction between IPv4 addresses and IPv6 addresses in the GUI. 

How to do it...

We will add another subnet to TenantA. This time, it will be an IPv6 subnet.

  1. Navigate to TenantA | Networking | Bridge Domains | TenantA-BD | Subnets.
  2. Click on Actions and select Create Subnet.

 

 

  1. Enter the IPv6 address and subnet mask.
  1. Click on SUBMIT.

How it works...

The new IPv6 subnet is added in the same way that we added IPv4 subnets. 

As you will have noticed from the other recipes in this chapter, routing with IPv6 is treated no differently to IPv4 routing--there is no graphical distinction between the two.

If we switch to the command line, using the NX-OS CLI, we can see that the subnets are all configured in one area (just SSH to the APIC controller):

apic1# sh run tenant TenantA
# Command: show running-config tenant TenantA
 tenant TenantA
   vrf context TenantA_VRF
 ...