Intel 7190 User Manual

Download

Intel® NetStructure™ 7190 Multi-Site Traffic Director

User Guide

Intel® NetStructure™ 7190 Multi-Site Traffic Director v.3.1.1

User Guide

Technical Product Notice

Information in this docume nt is provided in connection with Intel® products. No license, express or imp lied, by estoppel or otherwise, to any intellectual prope rty rights is granted by this document. Excep t as provided in Intel’s Terms and Conditions of Sale fo r such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel® products including liability or warranties relating to fitness for a particular purpose, merchantability, or in fringement of any patent, copyright, or other intellectual property right. Intel products are not intended for use in medical, life saving, or life sustaining applications.

Intel may make changes to specificat ions and prod uct descriptions at any time, without notice.

*Other brands and names are the propert y of thei r respectiv e owners.

Intel Corporation Network Equipment Division 13280 Evening Creek Drive San Diego, California 92128-4102 USA Main: (858) 391-1900 Fax: (858) 391-1920

A20163-002 November 29, 2000

Chapter 1 Introduction 1

What is an Intel® NetStructure™ 7190 Multi-Site Director? . . . . . . . . . . . . . . . . . . 1

Two Versions of the 7190 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Who Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

User Guide Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2 Theory of Operations 5

“Intelligent” DNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Traditional DNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Multi-Site Traffic Management Using Intel Load Balancers . . . . . . . . . . . . . . . . . 8

Typical Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Site Balancing Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Partial Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Chapter 3 CLI Configuration 17

Custom/Manual Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Adding Secondary 7190(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Commit the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

NSLookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Configure DNS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4 Multi-Site Scenarios 25

Scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Part 1 – Initial Configuration of a Simple Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Part 2 – Changing to Flash Response Mode Balancing. . . . . . . . . . . . . . . . . . . . . 31

Part 3 – Adding Load Balancers to an Existing Site . . . . . . . . . . . . . . . . . . . . . . . 32

Scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring in a Mixed Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 5 Boot Monitor 47

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Accessing the Boot Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Boot Monitor Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 6 CLI Reference 59

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Editing the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Pipes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Command Line Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

CLI Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Objects and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Global System Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

File Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Table of Contents

Chapter 7 SNMP Support 133

Standards Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Intel® MIB Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Supported MIBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Where to find MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Agent Metrics Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Service Metrics Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

ISV Metrics Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Site Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

SNMP Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Displaying SNMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Configuring Community Authentication & Security Parameters . . . . . . . . . . . . 141

Configuring Trap Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Configuring Other SNMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Chapter 8 Software Updates 145

Multiple Software Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Software Image Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Saving Your Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Downloading and Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Rebooting with the New Image and Verifying Installation . . . . . . . . . . . . . . . . . . 147

Restoring Your Previous Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Appendix A Diagnostics 149

Diagnostic LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Power Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Boot-time LED Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Runtime LED Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Runtime Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Log Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Displaying Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Appendix B Cleaning the Dust Filter 157

Appendix C Regulatory Information 159

iii

Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Appendix D Terms and Conditions and Software License 169

Glossary 177

Support Services 181

Index 185

Introduction

What is an Intel® NetStructure™ 7190 Multi-Site Director?

The Intel® NetStructure™ 7190 Multi-Site Traffic Director is a global site balancer. It gathers your geographically dispersed data sites into multiple “virtual servers,” thus giving you multifaceted, centralized control over widely distributed resources.

Performance

The 7190 looks at individual client requests and matches them up with the best of many geogra phically dispersed fulfill ment sites using the selection method most appropriate to your specific needs.

Reliability

The 7190 supports active-active redundant mode, meaning that multiple, active 7190s can be used simultaneously. When one fails, any remaining 7190s continue operation.

C H A P T E R 1Intel® NetStructure™ 7195 Multi-Site Traffic Director User Guide

Scalability

Two Versions of the 7190

The 7190 can work cooperatively with up to fifteen other 7190s in deployment across sites. A site may be managed by any Intel NetStructure™ e-Commerce Traffic Director or Intel NetStructure™ Commerce Director, whic h can in turn intell igently manage server farms, and return serve r performance data to the 7190. The 7190 also supports sites th at do not have an Intel

load balancers.

Flexibility

The 7190 offers six distinct methods of balancing your distributed resources, ensuring a solution for your multi-site pro bl ems.

There are two versions of the 7190 . One uses strong encrypt ion (128bit encryption) and the other uses weak encryption (56-bit encryption). The 7190 version that may be exported to certain countries is subject to U.S. export restrictions.

Who Should Use This Book

This user guide is intended for network administrators with a basic knowledge of:

• Networking concepts and terminology

• Network topologies

• IP routing

• DNS and BIND

User Guide Summary

In addition to this int roductio n, the user guide co ntains the followi ng chapters:

• 7190 Theory of Operation

An overview of the multi-site network, the 7190’s place in it, and some concepts you need to know to use the unit effectively

C H A P T E R 1 User Guide Summary

• CLI Configuration

Instructions on how to use the Command Line Interface (CLI) to manually configure additional sites, agents, zones, and services.

• Multi-Site Scenar ios

Descriptions of several typical multi-site challenges accompanied by their corresponding 7190 solutions

• Boot Monitor

An explanation and reference of the 7190’s configuration commands

• CLI Reference

Detailed descriptions of the 7190’s operational commands, including tree illustrations of the command system structure

• SNMP Suppor t

Details of 7190’s SNMP capabilities

• Software Updates

Software update procedures

• Diagnostics (Appendix A)

How to interpret the 7190’s LED display

• Cleaning the Dust Filter (Appendix B)

• Regulatory Information (Append ix C)

• Terms and Conditions (Appendix D)

End user terms, conditions, and licensing information

• Glossary

• Support Services

• Index

C H A P T E R 1Intel® NetStructure™ 7195 Multi-Site Traffic Director User Guide

Notes

Theory of Operations

NOTE: Intel Load Balancer refers to either Intel®NetStructure™ 7180/7185 e-Commerce Directors or the Intel®NetStructure™ 7140/7145/7170/7175 Traffic Directors.

Typical load balancers work by balancing traffic over a Local Area Network (LAN) to a Web farm. The Intel Multi-Site Traffic Dire ct or extends this balancing to multiple sites over a Wide Area Network (WAN). By balancing referrals to each site, the 7190 enables enterprises and Web hosting services to integrate geographically distributed content and services.

The advantages of such integration are many, including:

• There is increased fault tolerance and availability owing to

redundant sites . Multiple ac tive sites per mit uninterr upted servic e in the event of a localized outage in the data network.

• Customer response times are improved by directing users to

uncongested sites or data centers.

• Easy scaling of server farms can be accomplished.

Multi-site load balancing works best in concert with Intel® load balancers. The 7190 also support s multi-site load balancin g with sites that do not have Intel load balancers. In this case, the sites are balanced on the basis of availability, and not based on proprietary metric information.

® NetStructure™ 7190

C H A P T E R 2Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

“Intelligent”

DNS

Traditional DNS

The 7190 leverages the DNS architecture and proto col as the basis for its site balancing operations. Based on the info rmation gathered from all sites, the 7190 returns the address of the site that best meets the criteria for fulfilling t he request.

Traditional, or Round Robin, Domain Name Service (DNS) is a rudimentary means of server load balancing. Under this method, a single hostname is mapp ed to a list of multiple server IP addresses. When the DNS server resolves a request for that hostname, it return s the entire list to the requestor, then sorts it (the first name drops to the end of the list). Upon recei vi ng the l ist , the cl i ent requ esto r t ypi cal ly uses the first address. The next requestor of the ho stname receives the resorted list, and again most likely u ses the current first name. The list is resorted again, so that each sequential request sees a different “first choice” than the previous one. The chief benefit of Round Robin DNS is that it allows requests to be distributed to multiple hosts and, in theory, provides a layer of redundancy. On the negative side, the DNS server has no knowledge of the status of the sites to which it sends requests. Receiving sites may be heavily loaded or dead, thus the potential is high for unacceptably slow replies error messages to clients, which is out of the site operator’s control.

C H A P T E R 2 Traditional DNS

7190

7140/7170

(Los Angeles)

Client

(San Diego)

7140/7170

(Chicago)

ns.mstd-ex.com (Chicago)

Authority for msd-ex.com

Local DNS server

(San Diego)

Multi-Site Load Balancing

Authoritative DNS Servers

The DNS maps, or “resolves” hostnames into IP addresses. It is, in effect, a distributed database operating through a distributed, hierarchical system of Domain Name Servers. Thus, if t he local DNS server cannot resolve a name, it looks “upstream” to consult a R oot Domain Server for help. The Root Domain Server in turn asks the Authoritative Name Server (i .e., th e owner of t he name i t is tryi ng to resolve) to return the appropriate IP address for the requested name.

To illustrate

1. The client sends a query to its configured DNS (all clients are configured with the address of their DNS server) to resolve a particular domain name (e.g., www.mstd-ex.com).

2. The client DNS server sends a query to the Root Domain server for the .com domain (every DNS server is configured with the root server information) to resolve mstd-ex.com.

3. The Root Domain server responds with the address of the Authoritative DNS server fo r the mstd-ex.com domain.

C H A P T E R 2Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

4. The client DNS server sends a query to the mstd-ex.com Authoritative DNS server to resolve www.mstd-ex.com.

5. The Authoritative DNS server responds to the client DNS server with the IP address of www.mstd-ex.com.

6. The client DNS server responds to the client with the IP address of www.mstd-ex.com.

In the discussion above , the 7190 acts as autho ritative DNS server f or

zone.mstd-ex.com, which is the zone in which the name www.mstd- ex.com resides.

Multi-Site Traffic Management Using Intel Load Balancers

Multi-site load balanc ing solves most of the prob lems inherent in Round Robin DNS. Under the server load balancing model, servers are aggregated in a “server farm” behind a lo ad balan cer kn own by a Virtual IP address or “service.” (The service is the IP address of which the external network is aware.) By keeping track of such metrics as number of connections, which services are running, response time and the like, the load balancer knows the status of the servers. The 7190 retrieves metrics from the load balancer. Thus, when a client requests the service, the 7190 routes it to the site who has a server best able to fulfill it.

If the data center has an Intel Load Balancer, the 7190 works in concert with the “agents” in the load balancers by continually communicating with each site’s agent through site verification protocol. This keeps the 7190 informed of the following:

• Health of the load balancers.

• Individual service health and availability.

• CPU utilization of load balancers (as of 7140/7170, 7180

Software release 2.2.1)

• Response time for each service (as of 7140/7170, and 7180

software release 2.3)

• Number of connections to each load balancers (as of 7140/7170,

and 7180 software release 2.2.1)

Site verification protocol information is encrypted for secure communication between an Intel Load Balancer and the 7190.

C H A P T E R 2 Typical Configuration

Multi-Site Traffic Management Without NetStructure Load Balancers

The 7190 can support data centers, whether or not they have an I ntel Load Balancer. Without these Intel products, the 7190 can monitor site service availability by using an ISV method:

• Ping (ICMP)

• TCP Open probe

• HTTP URL probe

Typical Configuration

Los Angeles location Chicago location

servers

The 7190 can be used with a wide variety of topologies but a basic example of a 7190 conf iguration mig ht consist of t wo 7190s and four NetStructure 7140s (one 7190 at each location that the site is distributed across, and two 7140s in serial fail-over mode for each location). For illustrative purposes, these devices are configured to balance www.mstd-ex.com. Because the 7190 does not resolve records aside from hostnames (e.g., no MX records or reverse DNS lookups), your existing DNS server should remain authoritative for the domain, mstd-ex.com. A new zone, zone.mstd-ex.com, must be created and your existing DNS server must delegate authority for this zone to all

of the 7190s. An alias, www.zone.mstd-ex.com is created for www.mstd-ex.com. This zone and alias are transparent to users connecting to your site. They still requests www.mstd-ex.com and are referred to the optimal site by the 7190.

Intel

7190 primary

Internet

7180s

Clie nt

7190 secondary

7180s

servers

7190 Overview - A Basic Configuration

C H A P T E R 2Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Site Balancing Methods

The 7190 supports six site-balancing methods or algorithms. The operator chooses the method most appropriate to the deployment to optimize traffic volume, priority, resource availability, and the overall desired outcome.

Weighted Algorithms

• Weighted Round Robin - Two differences distinguish this

method from traditional, or round robin, DNS. First, the 7190 is aware of the status of the sites it balances thus, unlike legacy Round Robin, it does not indiscriminately send requests to servers that have gone down or are otherwise unable to fulfill requests. Second, weighted round robin allows the operator to skew the loading among availabl e sit e servi ces on t he basi s of a n assigned “weight.” (Weight takes into account differences in capabilities of site services.) Weighting allows the operato r to adjust loading on a percentage basis. For example, Site A is assigned a weight of 1, Site B, 2, and Site C, 7. Thus, Site A receives 10% of the traffic, Site B, 20% and Site C, 70%. This method can ensure the most efficient use of those sites with greater “horsepower,” while preventing the overtax ing of less powerful ones.

• W eighted Random - T he Weighted Random method is similar to

Weighted Round Robin with the exception that requests are not fulfilled serially. IP addresses are resolved in a random fashion. The weighting is accomplished as above. The benefit of this algorithm is that it is more effective at n ormalizing, or leveling, load.

Metric Algorithms

Using DNS to balance multiple sites is more effective when the referrals are based upon knowled ge of the actual loads on the servers. In addition, balancing effect ivene ss no ti ceab ly i ncrease d whe n b ackto-back referrals to the same site were not made even if metrics indicated one site service was the best both times. The 7190 metric algorithms reflect both of those findings.

These balancing algori thms are not availa ble for sites that do not have Intel load balancer s:

• Response Time - The Response Time method directs requests to

the site that has the fastest aggregate (i.e., across all servers) response time for the requested service. Likely users of this method are enterprises that have identified the efficient

C H A P T E R 2 Site Balancing Methods

fulfillment of a specific type or types of traffic as being crucial to their business goals. (Available with the 7140/7170, 7180 2.3 release.)

• Least Connections - The Least Connections method sends

requests to the site with lowest number of connections. This method permits the most efficient management of requests that are likely to require connections of long duration, such as FTP. (Available with the 7140/7170 and 7180 releases.)

• CPU Utilization of Local Load Balancer - This method directs

clients to the site whose load b a lancer has the lightest workload. The benefit of this method is most evident when used wi th sites performing processor-intensive Layer 7 load balancing. (Available with the 7170 2.2.1 release.)

Managing Unequal Site Servers

There is a “factor” command to determine a threshold factor in the event of two unequal servers. (see config dns zones <zonename> hostnames <hostname> siteservices <siteservicename> factor in Chapter 5, “CLI Reference.”)

The 7190 determines which IP address to return for a hostname, based on the performance of the IP address and port at a site. The three-step process is:

1. Determine the metric(s) with the smallest value.

2. Determine whether any remaining service(s) are close enough to

this best value to also be co nsidered. The quantifi cation of “close enough” is the factor. A factor o f 0 means con sider only services with the best value.

3. Randomly choose from all the services identified in the first two

steps.

A good example of the usefulness of this “close enough” threshold factor is when two unequal servers are deployed behind di fferent load balancers. Server A may be capable of handling 3000 connections per second. Server B may also be capable of handling that many connections per second, but is also servi ng more sites than Server A. The realistic connection limit of Server B may therefore only be about 500 connections per second. If Server A has 900 connections and Server B has 400 connections, then Server B is the site with the least number of connections, alth ough it is already 80% load ed while Server A is only 30% l oad ed. The better choice woul d be to give the traffic to server A. However , the 7190 has no knowled ge of the actual

C H A P T E R 2Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

load potential of the serve r s underneath the load balanc ers it monitors. Therefore it allows the next best thing. For example, it allows the user to declare that if Server A is within 24 00 connections (80% of maximum) of Server B, consider referrals to Server A even if Server B is the lowest. The factor setting would be 2400 for the service associated with Server A and 0 for the service associated with Server B.

Flash DNS

Network topology can greatly affect the overall transfer rate between a site and a client. A solution is to replicate sites on multiple networks (which are sometimes also distributed geographically). Without a 7190, it can be cumbersome to provide users with a list of mirror sites and then let them choose which one appears to be best for them.

Flash DNS addresses this probl em b y l et ting a 7190 at each network site send out responses to a DNS query for the site host name. If all responses are sent at the same time then the site that has the least network latency connectin g t o t he user should get its response to the user first. The user ignores all the other responses.

Partial Failures

Since many enterprise clients are behind firewalls that perform Network Address Translation (NAT), by default, the 7190 performs source IP using the IP address of the 7 190 that ori ginally receiv ed the DNS request. This feature can be disabled.

The 7190 maintains the current metric state of each service on a per host basis. A “service” is an IP address and port at a site. The maintained state has four levels relating to the amount of information that the 7190 has about each service.

Each load balancin g method handles parti al failures in t he same basic way. Each balancing method always tries t o f ind at l east one servi ce with a metric status of “OK” with which to balance. If no services are available at this highest metric state, and it is not using a metric balancing method, then it looks for at least one service with a metric state of “No Services”. If none are found t hen it look s for at lea st one service with a metric state of “No Metrics”. Finally, if no services have been found at a high enough metric state level to balance normally, it performs a round robin selection among all the enabled services.

C H A P T E R 2 Partial Failures

Status: OK

This state indicates that the required services behind this service are available on the associated load balancer. The metrics information for this service are current and can be used for metric load balancing.

Status: No Services

This state indicates that services other than the one(s) configured as required for the associated host are not available on the load balancer. Other services with this same service are available. Metric load balancing is not available for this service.

Status: No Metrics

This state indicates that th e Intel Load Balancer is not advertising any services that use this service. Metric load balancing is not available for this service.

Status: No Connection

The 7190 has lost or been unable to establish a connection to the fulfillment agent on the load balancer. No metrics information on any services from this load balancer is available. No load balancing methods are available fo r t hi s ser vi ce. It may only participate i n nonweighted round robin load balancing.

Service Standby

To achieve site service redundancy, customers often want to have backup services that are completely dark to normal traffic, but are instantly available to take over for a failed site service. The transition of traffic from the failed site service to the standby site service occurs without the need of operator intervention.

The Service Standby feature allows the designation of a site’s services for standby. If there is a 7190 located at the site, its operation is unaffected and continues in resolving queries and referring to active services. When the 7190 has detected a failed service, the failed service is not used in referrals. Once a failed service has been deemed active again, no further referrals are made to the standby service.

The determination to use or not use a standby site service is only made upon receipt of a query that involves the service. Therefore, a standby service is not activated to replace a failed service until a query is received, and a failed service is not shown as active until after a query is received.

C H A P T E R 2Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Multiple VIP Response

The DNS response from a 7190 may contain multiple answers. The number of answers and whether to include stand-by VIPs can be configured.

Active VIPs are included first in the response. A stand-by VIP is treated as an active VIP, if it is marked as “IN USE” due to a failed VIP. Stand-by VIPs are included after the active VIPs: (a) if the configuration is se t to incl ude th em and, (b ) the number of req uested additional VIPs in the response has not been met.

When using mutli-VIP r esponse with Flash load balancing, the Flash response attemp ts to use VIPs wi thin the same pee r group first bef ore including VIPs from the other peer groups.

Definitions

Understanding of the 7190 requires some specialized terms. The definitions provided here are specific to the context of multi-site load balancing and the operation of the 7190, thus there may be subtle differences between these and those offered in other sources.

Agent is a component of an Intel Load Balancer that gathers metric data and transmits i t t o t he 7190 . For the purposes of the d iscussions in this user guide, “agent” is synonymou s with “Traffic Director” or “e-Commerce Director.”

Agent IP refers to the real IP address of an Intel Load Balancer in its role as an agent to a 7190.

Intelligent Site Verification (ISV) is used to directly determine the availability of (1) a service or, (2) a service that is balanced using a third-party Load Balancer. Methods of verification include a site ping, TCP connect, and HTTP probe.

ISV Group refers to a collection of services available at a physical site. All services in a group share th e same ISV polling parameters.

If multi-VIP standby is enabled when using the Flash load balancing method, standby VIPs from a site are not included if all of the VIPS are (1) standby and, (2) not marked “IN USE” due to a failed VIP at another site.

C H A P T E R 2 Definitions

Primary 7190 is a 7190 that automatically transfers (copies) configuration information to secondary 7190s (through the Global Sync process). Configuration may only be changed on a Primary

7190. Service is the Virtual IP (VIP) and port number of an application

service available at a site. Authoritative Server is a DNS name server that has co mplete name

space information regarding the hosts within a given zone (see below).

Authority is an attribute of a DNS name server with respect to a specific part of the DNS name space, or zone (see below). A name server is said to have authority over a zon e, by whi ch that se rver has complete name space information for that zone.

Zone is a portion of a DNS name space for which a given name server has complete name space information. When a name server receives a request for a host outside of its zone, it replies with the name of the name server that is authoritative for a different zone and is likely to have the specific inform a tion required to satisfy the request.

C H A P T E R 2Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Notes

CLI Configuration

Custom/Manual Configuratio n

You can manually change any specific configuration parameters if any of the Quick Start Wizard default settings are not sufficient for your site.

It is recommended that you use the custom configuration method only after you have comp leted the initial configuration with the Quick Start Wizard. See the Intel® NetStructure™ 7190 Multi-Site Traffic Director Getting Started Guide for instructions on using the Quick Start Wizard.

C H A P T E R 3 Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

7190 (Primary)

host name: ns1.xyz-ex.com IP address: 10.54.67.2

7xxx Load Balancer

IP address 10.54.67.4

service VIP 10.54.67.5 port 80 service VIP 10.54.67.6 port 80

service VIP 10.54.67.7 port 255

service VIP 10.54.67.8 port 255

generic load balancer

IP address 10.54.67.3

Adding Secondary 7190(s)

Data Center 1

Network Topology

Map of

w ww.xyz-ex .co m

Data Center 2

generic load balancer

IP address 10.100.68.3

service VIP 10.54.68.7 port 255

service VIP 10.54.68.8 port 255

7xxx Load Balancer

IP address 10.100.68.4

service VIP 10.100.68.5 port 80

service VIP 10.100.68.6 port 80

7190 (Secondary & Peer)

host name: ns2.xyz-ex.com IP address: 10.100.68.2

Sample Network Topology

Now that the primary 7190 is up and running, the additional 7190s can be easily added by configuring them as secondary 7190s. They receive all their configuration information from the designated primary 7190 through the Global Sy nc proc ess, which aut omatic ally transfers the primary 7190 configuration to any secondary 7190s.

Similar to a typical DNS server, all 7190s are treated as equals by other DNS servers. The terms of primary and secondary only refers to where a 7190 gets its new configuration information. The 7190 only allows the configuration to be changed on a primary 7190. Secondaries get their configuration from their designated primary 7190 and store a copy of the recei ved configur ation loca lly. Shou ld a secondary be unable to con tact a primary i t fu nctio ns normal ly usi ng its stored configuration. All 7190s have the same picture of the current Agent metrics and are eq ually capable of r esponding. S hould one fail the existing DN S protocol automatic ally routes requests to the non-failed 7190s.

The theoretical secondary ns2.xyz-ex.com (IP 10.100.68.2) can resolve requests for www.somedomain.xyz-ex.com by becoming a secondary of the 7190 at 10.54.67.2. From the CLI on the proposed second 7190, execute the command:

C H A P T E R 3 Custom/Manual Configuration

NOTE: User-entered names and IP addresses in the example are for illustrative purpo ses only. The appropriate values for your installation may vary.

An Intel_7xxx Load Balancer refers to Intel®NetStructure™ 7180/7185 e-Commerce Directors or the Intel®NetStructure™ 7140/7145/7170/7175 Traffic Directors.

#config dns secondary 10.54.67.2 Warning: Your current dns configurations will

be lost. Are you sure you want to become a Secondary

(Yes/No):yes Now running as a Secon dary.

If the DNS configuration of 10.54.67.2 is changed, the new configuration can be prop agated to 10.100.68.2 by the commit all command.

Creating Agents

An agent refers to the Intel Load Balancers at each site. They are used to keep the 7190 informed of site status, response time, and number of current connections of the server farm they are balancing.

To add an agent, type the following:

Intel 7190# config dns agents create lb1 ip

10.54.67.4 Intel 7190# config dns agents create lb2 ip

10.100.68.4

Associating Services with Agents

Next, services must be associated with agent(s):

Intel 7190# config dns agents lb1 services create 10.54.67.5:80

Intel 7190# config dns agents lbi services create 10.54.67.6:80

Intel 7190# config dns agents lb2 services create 10.100.68.5:80

Intel 7190# config dns agents lb2 services create 10.100.68.6:80

Creating Zones

The next step is to create a zone (e.g., somedomain.xyz-ex.com) on the

7190. The command to do this is:

Intel 7190# config dns zones create somedomain.xyz-ex.com

C H A P T E R 3 Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

NOTE: The 7190 must be authoritative for this zone—the existing DNS server should delegate the domain to the 7190.

Creating Authority Records

Next, authority records for your two 7190s are created. These sites are used to tell DNS servers who they can query directly for other hosts in the current zone. In order for the 7190 to perform effecti vely, only 7190s should be authoritative for the zone.

For example, hostname ns1.xyz-ex.com at IP address 10.54. 67.2 and hostname ns2.xyz-ex.com at 10.100.68.2. The authoritative DNS servers for xyz-ex.com should contain records for these hostnames, as well as the corresponding NS records for somedomain.xyz-ex.com. (See the section, Existing DNS Servers.)

Intel 7190# config dns zones somedomain.xyzex.com

7190/config/dns/zones/somedomain.xyz-ex.com#

create-author ity ns1.xyz-ex. co m ip

Create Authority Successful 7190/config/dns/zones/somedomain.xyz-ex.com#

create-author ity ns2.xyz-ex. co m ip

10.100.68.2

Create Authority Successful 7190/config/dns/zones/somedomain.xyz-ex.com#

info

Zone: somedomai nex.xyz-ex.co m Authority Records TTL: 7200 Authority Name: ns1.xyz-ex.com

Authority IP: 10.54.67.2 Authority Name: ns2.xyz-ex.com

Authority IP: 10.100.68.2 Zone = somedomainex.xyz-ex.com Authority Records TTL = 7200 Authority Name : ns1 .xyz-ex.com Authority IP: 10.54.67.2 Authority Name : ns2 .xyz-ex.com Authority IP: 10.100.68.2

10.54.67.2

C H A P T E R 3 Custom/Manual Configuration

Creating Hosts

Next, the hostname www.somedomain.xyz-ex.com is created:

7190/config/dns/zones/somedomainex.xyzex.com# hostnames create www

Create Hostname Successful

The next step is to map the services www.somedomain.xyz-ex.com to the load balancer. The following assumes the IP addresses of the load balancer to be 10.54.67.4 (service 10.54.67.5:80) and 10.100.68.4 (service 10.100.68.5:80), and that th e agents are enabled and run ning on the default port 1999. (Agents are enabled or disabled using the CLI of an Intel Load Balancer, with the command, config sys multisite <e nabl e|di sable> .) It is assumed t hat t he a gent names are the same as their IP addresses.

7190/config/dns/zones/somedomainex.xyzex.com# hostnames www siteservices

7190/config/dns/zones/somedomainex.xyzex.com/hostnames/www/siteservices# map

lb1:10.54.67.5:80

Site Service Mapped 7190/config/dns/zones/somedomainex.xyz-

ex.com/hostnames/www/vips# map

lb2:100.68.5:80

Site Service Mapped

Commit the Configuration

The commit command is used at this to point put the configuration into effect.

7190/config/dns/zones/somedomain.xyz-ex.com/ hostnames/www/vips# commit all

Warning: Your active configuration will be overwritten.

Are you sure you want to commit the configuration (yes|no)? yes

Configuration has been committed

C H A P T E R 3 Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

NSLookup

Configure DNS Servers

NOTE: If the 7190 was not configured with a primary name server during setup from the Boot Monitor, the nslookup command fails.

The nslookup utility can verify that the 7190 is correctly resolving www.somedomain.xyz-ex.com:

Intel 7190# nslookup www.somedomain.xyz-ex.com

Server: server1.xyz-ex.com Address: 192.168.16.4

Name: www.somedomain.xyz-ex.com Address: 192.16 8.16.23

The existing DNS server or servers must be correctly configured to work with the 7190s. Entries need to be made that delegate the responsibility of resolving DNS queries for www.xyz-ex.com to the 7190s. This can be done in one of two ways. The first way is to delegate the entire zone to the 7190. This works fine as long as only type A records need to be returned for this zone. The 7190 is a high performance specialized DNS server and supports only the more common type A records.

The recommended way of configuring your existing DNS server is delegate partial auth ority by al iasing . All of the 7190s ( both primary and all secondaries) must be included in the authority record (NS) portion of the delegation.

Multiple-VIP Response

A DNS response may contain multiple answers. A standby VIP is automatically considered as a resp onse if it is marked “IN USE” due to a failed VIP. When multi-VIP standb y is enabled, standby VIPs are included in a response if the number of additional VIPs in the response has not been met

dns zones <zonename> hostnames <hostname> multi-vipstandby enable.

7190#config dns zones somedomain.xyz-ex.com hostnames www multi-vip-standby enable

. To include standby VIPs, type config

C H A P T E R 3 Custom/Manual Configuration

The number of additional answers in a response can be configured. The range is from 0 to 15.

7190#config dns zones somedomain.xyz-ex.com hostnames www add-rec-responses 4

To verify whether multi-VIP standby is enabled or check the numb er of additional responses, type confi g dns zones

<zonename> hostnames <hostname> info.

7190#config dns zones somedomain.xyz-ex.com hostnames www info

C H A P T E R 3 Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Notes

Multi-Site Scenarios

Scenario 1

One Web site, two geographical sites (one server each), two 7190s, optional 7110s

Introduction

An e-commerce company with a single Web site (www.mstd-

ex.com) wants to expand their site to two geographically dispersed

locations so that customers can be referred to the site that gives them the fastest response time. They initially d eploy only a si ngle server at each site (no load balancers), but they want the ability to expand as the demand on their Web site increases.

Initially, a 7190 would be deployed at each site. Optional 7110s could be deployed in front of each server for HTTPS traffic. Since only one server is being deployed at each site no load balancers are required. The 7190s is set up to monitor the health of the Web site by performing a periodi c HTTP p robe of t he main Web page on each server. After verification that the initial configuration is working properly, the balancing method is

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

changed to Flash Response Mode to deliver the site that has the least network latency to potential customers.

Part 1 – Initial Configuration of a Simple Site

west coast

7190

10.1.1 .1

10.2.1.100 10.2.2.100

Key Concepts:

• No Load Balancers (non-brokered)

• ISV

• Two Sites

• Configuring a Secondary 7190

• Delegating Authority to a 7190

Router Router

7110

internet

7110

east coast

7190

10 .1.2. 1

Server

Simple Site (Scenario 1)

Procedure

In this scenario each site is treated as its own ISV Group, since there are no load balancers at either site. Both sites could be put into one single ISV Group for this simple example, but for a majority of situations it is better t o have a one- to-one mapping of I SV Groups to sites.

C H A P T E R 4 Scenario 1

The 7190 at the westco astsite is the pr imary 7190. Except in very rare cases there should only be one primary 7190. All other 7190s in the network should be secondaries so they can sla ve their con figuration s to the primary 7190.

Step 1. Create the ISV Groups for each site and associate their services.

The creation of an ISV Group i s primarily for management purposes. The ISV Group is referred to by name. This allows you to choose a name that is meaningful to you in your network environment (e.g., westcoastsite). Names are case insensitive.

config dns isvgroups create westcoastsite westcoastsite services create 10.2.1.100:80 create eastcoastsite eastcoastsite services create 10.2.2.100:80 info

Step 2. Select HTTP probe as the ISV method and associate a URL with each service.

NOTE: Only the actual file name is entered in the URL string. The Service VIP and Port already imply http://www.mstdex.com.

Since there are no load balancers, ISV must be used to determine site service availability. In this scenario the site represents a distributed Web site. The best way of determining site service availability is a combination of ISV and traffic monit oring. Only a load balancer can do this. The next best thing is ISV using an HTTP probe. For this scenario only the main Web page (http://www.mstd-ex.com/ main.html) is probed.

config dns isvgroups westcoastsite services

10.2.1.100:80 url /main.html config dns isvgroups eastcoastsite services

10.2.2.100:80 url /main.html

Step 3. Create the delegated zone for the hostname and the authority records for the zone.

In order for the rest of the world to kn ow that t he 7190s are the p lace to go for resolving the hos tname www.mstd-ex.com they must be made authoritative for the domain mstd-ex.com. This could be

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

impractical, so the solution is to make the 7190s authoritative for a zone within the mstd-ex.com domain, rather than for the entire domain. For this example the authoritative name serv er for the mstdex.com domain delegates authority of a new zone within its domain to the 7190. This zone is called geo.mstd-ex.com. The hostname

www.mstd-ex.com is aliased to www.geo.mstd-ex.com. Anyone

querying the mstd-ex.com name ser ver for the address o f www.mstd-

ex.com is told to ask one of the 7190s for the address of www.geo.mstd-ex.com.

config dns zones create geo.mstd-ex.com geo.mstd-ex.com create-authority nswc.mstd-

ex.com ip 10.1.1.1 geo.mstd-ex.com create-authority nsec.mstd-

ex.com ip 10.1.2.1 info

Step 4. Create Host and Specify Balancing Method.

When you create the hostname you can specify the balancing method to use in selecting which site services are referred. For this scenario, the balancing meth od eventually is Flash Re sponse Mode. But for initial testing of th e network and configuration it is oft en best to configure first with Weighted Round Robin mode. This allows for easy verification of the configuration because the query r esponses are deterministic. Once the initial configuration is verified the balancing method can be changed to the production method (Part 2 of this scenario).

config dns zones geo .mstd-ex.com ho st names create www www method wrr info

C H A P T E R 4 Scenario 1

Step 5. Map Services to Hostname.

DNS is essentially a means of mapping hostnames to IP addresses. The 7190 takes this mapping one step further by allowing the mapping of hostnames to services (IP address and service port). In this step the services that were created in Step 1 are mapped to the hostname created in Step 2.

config dns zones geo .mstd-ex.com. hostnames create www www siteservice s map westcoastsi te:10.2.1.100 :8 0 map eastcoastsi te:10.2.2.100 :8 0 info

Step 6. Save and activate the configuration.

The 7190 maintains two copies of configuration. One is the active copy of the configuration used by the name server function of the

7190. This configuration i s accessed by all the show commands. The other copy is for in-work changes of the configuration. This configuration is accessed by all the config commands. This is the copy in which we have bee n entering the new config uratio n. In order to make the current in-work configuration active, the configuration must be committed using the commit command.

Save and Commit commands: The difference between the save and commit commands is often a source of confusion for ne w users. The save command is used to make a snapshot of the act ive configuration.

The commit command is used to make the in-work configuration active. Once you have a good working configuration it is always a good idea to save a snapshot of this confi guration before yo u do your next commit. This way if there is a problem with the new configuration you can use the restore command to revert to the previous configuration.

commit all

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Step 7. Configure the Secondary 7190.

Configuration of secondary 7190 s is very easy. First you use the Boot Monitor to configure the har dware and networ k infor matio n (see the chapter on Installation , Startup and Confi guration). Then you choose “Become a Secondary” in the Quick Start Wizard when i t comes up. Enter the IP address of the primary 7190 (10.1.1.1). In a matter of seconds after issuing the command the secondary has a copy of the configuration from the primary. Subsequent commit commands automatically transfer the confi guration to every attached seco ndary. This automatic process of transfer ring (copying) a configuration fr om primary to secondary 7190s is called Global Sync.

Step 8. Delegate authority to the 7190s.

The primary name sever responsible for the mstd-ex.com domain needs to be modified. Th e modi fi cat ion s var y d epend ing on the type and version of the DNS server used. For this example it is assumed that a Bind server is being used.

At a Bind DNS server, add the following lines to the database file for the mstd-ex.com domain. Typically this file would be called something like “db.mstd-ex”.

geo.mstd-ex.com. IN NS nswc.mstd-ex.com. geo.mstd-ex.com. IN NS nsec.mstd-ex.com. nswc.mstd-ex.com. IN A 10.1.1.1 nsec.mstd-ex.com. IN A 10.1.2.1

www.mstd-ex.com. CNAME www.geo.mstd-ex.com.

Step 9. Verify the configuration and network operation.

There are many tools available to accomplish this step. The simplest is to ping www.mstd-ex.com. Since we have initially configured for Weighted Round Robin (with a weight of 1) we expect to ping

10.2.1.100. After waiting at least 60 seconds (the default Time To Live for a 7190 response) perform another ping. This time it should ping 10.2.2.100. Performing th is a third time should resul t in the first service being pinged again.

C H A P T E R 4 Scenario 1

Part 2 – Changing to Flash Response Mode Balancing

Key Concepts:

Flash Response Mode

•

• Associating 7190s with a site

Procedure

Now that the 7190 is configur ed and functioning prope rly it is time to modify the configuration to use Flash Response Mode balancing instead of Weighted Round Robin.

Step 1. Associate 7190s with a site.

Flash Response Mode works by sending DNS responses back to the client from a source that is as close (network wise) as possible to the address it is returning. Only the 7190s are capable of sending Flash responses.

config dns isvgroups westcoastsite flash-src 10.1.1.1 config dns isvgroups eastcoastsite flash-src 10.1.2.1

Step 2. Change the host balancing method to Flash Response Mode.

config dns zones geo .mstd-ex.com hostnames www method flash

Step 3. Commit the configuration changes.

Now that the changes are completed, save a snapsh ot and commit the configuration. Note that now that a secondary 7190 is online these configuration changes are instantly propagated t o the secondary 7190 (eastcoastsite) whenever the commit all command is executed.

save first-cfg commit all

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Part 3 – Adding Load Balancers to an Existing Site

Key Concepts:

Adding a Load Balancer (Agent)

•

• Disabling a Site

• Mixture of Brokered and Non-brokered Sites

• Configuring for Future Expansion

• Deleting an ISV Group

• Adding and Deleting Services

After the sites have been up and running for a while it is still easy to change the configur ation to add new servers, services and hosts. But if the site data traffic increases significantly it is often advantageous to add load balancers to manage the traffic to the Web servers. Done correctly, the addition of a load balan cer at a site can be handled with minimal service interrup tion.

There are two methods to handle this transition. The first method requires that all existing network addresses be kept in place. The 7190s would continue to refer clients directly to the servers until the configuration changes are committed. The second method assumes that addresses of the servers might change. The act of changing network addresses of servers usually entails t aking a site offline while transitioning.

The 7190 has some built-in features that make this transition almost as simple as the first method. In this sect ion, th e 7190 is us ed to take sites offline (no new referrals) to add a load balancer at each site.

C H A P T E R 4 Scenario 1

west coast

Router Router

east coast

internet

7190

7170

(se rve rs )

7110

Services

www.mstd-ex.com

10.2.1.50:80

7190

10.1.2.110.1.1.1

7110

7170

(servers)

Services

www.mstd-ex.com

10.2.2.50:80

ISV Groups and Services

Step 1. Add the load balancers and their services to the 7190 configuration.

The 7190 allows agents (load balancers) and ISV Groups and their services to be added prior to their availability. They can be added and then designated as disabled. This prevents any referrals to the new services until they are enabled. When an agent or ISV Group is disabled all their services are automatically disabled in every hostname that currently uses them. Further, no communication is attempted to the disabled agent/ISV Group.

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

If a service is disabled individually, but the agent/ISV Group is left enabled then no referrals are made to that service, but communicat ion is attempted to the services associated agent/ISV Group.

config dns agents create westcoastbroker ip 10.1.1.2 westcoastbroker services create 10.2.2.50:80 disable config dns agents create eastcoastbroker ip 10.1.2.2 eastcoastbroker services create 10.2.2.50:80 disable config dns agents info

Step 2. Map the new services to a hostname.

When services are mapped to a hostname they are set to the enable state of their parent agent/ISV Group. If the agent/ISV Group is disabled then the mapped service is disabled. In the last step we created agents and disabled them. Therefore we do not need to explicitly disable them after mapping them.

config dns zones geo .mstd-ex.com hostnames www siteservices map westcoastbr oker:10.2.1.5 0: 80 map eastcoastbr oker:10.2.2.5 0: 80

C H A P T E R 4 Scenario 1

Step 3. Delete the first site to transition over.

For the purposes of this scenario, the eastcoastsite converts over first. By deleting the site (deleting the sites ISV Group), the 7190s makes all new referrals to the remaining sites. In this case that leaves just the westcoastsite, since the brokered sites are still disabled. Deleting a site also causes the removal of all of its associated services from hostname mappings. To prove this, check the hostname after deletion.

config dns isv-groups delete eastcoastsite config dns zones geo.mstd-ex.com hostnames www

info

Step 4. Commit the new configuration.

At this point, you can save and commit the configuration.

save before-upgrade commit all

Step 5. Bring the new eastcoastbroker hardware on line.

After the commit, the site known as eastcoastsite no longer receives traffic from new referrals. It may still continue to receive some residual traffic from cached referrals or current connections. Configure the load balancer known as the eastcoastbroker. Verify that it has the service 10.2.2.50:80 configured.

Step 6. Enable the eastcoastbroker and delete the westcoastsite.

Similar to disabling an agent, enabling an agent automatically enables all of its services mapped to hostnames.

config dns agents eastcoastbroker enable config dns isvgroups delete westcoastsite commit all

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Step 7. Bring the new “westcoastbroker” hardware on line.

After the commit, the site known as “westcoastsite” no longer receives traffic from new referrals. It may still continue to receive some residual traffic from cached referrals or current connections. Configure the load bal ance r known as t he “westcoastbroker”. Verify that it has the service 10.1.2.50:80 configured.

Step 8. Enable the westcoastbroker.

After this step both sites are oper a tional, and talk to the load balancers.

config dns agents westcoastbroker enable commit all

C H A P T E R 4 Scenario 2

Scenario 2

Multiple sites, server farms, multiple hostnames, multiple 7190s, generic (not Intel) load balancer

A large company with multiple divisions wants to integr a te most of those division Web sites onto server farms located at two new geographically dispersed data centers. One division already has an existing brokered server farm at a third site that they refuse to give up. The load balancer at this third site is not an Intel load balancer. They want all of the Web traffic to be balanced between all of these sites. The division with the legacy brokered site wants to direct clients to the site with the least network latency (Flash Response Mode). They are extremely concerned about site availability and do not tolerate a solution that has any single point of failu r e. To further minimize the impact of any network outages that may affect one of thei r sites, they are establishing a smaller backup site that is used for testing new pages and should only receive traffic if one of the main sites fails. Because each division of the company is maintaining its own Web sites on the servers, multiple hos tnames with different services for each hostname must be supported. The types of services vary from HTTP, HTTPS to FTP.

Configuring in a Mixed Environment

This scenario is meant to emphasize the flexibility of the 7190 for handling a wide variety of diverse requirements simultaneously. Scenario 1 concentrated on basic configuration issues. Scenario 2 concentrates on features not previously mentioned (redundancy and service standby) as well as the advantages of using the 7190 with Intel load balancers (metric load balancing).

Key Concepts:

• Redundancy

• Service Standby

• Four (4) Sites

• ISV

• Generic (not Intel) Load Balancers

• Metric Load Balancin g

• Flash Response Mode

• Mixture of Brokered and Non-brokered Sites

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

• Different Site Combinations for Each Hostname

• Different Balancing Methods for Each Hostname

• Associating Services with Hostnames

Procedure

Step 1. Create agents for each of the sites brokered by Intel load balancers and associate their services.

For this example, there is one existing site used for only one division’s Web site. This site enforces the fact that not all sites have to be identical.

The 7190-to-site association is also done at this time since at least one Web site uses Flash Response Mode. The load balancers are used as the backup Flash source. In this scenario of four sites only two 7190s are actually required. If Flash Response Mode is used the load balancers can broadcast t he DNS responses under the directio n of the 7190s, but using the load balancers may have an impact on performance, so it is reco mmended t hat a 7190 be placed at each si te and the site load balancer designated as a backup Flash source. This prevents the 7190 from being a singl e point source of fa ilure witho ut impacting the performance of the load balancer except upon a 7190 failure.

Since redundancy is a key issue, all of the load balancers are deployed in pairs with serial failover enabled. This means that each load balancer actually has three IP addresses. The IP address that is used to communicate with the 7190 is the Online Outside IP Address (management address). This makes the failure of a load balancer transparent to the 7190 except for a momentary loss of connection that provides the load balancer metrics.

C H A P T E R 4 Scenario 2

• Create Site 1 and associate services:

config dns agents create site1 ip 10.1.1.2 site1 flash-src 10.1.1.1 flash-backup- src 10.1.1.3 services create 10.1.1.100:80 create 10.1.1.100:443 create 10.1.1.102:21 create 10.1.1.103:80

Site 1

7190

ns1.mstd-ex.com

10.1.1.1

7180

(2)

(servers)

internet

Router

7190

10.1.1.3

10.1.1.2

Services

www.mstd-ex.com 10.1.1.100:80 www.secure.div1.mstd-ex.com 10.1.1.101:443 ftp.div1.mstd-ex.com 10.1.1.102:21 www.div2.mstd-ex.com 10.1.1.103:80

(hot

backup

for Flash)

Site 1

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

• Create Site 2 and associate services:

config dns agents create site2 ip 10.1.2.2 site2 flash-src 10.1.2.1 flash-backup- src 10.1.2.3 services create 10.1.2.100:80 create 10.1.2.100:443 create 10.1.2.102:21 create 10.1.2.103:80

Site 2

Router

7190

ns2.mstd-ex.com

10.1.2.1

7180s

(2)

(servers)

7190

10.1.2.3

10.1.2.2

Services

www.mstd-ex.com 10.1.2.100:80 www.secure.div1.mstd-ex.com 10.1.2.101:443 ftp.div1.mstd-ex.com 10.1.2.102:21 www.div2.mstd-ex.com 10.1.2.103:80

Site 2

(hot

backup

for Flash)

C H A P T E R 4 Scenario 2

• Create Backup Site and associate services

config dns agents create backupsite ip 10.1.4.2 backupsite flash-src 10.1.4.1 flash-backup- src 10.1.4.3 services create 10.2.4.100:80 create 10.2.4.100:443 create 10.2.4.102:21 create 10.2.4.103:80

Backup Sit

7190

Router

7190

(hot

backup

for Flash)

ns5.mstd-ex.com

10.1.4.1

7170s

(2)

10.1.4.2

(servers)

7110

Services

10.2.4.100:80

10.2.4.101:443

10.2.4.102:21

10.2.4.103:80

10.1.4.3

Backup Site

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Step 2. Create ISV Group for the generic (not Intel) brokered site and associate its service.

This site is a legacy site with a ge neric load balancer. The 7190 can function quite well in th is e nv ironment, but is not able to o bt ain metric information to support one of the metrics oriented balancing methods. Generic load balancers should be set up as an ISV Group. The brokered services offered by th e load bal ancer are confi gure d in the 7190 just like any other service (VIP and port).

Assume that the Web page s behind the single HTTP serv ice available at the site are constantly changing. In this case it might be unwi se to probe for a specific URL, and preferable to verify the presence of the HTTP server by attempting a periodic TCP connection.

The scenario description stated that the service provided at this site was to use Flash Response Mode. Since no load balancer is present, only the 7190 can broadcast Flash respon ses. This is a single point of failure, so a second 7190 is located at this sit e. The second 7190 does not need to be listed as authorita tive for any zo nes, but this would be a waste of a good resource.

config dns isv-groups create site3 site3 flash-src 10.1.3.1 flash-backup- src 10.1.3.2 services create 10.2.3.103:80

10.2.3.103:80 method tcp

C H A P T E R 4 Scenario 2

Site 3

internet

Router

7190

ns3.mstd-ex.com

10.1.3.1

generic

load balance r

Server

www.div2.mstd-ex.com

10.2.3.103:8 0

7190

ns4.mstd-ex.com

10.1.3.2

Site 3

Step 3. Create the delegated zones for the hostnames and the authority records for each zone.

Since 7190s are deployed at every site t here is no reason to not utilize all of them to their full capabilities. All that is required to do this is to make all of the 7190s authoritative for both zones. Note that there is no need for the ns3 and ns4 to be listed as authoritative in the div1.mstd-ex.com zone. Further note that the 7190s used for hot standby redundancy a re n ot li sted as a uthori ties. I f it wer e not for the requirement of using Flash Response Mode for balancing

www.div2.mstd-ex.com, there would need to be only two 7190s in

the entire network. A 7190 only needs to be collocat ed ( on th e same network) with a site if Flash Response Mode is used and the load balancers are not configured as a primary Flash source for performance reasons.

config dns zones create div1.mstd-ex.com div1.mstd-ex.com create-author ity ns1.mstd-ex .c om ip 10.1.1.1 create-author ity ns2.mstd-ex .c om ip 10.1.1.2 create-author ity ns3.mstd-ex .c om ip 10.1.1.3 create-author ity ns4.mstd-ex .c om ip 10.1.1.4

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

create-author ity ns5.mstd-ex .c om ip 10.1.1.5 config dns zones create div2.mstd-ex.com div2.mstd-ex.com create-author ity ns1.mstd-ex .c om ip 10.1.1.1 create-author ity ns2.mstd-ex .c om ip 10.1.1.2 create-author ity ns3.mstd-ex .c om ip 10.1.1.3 create-author ity ns4.mstd-ex .c om ip 10.1.1.4 create-author ity ns5.mstd-ex .c om ip 10.1.1.5

Step 4. Add hosts for the first zone and map their services.

A limitation of DNS is there is no bui l t-i n way of conveying exactly what service the client actually needs. A request for www.mstd-

ex.com could easily be for either HTTP or HTTPS service. A major

feature of the 7190 is that it is servic e aware. It knows about the act ual availability of services and can direct clients to the best site for that service. The problem lies in that the 7190 has no idea what service the client wants unless a one-to-one mapping of service types to host names is made in the configuration. In this example scenario it would be easy to lump both the HTTP and HTTPS services together in the configuration for the hostname www.div1.mstd-ex.com. But a problem could occur if one of the services ever failed at a site; the others are still avail able. Even though one service has failed, the other is still available and all that is returned to the clien t is the IP address. The subsequent attempts by the client to use the referred address fails because it is asking for a service that is unavailable at that site. The solution requires a little more work in the host Web pages, but allows full advantage to be taken of the service awareness of the 7190. If unique hostnames are used for each service type, thi s prob lem never occurs. Note that if the load balancers are either Intel® NetStructure

7180s or are fronted by Intel® NetStructureTM 7110s, there is less of an issue with combining HTTP services with HTTPS services. Most of the traffic ever reaching a server would be HTTP.

In this scenario the services avail able on a single Web sit e have been divided into three different hostnames: www (HTTP), wwwsecure (HTTPS), and ftp (FTP). Another advantage of dividing the service types like this is that each hostname can be configured to use a different balancing method. Typically FTP traffic is fewer connections, but longer connect ion times. T his is idea l for bal ancing by Least Connections. Secure traffic (HTTPS) or layer 7 load

C H A P T E R 4 Scenario 2

balancing (Rich Mode) can place a heavy burden on the load balancers. This is ideal for balancing by CPU Utilization. Layer 4 load balancing is typically many short duration connections. In this case response time can be used as a direct measure of the actual se rver farms loading. This is idea l fo r balancing by Response Time.

The mapping of services to hostnames is also the easiest place to designate a service standby. If the service had been designated as standby in the agent record when it was first confi gured, it would have no effect. The standby command for an agent or ISV Group is a shortcut to placing t hat servi ce in standby in all the h ostnames t hat use that service at the time the command is issued.

config dns zones div 1.mstd-ex.com hos tnames create www www method avgresp siteservices map site1:10.1. 1.100:80 map site2:10.1. 2.100:80 map backupsite: 10.1.4.100:80 backupsite:10.1.4.100:80 standby config dns zones div 1.mstd-ex.com hos tnames create wwwsecure wwwsecure method cpu siteservices map site1:10.1. 1.100:443 map site2:10.1. 2.100:443 map backupsite: 10.1.4.100:44 3 backupsite:10 .1.4.100:443 st an dby config dns zones div 1.mstd-ex.com hos tnames create ftp ftp method conn siteservices

C H A P T E R 4Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

map site1:10.1. 1.102:21 map site2:10.1. 2.102:21 map backupsite: 10.1.4.102:21 backupsite:10.1.4.102:21 standby

Step 5. Add host for second zone and map its services.

config dns zones div 2.mstd-ex.com hos tnames create www www method flash siteservices map site1:10.1. 1.103:80 map site2:10.1. 2.103:80 map site3:10.1. 2.103:80 map backupsite: 10.1.4.103:80 backupsite:10.1.4.103:80 standby

Step 6. Save and activate the configuration.

For a discussion of what is actually happening in this step see Scenario 1, Part 1, Step 6.

save first-cfg commit all

Step 7. Configure the Secondary 7190s.

For this scenario the primary 7190 i s the 71 90 lo cated at site1. All of the other 7190s are seconda r ies to th is si ng le primary. For details o n how to configure a secondary see Scenario 1, Part 1, Step 7.

Step 8. Delegate authority to the 7190s.

See Scenario 1, Part 1, Step 8 for an example of the type of entries required in a Bind domain da tabase file to delegate auth ority. In reality the Bind files for this scenario would be quite complex because it would involve multiple divisions of a large company. Attempting to addr ess the type of issues that might be involved goes well beyond the scope of this scenario.

Boot Monitor

The Intel 7190 Boot Monitor Command Line Interface (CLI) allows you to configure boot options and manage boot configuration files. Typically, the Boot Monit or is us ed only d uring in iti al confi gurati on or major reconfigurations, should the latter become necessary. Dayto-day operations are managed with the CLI. See the Chapter 2, “Theory of Operations,” for an overview of 7190 operations. See Chapter 6, “CLI Reference,” for details on specific commands.

General categories of ta sks per for med t hr ou gh t he Boot Monitor are:

• Configure and display boot options, including the configuration

file

• Manage the boot configuration file system

• Configure and change IP parameters

C H A P T E R 5Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

System Requirements

You can use any terminal or personal computer with a terminal emulator as the CLI command station.

The terminal must have the following features:

• 9600 bits per second, 8 data bits, 1 stop bit no parity, no flow

control.

• Serial terminal emulation program such as Terminal or

HyperTerminal® for Windows® NT or HyperTerminal for Windows 95 or 98.

• Cable and connector to match male DTE connector (DB-9).

Accessing the Boot Monitor

NOTE: After configuring the 7190 in the Boot Monitor, you must enable autoboot for the devic e to boot into normal operating mode.

To access the Boot Monitor Command Line Interface, interrupt the boot sequence by pressing a key at the following prompt:

Press any key to stop au toboot

In a few seconds the following prompt appears, confirming that the Boot Monitor is running:

monitor>

Boot Monitor Command Reference

The Boot Monitor contains the following commands:

C H A P T E R 5 Boot Monitor Command Reference

Command Description autoboot

Use this command to enable or disable the Autoboot function. When Autoboot is enabled, during st artup th e 7190 prompts you to pr ess a key to enter the Boot Monitor command line interface. If you ignore the prompt, startup concludes with the 7190 in normal operating mode (displaying the Intel 7190# prompt). When Autoboot is disabled, the startup sequence is interrupted and displays the Boot Monitor interface (displaying the monitor> prompt). Autoboot is enabled by default.

To enable Autoboot, press Enter to accept the default “enable.” To disable, enter disable, then press Enter.

Example:

monitor>autoboot Autoboot? [enable]--->

Boot Monitor Command Reference

C H A P T E R 5Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description boot

NOTE: Userentered names and IP addresses in the example are for illustrative purposes only. The appropriate values for your installation may vary.

This command boots the 7190 using a specified configuration.

Example:

monitor>boot Current active configuration

---------------------------Product: 7190 Version: 3.0 Patch Level: 0.0 Build: D18

---------------------------Current time: Fri Mar 31 14:04:56 Current Config: default.cfg Hostname: intel7190 Using DHCP: No IP Address: 10.1.1.11 Netmask: 255.255.255.0 Default Route: 10.1.1.1 Domain: xyz-ex.com Primary nameserver: 10.1.1.101 NTP: Enabled Servers: 10.1.1.2 NIC setup: auto Autoboot: Enabled Boot timeout: 5 (seconds)

Boot current configuration? [y] Please stand by, the system is being rebooted.

delete

This command deletes the specified configuration file from 7190.

Example:

monitor>delete Enter the configuration file to delete [] ---> filename.cfg

Boot Monitor Command Reference

C H A P T E R 5 Boot Monitor Command Reference

Command Description dir

dhcp

dns

This command displays the list of saved boot configuration files.

Example:

monitor>dir File name

---------- *default.cfg

This command allows you to enable or disable the use of DHCP by the

7190. When DHCP is enabled, the 7190 receives its configuration parameters from the DHCP server at startup. When DHCP is disabled, the 7190 ignores the DHCP server, and so must be manual ly con f ig ur ed at startup. Respond to the prompt with y to enable, respond with n to disable. DHCP is disabled by default.

Example:

monitor>dhcp Do you wish to use DHCP? [n]--->y

Press Enter to accept the default, n to disable DHCP, or enter y, then press Enter to enable.

Use this command to specify the domain and (optionally) nameserver(s). The 7190 prompts you for the required information.

Syntax:

monitor>dns

Example:

monitor>dns Enter domain ("-" to delete) [somedomain.com] --->somedomain.com Primary Name Server (<return> to end) [209.218.240.1] --->209.218.240.1 Secondary Name Server (<return> to end "-" to delete) [] --->

Boot Monitor Command Reference

C H A P T E R 5Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description factory_reset

NOTE: factory

_reset

does not delete saved configuration files.

CAUTION: This command rewrites the default configuration to the default.cfg configuration file.

halt

This command resets system to factory defaults. Values affected by this command are:

• Entire current DNS configuration is deleted

• Route parameters

• CLI parameters

• IP address

• Default route

• Hostname

• Domain

• Name servers

• DHCP is disabled

• Autoboot is set to “enabled”

This command halts the 7190 system.

Boot Monitor Command Reference

C H A P T E R 5 Boot Monitor Command Reference

Command Description help

This command lists all Boot Monitor commands or optionally displays syntax for a specified command.

Example:

monitor>help autoboot Enable or disable autoboot boot Boot saved configuration delete Delete a saved configuration file dhcp Use DHCP to configure system dir Directory of saved config files dns Configure domain and name server(s) factory_reset Reset system to factory defaults halt Use to halt 7190 system help Show list of available commands host Set host name info Show system status ip Set IP address load Load a specified configuration netmask Set netmask nic Configure network interface card route Set default route save Save the current configuration setdate Set the real-time clock setup Configure unit show Show saved configuration info version Display software version info

Boot Monitor Command Reference

C H A P T E R 5Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description info

This command displays the current boot configuration.

Example:

monitor>info Current active configuration

---------------------------Product: 7190 Version: 3.0 Patch Level: 0.0 Build: D18

---------------------------Current time: Thu Mar 31 12:04:39 2000 Current Config: default.cfg Hostname: www Using DHCP: No IP Address: 10.1.1.11 Netmask: 255.255.254.0 Default Route: 10.1.1.1 Domain: xyz-ex.com Primary nameserver: 10.1.1.10 NIC setup: auto Autoboot: Enabled Boot timeout: 5 (seconds)

Use this command to specify the IP address of the 7190.

load

Example:

monitor>ip Enter IP address [10.1.1.11] --->10.1.1.111

Load a previously saved configuration file into memory.

Example:

monitor>load Do you want to load a saved configuration? [n] --->y Configuration file name? [savedcnfg.cfg] ---> Configuration loaded: savedcnfg.cfg

Boot Monitor Command Reference

C H A P T E R 5 Boot Monitor Command Reference

Command Description netmask

nic

route

Use this command to specify the netmask.

Example:

monitor>netmask Enter Netmask [255.255.254.0] --->255.255.254.0

Use this command to configure network interface card (NIC) parameters. Assurance of compat i bili ty wi th some older switches, hubs, or routers, may require that you directly specify the Ethernet speed and duplex mode of the network interface card for the 7190. The nic command, available at the serial console, allows you to specify these characteristics.

Example:

monitor>nic Auto config NIC card? [y] --->n 1 - 100BaseTx 2 - 10BaseTx Select Media Type (1 or 2): [1] --->1 Use Full Duplex? [y] --->y Done Ether config: 100basetx,full_duplex

Use this command to specify the default route (gateway).

Example:

monitor>route Enter default route [10.1.1.1] --->

save

Use this command to save the current configuration. Changes made during the current Boot Monitor session are lost unless you use the

save command.

Boot Monitor Command Reference

C H A P T E R 5Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description settime

NOTE: Flash does not work correctly if settime is not configured.

Use this command to configure the date and time of the 7190. One way to configure this is by using the Network T ime Pro tocol (NTP). The user is prompted if NTP should be used, and is then prompted for IP addresses of the NTP servers. Be sure that the selected NTP servers are a reliable source for NTP time and that the NTP server latency is less than 20 milliseconds. If NTP is not used, then the date and time ar e configured manually.

When you say no for “Use NTP?” the setdate prompts are displayed. When you specify yes, you ar e prompt ed for the NTP server a ddress(es).

Example:

monitor>settime Use NTP? [y] --->n Warning: Load Balancing Method FLASH will not work without NTP The current time is now: Wed Jan 12 20:23:53 2000 Enter the year (YYYY): [2000] ---> Enter the month (MM): [01] ---> Enter the day (DD): [12] ---> Enter the hour (HH): [20] ---> Enter the minute (MM): [23] ---> Enter the seconds (SS): [53] ---> Wed Jan 12 20:23:53 2000 Network Initialization... Application Initialization... monitor>settime Use NTP? [y] --->y Enter Name or IP address of NTP server: [] Enter an additional IP address of an NTP server or <return> to end [] --->209.218.240.1 Enter an additional IP address of an NTP server or <return> to end [] ---> monitor>

When logging in to CLI, system date/time is displayed. If NTP is enabled and operational, NTP information is also be displayed.

Boot Monitor Command Reference

C H A P T E R 5 Boot Monitor Command Reference

Command Description setup

show

NOTE: Use the dir command to display the list of saved configuration files.

This command initiates the setup procedure of the 7190. The system displays prompts for all inputs necessary to initialize system.

Example:

monitor>setup Auto config NIC card? [n] --->y Done Ether config: auto Enter hostname [nsb-9] ---> Autoboot? [enable] ---> Enable DHCP? [n] ---> Enter domain (’-’ to delete) [mysite_ex.com] ---> Primary name server (’-’ to delete) [10.1.1.10] --> Add additional name server (<return> to end) [] ---> Enter IP address [10.1.1.1] ---> Enter Netmask [255.255.254.0] --->

This command displays a specified saved boot configuration file. Type show, then the name of the configuration file you wish to view. Example:

monitor>show Configuration file name? [] ---><filename>

Boot Monitor Command Reference

C H A P T E R 5Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Notes

CLI Reference

The Intel® NetStructure™ 7190 Multi-Site Traffic Director is fully configurable through the Command Line Interface (CLI). The CLI is accessible either through Telnet to the 7190, or the serial port. Commands exist in a logical hierarchy. This chapter contains a summary command list, illustrations of the command tree structure, and a comprehensive reference with descriptions of all commands, their parameters, and if app licab le, examples of their output displ ay.

Environment

Editing the Command Line

The 7190’s CLI provides many key combinations for ease of ed iting. These are described in Table 6-. The list is also avai l able i n the CLI. Type help ttychars and press Enter.

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

CTRL-A CTRL-B CTRL-C CTRL-D CTRL-E CTRL-F CTRL-H CTRL-L-<TAB>

Move insertion point to beginning of line Move insertion point back one character Prompts to stop the currently running function Delete character under cursor Move insertion point to end of line Move insertion point forward one character Backspace Show all possible completions of the current command

branch at the current level

CTRL-L CTRL-N or Down Arrow

Clear screen Next item in Command History (see “Command History”

below)

CTRL-P or Up Arrow CTRL-R CTRL-S CTRL-T CTRL-U CTRL-W <TAB>

Previous item in Command History Reverse Command History search Forward Command History search Transpose character over cursor with preceding character Delete from cursor to beginning of line Delete from cursor to beginning of word Display all possible commands and levels available from

current level, exce pt global commands and dynamic nodes.

CTRL-_ Esc-< Esc-> Esc-Backspace or Esc-CTRL-H Esc-B Esc-C Esc-D Esc-F Esc-L

Undo the last character Display beginning of Command History Go to end of Command History Delete previous word Move insertion point back one word Capitalize letter and move to end of word Delete from cursor to end of word Move insertion point forward one word Make letter lower case and move insertion point to end of

word

Esc-U Insert

Capitalize entire word Toggle insertion mode (insert or overwrite)

Key Combinations

C H A P T E R 6 Environment

Command History

The 7190’s CLI records recently executed commands and al lows you to review them.

history <n>

With no parameter <n> specified, history displays the last ten commands entered by the user. The integ er <n> spe cifies the history index number. When <n> is specified on the comman d line, the ten commands executed before that of the specified index number are displayed.

! <n> or h <n>

NOTE: You must include

a space between the “!” or “h” and the history index

number

NOTE: Do not enclose the search target in quotes.

Executes the command beginning at the specified history index number.

Pipes

Any command can be piped to either grep <grepstring> or more.

• Output display of commands piped to grep is limited to lines

containing <grepstring>.

• Output of commands piped to more appears a page at a time for

easier readability.

• Pipes can be cascaded (typically with a final pipe to more).

Example: config sys info | grep telnet | more

• Multiple grep commands can be cascaded to search for multiple

words. Example: config sys info | grep telnet | grep port

Online Help

7190 provides online help in the following forms:

• Type help to describe help features.

• Type help ttychars to display a list of special terminal editing

characters.

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

• Type help <command> for a description of a specific command

or, if relevant, a list of sub-commands you can enter from within <command>.

• Type? to display a path list of commands and parameters

available from the current prompt or <command> forward.

• Typing? or help as one of a command’s parameters, i.e.,

<command>, displays help regarding the parameters available for <command>.

Command Line Syntax

The CLI uses the following syntax:

Angled brackets (<>) Straight brackets ([ ])

Braces ({}) Bold

Vertical bar (|)

Angled brackets designate where you enter variable parameters. Choices of parameters appear between straight bracke ts, separat ed by

vertical bars. Optional commands or parameters appear between braces. Commands shown as they are entered after the CLI prompt appear in

bold type. (The prompt appears in normal typeface to distinguish it from the command text.)

Separates choices of input parameters within straight brackets. You may choose only one of a set of choices separated by the vertical bar. (Do not include the vertical bar in the command.)

Command Line Syntax

C H A P T E R 6 CLI Command Summary

CLI Command Summary

This section contain s diagrams and li sts of the 7190 ’s CLI commands categorized by function. Complete details of CLI commands appear in the command reference section of this chapter.

Objects and Parameters

The following figures illustrate the show and config branches of the CLI-configurable objects and their relationships to one another within the 7190.

show

ROOT

info

config

commands

cli

info

zones

info

stats

info

stats

hostnames

info

stats

info

stats

siteservices

info

stats

info

stats

dns info

stats

info all

stats all

status

agents

info

stats

info

stats

services

info

stats

info

stats

flash

info

isvgroups

info

stats

info

stats

services

info

stats

info

stats

sys

info date

software info

snmp info wizard info

secondary info

ssh info

logs

display

display-old

Command Tree (Show)

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

show

commands

cli

info

port

prompt

screenlines

telnet-sessions

timeout

users

username

delete

software

delete install

secondary

create delete

enable disable

community

info

boot

any

flash

list

info

ssh info

trap

info

port create delete

info

create delete

ROOT

info

sys

info

logs

display

display-old

SNMP

info

auto-topology

port

sysContact

sysName

sysLocati on

wizard

info enable disable

ntp

info create delete

config

zones

info

stats create delete

rename

create-authority delete-authority

authority-ttl

hostnames

rename

authority

add-rec-responses multi-vip-s ta nd by disable multi-vip-standby enable

siteservices

info

stats

info create delete

stats

info

vips

ttl

method

stats

info

map

unmap

max-delay

poll-interval

num-polls drop-miss

dns info

stats

info all

stats all

status

log

primary

secondary

flash

info

enable

disable aliasing

agents

info

stats create delete

rename

info

stats

enable

disable agent-ip

agent-port

interval timeout

flash-src

flash-port

flash-backup-src

flash-backup-port

services

stats

info

enable

disable

standby

create delete

rename

stats

info

enable disable

standby

weight

factor

stats

info enable disable

standby

weight

factor

isvgroups

info create delete

rename

info

stats

enable

disable interval timeout

flash-src

flash-port

flash-backup-src

flash-backup-port

services

stats

info enable disable

standby

create delete

rename

stats

info enable disable

standby

weight

method

url

Command Tree (Config)

C H A P T E R 6 CLI Command Summary

Global System Commands

? !<n> or h<n> !! … | grep … | more

arp back (also box, top, toplevel) box (also back, top, toplevel) commit all commit local clearstats dbpr exit (also logout, quit) halt help history info logout (also exit, quit) netstat nslookup ping quit (also exit, log out) reboot revert factory-default start-wizard top (also back, box, toplevel) toplevel (also back, top, box ) traceroute who

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

File Management Commands

cat copy dir get put remove restore restore-verbose save

CLI Commands

NOTE: The config info commands display uncommitted configuration information that is inactive. The show info commands display the active configuration information. A commit command is necessary before any config commands become active, after which the

show info and config info commands displays

matching information.

config cli

info login-attempts more port prompt screenlines telnet-sessions timeout username <username> password <password> level users delete

System Commands

config sys

info logs display logs display-old ntp create <ntpserver> ntp delete <ntpserver> ntp info secondary info secondary any secondary flash secondary list secondary create <IP> secondary delete <IP> software info software boot

C H A P T E R 6 CLI Command Summary

software delete software install secondary info secondary any secondary flash secondary list secondary create <IP> secondary delete <IP> ssh info ssh enable ssh disable wizard info wizard enable wizard disable

SNMP Commands

config sys snmp

info auto-topology <enable|disable> port <#> sysContact <con tact person> sysName <system name> sysLocation <system location> community info community creat e <community strin g> ip <IP

address> rights <snmp rights> community delet e <string> ip [<IP

address>|any] trap info trap port <trap port> trap create <IP address> community <community

string> trap delete <IP address> community <community

string>

DNS Commands

config dns

stats stats all status info info all

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

log primary secondary

config dns agents

info stats metrics metrics <IP address> port <port#> create <agentname> ip <IP address> delete <agentname> rename <agentname> new <agentname>

config dns agents <agentname>

info stats metrics metrics <IP address> port <port#> enable disable agent-ip agent-port interval timeout flash-src flash-port flash-backup-src flash-backup-port

config dns agents <agentname> services

info stats enable disable standby create <servicename> delete <servicename> rename <servicename> new <servicename>

C H A P T E R 6 CLI Command Summary

config dns agents <agentname> services <servicename>

info stats enable disable standby weight factor

config dns isvgroups

info create <isvname> delete <isvname> rename <isvname> new <isvname>

config dns isvgroups <isvname>

info stats enable disable interval timeout flash-src flash-port flash-backup-src flash-backup-port

config dns isvgroups <isvname> services

info stats enable disable standby create <servicename> delete <servicename> rename <servicename> new <servicename>

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

config dns isvgroups <isvname> services <servicename>

info stats enable disable standby weight method <probemethod> url <url>

config dns zones

info stats create <zonename> delete <zonename> rename <zonename> new <zonename>

config dns zones <zo nename>

info stats create-author ity <authorityn am e> ip

<ipaddress> delete-author ity <authorityn am e> authority-ttl

config dns zones <zo nename> hostnam es

info stats create <atypehostname> delete <atypehostname> rename <atypehostname> new <atypehostname>

config dns zones <zo nename> hostnam es <hostname>

info stats ttl method authority add-rec-responses <addrecrespval> multi-vip-standby enable multi-vip-standby disable

C H A P T E R 6 CLI Command Summary

config dns zones <zonename> hostname s <hostname> siteservices

info stats map unmap

config dns zones <zonename> hostname s <hostname> siteservices <s iteservicenam e>

info stats enable disable standby weight factor

config dns flash

info enable disable aliasing max-delay poll-interval num-polls drop-miss

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Show Commands

show cli info show sys

info date ntp info secondary info snmp info ssh info logs display logs display-old software info wizard info

show dns

info flash info stats info all stats all status

show dns zones

info stats

show dns zones <zone name>

info stats

show dns zones <zone name> hostnames

info stats

show dns zones <zone name> hostnames <ho stname>

info stats

C H A P T E R 6 CLI Command Summary

show dns zones <zone name> hostnames <ho stname> siteservices

info stats

show dns zones <zone name> hostnames <ho stname> siteservices <s iteservicenam e>

info stats

show dns agents

info stats metrics

show dns agents <agentname>

info stats metrics

show dns agents <agentname> services

info stats

show dns agents <agentname> services <servicename>

info stats

show dns isvgroups info show dns isvgroups <isvname>

info stats

show dns isvgroups <isvname> services

info stats

show dns isvgroups <isvname> services <servicename>

info stats

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Global System Comman ds

Command Description ? ! (also h, history)

!! arp back (also ..) box (also top)

commit all

commit local

Displays all the commands at the command level. Displays the command history.

Syntax:

!<n>

where: n is the command index number from history list.

Repeats the last command. Displays 7190’s ARP table. Moves up one level in the CLI command tree. Moves back to the beginning (root level) of the CLI branch

command tree. Saves changes and informs the DNS server of new

configurations. It writes all changes to t he disk and propagat es the configurations to the secondary 7190s.

Saves configuration information on the local 7190 only (i.e., no information migrates to the secondary 7190s on the network.) This command is useful for testing new configurations.

Global System Commands

C H A P T E R 6 CLI Command Summary

Command Description dbpr

Displays information on the active configuration down to the agent VIP level. This command is useful for assessing the effectiveness of the current balanc ing settings. Options consist of a hyphen and letter followed by a user-specified parameter or parameters. Syntax:

dbpr [host | agent | fla sh] {options}

where: host specifies that the command is to display information from a specified host. agent specifies that the command is to display information from a specified agent. flash specifies that the command is to display flash latency information between peers.

Options:

-a agent_ip agent_port limits the display output to information related to the load balancer id entified by agent_ip and agent_port.

-h hostname limits display output to information related to the host identified by hostna m e. Used together with the "-a" o pt ion, the "-h" option limits the display information to a specific service on the specified load balancer.

-z zonename limits display output to information related to hosts within zonename. This option is ignored if combined with the "-h" option. Combining this option with the "-a" option constrains the display info rmation to specific servic e(s) on the specified load balancer.

-f overrides the default display limit of statistics and metrics only . Addit ional i nformatio n disp layed wh en "- f" is use d incl udes weight, factor, TTL, and authority records.

-v vip_ip_address limits output to information relating to VIPs with an IP address of ip_address. This option can be combined with the "-a", "-h", and "-z" options to display information related to a narrow subset of VIPs or even a single VIP. For example:

dbpr host -v 10.234.2.2 -h www.foo-ex.com -a

192.168.16.3 1999

Global System Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description dbpr (cont’d)

exit halt

help history, (also !, h)

Displays a single VIP- the one associated with host www.fooex.com whose IP address is 10.234.2.2 and is on t he load balancer at 192.168.16.3:1999

-c causes the referral statistics associated with a ll displayed VIPs to be cleared following the display.

Exits the CLI. Shuts down the 7190 preparatory to power off. If you wish to

return the 7190 to operational mode from the halted state, you must manually reboot u sing the swi tch labeled "Reset" on the rear panel.

Displays help for the CLI. Displays the command history list or rec alls a command by i ndex

number from the history list. Syntax:

history {<n>}

where: n is the command index number from the history list

Global System Commands

C H A P T E R 6 CLI Command Summary

Command Description info

Information is displayed one pa ge at a time if the file size is greater than 500K even when more (‘paging’) is disabled. This info command (at the root level) displays only current configurations, i.e., ‘committed’ changes (performed in the Config branch). This is the same information displayed from info commands on the Show branch of the CLI commands.

System Information

•

Including the 71 90’s unit identifier, MAC address, IP address, Netmask, Broadcast, Default Route, and Nameservers.

SNMP Information

Including SNMP state (running or stopped), if auto-topology

•

state (enabled or not), agent port, SysName, SysLocation, Community information, Trap information

Software Information

•

For each installed version: Image index number, Product description, Version number, Patch number, Build number

CLI Information

Number of concurrent Telnet sessions allowed, Root prompt,

•

(number allowed of) Login attempts, More (‘paging’) state, (number of) Screenlines, System ID, CLI Timeout value, CLI port number, Wizard state (enabled or disabled)

logout

NTP Servers Information

Displays information about any configured NTP servers.

•

DNS Information

•

Primary or secondary (stat e), Logging sta te, Flash Infor mation (Flash state, Polling In te rval, Max Broadcast Delay, aliasing state, Number of Polls, Drop Misses), Agent information and services configured under each agent , I SV Group in fo rmati on and services under the ISV, Zone info rmatio n , Host name and information (load balancing method), and Site Services information.

Exits the current logged-in session.

Global System Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description netstat ping

quit reboot revert factory-default

NOTE: Only those parameters set within the CLI are affected.

Displays the 7190’s routing tables. Tests the network connection to another networking device. It

sends an ICMP packet f rom the 7190 to the t arget device; when i t receives the packet, it sends a ping reply. When the 7190 receives the reply, it displays a message indicating that the specified IP address is alive. If the unit receives no reply, it displays a message indicating that the target device is not responding. Syntax:

ping <ipaddress | hostname>

where:

ipaddress is the IP address of the other networking device. hostname is the host name of the other networking device.

Exits the current session. Reboots the 7190. Returns the configuration to the last committ ed configuration. Resets the 7190 to its original factory configuration. Original

factory settings are listed below. Networking parameters controlled through the Boot Monitor are

not affected by the factory-default command. CLI factory settings:

start-wizard

toplevel (also box)

• Entire DNS configuration is deleted.

• 7190 is set to primary.

• Telnet port is set to 23.

• Prompt is reset to product name.

• Maximum Telnet sessions is set to 0.

• Idle timeout is set to 900 seconds.

• Maximum login attempts is set to 3.

Starts the Quick Start Wizard, which is an automated, intera ctive system configuration tool.

Changes the prompt level to the system top or box level.

Global System Commands

C H A P T E R 6 CLI Command Summary

Command Description traceroute who

Displays the route that packets travel to the network host. Displays the list of all users currently logged in.

Global System Commands

File Management Commands

Command Description cat

copy

Displays contents of the specified saved configuration file. Syntax:

cat <filename>

where: filename is the name of the file to be displayed.

Copies an existing configuration file to a new file. Syntax:

copy <source> to <destination>

where:

source is the name of the original file. destination is the name of the target file.

dir

get

Displays a list of saved configuration files. Also displays the last loaded configuration file.

Retrieves a configuration file from a TFTP server. Because the TFTP protocol has no user-login or validation, sites employing it typically enforce some file access restrictions. Such restrictions are specific to each site and vary widely in scope and methods. Syntax:

get <TFTP URL>

where: TFTP URL is the address of the tftp server from which you wish to retrieve the configuration file Example: get tftp://192.168.30.2/ tftpboot/get.cfg This helps to save configuration files out s ide the box.

File Management Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description put

remove

restore

Transfers a configurat ion t o th e spec ified re mote file o r di rectory. If the remote-directory form is used, the remote host is assumed to be a UNIX device. Because the TFTP protocol has no userlogin or validation, sites employing it typically enforce some file access restrictions. Such restrictions are specific to each site and vary widely in scope and methods. Syntax:

put <filename> to <TFTP URL>

where: TFTP URL is the address of the tftp server to which you wish to send the configuration file. filename is the nam e of the file to send. Example: put default.cfg to tftp://192.168.30.2/tftpboot/default.cfg

Removes a configuration file. Syntax:

remove <filename>

where: filename is name of the configuration file to be removed.

Restores a CLI configuration from a previously saved file. (See save.) Syntax:

restore <filename>

where: filename is the name of the configur ation file to be restored. (The default file name is default.cfg.) Execute the command commit local or commit all to activate the restored configuration.

restore-verbose

As restore above, but displays each line of the restored file.

File Management Commands

C H A P T E R 6 CLI Command Summary

Command Description save

NOTE: Username commands are not valid in configuration files, i.e., save and restore operations do not include username data. Use the command config cli username to restore user names and passwords.

Saves the current CLI configuration to a file of the specified name. This information is saved in a text file. (See also restore.) Syntax:

save <filename>

where: filename is the file name under which the configuration is stored. (The default file name is “default.cfg.”)

File Management Commands

Configuration Commands

Config CLI Commands

Command Description config cli

Changes the prompt level to config cli.

Config CLI Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description

info

Displays the status of all variables at the config cli level. Information displayed:

• Number of concurrent telnet sessions allowed

• Root prompt

• Number of login attempts allowed

• More (‘paging’ enabled/disabled)

• Number of screenlines

• System ID

• CLI timeout (number of timeouts)

• CLI port (port number)

Example:

Telnet sessions: 0 Root prompt: Intel_7190 Login attempts: 3 More: disabled Screenlines: 25 System Id: 7190 CLI timeout: 900 CLI Port: 23

config cli

delete

Deletes a user. Syntax:

config cli delete <username>

where: username is the username of the user you wish to delete.

Allows you to specify the maximum allowable number of failed login attempts before closing the connection on a Telnet session. Syntax:

config cli login-attempts <tries>

where: tries is a number from 1 to 30.

Config CLI Commands

C H A P T E R 6 CLI Command Summary

Command Description

NOTE: If information is greater than 500,000 bytes, the display is automated to display one page at a time.

port

prompt

config cli

screenlines

This paging command allows you to set scrolling of the output display to one page at a time or to continuous display. Syntax:

config cli more [enable | disable]

where:

enable allows you to scroll one page at a time. disable results in continuous scrolling .

Specifies the Telnet port on which the CLI runs. Syntax:

config CLI port <port>

where: port is a valid port. Valid ports are port 23 or any port between 1024 and 65535. The default is port 23.

Changes the r oot level pro mpt. Syntax:

config cli prompt <prompt>

where: prompt is the new prompt name. The default prompt is an abbreviation of the product’s name, e.g., “Intel_7190.” The default prompt can be restored by entering ““ as the prompt name.

Specifies the number of lines in the output display. Syntax:

config CLI screenlines <nlines>

where: nlines is the number of output lines (8 to 64). The default number of screenlines is 25. If ‘nlines’ does not match the lines in the screen, output is not displayed properly.

Config CLI Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description

telnet-sessions

NOTE: If you set the number of sessions to 0, you are disabling all future Telnet sessions to the 7190. To reset Telnet, you must access the device through the serial port and login, then change the Telnet session count from 0, to a number from 1 to 8

timeout

NOTE: Too small of a timeout value renders the CLI useless.

Sets the allowable number of concurrent inbound remote CLI login sessions. Syntax:

config CLI telnet-sessions <nsessions>

where: nsessions is the number of allowed sessions (0 to 8). The default number of sessions is 0. .

Sets or changes the idle timeout period before automatic logout for CLI sessions. The timeout value can be set to 0, which specifies no timeout

. To set a value, use the range 30 to 65535 seconds. Syntax:

config CLI timeout <seconds>

where: seconds is the timeout pe riod i n seconds (0, o r a ran ge of 30 to

65535). The default is 900 seconds (15 minutes).

Config CLI Commands

C H A P T E R 6 CLI Command Summary

Command Description config cli

username

NOTE: Username commands are not valid in configuration files, i.e.,

save config and restore config operations do not

include username data.

users

Add, change, or delete the login or password. The default user name, “admin” cannot be deleted. Syntax: To delete a user:

config cli username [delete] <name>

To add or update a user:

config cli username <name> password <password> level <ro | rw | rwa>

where: name is t he login name. (Must be from four to six teen character s with no spaces.) password is the password. (Must be from four to sixteen characters with no spaces.) level is the author ization level for the user:

• ro = read only (user can read, but cannot modify data)

• rw = read & write ( user can r ead and modif y data, bu t cannot

add or delete users)

• rwa = read & write admin (user can read and modify data,

and can add and delete users)

View all usernames and their access levels that exist in the system. Syntax:

config cli users

Config CLI Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Config Sys Commands

Command Description config sys

info

NOTE: The default route is the same as the default gateway.

logs display

Changes the prompt level to the System Config branch. Displays the 7190’s current system information.

For example:

System Id: MAC Address: 0:90:27:73:f0:e4 IP Address: 10.1.10.227 Netmask: 255.255.0.0 Broadcast: 10.1.255.255 Default Route: 10.1.1.1 Nameservers: mysite-ex.com

10.1.1.10

Displays the contents of the specified log file. Syntax:

where:

all - displays all log messages dns - displays DNS activ ity and health monitor information on

this 7190.

ntp - displays ntp messages system - displays system messages monitor - displays monitoring messages stats - displays statistical informatio n

logs display-old

software

Displays the contents of the old log file. Syntax:

config sys logs display-old <system|dns|ntp|stats|all>

Changes the prompt level to config sys software.

Config Sys Commands

C H A P T E R 6 CLI Command Summary

Command Description config sys

software info

software install

NOTE: Save your configurations before installing or booting a new image. Up to five (5) images can be installed on a 7190.

software boot

NOTE: Save your configurations before installing or booting a new image.

Displays all images that have been installed in the 7190. This includes the index number , the product name, the v ersion number, the patch number , the buil d number and the word “Running” next to the image that is currently active on the 7190. For example:

Index Product Version Patch Build

----- ------- ------- ----- ----1 Intel_7190 3.1 0.0 D3 Running 2 Intel_7190 3.0 0.1 D6

Download and install 7190 software through the FTP protocol. Once installed, images are selected for execution by using the command, config sys software boot. Syntax (ftp):

config sys software install <ftp url> {user <user name>} {password <password>}

where: url is a valid URL iden tifyi ng th e soft ware imag e t o downl oad. It must be of the form ftp://<host>/<path_name> . user name is the user name to use for logging in during file transfer (ftp only). password is the password to use for logging in during file transfer (ftp only).

Select a software image and reboot the system under that image. Syntax:

config sys software boot <index>

where: index is a valid index number of an installed software image, as displayed using the command, show sys software info.

Config Sys Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description config sys

software delete

secondary

NOTE: secondary commands do not need to be committed to become active (they are in effect for any future connection attempts).

secondary any

secondary info secondary flash

Delete old versions of the software from local storage. It can be used to free local storage to install a version update or product upgrade. Syntax:

config sys software delete <index>

where: index is a valid index number of an installed software image, as displayed using the command,

config sys software info

(also: show sys softw are info) Changes the prompt level to the config sys secondary

branch.

Allows any secondary 7190 to connect to the primary 7190. This command is executed on the primary 7190.

Displays information about which secondary 7190s can connect. Allows only secondary 7190s with an IP address in the Flash peer

list to connect. This command is executed on the primary 7190.

secondary list

secondary create <ip>

secondary delete <ip>

NOTE: Deleting an address prevents future connections for the specified address.

Displays only secondary 7190s configured using the config sys secondary cr ea te <ip> command.

Adds addresses to the config sys secondary list. These are addresses of 7190s that can be connected as secondaries.

Deletes addresses from the config sys secondary list.

Config Sys Commands

C H A P T E R 6 CLI Command Summary

Command Description config sys

ssh info

ssh enable ssh disable

config sys

wizard info wizard enable

wizard disable ntp create

NOTE: If you used selected Flash load balancing in the Quick Start Wizard, you need to configure NTP.

Displays the current status of SSH enable or disable. If the status was just changed, it reflects the changed status that is pending for the reboot.

Enables SSH connections the next time the box is rebooted. Disables SSH connections the next time the box is rebooted. Displays information about whether the Wizard is enabled or

disabled. By default, Wizard is enabled. Enables the Quick Start Wizard. The Quick Start Wizard is an

automated, interactive method to configure the 7190. It is available only through the serial port if enabled after Boot Monitor.

Disables the Quick Start Wizard. Adds an NTP server.

Syntax:

ntp create <ntpserver>

where: ntpserver is the fully qualified hostname or the IP address of the Network Time Protocol Server.

ntp delete <ntpserver>

config sys

ntp info

Deletes an NTP server. Syntax:

ntp delete <ntpserver>

where: ntpserver is the fully qualified hostname or the IP address of the Network Time Protocol Server.

Displays information about any configured NTP servers.

Config Sys Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Config Sys SNMP Commands

Command Description config sys snmp

info

port

auto-topology

sysContact

sysLocation

Changes the prompt level to config sys snmp. Displays information about SNMP agent port, sysContact,

sysName, sysLocation and auto-topology Allows you to specify the port on which the 7190 recei ves SNMP

requests. Syntax:

config sys snmp port <agentport>

where agentport is a number between 5020 and 65535 (the default is 161)

Enables or disables operation of the auto-topology protocol. The default is

disable.

Syntax:

config sys snmp auto-topology [enable|disable]

Allows you to specify a value for the MIB-II variab le sysC ontact. The default is null. Syntax:

config sys snmp sysContact <string>

where string is a string of displayable characters. Allows you to specify a value for the MIB-II variable

sysLocation. The default is null. Syntax:

config sys snmp sysLocation <system location>

where system location is a string of displayable characters.

sysName

config sys snmp

community info

Allows you to specify a value for the MIB-II variable sysName. The default is the hostname of the 7190. Syntax:

config sys snmp sysName <system name>

where system location is a string of displayable characters. Displays the community strings the 7190 is configured to accept,

such as Community (name), IP address, and Rights. Rights are ro (read-only) and rw (read-write).

Config Sys SNMP Commands

C H A P T E R 6 CLI Command Summary

Command Description community create

community delete

Specifies community strings that the 7190 accepts on incoming SNMP requests. Up to 10 community strings can be created. Syntax:

config sys snmp community create <string> ip [<IP address>|any] rights [ro|rw]

where string is the name of the community you wish to create,

ip address is the IP address of the host from which you

accept this community string. If any is specified, the community string is accepted on requests from any IP address.

ro means the

community string has read-only privilege. rw means the community string has read-write privilege. The default community strings are

public any ro and private any

Deletes a community string that the 7190 can accept on incoming SNMP requests. Syntax:

config sys snmp community delete <string> ip [<ip address> | any]

where: string is the name of the community string you wish to delete, and which you do not accept this community string. If

ip address is the IP address of the host from

any is

specified, the community st ring does not ac cept requests from an y IP address.

trap create

config sys snmp

trap port

Allows you to specify the host to which 7190 sends SNMP traps. Up to 10 trap receivers can be created. By default the trap receiver list is empty, that is, no traps are sent. Syntax:

config sys snmp trap create <ip address> community <community string>

where ip address is the IP address of the host to which you wish to send SNMP traps. community st ring is sent with all traps sent to the IP address.

Specifies the trap port number. The port number is between 5020 and 65535. Default is 162. Syntax:

config sys snmp trap port <trap port>

where trap port is the designated number.

Config Sys SNMP Commands

C H A P T E R 6Intel® NetStructure™ 7190 Multi-Site Traffic Director User Guide

Command Description

trap delete

Deletes a host from the trap receiver list. Syntax:

config sys snmp trap delete <ip address> community <community string>

where ip address is the IP address of the host you wish to delete from the trap receiver list, and identifier associated with specified access rights.

trap info

Displays the trap receiver list of:

• Trap ID Address

• Trap Community

Config Sys SNMP Commands

Config DNS Commands

Command Description config dns config dns

info

Moves you to the config dns command level. Displays DNS information.

For example.

DNS Information

community string is an

Running as a Primary Logging is Disabled

Config DNS Commands

Intel 7190 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Intel® NetStructure™ 7190 Multi-Site Traffic Director v.3.1.1

Technical Product Notice

Table of Contents

Introduction

What is an Intel® NetStructure™ 7190 Multi-Site Director?

Two Versions of the 7190

Who Should Use This Book

User Guide Summary

Theory of Operations

Traditional DNS

Multi-Site Traffic Management Using Intel Load Balancers

Typical Configuration

Site Balancing Methods

Partial Failures

Definitions

CLI Configuration

Custom/Manual Configuratio n

Adding Secondary 7190(s)

Commit the Configuration

NSLookup

Configure DNS Servers

Multi-Site Scenarios

Scenario 1

Introduction

Part 1 – Initial Configuration of a Simple Site

Part 2 – Changing to Flash Response Mode Balancing

Part 3 – Adding Load Balancers to an Existing Site

Scenario 2

Configuring in a Mixed Environment

Boot Monitor

System Requirements

Accessing the Boot Monitor

Boot Monitor Command Reference

CLI Reference

Environment

Editing the Command Line

Command History

Pipes

Online Help

Command Line Syntax

CLI Command Summary

Objects and Parameters

Global System Comman ds

File Management Commands

Configuration Commands