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

 Infrastructure Platform Design TA357
V1.0 Asset Management

1 Introduction
1.1 Purpose
This document details the TELUS internal portion of the infrastructure for the Peregrine Asset Center
component of the Asset Management environment.

1.2 Document Owner

BT IS Infrastructure, Infrastructure Design Group.

1.3 Document Scope

The document contains detailed diagrams, interface standards, protocols, and other details in support of
the network and infrastructure components for the Asset Management environment to access the TELUS
internal network and resources. The design provides information on how to configure and install the
infrastructure components for the Asset Management servers.

1.4 Reference documents

Document From Date Document
Version
TELUS Internal Asset & Request Management Program Michael England Jun 2005 V1

1.5 Infrastructure Design Document Signoff

This table documents the acceptance of the Design Solution by the involved teams’ representatives.
 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

 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.6 Revision History

Version Author Date Revision Details

Completed
1.00 John Holmes April 20, 2006 Initial document create

1.7 Delivery Teams Involved

Team Manager Date Sign Of

IS Operations – Intel Roy Brassington

IS Operations - Unix Dimitar Ivanov
BT Asset Management Ken O’Connell

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

2 Infrastructure Design
2.1 Infrastructure Specification
This infrastructure design provides hardware and software for Peregrine Asset Center for the TELUS
Asset and Request Management Program. 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.

The infrastructure solution provides for a development / test environment, and a production environment.
Each environment is comprised of the following components:

 Web layer - Weblogic

 Application layer - ConnectIT and Asset Center
 Database layer – Oracle DB

Development and test will share the same set of resources. The Web layer will use existing test Sun
v240 Weblogic servers located in the B2B environment in CIDC. For the application layer, Windows is the
vendor recommended platform due to the graphic intensive nature of the application. A single IBM x346
server will host the Peregrine application components – Asset Center and Connect-IT. For the database
layer, the shared Sun v440 Oracle database cluster will be used to host the Peregrine database.

Production will occupy its own set of resources, with sharing occurring only at the web layer at this time.
The Web layer will use existing production Sun v240 Weblogic servers located in the B2B environment in
CIDC. For the application layer, Asset Center will be hosted on a separate IBM x346 server and Connect-
IT will be hosted on two IBM x346 servers. As the planning was at an early stage when the infrastructure
was being specified and there were many unknowns about capacity loads, the vendor recommendations
were to separate Asset Center from Connect-IT, and to provide sufficient capacity for Connect-IT to
accommodate growth. As Connect-IT sizing was preliminary, two servers were forecast as sufficient
capacity, however actual capacity consumption will depend on the scenarios under development. For the
database layer, a new Sun v440 Oracle database cluster will be used to host the Peregrine database.
This database server is sized for 1m to 2m asset records, which is expected to exceed the requirements
and utilization of this project. Therefore, any spare capacity will be absorbed into the general shared
resource pool for Oracle, and other databases will be assigned to use this resource provided there is no
impact on the Asset Center application.

The project will consist of multiple phases, tentatively set as:

1) Pilot Stage
a. Marimba pilot and rollout for 2,000 servers
b. Asset Center pilot
2) Asset Center server side, end July
3) Marimba desktop, end June
4) Enterprise Resource Management, Get-Resources
5) Patch management, desktop and servers, SMS replacement
6) Wireless servers
7) Wireless desktops, may be done in parallel with phase 3
8) Addition phases to be determined, including TQ timing

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

2.2 Functional Requirements

Environment Requirements
 There will be two environments; a combined development/test environment and a production
environment.
 The development/test and production environments will use separate hardware.
 The development/test environment will be a scaled down version of the production environment.
 The solution will be multi-tiered, with a web presentation layer, an application layer and a
database layer.

Hardware and System Software Requirements

 TELUS standard monitoring and alerting tools will be deployed according to the service levels of
each environment.
 Default monitoring and altering will be implemented.
 The database will be run on an active-passive failover configuration.
 The web service will run on an active-active configuration, with load balancing provided by in-
place F5 load balancing services.
 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.
 The database will use EMC tier 2 enterprise storage.

Access Requirements
 Access will be internal access from TELUS corporate network users only.
 There will be no external vendor support access provided or required.
 There will be 10 named users and 15 floating users of Asset Centers.
 Most access will be from a browser client, with fewer fat clients.

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.IT server and third party interface tool from Peregrine.
 The solution may interface to BMC Atrium CMDB in the future.
 The interface will use out-of-the-box tools, with entry points for interfaces being defined.
 Marimba, CED, LDAP are straightforward and were planned extensively in pilot.
 SAP interface will require more work

Reporting Requirements
 Reporting will be done with native Asset Center reporting through at least phase 2.
 Cognos will be reviewed and considered as a reporting tool for future
 There will be daily, weekly and monthly reporting produced.
 Most reports will be scheduled, and will be posted on the web site for end user extraction.

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

Database & Storage Requirements

 Database will be Oracle 10g.
 There will be 3 database instances, one each for Development, Test and Production
environments.
 Development and Test database instances will be 20GB each, including data and Oracle
overhead
 Production data instance will be 60GB, including data and Oracle overhead

Network Requirements
 Network connectivity, will be dual GbE connections for each server, with failover
 Servers will be deployed in Toll 8 data center, and network connectivity provided from that access
point.

Operations and Support Requirements

 TELUS will provide tiers 1 to 3 server technical support.
 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.

Availability/Recoverability Requirements
 The support maintenance window will be from 11pm to 5am Pacific time.  
 Outages will be negotiated to find a mutually acceptable outage window.
 Infrastructure availability target is 99.85% and will be measured on a monthly period.
 Production server support will be at Gold support level.
 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.
 Capacity forecasts will cover the first 12 months of deployment.
 Growth points will be the addition of server and desktop asset information from wireline and TQ.
 Sizing is based on 30,000 desktops and 4,000 servers
o For desktops, up to 10:1 assets for desktop with software included (depends on what
titles are tracked)
o For servers, from 3:1 to 4:1 assets per server
 Initial sizing parameters:
o Database; will support from 1m to 2m asset records at the top end with all assets counted
for servers and desktops
o ConnectIT; will support an initial set of scenarios via 2 production Intel servers, with
horizontal scaling providing if needed by adding more Intel servers, depends on scenario
design which affects the performance of this component
o Asset Center; will be lightly loaded, requires a small entry-level Intel server
o Web; will support enterprise-wide web access, will scale horizontally if Request
Management is added at a later phase
 Performance will be assessed throughout deployment.

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.
Retain backups for 180 days. Weekly backups stored offsite.

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

o App-Full backups of production and test/dev weekly. Retain backups for 180 days.
Weekly backups stored offsite.

Deployment and Implementation Requirements

 Implementation will proceed in alignment with the project phases.
 The initial working asset center will be completed in summer 2006.

Conversion Requirements
 Where applicable, data will be loaded via Peregrine process.
 There will be no conversion interfaces, servers, or storage needed.

Security Requirements
 Standard security model will be followed.
 User ids will be authenticated via LDAP.

2.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, 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.4 Assumptions and constraints

 The project will deliver in multiple phases, with Wireline the focus of the early phases, and
Wireless and TQ to come in later phases.
 Request management is not in scope of the initial infrastructure, and some expansion of
hardware may be needed if request management is deployed in a later phase.
 Other competing asset services and databases, e.g. Algernon, will be phased out and replaced
by Marimba/Peregrine.
 Where available, existing infrastructure will be used to meet needs.
 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, SLA or otherwise

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

3 Hardware and Storage

3.1 Development / Test Environment Details
scal1288 Function: Internal Web Servers
scal1289 Location: Calgary, CIDC
Connectivity: Using Connectivity for Web Servers with Load Balancers
Hardware: Sun V240 2x1Ghz cpu, 4 GB, 4x36GB 10k internal (Raid 1), 1 Onboard NIC
with 4 100BT ports, 1 QFE NIC with 4 10/100BT ports, redundant power
Software:
 Solaris 9
 SUNOne Web 6.1
 BEA 6.1 SP5 proxy plug-in
 Netbackup Client 5.1
 BMC Patrol 3.5
 AssetCenter Web 4.4.1
 AssetCenter Client
 Oracle Client (everywhere AC Client is installed)
abapp143 Function: Asset Center / Connect-IT
Location: Edmonton, Toll 8
Hardware: IBM x346, 2 CPU, 4 GB, 4 x 73GB 10K internal (Raid 1)
Software:
 Windows Server 2003 Standard Edition
 BMC Patrol 3.5
 Netbackup Client 5.1
 Peregrine Asset Center 4.4.1
 Oracle client SQL*Net
 Peregrine Connect-IT 3.6
 SAP JCO (Java Connector) 2.0.6

sedm1323 Function: Clustered Database
sedm1325 Location: Edmonton, Toll 8
Hardware: Sun v440, 4 CPU, 12 GB, 4 x 73GB 10K internal (Raid 1)
Software:
 Solaris 9
 Oracle 10g
 Veritas Foundation Suite HA 4.1
 Oracle Failover Agent 2.0
 BMC Patrol 3.5
 Netbackup Client 5.1

3.2 Production Environment Details

scal1303 Function: Internal Web Servers
scal1304 Location: Calgary, CIDC
Connectivity: Using Connectivity for Web Servers with Load Balancers
Hardware: Sun V240 2x1Ghz cpu, 4x36GB Drives, 4 Gig Memory, 1 Onboard NIC with

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

4 100BT ports, 1 QFE NIC with 4 10/100BT ports, redundant power

Software:
 Solaris 9
 SUNOne Web 6.1
 BEA 6.1 SP5 proxy plug-in
 BMC Patrol 3.5
 BMC Perform 7.1
 BMC Perceive 7.1
 Netbackup Client 5.1
 AssetCenter Web 4.4.1
 AssetCenter Client 
 Oracle Client (everywhere AC Client is installed)
abapp140 Function: Asset Center
Location: Edmonton, Toll 8
Hardware: IBM x346, 2 CPU, 4 GB, 4 x 73GB 10K internal (Raid 1)
Software:
 Windows Server 2003 Standard Edition
 BMC Patrol 3.5
 BMC Perform 7.1
 BMC Perceive 7.1
 Netbackup Client 5.1
 Peregrine Asset Center 4.4.1
 Oracle client SQL*Net

abapp141 Function: Connect-IT

Location: Edmonton, Toll 8
Hardware: IBM x346, 2 CPU, 4 GB, 4 x 73GB 10K internal (Raid 1)
Software:
 Windows Server 2003 Standard Edition
 BMC Patrol 3.5
 BMC Perform 7.1
 BMC Perceive 7.1
 Netbackup Client 5.1
 Peregrine Connect-IT 3.6
 SAP JCO (Java Connector) 2.0.6
 AssetCenter 4.4.1 Full install, Includes Client (correct, 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, Toll 8
Hardware: IBM x346, 2 CPU, 4 GB, 4 x 73GB 10K internal (Raid 1)
Software:
 Windows Server 2003 Standard Edition
 BMC Patrol 3.5
 BMC Perform 7.1
 BMC Perceive 7.1
 Netbackup Client 5.1
 Peregrine Connect-IT 3.6

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

 SAP JCO (Java Connector) 2.0.6

 AssetCenter 4.4.1 Full install, Includes Client (correct, 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, Toll 8
Description: Test clustered database server for Peregrine database
Hardware: Sun v440, 4 CPU, 12 GB, 4 x 73GB 10K internal (Raid 1)
Software:
 Solaris 9
 Oracle 10g
 Veritas Foundation Suite HA 4.1
 Oracle Failover Agent 2.0
 Quest Foglight 4
 BMC Patrol 3.5
 BMC Perform 7.1
 BMC Perceive 7.1
 Netbackup Client 5.1

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

3.3 Physical Infrastructure

3.3.1 Logical Network Diagram

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

3.3.2 Physical Network Diagram

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

3.3.3 Bill of Materials

Model Configuration Draw Price Qty Total $
Down
Sun v440 4 CPU, 16GB, 4x73GB 2
IBM x346 2 CPU, 4 GB, 4x73GB 1
IBM x346 2 CPU, 4 GB, 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, incl. 2
GBICs
Avocent KVM Cat 5 interface module 20
interface
Avocent KVM license DSView 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.1
Veritas Cluster Server Oracle 8i/9i Failover 2
Agents
NBU Agents V4.5 Client Licenses Y 9
NBU Database Agents V4.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, Software, Deployment

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

3.4 Network
3.4.1 Switch Ports, 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.0 Asset Management

Specification Details

Location
Located in CIDC for existing shared Web servers, all other servers in Toll 8.

Management Tools
Standard tools to be installed.

NICs
Port teaming is planned.

Console Management
IBM Remote Supervisor Adaptor II included for IBM xSeries servers
ALOM remote console for Sun servers.
Consoles are on separate VLANs.

Network
All VLAN connections and switches are GbE, except for console management, 100MB.

Backup
Using enterprise Netbackup.

Storage
All storage needs met enterprise storage using CX700 frame.

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

4 Operation Requirements & Guidelines

4.1 Maintenance Window
Maintenance window is 11pm to 5am.

4.2 Known Problems and Workarounds

There are no known problems or workarounds.

4.3 Hardware & Software Vendor Contacts and Contractual

Information
Vendor support is to be provided in the local site with support details specified during implementation.

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

5 Appendix
5.1 x346 Server Connectivity Diagram

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

 Infrastructure Platform Design TA357
V1.0 Asset Management

5.2 v440 Server Connectivity Diagram

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