Here comes iOS 8...

So Apple is about to release iOS 8... Have you done anything special to
your network setup to accommodate the traffic flood ie traffic shaping
rules, cache servers, etc?

I heard that Apple Caching servers won't work with this update, so I'm
guessing it will be pushed through Akamai servers as is usually is.

- Zachary

I've been waiting all morning.
  
Expedited repair of a primary link to prepare for the traffic. Not that it
didn't have multiple backups. But one doesn't trifle with IOS8 release
traffic.. If it's anything like IOS7 was..
  
Nick Olsen
Network Operations (855) FLSPEED x106

For those that are curious, it looks like the download is 1.1 gigs.

-Grant

At first we saw traffic going directly to Apple (swcdn.apple.com) via our
commercial link, then it went to llnw.net, and now it is going to Akamai.

access1-srp#traceroute swcdn.apple.com
Translating "swcdn.apple.com"...domain server (132.206.44.21) [OK]

Type escape sequence to abort.
Tracing the route to geo.buni.guat.aaplimg.com (17.253.2.221)

  1 internet2-vlan677.GW.McGill.CA (132.216.255.107) [AS 17356] 4 msec 0
msec 0 msec
  2 vtelinet-216-66-110-108.vermontel.net (216.66.110.108) [AS 17356] 12
msec 8 msec 8 msec
  3 206.126.115.175 [AS 17356] 12 msec 8 msec 12 msec

Depending on the device used, the zip file can range from

Length: 1515061530 (1.4G) [application/octet-stream]

To

Length: 2119504233 (2.0G) [application/octet-stream]

Parsed from http://mesu.apple.com/assets/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml

Grant,
Do you have a reference? Someone just told me it is more around 5GB.

Later,

I think it requires 5.7G of free space on the device -- but the download is not that big.

The download was ~1.1GB, the installer requires almost 5GB free to proceed.

Tyler.

According to devices I have seen numbers have been between 800MB and 1.3GB

iPhone 4S, iPhone 5, iPad 2 (3G), iPad Air (LTE)

Regards
Alexander

Alexander Neilson
Neilson Productions Limited

alexander@neilson.net.nz
021 329 681
022 456 2326

Someone just told me its 5GB free space needed. That makes sense where
someone could have read it wrong. Thanks.
5GB for for iphone seemed a bit odd.

Slight differences depending on platform. For my 5S, the OTA patch is 1.1GB, and the clean install is 2.05GB. Both compressed, of course.

                -Bill

My reference was the update page in settings said the download was 1.1 gig

Grant

Hi,

Do you have a reference? Someone just told me it is more around 5GB.

It seems to depend on the device. IIRC my iPhone 4S downloaded ±0.9GB and my iPad Mini ±1.3GB. That might be because the 4S is still a 32-bit device.

Cheers,
Sander

FWIW ...

http://techcrunch.com/2014/09/18/ios-8-adoption-off-to-a-slower-start-than-ios-7-say-multiple-usage-trackers/

----------------------------------------
From: "Zachary McGibbon" <zachary.mcgibbon+nanog@gmail.com>
Sent: Wednesday, September 17, 2014 12:59 PM
To: "NANOG" <nanog@nanog.org>
Subject: Here comes iOS 8...
So Apple is about to release iOS 8... Have you done anything special to
your network setup to accommodate the traffic flood ie traffic shaping
rules, cache servers, etc?

I heard that Apple Caching servers won't work with this update, so I'm
guessing it will be pushed through Akamai servers as is usually is.

- Zachary

Interestingly enough, it seems Apple primarily used it's own, new, CDN for the iOS 8 release:

That's we thought and what we experienced but as the day went on they definitely shifted some load to Akamai.

-dan

Dan Brisson
Network Engineer
University of Vermont

[...]

Interestingly enough, it seems Apple primarily used it's own, new, CDN for the iOS 8 release:

Apple chose to handle iOS 8 rollout with own content delivery network | AppleInsider

I noticed same. Moreover, Apple appears to be reaching 701 over
3356/174 in my neck of the woods, which is not the wisest move, due to
congestion, and thus painstakingly slow transfer speeds.

Null routing 17.253.0.0/16 caused downloads to fall back to Akamai,
where performance was quite snappy.

(I'm not saying this is a good idea, or recommended at scale -- just
sharing my observations.)

FWIW,
-a