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
Multicast PIM on UDL: –SFC, AIT, ASTI (4 th 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
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]
QoS Policy Proposal Priority order 1.[S1] 2.[S3] 3.[P1] 4.[P2][S2] How much bandwidth? Implementation schedule?
Technical Issues What software to use? –DUMMYNET –altq Partners experience?
What we want Priority control –DUMMYNET –Altq Traffic shaping –Limit unicast when there is multicast Bandwidth reservation
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
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
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 ITBs latter half (24.64/28) Move AIT to ITBs 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@
C-band Address Change Plan Needs /29 x 5 NUOL: reserve address, postpone action ASTI: 26.96/29 (its up to SFC) TP: 26.104/29 (its 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 (its up to SFC) Schedule: after 7/2 (lets work on schedule!)
C-band Address Change Plan Reclaiming, New prefix: –22.214.171.124/28 ASTI NOC –126.96.36.199/28 USM NOC –188.8.131.52/28 TP NOC –184.108.40.206/28 IOIT NOC Schedule: same time with satellite link renumbering if it is convenient
Policy Routing ASTI: HTTP traffic; updates from bio- mirror (need specifics) ITB: no change on request IOIT: no request at this moment
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
AI 3 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?
Requests from Suguru –Webdav, for sharing PPT –Contact information (MoU, operators) –For visitors: Products and Publications Mission statement Organization structure Contact info Events
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)
Your consent to our cookies if you continue to use this website.