CampusGigaPoP IPv6

1
Campus/GigaPoP IPv6

• Addressing, Software Versions, Topology Issues,
  DNS Support, Traffic

2
Campus Addressing

• Most sites will receive /48 assignments
• 16 bits left for subnetting - what to do with
  them?

EUI host address (64 bits)
Network address (48 bits)
16 bits
3
Campus Addressing

• Sequentially, e.g.
• 0000
• 0001
• FFFF
• 16 bits 65535 subnets

4
Campus Addressing

• Sequentially
• Following existing IPv4
• Subnets or combinations of nets subnets, or
  VLANs, etc., e.g.
• 128.8.60.0/24 003c
• 128.8.91.0/24 005b
• 128.8.156.0/24 009c
• 156.56.60.0/24 vs 129.79.60.0/24?
• 013c or 383c or 9c3c vs 023c or 4f3c or 813c

5
Campus Addressing

• Sequentially
• Following existing IPv4
• Topological/aggregating
• reflecting wiring plants, supernets, large
  broadcast domains, etc.
• Main library 0010/60
• Floor in library 001a/64
• Computing center 0020/55
• Student servers 002c/64
• Medical school 00c0/50
• and so on. . .

6
New Things to Think About

• You can use all 0s and all 1s! (0000, ffff)
• Youre not limited to 254 hosts per subnet!
• Switch-rich LANs allow for larger broadcast
  domains (with tiny collision domains), perhaps
  thousands of hosts/LAN
• No secondary subnets (though gt1
  address/interface)
• No tiny subnets either (no /30, /31, /32)plan
  for what you need for backbone blocks, loopbacks,
  etc.

7
New Things to Think About

• Every /64 subnet has far more than enough
  addresses to contain all of the computers on the
  planet, and with a /48 you have 65536 of those
  subnets - use this power wisely!
• With so many subnets your IGP may end up carrying
  thousands of routes - consider internal topology
  and aggregation to avoid future problems.

8
New Things to Think About

• Renumbering will likely be a fact of life.
  Although v6 does make it easier, it still isnt
  pretty. . .
• Avoid using numeric addresses at all costs
• Avoid hard-configured addresses on hosts except
  for servers
• Anticipate that changing ISPs will mean
  renumbering

9
Router Software Versions

• JUNOS 5.1 and up Line Rate v6 (just turn it on)
• IOS 12.2T and up - for most ISP-type routers
• IOS 12.0(19)ST and up - GSR only
• IOS process-switches IPv6 traffic with the router
  CPU, so beware high traffic loads (though this is
  a good problem to have!)
• No IPv6 support on 65xx/76xx or 73xx yet.

10
Topology Issues

• V6 in a production network

11
Layer-2 Campus1 Switch
Bldg Switch
Big Core Switch
Bldg Switch
Bldg Switch
Big Core Router
12
Layer-2 Campus1 Switch
Bldg Switch
Big Core Switch
Bldg Switch
Bldg Switch
Big Core Router
Small v6 Router
13
Layer-2 Campus2 Core Switches
Bldg Switch
Bldg Switch
Bldg Switch
Big Core Switch
Big Core Switch
Big Core Router
Big Core Router
14
Layer-2 Campus2 Core Switches
Bldg Switch
Bldg Switch
Bldg Switch
Small v6 Router
Big Core Switch
Big Core Switch
Big Core Router
Big Core Router
15
Layer-3 Campus
Bldg Router
Big Core Router
Bldg Router
Bldg Router
Border Router
16
Layer-3 Campus
Host with 6to4
Bldg Router
Big Core Router
Bldg Router
Bldg Router
Border Router with 6to4
17
Edge Router Options
Host v4/v6
Bldg Switch
VLAN2
VLAN1
Switched Core
Bldg Switch
VLAN1
Host v4-only
VLAN1
VLAN1
VLAN2
Commodity Router v4-only
Internet2 Router v4 and v6
18
Routing Protocols

• iBGP and IGP (RIPng/IS-IS)
• IPv6 iBGP sessions in parallel with IPv4
• Static Routing
• all the obvious scaling problems, but works OK to
  get started, especially using a trunked v6 VLAN.
• OSPFv3 is coming
• It will run in a ships-in-the-night mode relative
  to OSPFv2 for IPV4 - neither will know about the
  other.

19
DNS Issues

• BIND Versions
• All modern versions of BIND support AAAA
• BIND9 can use IPv6 transport for queries
• IPv6 root servers
• ip6.int vs. ip6.arpa
• ip6.arpa is in the roots.

20
Equipment Needs

• Tunnel Router (Cisco 2600) 2,000
• A router with two Ethernet interfaces is best, to
  avoid one-armed routing.
• Workstation Linux Box 1,000
• For testing and demonstrations, any old cast-off
  Pentium will get you going. . .

21
Future Needs

• Routers better v6 support, new features, speed
• Servers Dual-Stack, Application support
• Topology Border/Core Designs

22
Traffic

• Not much - this graph is of IPv6 NNTP traffic
  between UO and NYSERNet on June 20, which at the
  time was the only non-routing-protocol v6 traffic
  over Abilene. There are a few other occasional
  tests, but WE NEED MORE TRAFFIC!

23
Contacts

• Internet2 IPv6 Working Group
• ipv6.internet2.edu
• Grover Browning
• gcbrowni_at_iu.edu
• Abilene NOC
• noc_at_abilene.iu.edu