The source of this information is open to the Internet and is for personal study only. Please do not commercialize it. If there is any infringement, please contact to delete it. For more information, please visit the official account: Wisdom Solution Library.
Directory
1 General
1.1 Project background
1.2 Basis for preparation
1.3 Feasibility report project composition and research scope
1.3.1 Project Composition
1.3.2 Scope of study
1.4 Project construction period and business satisfaction period
1.5 Brief Conclusion
2 Current situation and demand analysis
2.1 The status quo of IDC's unified operation and management platform
2.2 needs analysis
3 Overall construction scale
3.1 Construction principles
3.2 Platform Positioning
3.3 Overall functional architecture
3.4 Technical Architecture
3.4.1 Container + microservice architecture
3.4.2 WeChat technical architecture
4 Software construction plan
4.1 Service Portal Management
4.1.1 Operation Management Portal
4.1.2 Information Display Portal
4.1.3 Customer Service Portal
4.2 Operation and maintenance management
4.2.1 The entry and exit of personnel and materials
4.2.2 Device restart
4.2.3 Power on and off the cabinet
4.2.4 Jumper construction
4.2.5 Technical Support
4.2.6 Alarm monitoring
4.2.7 Scheme comparison
4.2.8 Work Order Quality Inspection
4.3 Operation Management
4.3.1 Capacity warning
4.3.2 Event Management
4.3.3 Lease management
4.3.4 Business management
4.3.5 Service Management
4.4 Report statistics
4.4.1 TOPN report of computer room resource idle rate
4.4.2 Computer room resource usage report
4.4.3 TOPN Report of Customer Resource Idle Rate
4.4.4 Customer Resource Usage Report
4.4.5 Detailed report of IDC listed equipment
4.4.6 Detailed report of resources released by IDC
4.4.7 Comprehensive statistical report of products
4.4.8 Ranking Statistics of Business Development Units
4.4.9 Trend Analysis of Business Development Units
4.5 Resource Management
4.5.1 Full resource management
4.5.2 Topology Management
4.5.3 Account Manager Management
4.5.4 Resource statistics and management
4.6 System Management
4.6.1 Device configuration management
4.6.2 User and permission management
4.6.3 Log Management
4.6.4 System Device Management
4.7 Requirements for supporting system transformation
4.7.1 Comprehensive capital system
4.7.2 Unified collection system
4.7.3 Centralized fault management platform
4.7.4 EOMS system
4.7.5 ESOP system
4.7.6 OA system
4.7.7 4A system
4.7.8 ESB system
4.7.9 Computer room access terminal management system
5 System software and hardware construction plan
5.1 Resource pool hardware
5.2 Access management terminal
6 Supporting requirements
6.1 Computer room space and power requirements
6.2 Transmission Requirements
6.3 Pipeline requirements
7 Suggestions on construction progress
7.1 Project Completion Time Requirements
7.2 Project Implementation Schedule
1 body construction scale
1.1 Construction principles
1. General principles
In order to ensure the simple and efficient operation of the entire network and balance the distribution of traffic flows, we follow the principles of high-speed link setting and minimum link setting principles, and highlight the light-load design principles of network links, optimize the network structure, and make reasonable adjustments to the traffic , while fully considering and ensuring network redundancy, the network structure design minimizes network changes to achieve bandwidth expansion and optimization, and the network topology design ensures load balancing of router capacity as much as possible. The following principles are followed in the IDC egress bandwidth expansion project:
1) Advanced: In network design, according to user needs and network development trends, the technology adopted is technologically advanced. The high starting point is suitable for large-grained services, and the carrier-grade IDC egress layer, which can realize fixed and mobile unified bearing, fully considers Future demand for new business and new technology development;
2) High availability: Considering the frequent expansion of IDC export equipment, try to use high-bandwidth, high-scalability high-performance data center switches as core node equipment, and at the same time, support high-performance routing protocols, QoS capabilities and high quality communication lines;
3) High reliability: the network system must have disaster recovery and fault tolerance capabilities to ensure that the system can work uninterrupted in unexpected situations; the key components of network equipment must adopt redundant design, support hot swap, and eliminate single point of failure; Backup of network equipment resources and communication lines, and be able to quickly switch between master and backup resources when a part of the system fails;
4) Openness and standardization: network equipment must be open, that is, network equipment that conforms to international standards and can realize the interconnection of products from multiple manufacturers;
5) Scalability: The network system should be able to expand flexibly. It can support future needs through expansion, and can expand the functions of existing network equipment through product upgrades, adopting new technologies, or adding modules.
Scalability is reflected in the following aspects:
l Business scalability;
l Port scalability;
l Scalability of relay rate;
l Scalability of network equipment capacity.
6) Security: The operation of the network should be in a controllable manner to ensure its security; the security of the network should be realized through a centralized control mechanism as much as possible; unauthorized personnel should not be able to enter the network, It is also necessary to implement a hierarchical security control mechanism, and determine their access rights according to the level of specific users;
7) Manageability: the network system should be able to support SNMP, SNMPv2, etc., which is convenient for computer managers to monitor the operation status of the network at any time through the network management software. Once a fault occurs, the error location and cause can be automatically reported; Incorporated into the IDC network management monitoring system.
8) Investment protection: rationally utilize the original equipment, according to the resource utilization of the existing network, dismantle idle time to make up for busy work, protect the original investment interests, and save investment.
2. General principles of software development
1) General requirements
The system follows the principles of openness, safety and reliability, advancement, efficiency, ease of use, maintainability and scalability.
The system construction is based on the industry's open standards, including various network protocols, hardware interfaces, database interfaces, etc., to ensure the vitality of the system, protect investment, and reflect good scalability and interoperability.
The system follows a simple, easy-to-use, and unified Chinese customer interface, provides maintenance management and real-time monitoring functions, and simplifies the use and maintenance of the system.
The system design fully considers the scalability, and can support the expansion of the system in various ways, including the increase of business functions, system upgrade and system expansion.
2) Application software requirements
Real-time: When the system completes various real-time functions, it must ensure the real-time response of the system, including real-time fault monitoring, real-time performance analysis and operation and maintenance.
Security: The system has a multi-level security management mechanism.
Reliability: To avoid the normal and stable operation of the entire system affected by a single point of failure, and to avoid the loss of key management information, it is necessary to have the corresponding system fault tolerance. The entire application software system should be able to work continuously for 7×24 hours. When any module in the application software is updated and loaded, the business operation and service will not be affected under the premise of not updating the interface with the upper and lower modules.
Maintainability: The system has perfect self-monitoring and management functions, and must have fault diagnosis and fault location functions.
Operability: Provide friendly Chinese graphical operation interface and online help. With complete operation rights management function and perfect system security mechanism, it can have detailed records for each operation of each operator, and generate an alarm for each illegal operation; the application software should have a high degree of automation, such as: automatic Task scheduling, automatic fault alarm, automatic task recovery, etc.
Openness: fully consider the interface with other systems.
Scalability: The software design of the system adopts a modular architecture, and the introduction of new functions does not affect the original functional modules, so it must have good scalability.
Normative: follow the relevant norms of China Mobile.
3) Database software requirements
The database system used in the system must meet the following requirements:
Support ANSI/ISO SQL-89, ANSI/ISO SQL-92 standards;
Support Chinese characters internal code, in line with double-byte encoding;
Support the hardware platform and operating system platform of mainstream manufacturers;
Has good scalability;
Support mainstream network protocols (such as: TCP/IP, IPX/SPX, NETBIOS and mixed protocols);
It has good openness and supports mutual visits of heterogeneous databases;
Possess the technologies required to support parallel operations (such as: multi-server collaboration technology, transaction processing integrity control technology, etc.);
Support online transaction processing (OLTP), requiring fast loading of data, efficient concurrent processing and interactive query;
Support database storage encryption and corresponding redundancy control;
Support online storage and backup functions (such as: tape mode, disk mode);
It has strong fault tolerance, error recovery, error recording and early warning capabilities;
It can avoid the occurrence of database deadlock, and once the deadlock can be automatically unlocked.
1.2 Platform Positioning
The enterprise IDC unified operation and management platform will be based on the unified management requirements of the entire network IDC, and centrally present, analyze and manage the IDC operation and maintenance data and related processes of the entire network. The platform focuses on the overall grasp of the IDC resources, performance, and service level of the entire network, and receives necessary data such as resources, performance, alarms, and customer business information transmitted by various professional network management systems, integrated resource management systems, and centralized fault platforms. Unified presentation and analysis. Various basic functions are still in the charge of various professional network administrators, comprehensive resource management systems, and centralized fault platforms.
In this issue, the IDC unified operation management platform will be built and deployed in a centralized way, and it will be connected with the existing IDC operation and maintenance support system to obtain data on resources, assets, capacity, energy consumption, performance, business, operation and maintenance, etc., to realize Unified management of IDC O&M and operations.
1.3 Overall functional architecture
The functional architecture of the enterprise IDC unified operation management platform is shown as follows:
Figure 31 The overall functional architecture of the system
1.4 Technical Architecture
1.4.1 Container + microservice architecture
If the system software provider can deploy based on containers and develop using microservice architecture, it will be in an advantageous position in the subsequent bidding selection.
Figure 32 Schematic diagram of container + microservice technology architecture
The system construction needs to be based on the cloud architecture of virtualization, centralized management, distributed computing and automatic scheduling, which can realize rapid business deployment and flexible application, and adopts a distributed elastic architecture to support horizontal linear expansion of applications.
The system needs to have the evolution capability of container-level and service-level cloudification: the container will be provided by the mobile company's integrated cloud resource pool to provide virtual machine resources; system-related middleware will be provided and deployed by the manufacturer itself (including redis, database, mq, etc.); The container resource scheduling framework implements the scheduling and management of container resources.
The system needs to have the ability to design for the microservice architecture, split and reconstruct modules with mixed functions into single-business, high-cohesion microservice applications, and support business service capability clusters and containerized deployment.
The system needs to support the introduction of "micro-service management and control platform": through the "micro-service management and control platform", the business services that have been micro-serviced can be managed and orchestrated. Service governance and orchestration include: microservice access, registration, release, dependency configuration, service call chain tracking, etc.
1.4.2 WeChat technical architecture
In addition to implementing traditional WEB pages, the portal system of this issue also needs to implement portal services based on WeChat. The page display is realized with the help of WeChat, and the IDC unified operation and management platform needs to realize the interaction with the WeChat platform.
Figure 33 Schematic Diagram of Wechat Terminal Technical Architecture
1. The system needs to provide the service portal support capability of the WeChat terminal. The functions include: information promotion, operational service capability display, process approval, self-service fault reporting, QR code authentication, and customer service requests;
2. It is necessary to apply for the WeChat enterprise official account of the DCIM system during implementation, and select the development mode and provide it for the system to use;
3. The system needs to develop and implement the WeChat portal interface, and interact with WeChat users for various functional data;
4. The business service group provided by the microservice framework (if the microservice framework is not used, then the functional modules of the application layer) provide the data support required by the front-end portal.
The space is limited and cannot be fully displayed. If you like the information, you can forward + comment, and private message for more information.