1 / 45

Network Transition

Network Transition. Matt Zekauskas Internet2 Community Design Workshop 15, 16 June 2006 Indianapolis, IN. Transition: what it means to me. Moving existing IP-level connectivity from current Abilene to the new network 15 month horizon

helia
Download Presentation

Network Transition

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Network Transition Matt Zekauskas Internet2 Community Design Workshop 15, 16 June 2006 Indianapolis, IN

  2. Transition: what it means to me • Moving existing IP-level connectivity from current Abilene to the new network • 15 month horizon • Moving routers from Qwest space to Level3 space, and using our own OC192’s instead of Q-Wave OC 192s • Re-homing connectors to Level3 space

  3. Caveats • Any specific examples herein are just that – examples • The real plan will be built with your input • Many things may change, e.g., sequencing, number of routers, router placement

  4. Overview • Current assumptions • A snapshot of what this might look like • What do we need to know

  5. Assumptions • Re-use existing Juniper T-640s • Similarly, core links left as OC 192 for now • Reduction in number of routers possible because of flexible optical network, fewer connectors due to aggregation • For now, assume 8 routers: • NYCM, CHIN, DNVR, STTL, LOSA, HSTN, ATLA, WASH • Drops IPLS, KSCY, SNVA • Another possibility is 9, replace DNVR with Salt Lake & KSCY; there are others

  6. Generic Plan • Ensure optical plant built to target location(s) • Place router in Level3 space • Use temporary fiber + optical gear to patch between Qwest and Level3 space • Use optical plant to attach to adjacent routers that currently exist in Level3 space with our own OC 192’s

  7. Generic Plan Example: Los Angeles Qwest Level3 SNVA STTL, DNVR via SNVA Infinera T-640 ADM HSTN conn. HSTN via SAN

  8. Generic Plan Example: Los Angeles Qwest Level3 SNVA STTL, DNVR via SNVA Infinera T-640 T-640 ADM HSTN conn. HSTN via SAN

  9. Generic Plan (cont) • Patch between Qwest & Level3 space • Move connectors that can move to Level3 space easily (or have been scheduled appropriately) • Patch connectors that need additional time to move • Temporarily patch Qwest backbone circuits to adjacent routers in Qwest space

  10. Generic Plan Example: Los Angeles Qwest Level3 SNVA STTL, DNVR via SNVA Infinera T-640 T-640 ADM HSTN conn. HSTN via SAN

  11. Generic Plan Example: Los Angeles Qwest Level3 SNVA STTL, DNVR via SNVA Infinera T-640 T-640 ADM HSTN conn. HSTN via SAN

  12. Generic Plan Example: Los Angeles Qwest Level3 SNVA STTL, DNVR via SNVA Infinera T-640 T-640 ADM conn. HSTN HSTN via SAN

  13. Generic Plan (cont) • Router in Qwest space can now be decommissioned, and reconfigured for the next installation • Abandoned Qwest backbone circuits can be released back to Qwest • Once all peers and connectors are homed to Level3 space, remove temporary optical gear and release fiber

  14. Generic Plan Example: Los Angeles Qwest Level3 SNVA STTL, DNVR via SNVA Infinera T-640 T-640 ADM conn. HSTN via SAN

  15. Generic Plan Example: Los Angeles Qwest Level3 STTL, DNVR via SNVA Infinera T-640 T-640 ADM conn. HSTN via SAN

  16. Example: Los Angeles Qwest Level3 STTL, DNVR via SNVA Infinera T-640 T-640 ADM conn. HSTN via SAN

  17. Strawman: East to West… Just an example to generate ideas

  18. Strawman – East to West What this doesn’t show • Connector sequencing (when they might move to new router locations) • When we can pull optical gear out of Qwest locations • Exact geographic locations

  19. Strawman – East to West Key • Juniper router on today’s Abilene • Juniper router on new infra. • Optical gear • Cross-connect / Jumper • Qwest OC 192 • NewNet OC 192 (reuse of hw)

  20. Strawman – East to West

  21. Strawman – East to West

  22. Strawman – East to West

  23. Strawman – East to West

  24. Strawman – East to West

  25. Strawman – East to West

  26. Strawman – East to West

  27. Strawman – East to West

  28. Strawman – East to West

  29. Strawman – East to West

  30. Strawman – East to West

  31. Strawman – East to West

  32. Strawman – East to West

  33. Strawman – East to West

  34. Strawman – East to West

  35. Strawman – East to West

  36. Strawman – East to West

  37. Strawman – East to West

  38. Strawman – East to West

  39. Strawman – East to West

  40. Strawman – East to West

  41. Community input

  42. What do we need to know? Key questions: • If you are already in Level3 space • Where? • Dark fiber? Lit? • What constraints do you have on a move? • Can we together generate a mutually acceptable schedule?or • When do contracts for Qwest PoP access circuits expire? • Early adopters will likely determine schedule

  43. What do we need to know? • Would you be able to move up? • 1G? • 10G? • Do you have any fiber between Qwest pops with Abilene routers and the local Level3 PoPs? • We have some in the HOPI cities (LOSA, STTL, CHIN, NYCM, WASH)

  44. Other Questions • If you have a small-ish connection, have you considered working with others in your region to aggregate? • Redundancy needs in the future? • Commercial access desires?

More Related