Cisco TechAdvantage Webinars Creating the Network at Cisco Live Orlando: Technical Case Study Patrick Warichet: Core Design and Switching Backbone Ryan D’Souza: Wireless Design Joe Clarke: Network Management Jason Davis: Network Management and Automation We’ll get started a few minutes past the top of the hour. Note: you may not hear any audio until we get started.
48
Embed
Creating the Network at Cisco Live Orlando: Technical Case Study TechAdvantage Webinar
Have you ever wondered what is involved building and tearing down a network in the span of a week? We will give you an inside view into the Cisco Live Orlando event network, the technologies used, and the Network Operations Center or NOC that managed it.
The Cisco Live network is one of the most critical elements of the conference. It requires hundreds of access switches (wired), access points (wireless), and provides network services like load balancing, IPv6, and network monitoring to meet the constant needs of attendees.
Cisco engineers and experts Joe Clarke, Jason Davis, Ryan S D'Souza, and Patrick Warichet will share their area of expertise and role they played from the overall architecture and design to routing, switching, wireless, network management and automation.
In addition, we will cover what worked, best practices followed and statistics from the event. You will benefit from hearing what we did, how we did it and what we learned, all over the course of the week! Download the WebEx Replay at: https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=EC&rID=72318727&rKey=349eabd73f199d04
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Cisco TechAdvantage Webinars Creating the Network at Cisco Live Orlando: Technical Case Study
Patrick Warichet: Core Design and Switching Backbone Ryan D’Souza: Wireless Design Joe Clarke: Network Management Jason Davis: Network Management and Automation
We’ll get started a few minutes past the top of the hour.
Note: you may not hear any audio until we get started.
§ UCS release (2.1.1a) provides support for multi-hop FCOE capability – “FCOE uplink port” supported on both FI 6100 and 6200 (native ports + extension
module ports for both models)
§ Nexus 7000 is a Director Class FCOE platform: supports FCOE with F1 (NX-OS 5.2), F2 (NX-OS 6.1.1) and F2E (NX-OS 6.1.2) series line cards: – F1 with SUP1 or SUP2/SUP2E – F2/F2E with SUP2 or SUP2E (SUP1 not supported in this case) – ETH or FCOE ports on F1/F2/F2E (no FC port)
§ VSS Quad-Sup SSO and Multi-chassis Etherchannel (10 / 40 GE links)
§ Routing protocols - OSPF and BGP for IPv4 and IPv6
§ Network Management - SNMPv3,
Control Plane Policing, Syslog, etc.
§ Flexible NetFlow on Sup2T for IPv4 & IPv6 traffic
§ Multicast
22
1 Terabyte of Multicast traffic during the show Vlan361 is up, line protocol is up <SNIP> L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 741428621 pkt, 1009825781802 bytes L3 out Switched: ucast: 5 pkt, 590 bytes - mcast: 0 pkt, 0 bytes 741429788 packets input, 1006860549402 bytes, 0 no buffer
Snapshot from ‘show version’ on the Core switch: 4 Virtual Ethernet interfaces 108 Gigabit Ethernet interfaces 116 Ten Gigabit Ethernet interfaces 4 Forty Gigabit Ethernet interfaces
§ Split-brain mode on Distribution switch (10GE/40GE mixed mode)
40GE ports to the Core, and 10GE to the Access on the same module hw-module switch 1 slot 1 operation-mode port-group 2 TenGigabitEthernet hw-module switch 2 slot 1 operation-mode port-group 2 TenGigabitEthernet
§ Multi-chassis Etherchannel between Core and Distribution VSS
Tweet information from IOS using EEM and Twitter's API Follow it CiscoLive NOC @CiscoLive2013 Download the code from https://supportforums.cisco.com/docs/DOC-19363
§ All devices managed with SNMPv3 authPriv (SHA / DES) § Prime NAM used to traffic volume and utilization
§ Flexible NetFlow sent from the 6500 core and distribution switches to FreeBSD VM “exploder” which forwarded to other collectors (Prime Infrastructure, Prime NAM, StealthWatch, and Plixer [WoS])
§ Syslog sent from all devices to FreeBSD then forwarded to interested parties