Design Principles

We will describe the design principles and the importance of

organizational network policies and procedures.
Fundamentally, you break the network design process into
manageable blocks so that the network functions within the
performance and scale limits of applications, protocols and network
services.
The designed network infrastructure must meet the following
objectives:

• Design a network that meets a customer’s requirements for

performance, security, capacity, and scalability.
• Document the customer’s current applications, protocols,
topology, and number of users.
• It should be adaptable to satisfy ever-changing applications
demands.
• Document the customer’s business issues that are relevant to a
network design project.
• The cost of future growth to meet the needs of business.

Building a network infrastructure requires a lot of planning, designing,

modeling, and most importantly information gathering.

When designing networks, it is important to look at available

resources, you have to implement the new network architecture but
also be sensitive to the quantity and quality of the resources available
to operate and manage the network.
Business Requirements of the Customer

For this aspect of determining the customer’s objectives, think

about the purpose of the project. Project how the business will
improve. Find out if the network is affecting the company’s capability
or effectiveness to develop, produce, and track products.
Scalability is a very important consideration, and it is wise for the
network designer to build a network that can scale. You should figure
out how much the company will grow in one year or in five years.
Technical Requirements of the Customer

Think about the type of technical problems you are trying to

solve. Consider the network’s Topology. Keep in mind scaling issues;
decide whether switched Ethernet will provide the necessary
bandwidth or whether Fast Ethernet is necessary to scale the network.

Technical requirements can be divided into the following areas:

• Performance requirements
• Applications requirements
• Network management requirements
• Security requirements
Performance Requirements

Determine the following performance requirements:

• Identify any issues concerning network latency and response
times.
• Find out if there is high utilization on LAN segments or WAN
links. Determine how often the WAN links go down.
Application Requirements

Determine the following application requirements:

• Find out what new applications have been introduced to the network.
• Determine the number of users using these applications.
• Find out the traffic flow for these applications.
• Identify what new protocols are being introduced to the network.
• Determine what applications are used during the daytime hours and
what are used during the nighttime hours.
• Determine the time of day that represents the peak usage hours of
applications.
Network Management Requirements

Determine the following network management requirements:

• Determine how the network is managed.

• Determine whether there is a network management station to view
network performance and faults.
• Ascertain whether there are any accounting and security
management requirements.
• Find out whether the staff is training on the network management
applications.
• Find out whether there is a station for configuration management.

Security Requirements

Determine the following security requirements:

• Determine what type of security is required.
• Find out what external connections are present in the network and
why they are there.
• Determine whether additional security is required on Internet
connections.

Steps for Network Design

The steps for designing a network are as follows:

1. Gather information to support the business and technical
requirements.
2. Assess the current network.
3. Consider the applications involved.
4. Design the local-area networks.
5. Design the wide-area network.
6. Design for specific network protocols.
7. Create the design document and select Cisco network
management applications.
Gather Information to Support the Business and Technical
Requirements
“Assessing the Existing Network and Identifying Customer Objectives,” as
mentioned below;

Assess the Current Network

This is the step during which you collect all data pertaining to physical,
logical, traffic, and management information of the network.

Physical Assessment

To perform a physical assessment, you need to document the physical

topology of the network. Create a diagram with all routers, switches, and hubs. A
list of network devices is created and the type and amount of devices is
documented. Physical connectivity between devices should also be documented;
also list the speed and type of media used between devices.
Logical Assessment

To perform the logical assessment, determine the following:

• The protocols that are being routed
• The IP address assignment scheme
• The Novell IPX address assignment
• The AppleTalk address assignment
• Whether any access list is used to filter addresses or broadcasts
• The Layer 3 architecture
.
Traffic Assessment

To perform the traffic assessment, determine the following:

• Document the traffic flows on the network.
• Determine how much traffic is on each segment.
• Locate the servers.
• Determine how much traffic is local to the segment and how much
traffic is external.
•
Management Assessment

Determine the current tools used for network management:

• Determine whether the customer has the necessary tools to
manage the network.
• Determine whether there is a management station
• Find out whether CiscoWorks is being used to manage routers and
switches.
• Verify whether there is capacity or performance monitoring tools.
• Determine whether a network protocol analyzer is available for LAN
segment troubleshooting.
• Find out whether any RMON probes are in use

Assessing the Existing Network and Identifying Customer Objectives

To create a comprehensive design that will meet your customer’s needs,

you must understand the customer’s objectives.
When a project scope has been defined, a project plan can be created to satisfy
the customer’s requirements. The success of the project plan and resulting
design proposal will rely heavily on your ability to collect data that is both
accurate and pertinent.
The Necessary Data for Characterizing the Existing Network

To help you understand and characterize your customer’s network, you

will review two basic areas of your customer’s business.
1. First you will review nontechnical data related to your customer’s business
goals, issues, and constraints. This information is essential to
understanding growth trends, corporate structure, and policies that would
affect your design.
2. The second major area you will need to review is the customer’s current
technical information. It is important to distinguish between business or
administrative information and technical data. However, as you are
collecting this data, it is important to see how they are related to each
other. Remember that the goal here is to understand your customer’s
 existing network and to uncover any problem areas you might encounter
later.
Assessing the Customer’s Corporate Profile Information

Understanding your customer’s network means understanding your

customer’s business. The profiling data will help you determine the following:
• Business goals and business type:
Determine what type of business your customer is engaged in and what
the company’s major business goals are for the future. The growth of a company
will differ from one to another; try to understand how you would measure the
growth of the company. Should you look for significant growth every six months,
or in one year, or over the next four years? This will help you determine the
scalability requirements and also help you understand the return on the
investment the customer is seeking. By researching your customer’s industry and
the competition, you will be able to better position Cisco products to help the
customer grow.
• Corporate structure
A network design usually resembles the corporate structure of a company
by having different networks for different departments, such as Marketing, Media,
Human Resources, and Accounting.
An organizational chart or a similar document can help you better understand the
corporate structure. An example of some information

Geographical structure
Determine how the customer’s company is spread geographically. You
should always review the geographical structure of the company with the
corporate structure. Doing this research helps you understand and locate major
user communities.
• Current and future staffing
The network must have enough flexibility to address the needs of the
existing staff as well as support the growth and expansion of a company.
To help you determine current and future staffing needs, ask the following
questions:
— Ask the network users how these network changes will affect them.
— Ask the network users which department or departments will be affected.
— Ask the IS staff how much in-house internetworking expertise there is.
— Ask the IS staff if the company plans to expand staff as required to support the
new internetwork design.
— Ask the IS staff who will help you design the internetwork.
— Ask if the new design will cause changes in job functions or possibly eliminate
jobs.
Policies and politics:
Provides an understanding of how the design and implementation of the
new network will affect the people and policies in the company. Find out whether
they have any current policies related to the infrastructure. An example would be
the corporate security policy or LAN access.
Assessing the Customer’s Technical Information
Before you can begin developing a design solution, you must assess the
company’s current network technical information. Technical data helps you
identify any network bottlenecks, understand how systems work together, and
determine whether there are any obvious issues in implementing the new design.
Technical assessment can be divided into the following areas:
• Performance
• Applications
• Network management
• Security

Performance Assessment
To assess the performance issues of the current network, you will want to
ask the following questions:
• Is there any latency?
• What is causing that latency?
• When do the performance problems happen?
• How will performance be affected by the proposed design?
• How much traffic flows between segments?
• Are there new applications, networks, or segments that will add to
the traffic?
Applications Assessment
To completely assess the applications on the current network, you will
need to look at the following:
• Applications: Identify the customer’s current applications and plans for future
applications, including information such as who uses the applications.
• Information flows: Analyze where information flows in the company and how
different applications and traffic affects that flow.
• Shared data: Determine where shared data resides and who uses it.
• Categorize data: This will help you understand the different types of data
passed along in the company’s network, such as routed protocols, non-routed
protocols, and routing protocols

Network Management Assessment

Ask the following questions to assess the company’s network
management situation:
• Who manages the network? Are all aspects of the network
managed by the same people?
• What type of network management is the client looking to
implement? Reactive versus proactive?
• What type of notification does the client want to warn it of
performance or fault issues?
• Who in the company knows how to perform network management
tasks?
Security Assessment
Finally, ask the following questions to assess the company’s network
security:
• What security risks concern the customer?
• What security risks are priorities to the customer?
• Are there any existing security policies? Are the policies
documented?
• What are the different access levels a user can have?
• What is the physical security of the network? Does everyone have
access to the data closet or center?
Twelve Steps for Documenting Your Customer’s Existing Network

Before you alter a network, you need to know what currently exists and
the impact of your design on the existing environment.
Step 1 Characterize the customer’s applications.
Step 2 Characterize the network protocols.
Step 3 Document the customer’s current network.
Step 4 Identify potential bottlenecks.
Step 5 Identify the business constraints and inputs into your network design.
Step 6 Characterize the existing network availability.
Step 7 Characterize the network performance.
Step 8 Characterize the existing network reliability.
Step 9 Characterize the network utilization.
Step 10 Characterize the status of the major routers.
Step 11 Characterize the existing network management tools.
Step 12 Summarize the health of the existing network.

Methodology to Network Design

The lifecycle of a network and a network design methodology based on
the lifecycle are presented. Each phase of the network design process is
explored in detail, starting with how to identify customer requirements, including
organizational and technical goals and constraints.
It begins with an introduction to the Cisco vision of intelligent networks and the
Service Oriented Network Architecture (SONA) architectural framework.
Service Oriented Network Architecture (SONA)
The extremely rich variety of application-level business solutions available
today and the need to integrate these applications drives the need for new
network architecture. This section introduces the Cisco vision and framework that
enable customers to build a more intelligent network infrastructure. The Cisco
SONA architectural framework shifts the view of the network from a pure traffic
transport-oriented view toward a service- and application-oriented view.
Business Drivers for a New Network Architecture
New business requirements, the growth of applications, and the evolution
of IT combine to drive the need for new network architecture.
In today’s business environment, intense competition and time-to-market
pressures are prompting enterprises to look for new IT solutions that can help
them better respond to market and customer demands. Consumers are asking
for new products and service offerings—and they want them fast. They are also
demanding improved customer service, enhanced customization flexibility, and
greater security, all at a lower cost.

In this environment, the IT model has evolved from mainframes, to client/server

models, to Internet applications, as illustrated in Figure 2-1.
The Cisco vision of the next phase of IT evolution is a real-time infrastructure that
integrates the network and the applications as one system.

Cisco SONA Framework

Using the SONA framework for intelligent networks, enterprises can
improve flexibility and increase efficiency by optimizing applications, business
processes, and resources to enable IT to have a greater effect on business.
The SONA framework leverages the extensive product-line services, proven
architectures, and experience of Cisco and its partners to help enterprises
achieve their business goals.
The SONA framework, shown in Figure 2-3, shows how integrated systems can
allow a dynamic, flexible architecture and provide for operational efficiency
through standardization and virtualization.

KEY POINT:
In the SONA framework, the network is the common element that connects and
enables all components of the IT infrastructure.
The SONA framework defines the following three layers:
■ Networked Infrastructure layer:
Where all the IT resources are interconnected across a converged
network foundation; The IT resources include servers, storage, and clients. The
Networked Infrastructure layer represents how these resources exist in different
places in the network, including the campus, branch, data center, enterprise
edge, WAN, metropolitan-area-network (MAN. The objective of this layer is to
provide connectivity, anywhere and anytime.
The Networked Infrastructure layer includes the network devices and links to
connect servers, storage, and clients in different places in the network.

Interactive Services layer:
Includes both applications networking services and infrastructure services,
this layer enables efficient allocation of resources to applications and business
processes delivered through the networked infrastructure;
This layer includes the following services:
— Voice and collaboration services
— Mobility services
— Wireless services
— Security and identity services
— Storage services
— Compute services
— Application networking services (content networking services)
— Network infrastructure virtualization
— Adaptive network management services
— Quality of service (QoS)
— High availability

Application layer:
This layer includes business applications and collaboration applications.
The objective of this layer is to meet business requirements and achieve
efficiencies by leveraging the interactive services layer. This layer includes the
following collaborative applications:
— Instant messaging
— Cisco Unified Contact Center
— Cisco Unity (unified messaging)
— Cisco IP Communicator and Cisco Unified IP Phones
— Cisco Unified Meeting Place
— Video delivery using Cisco Digital Media System
— IP telephony

The benefits of SONA include the following:

■ Functionality: Supports the organizational requirements.
■ Scalability: Supports growth and expansion of organizational tasks by
separating functions and products into layers; this separation makes it easier to
grow the network.
■ Availability: Provides the necessary services, reliably, anywhere, anytime.
■ Performance: Provides the desired responsiveness, throughput, and utilization
on a per application basis through the network infrastructure and services.
■ Manageability: Provides control, performance monitoring, and fault detection.
■ Efficiency: Provides the required network services and infrastructure with
reasonable operational costs and appropriate capital investment on a migration
path to a more intelligent network, through step-by-step network services growth.
■ Security: Provides for an effective balance between usability and security
while protecting information assets and infrastructure from inside and outside
threats.

Network Design Methodology

The network design methodology presented in this section is derived from
the Cisco Prepare, Plan, Design, Implement, Operate, and Optimize (PPDIOO)
methodology, which reflects a network’s lifecycle. The following sections describe
the PPDIOO phases and their relation to the network design methodology, and
the benefits of the lifecycle approach to network design.
Benefits of the Lifecycle Approach to Network Design
The network lifecycle approach provides many benefits, including the following:
■ lowering the total cost of network ownership:
— Identifying and validating technology requirements
— Planning for infrastructure changes and resource requirements
— Developing a sound network design aligned with technical requirements and
business goals
— accelerating successful implementation
— Improving the efficiency of the network and of the staff supporting it
— Reducing operating expenses by improving the efficiency of operation
processes and tools
■ Increasing network availability:
— Assessing the state of the network’s security and its ability to support the
proposed design
— Specifying the correct set of hardware and software releases and keeping
them operational and current
— Producing a sound operational design and validating network operation
— Staging and testing the proposed system before deployment
— Improving staff skills
— Proactively monitoring the system and assessing availability trends and alerts
— Proactively identifying security breaches and defining remediation plans

Improving business agility:
— Establishing business requirements and technology strategies
— Readying sites to support the system to be implemented
— Integrating technical requirements and business goals into a detailed design
and demonstrating that the network is functioning as specified
— Expertly installing, configuring, and integrating system components
— Continually enhancing performance
■ Accelerating access to applications and services:
— Assessing and improving operational preparedness to support current and
planned network technologies and services
— Improving service-delivery efficiency and effectiveness by increasing
availability, resource capacity, and performance
— Improving the availability, reliability, and stability of the network and the
applications running on it
— Managing and resolving problems affecting the system and keeping software
applications current

Design Methodology
When working in an environment that requires creative production on a
tight schedule—for example, when designing an internetwork—using a
methodology can be helpful. A methodology is a documented, systematic way of
doing something.
Following a design methodology can have many advantages:

■ It ensures that no step is missed when the process is followed.

■ It provides a framework for the design process deliverables.
■ It encourages consistency in the creative process, enabling network designers
to set appropriate deadlines and maintain customer and manager satisfaction.
■ It allows customers and managers to validate that the designers have thought
about how to meet their requirements.
Extracting Initial Requirements of Customer
Initial design requirements are typically extracted from the Request for
Proposal (RFP) or Request for Information (RFI) documents that the customer
issues. An RFP is a formal request to vendors for proposals that meet the
requirements that the document identifies.

Step 1 Extract the initial customer requirements (from the RFP).

Step 2 Query the customer for a verbal description of the initial requirements.
Step 3 Produce a draft document that describes the design requirements.
Step 4 Verify the design requirements with the customer, and obtain customer
approval.
Step 5 Revise the document as necessary to eliminate errors and omissions.
Steps 2 to 5 are repeated if the customer has additional comments about the
draft document.
Gathering Network Requirements
The process of gathering network requirements can be broken down into
five steps. During these steps (which are sometimes called milestones), the
designer discusses the project with the customer’s staff to determine and gather
the necessary data, including appropriate documentation.

As shown in Figure 2-7, the steps are as follows:

Step 1 Identify the planned network applications and network services.
Step 2 Determine the organizational goals.
Step 3 Determine the possible organizational constraints.
Step 4 Determine the technical goals.
Step 5 Determine the technical constraints that must be taken into account.
These steps provide the designer with data that must be carefully interpreted,
analyzed, and presented to support the design proposal. Throughout these
steps, the designer takes thorough notes, produces documentation, and presents
the findings to the customer for further discussion.
Technical Goals
The technical goals of the project must also be determined before the
design starts. Some sample questions the designer might ask to help determine
technical goals include the following:
■ What are your technology priorities?
■ How does your technology budgeting process work?
■ What infrastructure issues exist or will exist related to your applications
rollouts?
■ What skill sets does your technical staff need to acquire?
■ Does your current network have any performance issues?
■ Which portions of your network are considered mission-critical?
■ Do you anticipate significant growth in the number of network users over the
next few years?
■ How is your network managed now?

Sample Diagram, Help you to collect information and design any network.

With only this diagram, many questions remain about the network and the
expected network functionality, including the following:
■ What is the IP addressing scheme?
■ What level of redundancy or high availability currently exists in the network?
■ What level of redundancy or high availability is required in the new network?
■ What are the details of the security design?
■ What types of links are in the network?
■ What are the link speeds?
■ What are the planned Layer 2 and Layer 3 topologies?
■ How is connectivity provided to remote sites?
■ What network infrastructure services are in use, such as voice and video, and
what is planned?
■ Are existing wireless devices in place, or are any wireless deployments
planned?
■ What routing protocols are in use?
■ Are there any server farm or remote data center connectivity requirements?
■ What network management tools are in place?
It is important to get as much information as possible about the existing situation
before commencing design.

Redundant Models
When designing a network topology for a customer who has
critical systems, services, or network paths, you should determine the likelihood that
these components will fail and design redundancy where necessary.
Consider incorporating one of the following types of redundancy into your design:
• Workstation-to-router redundancy
• Server redundancy
• Route redundancy
• Media redundancy
Each of these types of redundancy is elaborated in the sections that follow.
Workstation-to-Router Redundancy
When a workstation has traffic to send to a station that is not local, the workstation
has many possible ways to discover the address of a router on its network segment,
including the following:
• Address Resolution Protocol (ARP)
• Explicit configuration
• Router Discovery Protocol (RDP)
• Routing Information Protocol (RIP)
• Internetwork Packet Exchange (IPX)
• AppleTalk
• Hot Standby Router Protocol (HSRP)

In Figure 4-5, the following sequence occurs:

1 The Anderson workstation is configured to use the Phantom router
as its default router.
2 Upon booting, the routers elect Broadway as the HSRP active router.
The active router
does the work for the HSRP phantom. Central Park is the HSRP
standby router.
3 When Anderson sends an ARP frame to find its default router,
Broadway responds with the Phantom router’s MAC address.
4 If Broadway goes off line, Central Park takes over as the active
router, continuing the delivery of Anderson’s packets. The change is
transparent to Anderson. If a third HSRP router was on the LAN, that
router would begin to act as the new standby router.

Server Redundancy

In some environments, fully redundant (mirrored) file

servers should be recommended. For example, in a brokerage firm
where traders must access data in order to buy and sell stocks, the
data can be replicated on two or more redundant servers.
Route Redundancy
Designing redundant routes has two purposes: load
balancing and minimizing downtime.
Most IP routing protocols can load balance across up to six parallel
links that have equal cost. Use the maximum-paths command to
change the number of links that the router will load balance over for
IP; the default is four, the maximum is six. To support load balancing,
keep the bandwidth consistent within a layer of the hierarchical model
so that all paths have the same cost. (Cisco’s IGRP and EIGRP are
exceptions because they can load balance traffic across multiple routes
that have different metrics by using a feature called variance.)

By using redundant, meshed network designs, you can minimize

the effect of link failures.
Depending on the convergence time of the routing protocols being
used, a single link failure will not have a catastrophic effect.
A network can be designed as a full mesh or a partial mesh. In a full
mesh network, every router has a link to every other router, as shown
in Figure 4-6. A full mesh network provides complete redundancy and
also provides good performance because there is just a single-hop
delay between any two sites.
A full mesh network can be expensive to implement in wide-area
networks due to the required number of links. In addition, practical
limits to scaling exist for groups of routers that broadcast routing
updates or service advertisements. As the number of router peers
increases, the amount of bandwidth and CPU resources devoted to
processing broadcasts increases.
When planning redundancy, follow guidelines for simple, hierarchical
design. Figure 4-7 illustrates a classic hierarchical and redundant
enterprise design that uses a partial mesh rather than full mesh
architecture. For LAN designs, links between the access and
distribution layer can be Fast Ethernet, with links to the core at Gigabit
Ethernet speeds.
Media Redundancy
In mission-critical applications, it is often necessary to
provide redundant media.
In switched networks, switches can have redundant links to each
other. This redundancy is good because it minimizes downtime, but it
may result in broadcasts continuously circling the network, which is
called a broadcast storm. Because Cisco switches implement the IEEE
802.1d Spanning-Tree Algorithm, this looping can be avoided in the
Spanning-Tree Protocol.
The Spanning-Tree Algorithm guarantees that only one path is active
between two network stations. The algorithm permits redundant paths
that are automatically activated when the active path experiences
problems.
Because WAN links are often critical pieces of the internetwork,
redundant media is often deployed in WAN environments. As shown in
Figure 4-8, backup links can be provisioned so they become active
when a primary link goes down or becomes congested.
Secure Models
This section introduces secure topology models. The information in this
book is not sufficient to learn all the nuances of internetwork security.
To learn more about internetwork security, you might want to read the
book Firewalls and Internet Security. You can keep up to date on
security issues. Secure topologies are often designed by using a
firewall. A firewall protects one network from another untrusted
network. This protection can be accomplished in many ways, but in
principle, a firewall is a pair of mechanisms: One blocks traffic and the
other permits traffic. Some firewalls place a greater emphasis on
blocking traffic, and others emphasize permitting traffic.
Figure 4-9 shows a simple firewall topology using routers.

Three-Part Firewall System

The classic firewall system, called the three-part firewall system, has
the following three specialized layers, as shown in Figure 4-10:
• An isolation LAN that is a buffer between the corporate internetwork
and the outside world. (The isolation LAN is called the demilitarized
zone (DMZ) in some literature.)
• A router that acts as an inside packet filter between the corporate
internetwork and the isolation LAN.
• Another router that acts as an outside packet filter between the
isolation LAN and the outside internetwork.
Device Naming Schemes

Having the right naming scheme can help the network staff
knows which device they are using without having to rely on a printed
spreadsheet or other outside reference.

For very small networks, you could use a naming system such as
jecky, Sleepy, and so on, but these names do not provide an
understanding of the function of these devices. As a better solution,
you could name servers based on their function or the group they
serve, such as Admin01, IT_Server01, and Finance01

For larger networks, you may want to use a country-city-site-number

scheme.
IP Addressing
 The most important requirement that the network designer has
in scaling a network is to assign addresses in a manner that can be
scaled.
Logical IP Addresses

An IP address is a unique 32-bit logical number assigned to a

network device. IP addresses are network-layer (Layer 3) addresses
and are represented in dotted decimal format.

Horizontal Plastic Cable Managers

19" Cable Manager with Plastic Rings, 1U (ring dimensions: 70 x 44.5 mm (2.76" x 1.75"))
CM-1U-PL

19" Cable Manager with Plastic Rings, 2U (ring dimensions: 70 x 44.5 mm (2.76" x 1.75"))
CM-2U-PL

19" Cable Manager with Plastic Rings and Cover, 1U (ring dimensions: 60 x 44.5 mm (2.36" x 1.75"))
CM-1U-PL-COV
Hardware

Our servers use 2U Intel Dual CORE Woodcrest Xeon Processors, 4MB cache, 4.0GB
ECC RAM, 3 x 320GB SATA II (3Gb/s) Hard Drives with Hardware Raid 5 for hard
drive redundancy, Hardened Secure Kernel and Redundant Power Supply Units.
Equipment

Our cage is cooled by Liebert AC units to maintain a constant temperature of 67 degrees.

Each cabinet is powered by dual 20 Amp power circuits each on a different UPS for fully
redundant power.
All CAT5 is prewired in to patch panels for efficient cable management.

Cables are properly managed to ensure good air flow and cooling.
We use a combination of Cisco and Foundry switches all connected via gigE to the core
switch.

Servers are also connected to APC reboot switches, as well as being behind a Cisco PIX
firewall.
All servers are backed by N+1 redundant UPS systems in additional to being backed by
the Diesel generator.

Data Center Profile:

Network
Multi-homed redundant fiber connections and peering with Tier-1 providers ensure you're always

connected and that your data takes the quickest, most efficient routes for optimal transfer speeds.

Maintenance and support contracts with all of our vendors, along with third party consultants, ensure

constant uptime and availability.

Redundant Core Switches

Patch Panels
 Internap FCP Appliances

Redundant Core Switches

Patch Panels

Patch Panels

Power
Uninterrupted power solutions that are flexible and upgradeable provide constant power to your

hardware. Our Mitsubishi UPS battery system takes over instantly while our diesel generator starts up.
 UPS System

Power Distribution Unit

Bypass Panel
 UPS System

Bypass panel

Redundant Power

UPS System

Generator

Generator
Security
Security
Multi-layer security control procedures, staffed 24/7, proximity card readers, and IP video monitoring

ensure that your hardware is never tampered with. Public access is not available unless personally

escorted by Gigenet staff or authorized ISP's.

IP Video Surveillance

Proximity Badge Reader

 Locking Cabinets

Fire Suppression
VESDA smoke detection, double-action dry pipe fire suppression modules prevent emergencies before

they start.

VESDA Processing Units

VESDA Processing Units

VESDA Processing Units

 Deluge Preaction Control Panel

Cooling
Leibert HVAC redundant architecture with overhead air distribution makes sure that your equipment is

always operating at optimum temperatures.

Leibert HVAC

Leibert
Leibert HVAC

Leibert HVAC

Leibert HVAC
Leibert HVAC