• Nexus Dashboard
  • USER: admin
  • PASS: cisco.123
  • ND Web interface
  • Switch Login
  • USER: admin
  • PASS: cisco.123
  • staging-spine1: 10.15.1.11
  • staging-leaf1: 10.15.1.12
  • staging-leaf2: 10.15.1.13
  • staging-leaf3: 10.15.1.14
  • staing-ext-rtr: 10.15.1.15
  • prod-spine1: 10.15.1.18
  • prod-leaf1: 10.15.1.19
  • prod-leaf2: 10.15.1.20
  • prod-leaf3: 10.15.1.21
  • prod-ext-rtr: 10.15.1.22
  • GitLab Server
  • USER: pod01
  • PASS: c1sco.123
  • Gitlab
  • Test VM Login
  • USER: cisco
  • PASS: cisco.123
  • staging-server1: 10.15.1.16
  • staging-server2: 10.15.1.17
  • prod-server1: 10.15.1.23
  • prod-server2: 10.15.1.24
  • Code-Server
  • address: https://10.15.0.161:8443/?folder=/home/pod01/workspace
Trigger CD Pipeline
CI/CD

Trigger CD Pipeline

In this part of the lab you will trigger the CD pipeline to automatically build the entire production fabric using GitLab

Step 1 - Navigate to the Merge Request

To open the merge request page:

  1. Click !# in the text Related merge request !# to merge stage



Step 2 - Merge the Request

On Merge Request details page:

  1. Click Merge



Step 3 - Navigate to Continuous Delivery Pipeline for Prod

Once code is merged, a new CD pipeline is triggered:

  1. Locate the new pipeline that was triggered
  2. Click the Pipeline number



Step 4 - Wait Until Pipeline is Finished

While the pipeline is running click on deploy_on_prod to see the various Ansible roles run against the Production Fabric to build it out using the CD Pipeline!

  1. Click on deploy_on_prod





This step will take around 14 mins to complete

This deploy_on_prod and verify_on_prod are doing the following:

  • The deploy_on_prod runs the build_fabric.yml script against the production fabric.
  • The verify_on_prod runs the verify_fabric.yml script against the production fabric.
  • This is effectively taking all of the scripts you built earlier for the staging fabric and runs them against a new target host file for the production fabric to build out your new production fabric using the CD pipeline in GitLab!


Step 5 - Login to Nexus Dashboard and Verify the New Production Fabric

In your browser, navigate back to your NDFC instance. If needed login using your username and password:

  • Username: admin
  • Password: cisco.123

Check fabric-prod

This time open the fabric page and check fabric-prod, NOT fabric-stage. Remember the CD pipeline pushes changes to the production fabric.

Navigate to LAN Fabrics page and Click fabric-prod, and verify production fabric is configured:

  1. Verify fabric-prod and external-fabric-prod have been created by the pipeline execution
  2. Double-click on fabric-prod



  3. Examine your prod fabric's Overview page. You should see a total of 4 switches, 2 L2VNIs (Networks), and 1 VRF.



  4. Click on Switches to view the switches added to your prod fabric and where the overlay configuration was configured



  5. Click on VRFs to view the VRFs added to your prod fabric. As you can see, it is the identical configuration intent you tested with your staging fabric.
  6. Double-click AnsibleVRF



  7. Click on VRF Attachments to view the VRF attached to your prod leaf switches.
  8. Verify VRF deployment to your three switches



  9. Click on Networks to view the Networks added to your prod fabric.
  10. Verify the networks deployed to your swithces
  11. Double-click AnsibleNet1



  12. Click on Network Attachments to view the Networks attached to your prod leaf switches.
  13. Verify networks deployed to your leaf switches
  14. Close your Network Overview



  15. Close your VRF to return back to the main prod fabric