Appendix B. IPT Planning Phase: Network Infrastructure Analysis Questionnaire

The purpose of this questionnaire is to help you collect the information that you need about a customer’s existing network infrastructure to provide to that customer a Cisco IP telephony (IPT) solution. To obtain the answers to this questionnaire, you can either take this questionnaire and meet with the customer or e-mail the questionnaire to the customer and have them complete it. Customers usually provide some part of the information requested in this questionnaire in their Request for Proposal (RFP).

After you obtain from the customer all the information requested in this questionnaire, you must ensure that the network infrastructure adheres to the Cisco AVVID infrastructure recommendations, presented in Chapter 4, “Planning Phase.” If you encounter deviations from the best practices, you must communicate this to the customer and recommend a solution before proceeding with the IPT deployment.

Note

Some parts of this questionnaire are available on Cisco.com as part of the IP Telephony Network Readiness Assessment tool, at http://tools.cisco.com/Assessments/jsp/welcome.jsp?asmt=VOIP.

The following is an outline of the sections in the Network Infrastructure Analysis Questionnaire:

  • Customer Business and Technical Expectations

    • Company Overview

    • Company Vision

    • 3- to 5-Year Plan

    • Solution Expectations

    • Project Expectations

    • Deployment Time-frame

    • Financial Expectations

  • Network Design

    • Hierarchy

    • Modularity

    • Layer 2 Design—Core Layer

    • Layer 2 Design—Distribution Layer

    • Layer 2 Design—Access Layer

    • Wide-Area Network

      • WAN Design and High Availability

      • WAN—Network Baseline

      • WAN—Capacity Planning

    • Routed Network—Layer 3 Design

      • IP Addressing

      • Routing Protocol

      • IP Hot Standby Routing Protocol

      • Quality of Service

  • Network Services

    • DNS

    • DHCP

    • NTP

    • Directories

    • Messaging System

  • Cabling and Network Links

  • Hardware Scalability

  • Software

  • Power Protection and Environmental Condition

    • Power Protection

    • Environmental Condition

    • Power Calculations

  • Security

Some sections might not be applicable to the network that you are planning, so skip any such sections.

Customer Business and Technical Expectations

At the beginning of the planning phase, you must summarize the customer’s business, techinical expectations, requirements, and future growth plans to accommodate the increasing demands of the customer in terms of supporting additional IP phones, supporting new features, or adding more applications.

Company Overview

Table B-1 provides the questions that you should ask a customer to get an overview of the customer’s company.

Table B-1. Company Overview

No.

Question

Answer

1

What is the customer name?

 

2

Briefly describe the customer’s business.

 

3

Provide a brief overview of the services and applications that the customer is running on the network.

 

4

Identify whether the deployment is a “green field” (new network) opportunity. If it is not, give a brief overview of the current network.

 

Company Vision

What is the company’s proposed goals and expected growth in the next 3 to 5 years?

3- to 5-Year Plan

What is the company’s 3- to 5-year plan for both voice (telephony) and data networks?

Solution Expectations

What are the company’s upper management expectations and requirements for the completed solution, including service levels, features, and functionalities?

Project Expectations

What are the company’s upper management expectations and requirements regarding the project (timelines, priority deployment sites, success criteria, cost expectations, and so forth)?

Deployment Timeframe

The objective of this section is to collect answers to the following questions:

  • What expectations does the customer have for the deployment of the IPT solution?

  • What timeline does the customer have for the deployment of the IPT solution?

  • Should you give any sites, departments, or users priority for deployment?

Use Table B-2 to provide the timeline and description of various phases.

Table B-2. Deployment Timelines

Target

Start Date

End Date

Brief Description of the Phase

Successful rollout of IPT for entire organization

  

Marks the complete IPT rollout in the entire organization

Phase 1

  

Includes IPT rollout at Headquarters

Phase 2

  

Includes IPT rollout at branch sites

Phase 3

  

Deploy additional IPT applications

Add additional phases as needed

   

Typically, large-scale deployments divide the complete IPT deployment into smaller phases. For example, Phase 1 might be to roll out IPT to a group of users who are located at Headquarters, Phase 2 might be to roll out IPT at some branch sites, Phase 3 might be to deploy additional IPT applications, and so forth. You need to expand Table B-2 and clearly specify how you want to prioritize the deployment to achieve your final goal of converting your customer’s network to end-to-end IPT.

Financial Expectations

What are the company’s upper management expectations regarding the new solution’s return on investment (RoI)?

Network Design

The questions provided in this section will help you to gather detailed information on the customer’s network infrastructure.

Hierarchy

Network hierarchy and modularity are perhaps the two most important aspects of network design. A hierarchical network is easier to understand and easier to support because consistent, expected data flows for all applications occur on the network over similar access, distribution, and backbone layers. This reduces the overall management requirements of the network, increases understanding and supportability of the network, and often results in decreased traffic-flow problems, congestion issues, and troubleshooting requirements. Having a network hierarchy also improves the scalability of the network by allowing it to grow without requiring major network changes. Finally, a hierarchical network promotes address summarization, which is important in larger IP routing environments.

Table B-3 provides the questions that you should ask a customer to understand if the network design follows a hierarchical model.

Table B-3. Network Design—Hierarchy

No.

Question

Answer

1

Does the network have separate core, distribution, and access layers that are appropriate for the number of campus users?

□ Yes

□ No

2

Are users, servers, and WAN services connected to the access layer for all campus environments?

□ Yes

□ No

3

If a distributed campus environment exists, does the network support a hierarchical and modular WAN core with defined core, distribution, and access connectivity?

□ Yes

□ No

Notes/Comments

In this section, you need to collect the customer’s LAN architecture diagram for all sites that require the IPT deployment. Based on the answers to the questions in Table B-3 and after studying the network layout, you need to document the strengths and weaknesses in the network and provide the recommendations to the customer to make the infrastructure ready to run IPT for this area of the network.

Modularity

A modular network uses consistent network modules for the access, core, and distribution layers. Using a consistent “model” for each layer of the network improves the supportability because it becomes much easier to properly test modules, create troubleshooting procedures, document network components, train support staff, and quickly replace broken components.

Table B-4 provides the questions that you should ask a customer to understand if the network is designed following the modular approach guidelines.

Table B-4. Network Design—Modularity

No.

Question

Answer

1

Does the network have consistent hardware and software modules deployed for the LAN server and user access?

□ Yes

□ No

2

Does the network have consistent hardware and software modules deployed for the LAN distribution and core layers?

□ Yes

□ No

3

Does the network have consistent hardware and software modules deployed for access and distribution layer WAN services?

□ Yes

□ No

Notes/Comments

In this section, you need to obtain information about the router and switch hardware deployed at the core, distribution, and access layers. Use Table B-5 to gather the information, which will be helpful later to do the following:

Table B-5. Network Design—Hardware List Example

Layer

Vendor, Product Family

Installed Modules

Part Number

IOS/CatOS Version Number

Core

Cisco Catalyst 6509

1000BASE-X Supervisor

Multilayer Switch Feature

Multilayer Switch Feature

WS-X6K-SUP1A-2GE

WS-F6K-MSFC2

WS-X6348-RJ-45

CatOS 8.1.(3)

12.1.20E2

Distribution

Cisco Catalyst 6509

1000BASE-X Supervisor

Multilayer Switch Feature

10/100BASE-TX Ethernet

WS-X6K-SUP2-2GE

WS-F6K-MSFC2

WS-X6348-RJ-45

CatOS 8.1.(3)

12.1.20E2

Access

Cisco Catalyst 3550

48 inline power Ethernet

2 Gigabit Ethernet ports

WS-C3550-48-EMI

12.1.20-EA1

  • Determine whether the routers and switches are capable of supporting inline power.

  • Determine whether the routers and switches have hardware or software revisions or versions that are required to run specific IPT features.

  • Calculate the number of inline power modules required to provide the power to IP phones.

  • Calculate the power supply requirements for modular switches.

Layer 2 Design—Core Layer

This section looks at design and configuration considerations for the core layer for larger campus deployments. Smaller organizations might have more of a collapsed model, with the distribution and core layer functionalities combined in the same device.

Core Layer Performance

Table B-6 provides a list of questions that you should ask a customer to understand the current core layer performance characteristics.

Table B-6. Network Design—Core Layer Performance

No.

Question

Answer

1

Is it possible to increase the core capacity?

□ Yes

□ No

2

Do core layer devices have the required system resources, including backplane utilization, packet forwarding capability, CPU and memory to support redundant core failover, and fast Layer 2 and Layer 3 convergence?

□ Yes

□ No

3

If a Layer 2 core is used, will the Layer 3 neighbor count scale to the required growth?

□ Yes

□ No

Notes/Comments

Describe the extent to which it is possible to increase the capacity of the core, either with existing hardware or by upgrading the hardware. Also, highlight any hardware limitations.

Core Layer High Availability

Table B-7 provides a list of questions that you should ask a customer to understand the current core layer high-availability characteristics.

Table B-7. Network Design—Core Layer High Availability

No.

Question

Answer

1

Does the campus core support redundant and modular core layer devices?

□ Yes

□ No

2

Do Layer 3 equal-cost paths exist through the campus core for optimal routing convergence?

□ Yes

□ No

3

Are core layer devices environmentally controlled and power protected for higher availability?

□ Yes

□ No

Notes/Comments

Highlight any configuration problem that is not in line with best practices for the configuration of core switches.

Core Layer Configuration

Table B-8 provides a list of questions that you should ask a customer to understand the current core layer configuration characteristics.

Table B-8. Network Design—Core Layer Configuration

No.

Question

Answer

1

Are links between core layer devices and distribution layer devices hard configured for matching speed and duplex settings?

□ Yes

□ No

2

If a Layer 3 core is used, are the interfaces configured with point-to-point subnets?

□ Yes

□ No

3

Is ISL trunking or 802.1Q trunking eliminated from core layer devices?

□ Yes

□ No

Notes/Comments

Highlight any configuration problem that is not in line with best practices for the configuration of core switches.

Layer 2 Design—Distribution Layer

This section reviews the distribution layer architecture, high-availability considerations, and configuration of the distribution layer in a large campus environment. Smaller organizations might have a collapsed architecture. In smaller environments, for high availability, Cisco recommends combining the distribution and core layers and placing the servers on the access layer.

Distribution Layer Performance

Table B-9 provides a list of questions that you should ask a customer to understand the current distribution layer performance characteristics.

Table B-9. Network Design—Distribution Layer Performance

No.

Question

Answer

1

Does the distribution layer have increased bandwidth to handle access scalability, access aggregation, and distribution failover?

□ Yes

□ No

2

Do the distribution layer devices have sufficient backplane, CPU, and memory resources for the required multilayer switching and features (including Hot Standby Routing Protocol [HSRP])?

□ Yes

□ No

3

Do distribution layer devices have the required resources to support LAN campus QoS parameters deployed at the distribution layer?

□ Yes

□ No

Notes/Comments

Highlight any configuration problem that is not in line with best practices for the configuration of distribution switches.

Distribution Layer High Availability

Table B-10 provides a list of questions that you should ask a customer to understand the current core layer high-availability characteristics.

Table B-10. Network Design—Distribution Layer High Availability

No.

Question

Answer

1

Does the distribution layer have redundant devices that can handle bandwidth requirements when alternate or primary distribution connectivity is unavailable?

□ Yes

□ No

2

Has the organization anticipated failover and recovery scenarios with the chosen routing protocol, HSRP, and spanning-tree configuration?

□ Yes

□ No

3

Is trunking between distribution layer devices configured only for VLANs where high-availability server access is needed for multiple access switches?

□ Yes

□ No

Notes/Comments

Highlight any configuration problem that is not in line with best practices for configuration of distribution switches.

Distribution Layer VLAN Architecture

Use Table B-11 to collect the VLAN architecture information at distribution layer switches in the campus network.

Table B-11. Network Design—Distribution Layer VLAN Architecture

No.

Question

Answer

1

In general, are VLANs maintained on two distribution layer switches and one access layer switch only, and not carried on any link between the distribution layer switches?

□ Yes

□ No

2

Are VLANs limited to two distribution layer devices and two access layer devices where high-availability access is needed?

□ Yes

□ No

3

Are management VLANs separated from user VLANs at the distribution and access layers?

□ Yes

□ No

Notes/Comments

Highlight any configuration problem that is not in line with best practices for configuration of distribution switches.

Distribution Layer Configuration

Table B-12 provides a list of questions that you should ask a customer to get an overview of the current distribution layer configuration.

Table B-12. Network Design—Distribution Layer Configuration

No.

Question

Answer

1

Is spanning tree configured on distribution switches, even when loops are not planned?

□ Yes

□ No

2

Are the two distribution switches configured as alternating roots and secondary roots for alternating VLANs, with corresponding HSRP active and HSRP standby routers, for load balancing and redundancy?

□ Yes

□ No

3

Has Backbone Fast been set for all distribution switches?

□ Yes

□ No

4

Do links between access and distribution layer devices have hard-coded matching speed and full-duplex settings?

□ Yes

□ No

5

Has trunk mode been set explicitly to on for trunking ports?

□ Yes

□ No

6

Has channel mode been set to desirable for port channels?

□ Yes

□ No

7

Is Uni-Directional Link Detection (UDLD) configured for switch-to-switch connections?

□ Yes

□ No

Notes/Comments

Highlight any configuration problem that is not in line with best practices for configuration of distribution switches.

Layer 2 Design—Access Layer

Access Layer Characteristics

Table B-13 provides a list of questions that you should ask a customer to get an overview of current access layer characteristics.

Table B-13. Network Design—Access Layer Characteristics

No.

Question

Answer

1

Does the access layer support 10/100-Mbps switched connections for all user end stations?

□ Yes

□ No

2

Does the access layer support 100- or 1000-Mbps switched connections for all server and distribution connections?

□ Yes

□ No

3

Does the access layer device support multiple queues to prioritize voice traffic where needed?

□ Yes

□ No

4

Can the access layer devices handle peak utilization from servers and clients?

□ Yes

□ No

Notes/Comments

Highlight your findings on the access layer characteristics.

Access Layer High Availability

Table B-14 provides a list of questions that you should ask a customer to understand the current access layer high-availability characteristics.

Table B-14. Network Design—Access Layer High Availability

No.

Question

Answer

1

Do access switches have redundant trunking to two distribution switches and only to the distribution switches?

□ Yes

□ No

2

Do critical access switches have redundant processors and power supplies?

□ Yes

□ No

3

Do high-availability servers have redundant connections to a single VLAN on two access switches?

□ Yes

□ No

4

Is auto-negotiation configured for clients?

□ Yes

□ No

5

Has duplex and speed been matched for server connections?

□ Yes

□ No

6

Is PortFast configured on client/server ports?

□ Yes

□ No

7

Is UplinkFast configured on switches that support high-availability servers, where forwarding and blocking VLAN trunks exist on the access switch?

□ Yes

□ No

Notes/Comments

Highlight any configuration or design problems that are not in line with best practices for configuration of access layer switches.

Wide Area Network

This section looks at hub-and-spoke design considerations in Frame Relay hub-and-spoke environments.

WAN Design and High Availability

Table B-15 provides a list of questions that you should ask a customer to understand how the WAN links are provisioned, current link utilizations and configured QoS parameters.

Table B-15. Network Design—WAN Design and High Availability

No.

Question

Answer

1

Do you have a hub-and-spoke topology network?

□ Yes

□ No

2

Will the WAN have redundant links to support high availability across the WAN?

□ Yes

□ No

Notes/Comments

In this section, you need to obtain the following information pertaining to the customer’s WAN architecture:

  • The customer’s WAN diagram

  • A description of the overall WAN architecture

  • A list of the overall WAN strengths and weaknesses

WAN—Network Baseline

This section examines whether the organization has properly planned for the addition of IP telephony traffic in terms of the existing traffic and the addition of RTP voice streams. This starts with a baseline of busy-hour or peak data traffic on trunk ports and extends to resource utilization for LAN devices, including buffers, memory, and CPU utilization on devices. Table B-16 provides a list of questions that you should ask the customer to gather the WAN base line information.

Table B-16. Network Design—WAN Baseline

No.

Question

Answer

1

Do you collect a baseline for your WAN (intended to support Cisco IP Telephony) that includes link utilization, queue depth, end-to-end packet delay, CPU, and memory?

□ Yes

□ No

2

Has the organization determined the potential impact of Voice over IP (VoIP) traffic in the WAN in terms of bandwidth utilization and system resources?

□ Yes

□ No

3

Does the current baseline and added traffic suggest that utilization and system resources are well within network capabilities, including peak link utilization below 75 percent and WAN links with a minimum of 128 kbps?

□ Yes

□ No

Notes/Comments

Use this section to document the data for link utilization, end-to-end packet delay, and CPU usage for the WAN link. Also collect and document the information about memory that is installed on the router at the main location and at the branches.

Highlight any potential problems for IPT deployment.

WAN—Capacity Planning

You should ask the questions given in Table B-17 to analyze the capacity of the existing WAN and determine how much extra bandwidth is required to run the voice traffic along with the data traffic on the same links.

Table B-17. Network Design—WAN Capacity Planning

No.

Question

Answer

1

Will the WAN be upgraded to support Cisco IPT solutions to help ensure consistent voice performance?

□ Yes

□ No

2

Will WAN links that support voice traffic meet minimum bandwidth requirements for Cisco IPT deployments? (64-kbps frame, 64-kbps leased line, or 768-kbps ATM or ATM/Frame Relay is required.)

□ Yes

□ No

3

In Frame Relay environments, will the organization have committed information rate (CIR) in the Frame Relay network for voice and configure traffic shaping to the CIR to guarantee voice traffic within the Frame Relay network?

□ Yes

□ No

4

In ATM environments, will the organization use ATM traffic classes such as constant bit rate (CBR) or variable bit rate real time (VBR-rt) to guarantee critical voice traffic across the ATM network and shape ATM traffic to the guaranteed bandwidth?

□ Yes

□ No

5

Will the WAN have adequate bandwidth to support peak voice usage across the WAN?

□ Yes

□ No

Notes/Comments

Overall, is the network ready to run the voice traffic over the data network?

Routed Network—Layer 3 Design

This section reviews the current IP addressing scheme and information on routing/routed protocols that are deployed in the data network.

IP Addressing

Use Table B-18 to gather the information on the currently deployed IP addressing scheme for the data network and the customer’s plans for assigning the IP addresses to IPT devices such as IP phones, voice gateways, call processing servers, etc.

Table B-18. Network Design—IP Addressing

No.

Question

Answer

1

Provide the information on current IP addressing scheme.

 

2

Does your organization have an IP addressing plan for integrating IP phones into the network?

□ Yes

□ No

3

Does the organization have plans to implement RFC 1918 for private addressing?

□ Yes

□ No

4

Does the IP addressing plan support IP address summarization?

□ Yes

□ No

Notes/Comments

Use this section to document the currently deployed IP addressing scheme along with VLAN ID assignments, VLAN naming and numbering conventions followed.

Routing Protocol

Use table B-19 to analyze the current IP routing design and configurations deployed in the network.

Table B-19. Network Design—IP Routing Protocol

No.

Question

Answer

1

Has the organization implemented Open Shortest Path First (OSPF) or Enhanced Interior Gateway Routing Protocol (EIGRP) for improved network convergence?

□ Yes

□ No

2

Does the organization use any other routing protocols that redistribute to/from the primary EIGRP or OSPF autonomous system?

□ Yes

□ No

3

Does the organization maintain standard routing protocol configurations for all routers in the network?

□ Yes

□ No

4

Are static routes confined to network edges for partner connectivity or ISDN backup?

□ Yes

□ No

5

Has the organization implemented IP summarization toward the core to reduce routing protocol overhead and ensure IP scalability?

□ Yes

□ No

6

Has the organization implemented stub or default routing in WAN hub-and-spoke environments to reduce routing protocol traffic overhead on WAN links?

□ Yes

□ No

7

Has the organization reviewed routing protocol impact and scalability based on device types, number of routes, and IP routing protocol neighbors?

□ Yes

□ No

8

Is routing disabled on user and server LAN interfaces to prevent core routing through user LANs?

□ Yes

□ No

9

Is routing filtered on access site WAN interfaces to advertise only WAN site information?

□ Yes

□ No

10

What other interior routing protocols are used in the network other than IP?

List:

Notes/Comments

Describe the overall routing design.

Provide network maps and diagrams for the Layer 3 design.

IP Hot Standby Routing Protocol

This section looks at HSRP considerations with respect to the common infrastructure model. Table B-20 provides the questions that you should ask a customer to understand how the HSRP is designed in the network.

Table B-20. Network Design—IP HSRP

No.

Question

Answer

1

Does the network use HSRP for redundant default gateway support?

□ Yes

□ No

2

Does the organization understand convergence issues given the number of HSRP groups supported on the device?

□ Yes

□ No

3

Does the network use the HSRP preempt feature to return control to the primary gateway, closely associated with the spanning-tree root for the VLAN?

□ Yes

□ No

4

Has the organization considered the HSRP track feature that is used to track backbone or WAN connectivity from the primary HSRP gateway?

□ Yes

□ No

Notes/Comments

Describe how and where HSRP is deployed in each part of the network. HSRP design might be complex when it is deployed in Layer 2 switches with internal and chassis redundancy.

Quality of Service

You should use the questions provided in Table B-21 to analyze whether the network devices have the quality of service (QoS) capabilities to support IPT.

Table B-21. QoS

No.

Question

Answer

1

Can auxiliary VLANs with 802.1Q/p be used for voice?

□ Yes

□ No

2

Can the voice bearer streams be marked as EF (Expedited Forwarding) and voice control streams as AF31 (Assured Forwarding 31)/CS3 (Class Selector 3)?

□ Yes

□ No

3

Is QoS configurable on devices where buffers might be reaching capacity?

□ Yes

□ No

4

Is Low Latency Queuing (LLQ) configurable on all WAN interfaces?

□ Yes

□ No

5

Is Link Fragmentation and Interleaving (LFI) configurable on all links where speed is below 768 kbps?

□ Yes

□ No

6

Do you have any mission-critical traffic besides voice (e.g., video, DLSW, etc.)? If Yes, please specify the traffic types and how they are currently classified in your network.

□ Yes

□ No

Notes/Comments

Describe the QoS strategy in place and highlight any potential problems when deploying voice over the data network.

Network Services

Network services are included because they are critical to the overall functionality of IP telephony environments. The major services are Domain Name Service (DNS), Dynamic Host Configuration Protocol (DHCP) and Network Time Protocol (NTP). This section looks at the configuration and resiliency of these services for high availability, overall manageability, and functionality requirements in the IP telephony environment.

DNS

DNS is an important network service. Table B-22 provides a list of questions that you should ask customers to evaluate configuration and resiliency of DNS in terms of network devices.

Table B-22. DNS

No.

Question

Answer

1

Does the organization have a resilient DNS architecture with primary and secondary DNS servers?

□ Yes

□ No

2

Provide the DNS server IP addresses and your fully qualified domain name.

□ DNS 1

__________________

□ DNS 2

__________________

□ FQDN

__________________

Notes/Comments

DNS is not mandatory for deployment of IPT. However, it provides load balancing and redundancy for accessing IPT XML services.

DHCP

DHCP is an important network service for large-scale IP telephone provisioning. All IP telephony implementations should implement DHCP for phone provisioning otherwise, manual phone configuration is required. The DHCP service should support option 150 (to support Cisco IPT implementations), which is one of the custom options that can be configured in the DHCP servers. These custom options allow the DHCP servers to provide additional information to the DHCP clients and, in case of IPT networks, the IP phones and the gateways. Option 150 in Cisco IPT networks provides the TFTP server information to the IPT endpoints. Use the questions in Table B-23 to get information about customer DHCP implementation.

Table B-23. DHCP Implementation Details

No.

Question

Answer

1

Does the organization use DHCP services to provide the IP addressing for clients?

□ Yes

□ No

2

What DHCP software (including version number) is in use?

□ MS DHCP

□ Lucent QIP

□ Other

□ Specify

3

Will the DHCP server support the configuration of customized options? (IP phones accept the TFTP server information in DHCP option 150 or 66.)

□ Yes

□ No

4

If the answer to question 3 is yes, can the IPT network use your existing DHCP server to provide the IP addresses to IPT endpoints such as IP Phones and voice gateways?

□ Yes

□ No

5

Is the DHCP service resilient with configuration backups and disk mirroring?

□ Yes

□ No

6

Do you use a centralized DHCP server for the entire organization?

□ Yes

□ No

7

If you have distributed DHCP services at the remote branches, does the router provide the DHCP services, or do you have a separate DHCP server for each branch office?

Provide details in the “Notes/Comments” section.

Notes/Comments

Add any additional information about the customer’s DHCP implementation.

Network Time Protocol

The use of NTP services in the network ensures that all the devices in the network use the same time source to synchronize their clocks. Use Table B-24 to evaluate the existing NTP configuration and setup in the customer’s network.

Table B-24. NTP

No.

Question

Answer

1

Does the organization currently use NTP?

□ Yes

□ No

2

If the answer to question 1 is yes, what are the NTP IP addresses of the NTP sources?

□ Source 1

_________________

□ Source 2

_________________

3

Do you want to configure the IPT devices to synchronize their clocks with NTP servers?

□ Yes

□ No

Notes/Comments

Understand how NTP is implemented today in the network and use the information gathered in Table B-24 to implement NTP in the voice devices, such as CallManager servers, IPT application servers, and gateways.

Directories

Organizations use directories to store employee-related information such as e-mail ID, phone numbers, location, user ID, authentication information, etc. Table B-25 provides the list of questions that you should ask the customer to understand the currently deployed directory.

Table B-25. Directory

No.

Question

Answer

1

What directory service is currently deployed in the organization?

□ Microsoft AD

□ Netscape

□ Sun One

□ iPlanet

□ Version

_______________

2

Is there a requirement to integrate the IPT applications with your existing corporate directory?

□ Yes

□ No

3

If directory integration is not a requirement, are you looking at providing the corporate directory access lookup from IP Phones?

□ Yes

□ No

Notes/Comments

Cisco IPT applications such as Cisco CallManager use an embedded directory (DC Directory) to store user information such as password, PIN number, phone number, speed dials, and so forth. If the customer’s organization has deployed a directory, Cisco IPT applications can integrate with it, without the embedded directory. This reduces the administrative overhead and provides a single repository for all the applications. Careful planning is required for the successful integration of IPT applications with the existing corporate directory.

Messaging System

Use Table B-26 to gather the information about customer’s current existing messaging system.

Table B-26. Messaging System

No.

Question

Answer

1

What is the current e-mail messaging environment used in the organization?

□ MS Exchange

□ Lotus Domino

□ Other

□ Version

_______________

2

Does the organization intend to deploy unified messaging along with the IP telephony deployment?

□ Yes

□ No

Notes/Comments

If the customer decides to use unified messaging, you should obtain some preliminary information on its messaging architecture. You can collect detailed information using the Voice-Mail Design Questionnaire in Appendix G.

Cabling and Network Links

Use Table B-27 to analyze if your customer network uses the industry standard copper/fiber cabling systems, redundancy, and diversity for riser, interbuilding, and long-distance WAN connections.

Table B-27. Cabling and Network Links

No.

Question

Answer

1

Does the organization follow common guidelines for twisted-pair Category 5 cabling installations?

□ Yes

□ No

2

Does the organization maintain well-organized patch cords and cable labeling for WAN cables, fiber, and copper?

□ Yes

□ No

3

Does the organization follow common guidelines for building or interbuilding campus fiber installations?

□ Yes

□ No

4

Is the fiber and copper cabling tested?

□ Yes

□ No

5

Does the organization have non-Ethernet segments in the network?

□ Yes

□ No

Notes/Comments

The information that you collect from Table B-27 helps you to analyze the existing cabling infrastructure and provide recommendations.

Hardware Scalability

This section reviews the hardware that is deployed in the network to ensure that feature requirements, scalability, and hardware resources will meet IPT requirements. The process of hardware replacement is also critical to higher availability. Table B-28 provides a list of questions that you should ask customers to analyze whether the existing hardware in the network supports the IPT deployment: If not, you can suggest the modifications required to support the IPT deployment.

Table B-28. Hardware Scalability

No.

Question

Answer

1

Are there any non-Cisco switches at the access layer in the network?

□ Yes

□ No

2

Do you need to connect the Cisco IP Phones to the non-Cisco access switches?

□ Yes

□ No

3

If you have non-Cisco switches, do they support 802.1Q/p?

□ Yes

□ No

4

Which Power over Ethernet (PoE) standard does the organization want to use?

□ Cisco PoE

□ IEEE 802.3af

5

Can the other Cisco switches in the access layer be field upgraded to support inline power?

□ Yes

□ No

6

Will the hardware scale to support the IPT endpoints, such as IP phones and gateways?

□ Yes

□ No

7

Does the organization have chassis redundancy where appropriate?

□ Yes

□ No

8

Does the organization have module redundancy where appropriate?

□ Yes

□ No

9

Does the organization keep spare hardware parts onsite?

□ Yes

□ No

10

Does the organization have a service contract with the hardware vendor to replace the defective parts? If yes, what is the agreed response time?

□ Yes

□ No

□ Response Time

_______________

Notes/Comments

You must determine the hardware scalability section for every site in the network. Key things to note are whether the access layer switches are Cisco or non-Cisco switches and the support of 802.1Q/p protocol, because these determine the QoS capabilities of access layer switches and which PoE standard the organization uses.

Software

This section looks at infrastructure software to help ensure that the software versions used will support features required by IP telephony, are tested, and are standardized within the organization. Table B-29 provides a list of questions that you should ask customer to understand the software certification processes that exist in the organization.

Table B-29. Software

No.

Question

Answer

1

Does the organization create and maintain software standards for the network?

□ Yes

□ No

2

Does the organization have a software certification process in place?

□ Yes

□ No

3

Is software tested before it is deployed on the production network?

□ Yes

□ No

4

Does the organization standardize on general deployment software where possible?

□ Yes

□ No

5

Does the organization maintain standard global software configurations?

□ Yes

□ No

Notes/Comments

Provide the versions of Cisco IOS and Catalyst OS running on the network.

Power Protection and Environmental Condition

This section looks at power and environment to help ensure that the organization has a power protection strategy for infrastructure components that support IP telephony. The organization should also perform environmental planning to ensure devices are properly environmentally conditioned for temperature and humidity. The equipment should also be located in physically secure locations, accessible only to networking staff.

Power Protection

Table B-30 provides a list of questions that you should ask customer to understand the current power protection strategy implemented in the network.

Table B-30. Power Protection

No.

Question

Answer

1

Are core and distribution layer devices that serve multiple buildings or sites power protected with UPS and generator backup?

□ Yes

□ No

2

Are access switches backed up with UPS or a generator where power-protected network access or IP telephony is required?

□ Yes

□ No

3

Does the organization use network components that support redundant power supplies?

□ Yes

□ No

4

Does the organization perform periodic maintenance on UPS and generator systems to ensure system availability?

□ Yes

□ No

Notes/Comments

When you deploy IPT and use an inline power method to deliver the power to IP Phones, delivering uninterruptible power is necessary to achieve high availability. It is especially important for the access layer switches to include redundant power supplies. Based on your observations collected from Table B-30, provide your recommendations in this section.

Environmental Condition

This section examines the processes followed in the organization to monitor and maintain the stable environmental condition for various components to function properly. Table B-31 provides a list of questions you should ask the customer to understand the current measures that are implemented for environmental conditioning.

Table B-31. Environmental Condition

No.

Question

Answer

1

Does the organization investigate heat dissipation, temperature, and humidity information for new product implementations?

□ Yes

□ No

2

Does the organization provide uninterrupted ventilation and cooling to network devices to maintain a consistent operating temperature and environment?

□ Yes

□ No

3

Does the organization use environmental monitoring systems for critical equipment locations?

□ Yes

□ No

4

Does the server room where you are planning to house the IPT servers, switches, and gateways have enough rack space?

□ Yes

□ No

5

Do you have adequate power outlets to support the additional devices?

□ Yes

□ No

6

What is the current capacity of the UPS system?

Capacity

_______

7

Can the existing UPS system handle the additional load to support the new IPT servers, gateways, and switches?

□ Yes

□ No

Notes/Comments

Based on the answers to the questions in Table B-31, you can provide the recommendations to the customer on the importance of constant checking of environmental conditions for power backup systems to ensure uninterruptible functioning of the IPT system.

Power Calculations

As part of the infrastructure analysis, you need to collect the information as per Table B-32. You will not know the type of Cisco IP phone models at the time of the planning phase. However, you need to determine the switch hardware and line card information so that you can size the power supply capacities on the switches correctly after you decide on the phone models. Typically, you decide on the phone model selection during the design phase. You need to come back to this table during the design phase and input your phone quantities selected phone models in Table B-32. (Refer to Table B-5 to get hardware information on the switches that are deployed in the network.)

Table B-32. Power Calculations

Switch Name, Location, Product Family, Chassis Type

Line Cards Installed

Input Voltage

Cisco IP Phone Model

Quantity

Recommendations from Cisco Power Calculator

   

7960G

7970G

7940G

  
   

7960G

7970G

7940G

  
   

7960G

7970G

7940G

  

Notes/Comments

You can input the information collected in Table B-32 in the Cisco Power Calculator (CPC), available on Cisco.com at http://tools.cisco.com/cpc/launch.jsp, to complete the power calculations.

In Table B-32, in the “Recommendations from Cisco Power Calculator” column, you can put the output of the CPC, such as whether the system can support the specified number of IP phones, whether the system requires additional power supply, etc.

Security

This section looks at general security practices followed in the organization. Table B-33 provides a list of questions you should ask the customer to gather this information.

Table B-33. Security

No.

Question

Answer

1

Has the organization developed a security policy regarding access to network devices, monitoring, privacy, and protection of information assets?

□ Yes

□ No

2

Has the organization implemented basic security measures such as strong passwords and password encryption to control access to the devices via network?

□ Yes

□ No

3

Are the network devices in a secure and locked location that requires authorization for physical access?

□ Yes

□ No

4

Is there a mechanism employed to authenticate users, control access to network devices, and provide accounting information for audit purposes?

□ Yes

□ No

5

What antivirus software does the organization use currently to protect the servers and workstations from viruses?

□ McAfee

□ Symantec

□ Trend Micro

□ Other

____________

□ Version No

____________

6

Does the organization currently use any host-based intrusion detection/prevention software? If yes, provide the name of the product and vendor.

□ Yes

□ No

□ Product

____________

□ Vendor

____________

7

Does the organization have a defined policy for applying the security hot fixes and operating system patches to critical servers? If yes, describe it in the “Notes/Comments” section. Include information such as how long it would take to apply a critical hot fix, what testing/certification procedures are followed, etc.

□ Yes

□ No

Notes/Comments

Based on the information in Table B-33, you can provide the recommendations, if necessary, to secure the IP telephony infrastructure components.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset