1 / 23

Operation BOF

Operation BOF. husni tokyo, 2003/06/21. Agenda. Usage of UDL(15minutes) Redundancy of satellite routers(10minutes) IPv4 Address assignment policy(15minutes) request based return not used address -> use it in each satellite link each satellite link use /29 multicast(10minutes)

ryder
Download Presentation

Operation BOF

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. Operation BOF husni tokyo, 2003/06/21

  2. Agenda • Usage of UDL(15minutes) • Redundancy of satellite routers(10minutes) • IPv4 Address assignment policy(15minutes) • request based • return not used address -> use it in each satellite link • each satellite link use /29 • multicast(10minutes) • Let's use PIM • policy routing(10minutes) • Zebra • Security

  3. Multicast • PIM on UDL: • SFC, AIT, ASTI (4th week of July), ITB (after 7/2, in July), IOIT (need to check) • PIM on c-band BDL: • sfc-sat is ready for PIMD, but not operated • USM: need assistance to configure • No PIM on Ku-band BDL

  4. Announce

  5. UDL Usage Situation • The UDL is getting fully utilized • Need a clear policy for maintaining QoS • Issues: • Shared link • SOI-ASIA use (lectures, sakurafubuki3rd) • Commodity traffic

  6. Toward The Best UDL Usage • Classify traffic • Multicast / Unicast • Partners / SOI-ASIA • Identify priority requirements • Define QoS policy • Technical issues

  7. Traffic Classification [S1] SOI-ASIA lectures [S2] SOI-ASIA related traffic (web, etc.) [S3] Sakurafubuki3rd [P1] Policy routed traffic [P2] UDL prefix’s generated traffic

  8. Priority Considerations • SOI-ASIA multicast traffic [S1][S3] is for everyone • not 24x7 • Policy routing [P1] is to be operational • There is no need to generate unnecessary traffic from UDL prefixes • can be policy-routed easily [P2] • limit the use to certain clients [S2]

  9. QoS Policy Proposal • Priority order • [S1] • [S3] • [P1] • [P2][S2] • How much bandwidth? • Implementation schedule?

  10. Technical Issues • What software to use? • DUMMYNET • altq • Partner’s experience?

  11. What we want • Priority control • DUMMYNET • Altq • Traffic shaping • Limit unicast when there is multicast • Bandwidth reservation

  12. Satellite Routers Redundancy • Current: • Cisco bridging mode (except SG: schedule Mid. July ~ Aug) • sfc-sat serves as the single router (use 4-port ethernet) • P2P netmask /30 • Next: • Cisco bridging mode (except SG) • Add another sat router: sfc-sat2 • P2P netmask /29

  13. Redundancy: Issues Add sfc-sat2 IPv4 address usage • some sites have low address utilization

  14. Address Change Schedule • JPN: • /29 x 7 • Change /30 x 7 into /29 x 3 • Need /29 x 4 = /28 x 2 • DNS issues • USM: no problem • IOIT: no problem • AIT: no problem • ITB: no problem • ASTI: no problem • TP: no problem

  15. Ku-band Address Change Plan • NARA-AIT 24.232 /29 • NARA-ITB 24.224/29 • Relocate NAIST-SFC ATM P2P VLAN (24.240/30) • Grab ITB’s latter half (24.64/28) • Move AIT to ITB’s latter half (24.80/28) • Schedule (need to coordinate) • Naist: 2 weeks from now • AIT: wait for Yoo comes back from France • ITB: after 7/2 • After 7/2, plan through ai3-ix@

  16. C-band Address Change Plan • Needs /29 x 5 • NUOL: reserve address, postpone action • ASTI: 26.96/29 (it’s up to SFC) • TP: 26.104/29 (it’s up to SFC) • USM:25.176/29 (no expected date for link to come back, do it right after 7/2 is ok?) • IOIT: 25.184/29 (it’s up to SFC) • Schedule: after 7/2 (let’s work on schedule!)

  17. C-band Address Change Plan • Reclaiming, New prefix: • 202.249.25.32/28 ASTI NOC • 202.249.25.64/28 USM NOC • 202.249.25.48/28 TP NOC • 202.249.25.80/28 IOIT NOC • Schedule: same time with satellite link renumbering if it is convenient

  18. Policy Routing • ASTI: HTTP traffic; updates from bio-mirror (need specifics) • ITB: no change on request • IOIT: no request at this moment

  19. Multicast • PIMD on UDL: AIT, ASTI (July), IOIT (need to check), ITB (July) • PIMD on C-band BDL: • sfc-sat is ready for PIMD • USM needs assistance on PIMD • No PIMD on Ku-band BDL

  20. USM EGP Routing • No issues in IPv4

  21. AI3 Website • No detailed from Jun • Events? • Activities? • Publications? • Kotaro will confirm with Jun • SFC will give content example • esp. in operational • propose a template in July • Need topology map from partners • Want the latest version in July • Please renew at site update session • Operational information • Topology map • Tips • Policy routing?

  22. Requests from Suguru • Webdav, for sharing PPT • Contact information (MoU, operators) • For visitors: • Products and Publications • Mission statement • Organization structure • Contact info • Events

  23. Web • For US: • Related organizations & contact points (APAN, Internet2, Star* • Holidays & important days in each country • Operational information • Persons: • Kotaro : in charge for web remake?; confirm with Jun; • Ayumi : helps kotaro • Baba : design? • Easy to update • File uploading areas (webdav)

More Related