410 likes | 580 Views
Sponsors. tech•ed backstage 2010. David Connors – Codify Jorke Odolphi – Microsoft Ben Parker – Parker Tech. Agenda. Hello and Welcome! Wi-Fi IPv4 / IPv6 DemoNet & the IPv4 Legacy Vendors and Vendon’ts and The Jiggle Test. Who’s who in the zoo?. Jack Morton Worldwide
E N D
Sponsors tech•ed backstage 2010 David Connors – Codify Jorke Odolphi – Microsoft Ben Parker – Parker Tech
Agenda • Hello and Welcome! • Wi-Fi • IPv4 / IPv6 • DemoNet & the IPv4 Legacy • Vendors and Vendon’ts and The Jiggle Test
Who’s who in the zoo? • Jack Morton Worldwide • Plus a zillion other vendors for A/V, signage, food, etc. • Jomablue • Technology Project Management & Logistics • Codify • Architecture, engineering and hard nerd questions • Jorke / Parker Tech Collaboration • DemoNet
Commissioning – We’ve heard of it! • WiFi Commissioning tips: • How to do it • Never let your standards drop • Take responsibility for the quality of your work
become a wifi expert in 15 minutes (apparently) IEEE 802.3 Ethernet • CSMA/CD • Various physical layers and speeds • Half or Full Duplex • Uses copper wires and electricity • Installers use expensive Fluke testers and do their job properly IEEE 802.11 WLAN • CSMA/CA • Various physical layers and speeds • Half Duplex • Uses luminiferousaether and juju magic • Installers talk gak at you, take all your money and don’t do their job properly
OMFG! Real World Tests! • Post Installation DOs • Run some file transfers! • With quiet RF and good gear you CAN get 100% throughput ALL THE TIME – NO REALLY!! • Post Installation DON’Ts • Check noise-floor and produce 200 pages of BS from AirMagnet and run • Use iPerf for contrived/useless results
Analysing RF Utilisation Wi-Spy DBx
2006: Post Install Real World Tests • Confirmed: • ~2500 kilobytes per second from the Internet to a WiFi client • Test done at each access point • Performed periodically throughout the event
2008: Same Process ... WTH?! • Yep, same commissioning procedure and testing: • Same RF survey and post install commissioning • Same physical equipment • Same configuration scripts • What happened?
2008: Symptoms • With light-medium load: • Everything worked fine! • Great performance! • With medium-heavy load (meal breaks): • Associations looked fine • Clients would get 169.254.x.x addresses • Clients with existing leases worked fine
DHCP • DHCPDISCOVER • Client -> Broadcast • Locate all DHCP Servers on the Network DHCPOFFER DHCP Server(s) -> Client Offer a lease DHCPREQUEST Client -> DHCP Server DHCPACK DHCP Server -> Client
One ... minor ... difference • Technology Operation located in G01 • Cable run too long for copper • Options • A) Drill into car park, run fibre = ~$5K • B) Traverse the Procure gear in the venue • Cheap = Bad
Example 1: Hall5 • DHCP request dispatched from Hall 5 South-West • Note: • The request is immediately repeated on the port by the SCEC switch a few ten thousandths of a second later. There should be only one request every few seconds. • The next slide shows what was received in G01.
Example 1: G01 • DHCP request received from Hall 5 South-West after SCEC core switch traversal • Note: • The DHCP transaction IDs match the previous slide so this is the same request. • The data that leaves the SCEC edge does not match what was sent! There are many times more packets received in G01! • In some cases there are 12 packets received in G01 when only one was sent by the client at the given time!
Example 2: Coalescing and delay of DHCP requests Note DHCP requests are still duplicated in pairs Initial request. Second request made five seconds later Third request made after eight seconds (due to DHCP back-off + slight randomisation as per the RFC)
Example 2: Coalescing and delay of DHCP requests G01 receives multiple requests a few 10000ths of a second apart.
Turn off DHCP Snooping on SCEC Core Correct behaviour: Non-duplicate DHCP Request / ACK pair Correct behaviour: Non-duplicate DHCP Request / ACK pair Correct behaviour: Non-duplicate DHCP Request / ACK pair Correct behaviour: Non-duplicate DHCP Request / ACK pair
2009/2010 – GCCEC • Cisco WLC 4404 of DOOM • Extensive Rectification • Nearly killed me • Described in detail at: • http://www.msteched.com/2010/Australia/VOC208 • http://www.techedbackstage.net/tag/wireless/
Logical Overview OTW Customer Premise Equipment Telstra Customer Premise Equipment OTW TID ADVA 3750 48T 1GBPS 1GBPS 3550 12 G IDF (there are 13 of these) 2970 2GBPS LACP TRUNK 3550 12 G 3550 12 G 3550 12 G 3550 12 G
IPv4 & IPv6 • Why?
hmmm 1. Turn multicast on to enable ipv6 RA 2. Ignore random ipv4 option that would lead you to believe this setting does not affect v6 3. Enjoy the loss of fail-over if the WLC dies because you are enabling ipv6’
poc lab 100% Windows routing. statefull & stateless config RA disabled even though enabled through gui… netshinterface ipv6 set interface <int> advertise=enabled netshinterface ipv6 set interface <int> advertisedefaultroute=enabled ipnat.sys old
the event /48 assigned from apnic 2001:dfb::/48 /64 network segments for delegate/production/management
the event Cisco 2811’s replaced 2008r2 servers 2 hours before go live Cisco Wireless LAN Controller blocks multicast by default High end virtualised environment directly connected via ipv6 hosting over 120 virtual machines for demos. A flat network with AD controllers live to the internet – your average MS sysadmin gets scared.. IPv4 regarded as legacy.
traffic IPv4 Traffic: 2TB Highly mixed IPv6 Traffic: 35GB http: youtube/google/facebook smb: misconfigured windows machines CDN’s are still on v4….
World’s Smallest Violin • Vendors and Vendon’ts • Two Words • delete startup-config • The Jiggle Test • 120+ hour work weeks (here’s a hint: never work out your hourly rate)
DemoNET 24 x HP BL460c Blades (4 Enclosures, 2 Racks): 8 x Highly Available Hyper-V Clusters (16 Servers) 1 x Highly Available Hyper-V SP1 Beta Cluster (2 Servers) 4 x Standalone Hyper-V 2 x Windows 7 Total 119 VMs: 35 Showcase VMs 72 VMs (36 Sessions) The numbers
DemoNET The layout
DemoNET IPv6: The world is accessible! Public (Route) address space IPv4: Legacy network Public (Route) and Private (NAT) address space The network (IPv6 is King)
DemoNET The network – pt2
DemoNET SYD/SIN/TPE > BNE Over The Wire Environment build (~30 days effort, 10 calendar days) Showcase and Speaker VM (imports) BNE > GCCEC Showcase prep Go live Logistics
Session Title Question and Answer Time
Related Content • http://www.techedbackstage.net/ • http://www.msteched.com/2010/Australia/VOC208
Thanks For Listening! Sponsors Be sure to submit your feedback if you want to be in the draw to win the Xbox 360 and other prizes!