Modern Data Center needs 10 th of April, Andrew Sedman, RCDD Head of Training and Technical Service R&M

Transcription

1 Modern Data Center needs 10 th of April, 2014 Andrew Sedman, RCDD Head of Training and Technical Service R&M

2 From the Classical Data Center to the Cloud Prior to cloud computing, a physical server handled individual applications In the cloud, physical servers are merged in a server cluster, and VMs are at applications disposal The computing power, storage and bandwidth used by these applications is still provided by the physical infrastructure

3 Classical vs. Virtualized Source: VMWare One OS per machine Software and Hardware are tightly bound to each other Resources are not fully utilized Inflexible and expensive infrastructure Hardware independent of OS and application VMs can be allocated to each system Optimized resources Flexible infrastructure

4 The Drivers in Data Center Networks Virtualized data centers and clouds have to be equipped with physical networks that accommodate a broad spectrum of IT requirements: Maximum throughput Minimum latency Maximum availability Quick deployment Visibility and manageability of the infrastructure Space limitations Application-specific cabling

5 Typical Cost Structure of Data Center 4%

6 Impact of Bad Networks 65% of system outages are related to cabling. Gartner 85% of SAN trouble tickets are caused by cabling. Brocade IT: 100 ms page load delay costs Amazon 1% sales (corresponds to 450m in 2012) Financial services: Outage of trading house test SAN after migration to 16GFC (potential damage: 3m per hour) Research institutes: Poor cabling can even revolutionize physics

7 Impact of Bad Networks Cabling is about 4% of the overall network cost But these 4% can keep the remaining 96% from operating properly and efficiently

8 Challenges Actions Result Curb Costs Virtualize Meet Bandwidth Requirements Ensure Availability We are down. Improve Network More Efficiency End-to-End Knowledge and Control Better ROI Reduced Power Monitor & Manage

9 MPO Description MPO = Multi Path push On or Multi fiber Push On IEC & TIA/EIA defined multi fiber connector with push-pull interlock, sliding sleeve and two alignment pins either side of the multiple fibers Ferrule Pin Hole F F Male Female

10 MPO Description Typically 12 or 24 MPO Upto 72 fibers in one MPO Optical Receiver MPO Connector Fiber Position Optical Transmitter MPO Connector Rx Rx Rx Rx Tx Tx Tx Tx Tx Tx Tx Tx Rx Rx Rx Rx Optical Transmitter MPO Connector Optical Receiver MPO Connector 12 fiber red = Send green = Receive 24 fiber

11 MPO Description Plug and play solution Quick, low risk installation SM too expensive, OM3/OM4 still cheaper Future connectivity options for 40G/100G No more jumbles of cables in raised floors. MPO base ensures effectiveness for the future. MPO modules and adapter plates can be retrofitted with AIM, making ports perfect to document. Trouble-free replacement of individual components Cabling changes can be carried out without inhouse team.

12 Quality requirements Fibers glued into ferrule body Accurate central positioning crucial Two main errors can occur: Angle error (angle of deviation) Radial displacement (concentricity) Separate MT ferrule from housing Allows longitudinal adjustment and interferometric measurement CANNOT BE TERMINATED ON-SITE

13 Quality requirements EN core dip tolerances Natural occurance during endface polishing Polishing geometry of all 12 endfaces Core Cladding Air Cladding Core Cladding Cladding

14 Quality requirements EN fibre protrusion Spring loaded ferrules Endface pressure during contact 100% testing Laboratory conditions Quality MPO connectors

15 MPO Method A Duplex Connectivity Parallel Connectivity

16 MPO Method B Duplex Connectivity Parallel Connectivity

17 MPO Method C Duplex Connectivity Parallel Connectivity No clear migration path

18 MPO/MTP Type S

19 MPO/MTP Type S

20 Infrastructure Management Abbreviation Jungle FMS = Facility Management System All above named examples will monitor, log and trigger alarms! ANM = Automated Network Monitoring

21 Infrastructure Management: Key aspects Highest availability Business processes are highly dependent on availability of a running network Configuration Management Database (CMDB) TIA/EIA 606-A ITIL AIM Documentation Reporting SOX Basel III Economical aspects Efficient installation and move, add and change process (IMAC) Transparent and documented network Financial aspects Cost reduction (Less downtime) Labeling & Inventory Mgmt ISO Managed & Secured Services Disaster Recovery / Fault & Problem Management Risk Management, ITIL, BASEL III, SOX Up-to-date document is essential to ensure business continuity

22 Why Automated Infrastructure Management (AIM)? Gartner: 59% of network problems caused by physical layer issues Documentation Accurate manual documentation requires high effort in creation and maintenance Impacts of human errors are significant Patching High failure rate during MAC processes Insufficient work order management Patching mistakes cause of 28% of downtime in data centers (Gartner) Stranded Switch Ports Due to an insufficient documentation up to 40% of all Switch Ports might be unused (Source: Frost & Sullivan)

23 Automated Infrastructure Management: Benefits Software Benefits Centralized database with entire physical infrastructure Controlled changes based on work order management Graphical illustration of network Powerful search and reporting features User permission control Full compliance to ITIL processes Better use of installed capacity With monitoring hardware Real-time physical connectivity monitoring Automatic update of database 100% accurate documentation Automatically keep track of all move, adds and changes Alerts on unsolicited changes

24 AIM Benefits Reduces cost and burden of documentation Provides remote visibility Reduction of Downtime Improved MAC coordination and verification Planned changes are visualized and verified Improved Equipment efficiencies Reduced Disaster Recovery cost Enhanced layer-1 security and accountability

25 AIM Features Improved and timely Diagnostics Holistic Physical Layer circuit traces Floor-plan Displays Graphical Rack Elevations Work-Order (MAC) processes Security enhancement and Rogue detection Network-Attached-Asset management Instant Audits and structured reports Environmental Sensor Monitoring Reduced cost of operation Full regulatory compliance

26 AIM Considerations Cost of Deployment Increased Footprint (in some systems) Restricts Network Architecture/Standards Requires Strict Process Adherence Periodic Audits needed to verify accuracy Is it compatible with Facility drawing formats Interfacing with Facilities work order systems Is it Power Management interfaceable Integration with a Data Center Infrastructure Management (DCIM) Using of open standards for data exchange with 3rd party systems AIM is only a part of a DCIM

27 ISO/IEC 18598: AIM System Requirements, ISO/IEC JTC1/SC25 Data Exchange, Applications Details to ISO/IEC Functional Requirements Integration with other business information and network management systems Data exchange framework Premises / Space Telecommunications equipment and connectivity Organizational elements Work orders Status: Committee Draft

28 Business Value AIM Value Stack AIM Value Stack Accelerated Value Capacity Planning Management Availability Management Asset and Connectivity Management Change Management Resource Management Operations Management

29 AIM Maturity Model Source: Gartner Automated Infrastructure Management Little documentation No standard change process Unrestricted access Outages commonplace No predictability Fragmented, inaccurate documentation High error rates (changes) Reliance on individual heroics Incident firefighting Limited monitoring Central documentation Change management process Limited access Reliable services Energy monitoring and measurement Service-driven approach Charge-back process Intelligent (business) capacity management Infrastructure monitoring strategy Integrated change configuration (CMDB) Eliminate stranded capacity End-to-end analysis Agile infrastructure management Predictive analysis Dynamic infrastructure Manual Reactive Proactive Service Oriented Optimization Operations Focus Business Processes

30 Cost for «Downtime» The average cost of data center downtime was approximately $5,600 per minute. (Gartner) Based on an average reported incident length of 90 minutes, the average cost of a single downtime event was approximately $505,500.

31 Bespoke system not easily adaptable Very costly Not suited to redundancy planning Space hungry Incapable to cooperate with other systems Not fit for purpose AIM of old

32 Retrofittable Cost effective Compact Capable to interact with other systems Now fit for purpose AIM of New

33 Questions?

34 Thank you! Thank you Andrew Sedman Head of Training and Technical Support