资源预览内容
第1页 / 共17页
第2页 / 共17页
第3页 / 共17页
第4页 / 共17页
第5页 / 共17页
第6页 / 共17页
第7页 / 共17页
第8页 / 共17页
第9页 / 共17页
第10页 / 共17页
第11页 / 共17页
第12页 / 共17页
第13页 / 共17页
第14页 / 共17页
第15页 / 共17页
第16页 / 共17页
第17页 / 共17页
亲,该文档总共17页全部预览完了,如果喜欢就下载吧!
点击查看更多>>
资源描述
Click To Edit Master Title Style,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Maintenance Challenges,Mike Hughes,The Challenge,Significant amounts of maintenance on both LANs,Complete upgrade of Extreme LAN hardware,Major upgrade of Foundry LAN(RX16s),Reconfiguration of backbone rings in both LANs,Deploying MRP2 on Foundry,EAPSv2 on Extreme,“Chains of dependencies,Would be a total of between 14-16 slots,It would take ages!,Maintenance is usually one,occasionally two slots per week,minimum 7 days notice,Plus,only one LAN at once to minimise risk,Would take between 3 and 4 months,Not accounting for failures/backouts,Would cause delays of an additional week per backout,Oh,and we needed to get it done sooner!,High demand for 10G ports!,Intense Approach,Block out whole weeks for maintenance,Allowing between 1 and 4 slots each week,Alternate between Foundry and Extreme,Allowing changes to settle in,Ability to rapidly reschedule(24 hours)for maintenance which overran or had to be backed out,Hire in external hands to assist,Reduce direct stress on LINX staff,Ensure“backup crew available next day,Breaking the News,First get your colleagues on side,Then,break it to your members!,Surprisingly well received,Especially given the“otherwise well still be finishing this in September situation,It seemed it would only cause significant problems for one member(using DNS-based load distribution),We even managed to mitigate some of that,Scheduling,6 new switches,All complete box swaps,One hard cutover,5 staggered migrations,2 different software upgrades,Involving 6 different switches,New inter-site fibre delivery,Backbone reconfiguration,Little opportunity to build“greenfield,Weekly Breakdown,Weekly Breakdown,We broke the“news to the members here,Weekly Breakdown,This window had to be backed out,Weekly Breakdown,This window had to be backed out,Weekly Breakdown,We retried using different code next day,Weekly Breakdown,and the rest two days later,Afterthoughts,The blocking out of whole weeks for maintenance worked,Especially when we could quickly reschedule that maintenance work which got backed out,Otherwise,wed have had at least 7 days“slip,The intensive approach worked,We havent had to raise a scheduled maintenance ticket until this week!,Prevented network operating for extended periods in“transitional state,What we started with,What we ended up with-Foundry,What we ended up with-Extreme,Any questions?,
点击显示更多内容>>

最新DOC

最新PPT

最新RAR

收藏 下载该资源
网站客服QQ:3392350380
装配图网版权所有
苏ICP备12009002号-6