Microsoft Power Point - Event Qatar 1st Nov Building A Campus LAN Only)

HP Networking Burhan Abu Baja burhan@hp.com +974 33 101 383 1 2010 Hewlett-Packard Development Company, L.P.
The
information contained herein is subject to change without notice
Topics of Discussion
High Availability what is it and why we need it? High Availability problems to solve High Availability how to make it?
Internal Use Only. HP Confidential.
What
Five nines 99.999% - 5 minutes in a year downtime Service availability (always on, internet dial tone) Absolute reliability and survivability Data integrity and protection
Why
Internet centralized service model Many people rely on network delivered service (service dependency) Around the clock operation no maintenance time. Carrier-grade systems a buzzword Business downtime costs a lot of money
Problem
Equipment and software not reliable enough MTBF and MTTR availability = (MTBF + MTTR)/MTTR Complex systems combination of MTBF of components MTTR for HW/SW automatic recovery (reboot) still bad
Mean Time To Repair Mean Time Between Failures
How
No single point of failure hardware, software, network Redundancy for hardware Warm restarts for software (problematic) so better rely on hardware redundancy as well
Redundancy Types
Load sharing, Load balanced, Active/Active, hot standby, cold standby 1:1, 1:N, M:N Chain redundancy versus block redundancy
Network challenges
Faults and Fault isolation Failures result of faults Ways to recover redundancy hot failover Hardware failover switching HW resources (network, fans, CPUs) Software failover applications, protocols, databases etc
Design principles
Hot swappability support to replace faulty units (FRUs) Resource (equipment and software modules) model and management Logging, trace, reporting of failures/switchovers Checkpointing (data mirroring or synchronization) initially and continuously Provisioning redundancy state, software upgrades, different versions.
9 Internal Use Only. HP Confidential.
Challenges of the Enterprise Campus Network Solution
10
11
Best Design Model of Enterprise Campus Network

WAN/Branches
Core Layer Hierarchical
Convergence Layer
Modular
Access Layer
Expandable
Redundant
Service Layer
Hierarchical Structure Design of Enterprise Campus Network

Hierarchical The hierarchical network architecture design, and strict definition of the functions of different layers 1. Access layer -The first-layer access of the network achieves L2/L3 access, QoS, broadcast storm suppression, edge port, access security authentication, VLAN, link binding, 802.1x, and PoE/PoE+. 2. Convergence layer Converges traffic from the cable distribution room and executes policies. It can provide functions such as first-hop gateway, route summary, load balancing, fast convergence, QoS, and the protection of core access users. 3. Core layer-Network backbone. It features high-speed data switching, high capacity, reliability, fast convergence, and ease of network expansion. Modular Divide topological regions according to architectural regions. Expandable According to service development requirements, expand the network through the simple replication of modular units Redundancy design Provide redundancy protection to equipment and links
13
High Availability how to make it?

Introduction to Non-Stop Forwarding Technology (NSF) Link Reliability Link Aggregation Technology RRPP Technology Smart Link Technology DLDP Technology High Reliability Networking Technologies VRRP Equivalent Route BFD IP FRR IRF
14
None Stop Forwarding
15
NSF schematic diagram
Forwarding Information Base
16
NSF schematic
As an important HA technology on the service plane, NSF ensures non-stop data forwarding when the control plane of the switch fails, for example, fault-triggered restart or routing oscillation, thus preventing various streams of the network from being impacted. To support NSF, a device should meet the following two requirements: The device should adopt the distributed architecture, with data forwarding separate from control, and support dual MPUs. When an active/standby switchover takes place, the standby MPU must save IP/MPLS forwarding entries (forwarding plane) successfully.
Status (control plane) of some protocols can be saved. For OSPF, IS-IS, BGP, LDP and other complicated protocols, it costs a lot or it is impossible to completely back up complicated status of the control plane. In contrast, by partly backing up some protocol status (or not backing up protocol status) and the help of adjacent devices, session connections on the control panel are not reset in the case of active/standby switchover so that forwarding is not interrupted.
17
GR schematic diagram
18
GR schematic
The technology for not resetting the control plane is called graceful restart (GR) of routing protocols, which shows that forwarding is not interrupted when routing protocols are restarted. The core of the GR mechanism is when the routing protocol of a device is restarted, it informs adjacent devices of keeping the neighbor relationship and routes to the device stable for a certain period. After the routing protocol is completely restarted, the adjacent devices help the device to synchronize the routing information and restore the routing information of the device to the state before the restart within the shortest time. During the entire protocol restart, network routes and forwarding are kept highly stable. The packet forwarding path is not changed in any way. The whole system can forward IP packets continually. The HP A-Series series switches support GR for OSFP/BGP/IS-IS/LDP/RSVP. When the active/standby switchover of MPUs takes place, the peer device continues keeping the protocol neighbor relationship with the local device, thus avoiding network oscillation and guaranteeing network stability.
Label Distribution Protocol (LDP) Resource Reservation Protocol (RSVP)
High Availability how to make it?

Link Reliability

Link Aggregation Technology RRPP Technology Smart Link Technology DLDP Technology
20
Link Aggregation Technology
21

Link aggregation/trunking/bonding technology. The essence of the technology is that a number of physical links between two devices are combined into a logical data channel, called an aggregated link. Two physical links between switches form an aggregated link. Logically the link is a totality. The internal composition and details of data transmission are transparent to the upperlevel services.
22

The physical links within the aggregation jointly complete the tasks of data transmitting/receiving, and provide backup to each other. As long as the aggregation has a normal member, the whole transmission link will not fail. If Link 1 fails, data tasks of Link 1 are rapidly transferred to Link 2 and data streams between two switches are not interrupted.
23
RRPP Technology
2 4
24
RRPP Technology (Rapid Ring Protection

Protocol)
Dedicated to Ethernet rings, RRPP is a link layer protocol, which avoids broadcast storm caused by data loops on a complete Ethernet ring. When one link on the Ethernet ring is cut off, RRPP rapidly restores communication path between nodes on the ring network. Most MANs and enterprise networks are ring networks to guarantee high reliability. However, failure of any node on the ring may affect services. Currently, STP and RRPP are common technologies used to solve loop problems on L2 networks. STP applications are relatively mature, but convergence is accurate to second. As a link layer protocol dedicated to Ethernet loops, RRPP supports faster convergence than STP. In addition, convergence time supported by RRPP is irrelative to the number of nodes on the ring network. RRPP can be applied to the networks with long diameters. The HP Switches supports RRPP multiple instances and establishment of multiple RRPP networks, thus meeting the flexibility requirements of networking.
RRPP Technology
Polling mechanism is that for master nodes on the RRPP ring to actively detect health of the ring network. The master node regularly sends Hello packets from its master port, which are transmitted on the ring by passing each transmit node in turn. If the loop is healthy, the secondary port on the master node receives the Hello packets before the timer expires and the master node keeps the blocking status of the slave port. If a loop is cut off, the secondary port on the primary node cannot receive Hello packets before the timer expires, the master node removes the blocking status of data VLAN on the secondary port and sends a Common-Flush-FDB packet to notify all transmit nodes of updating their own MAC entries and ARP/ND entries.
26
filtering database Neighbor Discovery
RRPP Technology
When discovering one of their ports in the RRPP domain is down, a transmit node, an edge node, or an auxiliary edge node sends a Link-Down packet immediately to the master node. After receiving the Link-Down packet, the master node removes the blocking status of the data VLAN on its secondary port and sends the Common-Flush-FDB packet to notify all transmit nodes, edge nodes, and auxiliary edge nodes of updating their own MAC entries and ARP/ND entries. After each node updates its own entry, data streams are switched over to normal links. In addition, RRPP can be configured on an aggregation group and link reliability is guaranteed by aggregation and RRPP.
27
Smart Link Technology
2 8
28

A Smart Link group is also called a flexible link group. Each Smart Link group contains two ports only. One is an active port and the other is a standby port. Normally, only one port is in active state, while the other port is blocked, in standby state. When the link of the active port fails, the Smart Link group automatically blocks this port and the standby port is switched over to be an active port. For example, the port is down and OAM unidirectional link occurs. In addition, Smart Link can be configured on an aggregation group and link reliability is guaranteed by aggregation and Smart Link. Smart link meets the requirement for rapid link convergence and also backs up active/standby links for redundancy and rapidly migrates active/standby links. In the networking with two uplinks, when the active link fails, the device automatically switches over traffic to the standby link, thus backing up links for redundancy.
29

Operations, Administration, and Maintenance

The main characteristics are as follows: Dedicated to two uplinks Rapid convergence (accurate to sub-second) Simple configuration, which facilitates user operation When a Smart Link is switched over, MAC address forwarding entry and ARP/ND entry on each device on the network may not be the latest. To properly send packets, a mechanism for updating MAC address forwarding entries and ARP/ND entries should be provided. Currently, two update mechanisms are available:
Automatically update MAC address forwarding entries and ARP/ND entries by traffic. This mode is applicable to interconnection to the devices (including the devices of other vendors) that do not support Smart Link. It should be triggered by upstream traffic. A Smart Link device sends Flush packets from a new link. This mode requires upstream devices to identify Flush packets on the Smart Link and update MAC address forwarding entries and ARP/ND entries.
When the original active link is failed over, the port is still in standby state without link status switchover, thus keeping traffic stable. This port is switched to be active only after next link switchover. Smart Link supports multiple instances. In different Smart Link instances, one port can assume different roles. For example, in instance 1, a port is an active port, while in instance 2, the port is a standby port. In this case, traffic load of different instances can be balanced between ports.
30
DLDP Technology
31
DLDP Technology
A special phenomenon occurs during actual networking, namely, unidirectional link. Unidirectional link means that the local end can receive the packets sent by the peer end over the link layer, but the peer end cannot receive the packets sent by the local end. Unidirectional link leads to a series of problems, such as loop in spanning tree topology.
Cross-connect of fibers
One disconnected fiber or one broken fiber
Take fiber as an example. A unidirectional link is classified into two cases: fibers are cross-connected; one fiber is disconnected or one fiber is cut off. Crossed fibers refer to the fibers which are connected reversely. Hollow lines indicate that one fiber is not connected or one fiber is cut off. 32 Internal Use Only. HP Confidential.
DLDP Technology
DLDP can monitor link status of fibers or copper twisted pairs. If a unidirectional link exists, DLDP automatically disables related ports or notifies users of manually disabling them according to user configuration to prevent network problems.
DLDP is a link layer protocol, which is used together with the protocols at the physical layer to monitor link status of devices. The automatic negotiation mechanism at the physical layer detects physical signals and faults. DLDP identifies peer devices and a unidirectional link, and disables an unreachable port. DLDP and the automatic negotiation mechanism at the physical layer work together to detect and disable physical and logical unidirectional connection. If the links at both local end and remote end can work properly at the physical layer, DLDP detects whether these links are properly connected and whether two ends can properly exchange packets at the link layer. This detection cannot be implemented by the automatic negotiation mechanism.
33
DLDP Technology
DLDP has the following two working modes: Common mode: In this mode, once the aging timer of a neighbor expires, one Advertisement packet with RSY tag/label is sent concurrently when the neighbor entry is deleted. Enhanced mode: In this mode, once the aging timer of a neighbor expires, the enhanced timer is started. Every one second, one Probe packet is sent to actively detect the neighbor. Eight Probe packets are continuously sent. If an Echo packet from the neighbor is not received when the Echo wait timer expires, the device is disabled.
34
Enhanced DLDP mode
DLDP Technology
In common mode of DLDP, the system can identify one type of unidirectional link only: cross-connected fibers. In enhanced mode of DLDP, the system can identify two types of unidirectional links. One is cross-connected fibers, and the other is one disconnected fiber or one broken fiber. When detecting the unidirectional link of the latter type, a port should be set to work in forced rate and forced full duplex modes. Otherwise, even if DLDP is enabled, DLDP is invalid. When the unidirectional link of the latter type occurs, the port that has optical signal at the receive end is disabled, while the port that does not have optical signal at the receive end is inactive.
35
High Reliability Technology of Network

Network reliability technologies include the following:
VRRP Equivalent route BFD FRR, including IP FRR, MPLS TE FRR
36
VRRP
37
VRRP: Virtual Router Redundancy Protocol
Virtual Router
Switch A
Switch B
Switch C
38
VRRP Parameters
VRRP priority

Range: 0-255 (0 and 255 are not configurable) If a router is the IP address owner: its priority becomes 255
Working mode

Preemptive Non-preemptive
Authentication mode

simple md5
Master / backup
Virtual Router
Switch A Master
Virtual IP address: 10.1.1.1/24
10.1.1.2/24 Host A
Switch B Backup
10.1.1.3/24 Host B
Switch C Backup
10.1.1.4/24 Host C
40
Load Balancing
Virtual Router 1 Master Host A Virtual Router 2 Backup Virtual Router 3 Backup
Switch A
Backup Host B
Master
Backup
Switch B
Switch C
Host C
Backup
Backup
Master
41
Equivalent Route
4 2
42
Equivalent Route
The HP A-Series series switches support equal-cost multi-path routing (ECMP). Each route supports eight equivalent paths for load balancing of IP or MPLS traffic and also supports Hash load balancing by driving traffic. ECMP minimizes occurrence of disordered packets. After path switchover, traffic is rapidly switched over to other active links, thus guaranteeing service reliability.
43
BFD
4 4
44
BFD
BFD is a network wide unified detection mechanism for fast detecting and monitoring the connectivity of network links or IP route forwarding. To improve the existing network performance, the adjacent protocols should be able to fast detect a communication fault, thus quickly establishing a backup channel to restore communication. BFD: Defined by the IETF, BFD rapidly detects faults of nodes and links. By default, the handshake time is 10ms. BFD enables detection with light load and short duration. BFD can detect any medium and any protocol layer in real time. The detection time and overhead range are wide. BFD can detect faults on any type of channel between systems, including direct physical link, tunnel, MPLS LSP, multi-hop routing channel and indirect channel. BFD detection results can be applied to IGP fast convergence and FRR. BFD protocol has been accepted and recognized by the industry and deployed widely.
45
BFD: Bidirectional Forwarding Detection

The HP A-Series series switches fully support BFD for VRRP/BGP/IS-IS/OSPF/RSVP/VPLS PW/static routing. On the basis of the dual planes (control plane and forwarding plane) of the traditional core switch, the switches adopt the unique design of the detection plane. The plane monitors network faults. It helps to implement 30ms fault detection and 50ms service switchover, ensuring that services are not interrupted. The detection plane and the control plane & forwarding plane are independent from each other and will not affect each other. They provide carrier-class equipment reliability and network reliability to users. A test shows that BFD switchover time of the HP A-Series is shorter than 50ms.
46
IP FRR: Fast ReRoute
47

The interruption of traffic transmission caused by a link or node fault on the network is restored only when the route is reconverged on the new topology. During the time interval between interruption and restoration, the packets that can reach the destination by penetrating the faulty part will be lost or undergo a loop. The route convergence process consists of the following aspects: 1. 2. 3. 4. Fault detection time Re-propagation time of the routing information (including the generation and propagation time of LSA/LSP) Route calculation time (including the time for LSDB route calculation after the change) Route delivery time (including inter-board synchronization of FIB entries and time for delivery to the driver)
Currently, a number of new technologies are used in fast convergence of routing protocols. For example, shorten fault detection time by BFD, lessen the time for re-propagating routing information by Fast Flood, and decrease the time for route calculation by ISPF and PRC. As a result, route convergence is greatly quickened. Currently, in the case of 10,000 routes, traffic interruption time caused by a network fault can be within one second. However, voice, video and other new network services pose more stringent requirements on the traffic interruption time. A large number of carriers hope to control the traffic interruption time caused by network faults within 50 ms or less. This requirement cannot be satisfied by the traditional routing protocol fast convergence technologies. At present, the new method that is being researched for meeting such a requirement is to calculate backup route in advance. In other words, when detecting a fault, a router does not disseminate route information or calculate a route at once.
48

Instead, the router replaces the failed route with the backup route to directly rectify the fault locally. During the process when the whole new route completes re-convergence, the pre-determined backup route is used for forwarding. In this case, traffic interruption time which is equal to the sum of the time for detecting an adjacent fault and the time for replacing the failed route with a backup route is greatly shortened. The new technology of using local preset repair path to provide protection for the failed link or router is called IP FRR.
49

The basic principle for IP FRR, Normally, the routing table of Switch B indicates that the packets with the destination of Switch E should be forwarded by Switch D. In addition, a backup path is added to the routing table of Switch B, that is, the packets with the destination of Switch E can be forwarded by Switch C. When detecting a link fault between Switch B and Switch D, Switch B forwards the packets with the destination of Switch E to the backup next-hop Switch C.
50
IRFv2 Overview
51
IRFv2 - Overview
No need for MSTP+VRRP
Common networking
IRFv1
IRFv2
IRFv2 Overview (2)
53
Operational Planes in Standalone Switches

Stackable Switches
MGMT CTRL FWD SRPU #1 SRPU #2 LPU #1 LPU # 2 LPU # 3 LPU # N
Chassis-based Switches
MGMT (Master) MGMT (Slave) MGMT (Proxy) MGMT (Proxy) MGMT (Proxy) MGMT (Proxy) CTRL (Active) CTRL (Standby) CTRL (Proxy) CTRL (Proxy) CTRL (Proxy) CTRL (Proxy) FWD-Crossbar (Active) FWD-Crossbar (Backup or Load Sharing) FWD FWD FWD FWD
Switch
54
Operational Planes in IRFv2

Stackable Switches
MGMT (Master) CTRL (Active)
FWD LPU #1 Unit #2 MGMT (Slave and Proxy) CTRL (Standby and Proxy) FWD MGMT (Slave and Proxy) CTRL (Standby and Proxy) FWD MGMT (Slave and Proxy) CTRL (Standby and Proxy) FWD LPU #2 LPU #N SRPU #1 SRPU #2
Chassis-based Switches
MGMT (Master)
MGMT (Slave) MGMT CTRL (Proxy) (Proxy) MGMT CTRL (Proxy) (Proxy) MGMT CTRL (Proxy) (Proxy)
CTRL (Active)
CTRL (Standby)
Unit #1
FWD-Crossbar (Active) FWD-Crossbar (Backup or Load Sharing) FWD FWD FWD
Chassis #1
CTRL (Standby) CTRL (Standby) FWD-Crossbar (Active) FWD-Crossbar (Backup or Load Sharing) FWD FWD FWD
Unit #3
SRPU #1 SRPU #2
Unit #4
LPU #1 LPU #2 LPU #N
MGMT (Slave) MGMT (Slave) MGMT CTRL (Proxy) (Proxy) MGMT CTRL (Proxy) (Proxy) MGMT CTRL (Proxy) (Proxy)
Chassis #2
IRF System
IRF System
Daisy Chain
Master
IRFv2: Members, Roles and Topology

Slave
IRF-port 2 IRF-port 1 IRF-port 2
Slave
IRF-port 1 IRF-port 2
Slave
IRF-port 1
Ring
Master
IRF-port 1 IRF-port 2 IRF-port 1 IRF-port 2 IRF-port 1 IRF-port 2
Slave
IRF-port 1 IRF-port 2
Slave
Slave
IRFv2 IRF Connections

IRFv2 systems are connected using any 10 GbE interface:
1
57
CX4 SFP+ XFP XENPAK
Inexpensive Local Connection cables are available for CX4, SPF+ and XFP ports.
Building and Maintaining IRF
58
Steps to Build an IRF

1. Assign a high IRF priority to the device you want to be the master and ensure its Member ID is 1.
irf member member-id priority 32
2. Assign a Member ID to each on of the other devices and reboot them. irf member current-member-id renumber newmember-id
Steps to Build an IRF (2)

3. Configure the IRF-ports in each device, save the configuration and turn them off. This step varies slightly between different product families
In the HP 4800G/HP S5500-EI: irf member 1 irf-port 1 port 2
In the HP S5800/S5820X and in the HP S7900E/HP S7500E interface ten-gigabit port-id shutdown irf-port 1/1 port group interface ten-gigabit port-id interface ten-gigabit port-id undo shutdown
60
Steps to Build an IRF (3)

4. 5.
Save the configuration of each device and turn them off. Connect the IRF links to build the IRF fabric.
Note: IRF-port 1 of one device must be connected to IRF-port 2 of the next device. Connecting IRF-ports of the same number will prevent the devices to recognize each other as members of the same IRF.
6.
Turn on the unit that needs to be the master (Member-id=1)

Wait until the boot process is complete before turning on the next device. This will guarantee that this unit will become the master.
7.
Repeat the process for each member (turn on and wait). This step is called device insertion. Always turn on a device connected to other devices that are already up and running.
61
IRF Merge: Master Election

1. The current master wins, even if a new member has a higher priority. (When a new member is added, IRF merge does not happen.) 2. A member with a higher priority wins. 3. A member with the longest system up-time wins. (The precision of the system up-time is ten minutes.) 4. A member with the lowest bridge MAC address wins.
IRF Split: MAD
Blocked Port
Broken IRF Link Device in Normal state Device in Recovery state
63
MAD Detection Protocols

MAD can be configured to use BFD or LACP as the IRF split detection protocol. MAD/LACP:
Uses a distributed Bridge Aggregation interface connected to a 3rd device to exchange MAD information To support this function LACP has been extended with MAD specific TLV fields.
MAD/BFD:

a special VLAN with ports in each member must be configured and each member device must be configured with an MAD IP address. These addresses are invisible for the rest of the network and no routing interface can be attached to an MAD/BFD enabled VLAN.
MAD: Collision Handling and Failure Recovery

Collision Handling
The part that contains the device with the lowest member-id remains in Normal state and the other goes into Recovery state. The ports of a device in recovery state become blocked. The administrator can exclude some ports from becoming blocked.
Failure Recovery
When the IRF link is back online, the IRF system detects that the IRF-ports are up and triggers the Recovery process. During the recovery, the part of the IRF that was in recovery state is rebooted to be re-inserted into the IRF.
Thank You!
66
2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Microsoft Power Point - Event Qatar 1st Nov Building A Campus LAN Only)

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Microsoft Power Point - Event Qatar 1st Nov Building A Campus LAN Only)

Diunggah oleh

Hak Cipta:

Format Tersedia

HP Networking Burhan Abu Baja burhan@hp.com +974 33 101 383 1 2010 Hewlett-Packard Development Company, L.P.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Mean Time To Repair Mean Time Between Failures

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Challenges of the Enterprise Campus Network Solution

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Best Design Model of Enterprise Campus Network

Core Layer Hierarchical

Hierarchical Structure Design of Enterprise Campus Network

Internal Use Only. HP Confidential.

High Availability how to make it?

Internal Use Only. HP Confidential.

None Stop Forwarding

Internal Use Only. HP Confidential.

NSF schematic diagram

Forwarding Information Base

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

High Availability how to make it?

Internal Use Only. HP Confidential.

Link Aggregation Technology

Internal Use Only. HP Confidential.

Link Aggregation Technology

Internal Use Only. HP Confidential.

Link Aggregation Technology

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

RRPP Technology (Rapid Ring Protection

Internal Use Only. HP Confidential.

filtering database Neighbor Discovery

Internal Use Only. HP Confidential.

Smart Link Technology

Internal Use Only. HP Confidential.

Smart Link Technology

Internal Use Only. HP Confidential.

Smart Link Technology

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

One disconnected fiber or one broken fiber

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Enhanced DLDP mode

Internal Use Only. HP Confidential.

High Reliability Technology of Network

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

VRRP: Virtual Router Redundancy Protocol

Internal Use Only. HP Confidential.

Virtual IP address: 10.1.1.1/24

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.

Internal Use Only. HP Confidential.