You are on page 1of 21

Infrastructure Platform Design

Short Form
TA357S

Asset Management Project
Peregrine Asset Center

April 24, 2006

V1.0

Infrastructure Platform Design TA357
V1.0 Asset Management

Table of Contents

1 Introduction................................................................................................................2
1.1 Purpose.................................................................................................................2
1.2 Document Owner...................................................................................................2
1.3 Document Scope...................................................................................................2
1.4 Reference documents...........................................................................................2
1.5 Infrastructure Design Document Signoff...............................................................2
1.6 Revision History.....................................................................................................3
1.7 Delivery Teams Involved........................................................................................3
2 Infrastructure Design................................................................................................4
2.1 Infrastructure Specification....................................................................................4
2.2 Functional Requirements.......................................................................................5
2.3 Non-Functional Requirements...............................................................................7
2.4 Assumptions and constraints.................................................................................7
3 Hardware and Storage..............................................................................................8
3.1 Development / Test Environment Details..............................................................8
3.2 Production Environment Details............................................................................8
3.3 Physical Infrastructure.........................................................................................10
3.3.1 Logical Network Diagram..............................................................................10
3.3.2 Physical Network Diagram.............................................................................11
3.3.3 Bill of Materials..............................................................................................12
3.4 Network................................................................................................................13
3.4.1 Switch Ports, IP Assignments........................................................................13
4 Operation Requirements & Guidelines.................................................................16
4.1 Maintenance Window..........................................................................................16
4.2 Known Problems and Workarounds....................................................................16
4.3 Hardware & Software Vendor Contacts and Contractual Information.................16
5 Appendix..................................................................................................................17
5.1 x346 Server Connectivity Diagram......................................................................17
5.2 v440 Server Connectivity Diagram......................................................................18

Last Modified: 4/17/2018 Page 1 of 22

The design provides information on how to configure and install the infrastructure components for the Asset Management servers.  They will be kept in a common project directory for the life of the project  TELUS BT will always sign-off on any major changes  All groups will sign-off on the original version  Only the groups directly impacted by document changes will be asked to sign-off Group Who Date Docume Qualifie nt d Version (Yes/No) BT Project Manager Calvin Lowe BT Infrastructure Design Dimitar Ivanov BT Architecture Chris Renter BT Windows Manager Roy Brassington BT Asset Management Ken O’Connell Last Modified: 4/17/2018 Page 2 of 22 .2 Document Owner BT IS Infrastructure.4 Reference documents Document From Date Document Version TELUS Internal Asset & Request Management Program Michael England Jun 2005 V1 1. 1.3 Document Scope The document contains detailed diagrams. interface standards. protocols. Infrastructure Platform Design TA357 V1. 1.1 Purpose This document details the TELUS internal portion of the infrastructure for the Peregrine Asset Center component of the Asset Management environment.5 Infrastructure Design Document Signoff This table documents the acceptance of the Design Solution by the involved teams’ representatives. and other details in support of the network and infrastructure components for the Asset Management environment to access the TELUS internal network and resources.0 Asset Management 1 Introduction 1. Infrastructure Design Group. 1.

2006 Initial document create 1.Unix Dimitar Ivanov BT Asset Management Ken O’Connell Last Modified: 4/17/2018 Page 3 of 22 .6 Revision History Version Author Date Revision Details Completed 1.7 Delivery Teams Involved Team Manager Date Sign Of IS Operations – Intel Roy Brassington IS Operations . Infrastructure Platform Design TA357 V1.0 Asset Management Acceptors’ Additional Comments and Qualifications Include any specific comments or conditions provided by stakeholders on the sign-off. Group Who Version Qualification Design Requestor 1.00 John Holmes April 20.

As the planning was at an early stage when the infrastructure was being specified and there were many unknowns about capacity loads. Get-Resources 5) Patch management. including TQ timing Last Modified: 4/17/2018 Page 4 of 22 .1 Infrastructure Specification This infrastructure design provides hardware and software for Peregrine Asset Center for the TELUS Asset and Request Management Program. Each environment is comprised of the following components:  Web layer . tentatively set as: 1) Pilot Stage a. however actual capacity consumption will depend on the scenarios under development. The project will consist of multiple phases. SMS replacement 6) Wireless servers 7) Wireless desktops. end July 3) Marimba desktop. and a production environment. Windows is the vendor recommended platform due to the graphic intensive nature of the application. two servers were forecast as sufficient capacity. Marimba pilot and rollout for 2. Infrastructure Platform Design TA357 V1. For the application layer. Asset Center pilot 2) Asset Center server side. with sharing occurring only at the web layer at this time. As Connect-IT sizing was preliminary. For the application layer. which is expected to exceed the requirements and utilization of this project. For the database layer. Production will occupy its own set of resources.Weblogic  Application layer . The Web layer will use existing test Sun v240 Weblogic servers located in the B2B environment in CIDC.ConnectIT and Asset Center  Database layer – Oracle DB Development and test will share the same set of resources. the shared Sun v440 Oracle database cluster will be used to host the Peregrine database. desktop and servers. This database server is sized for 1m to 2m asset records. For the database layer. Asset Center will be hosted on a separate IBM x346 server and Connect- IT will be hosted on two IBM x346 servers. Therefore.0 Asset Management 2 Infrastructure Design 2. A single IBM x346 server will host the Peregrine application components – Asset Center and Connect-IT. and other databases will be assigned to use this resource provided there is no impact on the Asset Center application. and to provide sufficient capacity for Connect-IT to accommodate growth.000 servers b. the vendor recommendations were to separate Asset Center from Connect-IT. The infrastructure is sized to meet forecasted Asset Center’s requirements for the next 6 to 12 months depending on what Asset Center modules are implemented over the planning period. a new Sun v440 Oracle database cluster will be used to host the Peregrine database. any spare capacity will be absorbed into the general shared resource pool for Oracle. end June 4) Enterprise Resource Management. may be done in parallel with phase 3 8) Addition phases to be determined. The Web layer will use existing production Sun v240 Weblogic servers located in the B2B environment in CIDC. The infrastructure solution provides for a development / test environment.

2 Functional Requirements Environment Requirements  There will be two environments. Last Modified: 4/17/2018 Page 5 of 22 .  The web service will run on an active-active configuration.  The development/test and production environments will use separate hardware. with entry points for interfaces being defined.  The application service will not be run as failover Storage Requirements  The web and application layers will use internal server disk to meet their low storage needs.  Most access will be from a browser client. with a web presentation layer.  There will be 10 named users and 15 floating users of Asset Centers. weekly and monthly reporting produced. with load balancing provided by in- place F5 load balancing services.0 Asset Management 2. Interface Requirements  Interfaces will be done to the following systems: o SAP o LDAP o CED o Marimba o Cognos  Interface will be done via the Connect.  The development/test environment will be a scaled down version of the production environment. CED.  Default monitoring and altering will be implemented. Access Requirements  Access will be internal access from TELUS corporate network users only.  The solution will be multi-tiered. LDAP are straightforward and were planned extensively in pilot.  The interface will use out-of-the-box tools.  The solution may interface to BMC Atrium CMDB in the future. and will be posted on the web site for end user extraction. a combined development/test environment and a production environment.  Cognos will be reviewed and considered as a reporting tool for future  There will be daily.  Most reports will be scheduled.  Marimba. Hardware and System Software Requirements  TELUS standard monitoring and alerting tools will be deployed according to the service levels of each environment. an application layer and a database layer.  SAP interface will require more work Reporting Requirements  Reporting will be done with native Asset Center reporting through at least phase 2.  There will be no external vendor support access provided or required. with fewer fat clients.  The database will be run on an active-passive failover configuration.  The database will use EMC tier 2 enterprise storage. Infrastructure Platform Design TA357 V1.IT server and third party interface tool from Peregrine.

 Growth points will be the addition of server and desktop asset information from wireline and TQ. including data and Oracle overhead  Production data instance will be 60GB. Availability/Recoverability Requirements  The support maintenance window will be from 11pm to 5am Pacific time.  Sizing is based on 30. will scale horizontally if Request Management is added at a later phase  Performance will be assessed throughout deployment. one each for Development. Retain backups for 180 days.  Production server support will be at Gold support level. Operations and Support Requirements  TELUS will provide tiers 1 to 3 server technical support. will support from 1m to 2m asset records at the top end with all assets counted for servers and desktops o ConnectIT.000 servers o For desktops. up to 10:1 assets for desktop with software included (depends on what titles are tracked) o For servers. depends on scenario design which affects the performance of this component o Asset Center.  Development and Test database instances will be 20GB each.  Application support provided by Supporting Units D&S team  Peregrine will provide tier 3 application support  Servers will be built following standard TELUS server build specifications.    Outages will be negotiated to find a mutually acceptable outage window. Data Backup Retention/Archiving Requirements  Backups will use the following backup patterns and retention: o DB-Full backups of production and test/dev weekly with incremental backups daily. and network connectivity provided from that access point. will be dual GbE connections for each server. Test and Production environments. with horizontal scaling providing if needed by adding more Intel servers. from 3:1 to 4:1 assets per server  Initial sizing parameters: o Database. will be lightly loaded.  Development and Test environment support will be at a Bronze support level. Capacity/Scalability Requirements  Initial capacity forecasts are based on vendor sizing guidance and factors. Weekly backups stored offsite. will support an initial set of scenarios via 2 production Intel servers.85% and will be measured on a monthly period.  Infrastructure availability target is 99. including data and Oracle overhead Network Requirements  Network connectivity.  There will be 3 database instances. with failover  Servers will be deployed in Toll 8 data center. will support enterprise-wide web access. Infrastructure Platform Design TA357 V1.000 desktops and 4. Last Modified: 4/17/2018 Page 6 of 22 .0 Asset Management Database & Storage Requirements  Database will be Oracle 10g. requires a small entry-level Intel server o Web.  Capacity forecasts will cover the first 12 months of deployment.

 There are no long term data retention or archiving needs  Point-in-time file copying or other fast recovery methods is not required for any data  There are no reporting requirements. e.3 Non-Functional Requirements  The solution will be delivered expediently to ensure critical path dates are met  The solution will use TELUS standards for equipment.4 Assumptions and constraints  The project will deliver in multiple phases. servers. with Wireline the focus of the early phases.  Other competing asset services and databases. Conversion Requirements  Where applicable. and some expansion of hardware may be needed if request management is deployed in a later phase. Algernon. Infrastructure Platform Design TA357 V1. Security Requirements  Standard security model will be followed. Deployment and Implementation Requirements  Implementation will proceed in alignment with the project phases. Weekly backups stored offsite. services and support unless compelling reasons exist to deviate from TELUS standards  Sufficient capacity will be provided in the solution to ensure unforeseen growth needs can be readily accommodated over the 12 month planning horizon 2. or storage needed. SLA or otherwise Last Modified: 4/17/2018 Page 7 of 22 . Retain backups for 180 days.g.  User ids will be authenticated via LDAP. and Wireless and TQ to come in later phases.0 Asset Management o App-Full backups of production and test/dev weekly. data will be loaded via Peregrine process.  There will be no conversion interfaces.  Where available.  The initial working asset center will be completed in summer 2006. will be phased out and replaced by Marimba/Peregrine. 2. existing infrastructure will be used to meet needs.  Request management is not in scope of the initial infrastructure.

1 Development / Test Environment Details scal1288 Function: Internal Web Servers scal1289 Location: Calgary.5  Netbackup Client 5.6  sedm1323 Function: Clustered Database sedm1325 Location: Edmonton.1  BMC Patrol 3. 12 GB.1  Peregrine Asset Center 4. Toll 8 Hardware: IBM x346.1  Oracle Failover Agent 2. 4 Gig Memory.0.2 Production Environment Details scal1303 Function: Internal Web Servers scal1304 Location: Calgary.1  BEA 6. 4 GB.1 SP5 proxy plug-in  Netbackup Client 5. 4 CPU. Infrastructure Platform Design TA357 V1. 4x36GB 10k internal (Raid 1). CIDC Connectivity: Using Connectivity for Web Servers with Load Balancers Hardware: Sun V240 2x1Ghz cpu.5  AssetCenter Web 4. redundant power Software:  Solaris 9  SUNOne Web 6. 4 GB.6  SAP JCO (Java Connector) 2.5  Netbackup Client 5.4. 1 Onboard NIC with Last Modified: 4/17/2018 Page 8 of 22 . 4 x 73GB 10K internal (Raid 1) Software:  Windows Server 2003 Standard Edition  BMC Patrol 3.0 Asset Management 3 Hardware and Storage 3.1  AssetCenter Client  Oracle Client (everywhere AC Client is installed) abapp143 Function: Asset Center / Connect-IT Location: Edmonton. 4x36GB Drives. 4 x 73GB 10K internal (Raid 1) Software:  Solaris 9  Oracle 10g  Veritas Foundation Suite HA 4. Toll 8 Hardware: Sun v440. 1 QFE NIC with 4 10/100BT ports.1 3.4. 2 CPU. 1 Onboard NIC with 4 100BT ports.1  Oracle client SQL*Net  Peregrine Connect-IT 3.0  BMC Patrol 3. CIDC Connectivity: Using Connectivity for Web Servers with Load Balancers Hardware: Sun V240 2x1Ghz cpu.

1 QFE NIC with 4 10/100BT ports.4. 2 CPU.5  BMC Perform 7.1  BMC Perceive 7. 2 CPU.6  SAP JCO (Java Connector) 2. 4 GB.5  BMC Perform 7.5  BMC Perform 7.1  Peregrine Asset Center 4. 4 GB.1 Full install.1  AssetCenter Client   Oracle Client (everywhere AC Client is installed) abapp140 Function: Asset Center Location: Edmonton.1 SP5 proxy plug-in  BMC Patrol 3. 4 GB. 2 CPU. Infrastructure Platform Design TA357 V1. 4 x 73GB 10K internal (Raid 1) Software:  Windows Server 2003 Standard Edition  BMC Patrol 3.4.1  AssetCenter Web 4.6 Last Modified: 4/17/2018 Page 9 of 22 .5  BMC Perform 7.0.1  Netbackup Client 5.1  Peregrine Connect-IT 3.1  BMC Perceive 7. redundant power Software:  Solaris 9  SUNOne Web 6.0 Asset Management 4 100BT ports.1  Peregrine Connect-IT 3. we will need the DLL of  AC to connect to the AC db from CIT)  Oracle Client (everywhere AC Client is installed)  Other ODBC drivers (or database clients) as required to connect to external data  sources abapp142 Function: Connect-IT Location: Edmonton. Includes Client (correct.1  Netbackup Client 5. Toll 8 Hardware: IBM x346. Toll 8 Hardware: IBM x346. 4 x 73GB 10K internal (Raid 1) Software:  Windows Server 2003 Standard Edition  BMC Patrol 3.4. Toll 8 Hardware: IBM x346.1  BEA 6.1  BMC Perceive 7. 4 x 73GB 10K internal (Raid 1) Software:  Windows Server 2003 Standard Edition  BMC Patrol 3.1  Netbackup Client 5.6  AssetCenter 4.1  Oracle client SQL*Net abapp141 Function: Connect-IT Location: Edmonton.1  Netbackup Client 5.1  BMC Perceive 7.

Infrastructure Platform Design TA357 V1. we will need the DLL of  AC to connect to the AC db from CIT)  Oracle Client (everywhere AC Client is installed)  Other ODBC drivers (or database clients) as required to connect to external data  sources sedm1355 Function: Clustered Database sedm1356 Location: Edmonton.1 Last Modified: 4/17/2018 Page 10 of 22 .1  Oracle Failover Agent 2. 4 CPU.6  AssetCenter 4.0. 12 GB.0 Asset Management  SAP JCO (Java Connector) 2.0  Quest Foglight 4  BMC Patrol 3.1  BMC Perceive 7.5  BMC Perform 7.4. 4 x 73GB 10K internal (Raid 1) Software:  Solaris 9  Oracle 10g  Veritas Foundation Suite HA 4.1 Full install. Includes Client (correct.1  Netbackup Client 5. Toll 8 Description: Test clustered database server for Peregrine database Hardware: Sun v440.

0 Asset Management 3.3. Infrastructure Platform Design TA357 V1.1 Logical Network Diagram Last Modified: 4/17/2018 Page 11 of 22 .3 Physical Infrastructure 3.

3.2 Physical Network Diagram Last Modified: 4/17/2018 Page 12 of 22 . Infrastructure Platform Design TA357 V1.0 Asset Management 3.

5 user 1 Avocent KVM 32 systems switch 1 Total Hardware Windows Server Standard Edition 7 BMC Patrol 1-2 Cpus Y 7 BMC Patrol 3-8 Cpus Y 2 BMC Perform 1-2 Cpus Y 5 BMC Perform 3-8 Cpus Y 2 Veritas HA Storage Foundation 2 HA Standard edition v4. incl.0 Asset Management 3. 4 GB.3 Bill of Materials Model Configuration Draw Price Qty Total $ Down Sun v440 4 CPU. 4x73GB 2 IBM x346 2 CPU. Software.3.5 Oracle DB Agents Y 2 Foglight estimate (DB 1 Monitoring) Crystal Reports Pro v11 (report 0 creation) Total Software Labour & Misc Power For 2x30amp PDUs 2 Unix SA Basic Setup server install 30 DBA Setup DB install 50 Unix SA Cluster Setup advanced configuration 70 Windows SA Setup estimate 2 days/server 98 Total Labour Total Hardware. 4x73GB 1 IBM x346 2 CPU. Deployment Last Modified: 4/17/2018 Page 13 of 22 . 4 GB. Infrastructure Platform Design TA357 V1.1 Veritas Cluster Server Oracle 8i/9i Failover 2 Agents NBU Agents V4. 2 GBICs Avocent KVM Cat 5 interface module 20 interface Avocent KVM license DSView 3 . 4x73GB 3 EMC Disk CX SAN Disk in GB 100 Emulex FC Cards 2GB 64bit PCI 4 McData DS-4700 switch port allocation 4 Tab Rack 44u with 2x30amp 1 PDUs FC cables connect v440s to fabric 4 GbE cables connect to TEN and 40 NBU Cisco 3750 24 port GbE.5 Client Licenses Y 9 NBU Database Agents V4. 16GB.

Infrastructure Platform Design TA357 V1.0 Asset Management Last Modified: 4/17/2018 Page 14 of 22 .

1 Switch Ports.4.4 Network 3.0 Asset Management 3. IP Assignments Last Modified: 4/17/2018 Page 15 of 22 . Infrastructure Platform Design TA357 V1.

0 Asset Management Last Modified: 4/17/2018 Page 16 of 22 . Infrastructure Platform Design TA357 V1.

Last Modified: 4/17/2018 Page 17 of 22 . Management Tools Standard tools to be installed. Consoles are on separate VLANs. Infrastructure Platform Design TA357 V1. 100MB. Backup Using enterprise Netbackup. Network All VLAN connections and switches are GbE. except for console management. Storage All storage needs met enterprise storage using CX700 frame. Console Management IBM Remote Supervisor Adaptor II included for IBM xSeries servers ALOM remote console for Sun servers.0 Asset Management Specification Details Location Located in CIDC for existing shared Web servers. all other servers in Toll 8. NICs Port teaming is planned.

4. Last Modified: 4/17/2018 Page 18 of 22 .1 Maintenance Window Maintenance window is 11pm to 5am.3 Hardware & Software Vendor Contacts and Contractual Information Vendor support is to be provided in the local site with support details specified during implementation. Infrastructure Platform Design TA357 V1.2 Known Problems and Workarounds There are no known problems or workarounds.0 Asset Management 4 Operation Requirements & Guidelines 4. 4.

0 Asset Management 5 Appendix 5. Infrastructure Platform Design TA357 V1.1 x346 Server Connectivity Diagram Last Modified: 4/17/2018 Page 19 of 22 .

0 Asset Management 5. Infrastructure Platform Design TA357 V1.2 v440 Server Connectivity Diagram Last Modified: 4/17/2018 Page 20 of 22 .