peerapp ultraband 1000 administration guide - grid configuration

5/28/2018 PeerApp UltraBand 1000 Administration Guide - Grid Configuration

1/126

UltraBand 1000Administration Guide

UltraBand 1000 Grid Configuration

Version 2.3

Release 1.3.0


2/126

Copyright

Copyright 2008 by PeerApp.

If you require any assistance, please contact us:

PeerApp Headquarters

PeerApp Inc.

Echo Bridge Office Park

381 Elliot Street, Suite 140LNewton Upper Falls

MA 02464, USA

http://www.peerapp.com

[email protected]


3/126

UltraBand 1000 Administration Guide - Grid Configuration i

Table of Contents

About This Guide ....................................................................................................... 1Chapter Summaries ........................................................................................................ 1Acronyms ........................................................................................................................ 2

Chapter 1 Overview ................................................................................................................... 3The Building Blocks of the Solution ................................................................................ 3Hardware Architecture ................................................................................................... 4Network Connectivity ..................................................................................................... 5Software Architecture .................................................................................................... 5Management .................................................................................................................. 6Management Connectivity ............................................................................................. 6

System Configuration ..................................................................................................... 7System Monitoring ......................................................................................................... 7Software Upgrades ......................................................................................................... 7Typical Network Configurations ..................................................................................... 8

Chapter 2 Working With UltraBand 1000 Management Tools ................................................... 10Working With the CLI ................................................................................................... 11

Getting Started with the CLI ................................................................................................ 11CLI Command Editing Features ............................................................. ............................... 12CLI Modes ............................................................................................................................ 13

TFTP Server ................................................................................................................... 14Working With the Configuration File ............................................................................ 15

Configuration File Sections .................................................................................................. 16Accessing UltraBand 1000 SNMP Information ............................................................. 16

Chapter 3 Configuring UltraBand 1000 ..................................................................................... 17Main Operational Features (Quick Jumpstart) ............................................................. 18The UltraBand 1000 Platform Features ........................................................................ 18

Caching Specific Features .................................................................................................... 19Platform Specific Features ................................................................................................... 21


4/126

UltraBand 1000 Administration Guide - Grid Configuration ii

Platform Operational Specific Features ............................................................................... 21Traffic Specific Features ............................................................. .......................................... 23

CLI-based Configuration ............................................................................................... 23Configuring Passwords......................................................................................................... 23Recovering Passwords ......................................................................................................... 23Configuring Management Network ..................................................................................... 24

Configuring Local Time ........................................................................................................ 24Managing the Caching Service ............................................................................................. 25Managing Servers ................................................................................................................ 25Resetting Management Service ............................................................ ............................... 26

File-based Configuration .............................................................................................. 26Configuring SNMP .......................................................... ...................................................... 26Configuring L4/L7 Switch Type ............................................................................................ 26Configuring P2P Protocols ................................................................................................... 27Configuring Bandwidth Management ................................................................................. 27Configuring Traffic Forwarding Options .............................................................................. 28Configuring Caching Policies ................................................................................................ 28Configuring Server Virtual IP Address ............................................................... ................... 29Configuring Server Data IP Address ..................................................................................... 29

Upgrading the System .................................................................................................. 30Upgrading UltraBand 1000 Software ................................................................ ................... 30Upgrading UltraBand 1000 License ..................................................................................... 30

Chapter 4 UltraBand 1000 CLI Commands ................................................................................ 32Regular Mode Commands ............................................................................................ 33Enable Mode Commands ............................................................................................. 51

Chapter 5 Monitoring UltraBand 1000...................................................................................... 81Chapter 6 Supported Setups .................................................................................................... 83

Using PBR on High Ports ............................................................................................... 84Alteon DPI with Asymmetric and UltraBand 1000 ............................................................... 84

Using Promiscuous Mode with Allot ............................................................................ 84Asymmetric Inline UltraBand 1000 with Allot 2540 ............................................................ 84 Asymmetric Inline UltraBand 1000 Grid with Allot 2540..................................................... 86

Using Bounce Mode with Sandvine .............................................................................. 87Asymmetric Grid UltraBand 1000 and PBR High Ports ........................................................ 87

Forwarding Flow ............................................................................................................ 88Cache-out Flow .............................................................................................................. 89Failure Handling ............................................................................................................. 90

Chapter 7 Sample Configuration Setups ................................................................................... 91PBR Configuration ......................................................................................................... 91

ISP Router Configuration ..................................................................................................... 91Cisco Router ................................................................................................................... 91Juniper M/T Series Routers ............................................................. ............................... 92

UltraBand 1000 Configuration ............................................................................................. 95PeerApp Router Configuration ............................................................................................ 96Alteon Configuration ........................................................................................................... 98

Multi-Tunnel Mode ..................................................................................................... 105ISP Router Configuration ................................................................................................... 105


5/126

UltraBand 1000 Administration Guide - Grid Configuration iii

UltraBand 1000 Configuration ........................................................................................... 106PeerApp Router Configuration .......................................................................................... 107Alteon Configuration ......................................................................................................... 107

Multi-Tunnel and VLAN Mode .................................................................................... 107ISP Router Configuration ................................................................................................... 107UltraBand 1000 Configuration ........................................................................................... 110

Alteon Configuration ......................................................................................................... 111

Promiscuous Mode ..................................................................................................... 112ISP Router Configuration ................................................................................................... 112UltraBand 1000 Configuration ........................................................................................... 112

Bounce Mode ............................................................................................................. 113ISP Router Configuration ................................................................................................... 113UltraBand 1000 Configuration ........................................................................................... 114Sandvine Configuration ..................................................................................................... 115

Appendix ACLI Reference ......................................................................................................... 117Regular Mode ............................................................................................................. 117Enable Mode ............................................................................................................... 118Configuration Mode ................................................................................................... 120Server Mode ............................................................................................................... 120


6/126

UltraBand 1000 Administration Guide - Grid Configuration 1

About This Guide

This guide describes PeerApps UltraBand 1000 P2P caching appliance. The UltraBand 1000 is a

network appliance designed for ISPs that localizes and reduces P2P traffic on your networks byup to 70%. The UltraBand 1000 intercepts P2P traffic on your network, monitors P2P activity,

caches requests, and serves the requested P2P files from the cache instead of the wide area

network.

The UltraBand 1000 is a family of products that can be configured as a single cache-engine

server (UltraBand 1000 Standalone Configuration) or a set of cache-engine servers (UltraBand

1000 Grid Configuration).

Chapter Summaries

This document is organized into the following chapters:

OverviewThis chapter introduces the UltraBand 1000, explains the parts andcomponents, and helps you understand the concepts required to use the rest of this guide.

Working With UltraBand 1000 Management ToolsThis chapter describes how to use themanagement tools provided by the UltraBand 1000, including the CLI, file upload and

download capabilities, the configuration file, and SNMP. The information provided in this

chapter is required to perform the management tasks in the remaining chapters.

Configuring UltraBand 1000This chapter describes how to configure and performmaintenance on the UltraBand 1000, including system configuration, network

configuration, and the P2P software functionality.

UltraBand 1000 CLI CommandsThis chapter describes how to work with theUltraBand 1000 CLI.

Monitoring UltraBand 1000This chapter describes how to monitor the UltraBand 1000by viewing networking and cache statistics.


7/126


Supported SetupsThis chapter defines the setups that are supported in UltraBand 1000installations.

Sample Configuration SetupsThis chapter presents the sample configuration files for thevarious setups that are supported in UltraBand 1000 installations.

CLI ReferenceThis appendix presents all the commands available in the CLI along withbrief explanations for each of them.

Acronyms

Table 1: Acronyms

Acronym Stands for

HASH ID A unique identifier for a file that is

retrievable using peer to peer protocol.

UB1000 UltraBand 1000.


8/126


1

Overview

The UltraBand 1000 is a network appliance designed for ISPs that localizes and reduces P2P

traffic on your networks by up to 70%. The UltraBand 1000 intercepts P2P traffic on yournetwork, monitors P2P activity, caches requests, and serves the requested P2P files from the

cache instead of the wide area network.

The UltraBand 1000 P2P easily integrates into your network. Its scalable architecture grows

with your network requirements and can scale to a multi-gigabit solution.

The Building Blocks of the Solution

The UltraBand 1000 solution is built on three key elements, which together provide theoptimal answer to your needs. The elements are all carrier grade, providing redundancy at all

levels and include:

Powerful L4/L7 switchThe switch is responsible for redirection of P2P traffic to thecaching engine and is placed seamlessly in the existing network. The configuration is based

on P2P protocol specific L4/L7 signatures, which ensure the P2P, and only the P2P, traffic is

forwarded to the Caching engine. The switch is introduced into the network as a Layer 2

switch connected with GbE links. The switch provides added value services, such as

applying policies (for example: capping, coloring packets, and blocking) to specific types of

traffic and the ability to provide detailed reporting and network analysis.

It is important to emphasize that the Switch does not interact in any way with the adjacent

equipment beyond the Layer 2 level. This is to say that there is no change to SRC or

Destination IPs.

The switch is only mandatory for promiscuous and bounce PBR mode.

Caching engine with multiple I/O processing modulesThe heart of the UltraBand 1000caching solution is the Caching Engine. The Caching Engine is based on a modular

technology, which can scale to a multiGigabit solution. The Caching engine analyzes the


9/126


P2P traffic and is in charge of the actual bandwidth savings achieved by caching and

retrieving files from the centralized storage.

Centralized storage arrayThe storage array is a high performance system selected toanswer the extreme demands posed by the P2P traffic. Centralized storage eliminates

content duplication, providing a scalable platform for increased bandwidth.

Figure 1 illustrates the UltraBand 1000 solution elements, L4/L7 switch, modular caching

engine, and centralized storage.

Figure 1: Solution Elements

The UltraBand 1000 solution is managed through an out-of-band network, which is separate

from the data flow, providing the ultimate security.

Hardware Architecture

The UltraBand 1000 is a carrier grade platform. The platform is made of four building blocks:

Management server Dual Core Intel Xeon. 2.0GB, 677MHz FBD. Dual Gigabit Ethernet.

Cache engine server Dual Quad Core Intel Xeon. 8GB 677MHz FBD.


10/126


Dual Gigabit Ethernet (onboard). Quad Port Gigabit network card.

L2 Ethernet switch

Aggregating iSCSI storage, control, and management traffic. CISCO 2960 with 24/48 ports.

L2/L3 Ethernet switch Depending on implementation (aggregating incoming/outgoing traffic).

If you are using UltraBand 2000, the modules are blades and not servers.

Network Connectivity

The external interfaces towards the network are GbE links. These interfaces can either be

single/multi mode fiber or copper. Internal links between the Caching engines, management

server, and storage arrays are GbE copper links.

Software Architecture

PeerApp has developed a high-performance caching engine, which provides efficientmanipulation of traffic.

There are four distinct layers in the software architecturenetworking, application, storage,

and distributed file system.

The network layer does not rely on previous L4/L7 detection of P2P, although this would result

in greatly improved performance.

The classifier manages the TCP sessions and is capable of basic detection of P2P protocols.

Non-P2P sessions, in the case of a miss in the L4/L7 switch or the use of a Layer 4 redirection

scheme, are forwarded transparently.

The inspection module works hand-in-hand with the classifier defining how to treat each

session. This module is protocol aware. Once the session has been established, the classifier

directs the session to the caching module, which either saves the data to disk and continues

forwarding it to the client, or intercepts the connection and serves the content from disk.

The storage layer is responsible for saving and retrieving data from the Distributed file system.

The disk manager decides what to save and maintains a local database, synchronized with all

the other caching servers, of all the content available.


11/126


All four layers are accessible via a management API and are centrally controlled by the

management server.

Figure 2: Software Architecture

Management

The UltraBand 1000 utilizes a centralized management system. The management server isresponsible for configuration, monitoring, and data collection from all the elements within the

solution (switches, storage, I/O servers, chassis). There are two ways to interact with the

centralized management system:

CLIA familiar context-based interface for easy configuration and basic monitoring. TheCLI is accessible via a text-based interface via the console cable and remote SSH (v2).

SNMPThe UltraBand 1000 provides a private MIB (SNMP v2) for easy access to all thecounters and information provided by the UltraBand 1000. This is especially useful for

customers who prefer using already existing 3rd

party software solutions. Monitoring via

the private MIB offers centralized access to the UltraBand 1000.

Management Connectivity

The UltraBand 1000 provides two physical means of connection to the management system:

RS-232Console connection to the CLItext based configuration and monitoring system. Out-of-band EthernetTCP/UDP connectivity to the management system. Remote access

is via SSH V2 (CLI) or SNMP.


12/126


In an out-of-band management network, the network access control should allow access

to the following ports for complete management functionality:

TCP 22 (SSH), 161 (SNMP). UDP 161(SNMP).

The UltraBand 1000 provides two security levels for usersregular and enabled. The user

database is stored locally on the appliance

Enabled users are permitted to perform configuration commands, maintenance procedures,

and low level debugging functionality.

The regular level is permitted read-only commands, providing monitoring and basic

debugging functionality.

System Configuration

Configurations are saved in text format and can be backed up on remote servers via TFTP.

Although not recommended, the text based configuration files may be manipulated remotely

and then downloaded to the UltraBand 1000 management server, providing a means of easily

maintaining and altering configurations of multiple appliances.

System Monitoring

The UltraBand 1000 provides the ability to remotely monitor the system, via the CLI when the

user is online, or via third party monitoring system, which uses SNMP and SNMP traps.

SNMPProvides access to all the statistics and environmental information in real-time. SNMP TrapsProvides alarm triggered notification, including hardware failures (fans,

temperature, power, physical interfaces) and performance thresholds such as CPU

utilization, and bandwidth consumption.

Software Upgrades

The UltraBand 1000 has two levels of software which are maintainedthe OS and application.

OS upgrades are done infrequently and are usually security patches.


13/126


Typical Network Configurations

Introducing the UltraBand 1000 into a network can be done in one of two ways - centralized

solution or localized per network zone (Metropolitan, POP, cable).

When doing network design, it is important to verify that the L4/L7 switch is placed on

a link where both directions of the session pass. This means that specific sessions

always go through the same L4/L7 switch. This limitation is due to the nature of P2P

traffic and the necessity to intercept the bi-directional connections.

The following diagrams show typical ways of deploying the UltraBand 1000.

Figure 3: PeerApp Network Solutions

The following describes the various solutions shown inFigure 3:

PBR/VRF routing solutionThis topology is used when the L4/L7 is not inline and therouter forwards at L4.


14/126


Basic inter-route solutionThis topology is for an ISP that wishes to put the L4/L7 inline. CMTS solutionThis topology is used when a cable service provider wishes to save

bandwidth within its network.

BRAS aggregation solutionThis topology is the same as CMTS but traffic is furtheraggregated.

Asymmetric data solutionsThese topologies may be used in cases where ingress andegress traffic may traverse in different routes.

Asymmetric topology with transparent forwarding solutionThis topology is used forintegration with Allot NetEnforcer in an asymmetric network topology.

Transparent forwarding solutionThis topology is used for integration with AllotNetEnforcer using port-based redirection.

The UltraBand 1000 is scalable to a multi-gigabit system and has been designed to grow withthe network requirements.

The basic unit consists of L4/L7 switch, multi-IO server chassis, 5 IO servers, single

management server and a single storage array. Introducing this solution to a network provides

redundancy of I/O data engines, management functionality, and the raid disk array.

To supply redundancy for L4/L7 switch, another L4/L7 switch should be deployed in a

hot-standby topology, much like that used in common networks.

Scaling up the solution is obtained by adding additional caching engines per chassis, multiple

chassis and increasing the storage.


15/126


2

Working With UltraBand 1000Management Tools

This chapter describes how to use the management tools provided by the UltraBand 1000,

including the CLI, file upload and download capabilities, the configuration file, and SNMP. The

information provided in this chapter is required to perform the management tasks in the

remaining chapters.

The UltraBand 1000 uses a number of different tools to help you configure, manage, and

monitor its performance. For some management tasks you may have a choice of which tool to

use. For instance, you can view all statistics both using SNMP and using the CLI.Table 2 lists

the different management tools that the UltraBand 1000 uses. Further information about

these tools is available in the remainder of this chapter.

Table 2: Management Tools

Management Tool Reference

Command-Line Interface (CLI) Use the CLI to perform most configuration and management tasks.

For a complete description of the UltraBand 1000 CLI commands,

refer toUltraBand 1000 CLI Commandson page32.

TFTP PeerApp provides license and software upgrades through the use of

upgrade files that are downloaded to the UltraBand 1000 using a

TFTP server.

In addition, the configuration is modified by downloading a

configuration file using TFTP.

Configuration File Use the configuration file to configure operational modes, caching,

and SNMP settings.

SNMP Use SNMP to monitor or view operational statistics of the

UltraBand 1000.

All the information available via SNMP is also available using

the CLI.


16/126


Working With the CLI

The Command-Line Interface (CLI) can be used to perform configuration, management, and

monitoring tasks required to manage the UltraBand 1000, including:

Configuring management settings, which includes: Configuring passwords. Configuring management IP addresses. Configuring local time.

Performing system maintenance, which includes: Managing the caching service. Managing servers.

Monitoring the system.You can also use SNMP to monitor the system.

Upgrading the system, which includes: Upgrading software. Upgrading license.Upgrading the system software or license is performed by downloading a new software or

license file to the UltraBand 1000.

For a complete list of all CLI commands, refer toCLI Referenceon page 117.

Getting Started with the CLI

There are two ways to access the system CLI:

Serial consoleThe serial console is used to access the standard CLI and the rescue CLI.The rescue CLI is used to enter the basic network and login information that you need to

get the system up and running and is only available from the serial console.

To access the standard CLI, login as admin. To access the rescue CLI, login as rescue.UltraBand 1000 ships with default passwords for both admin and rescue users set to

system serial number. Please make sure to change them. For instructions to change

passwords, refer to Configuring Passwords below.

Local area network (LAN) connection using ssh.Use sshto connect to the CLI over a LAN connection for regular access to the CLI. When

accessing the CLI using a LAN connection, use the login admin.


17/126


Before configuring the network settings for the UltraBand 1000, or if you have changed your

network settings so that UltraBand 1000 is inaccessible from outside, you must use the serial

console connection.

To log into the CLI using the serial console:

1. Connect to the USB port on the leftmost server in the chassis using USB-to-serial dongle.Use the following serial settings: 57600,N,1; hardware and software flow control

disabled.

After connecting to console of the management server the system prompts you for login.

2. Enter the special maintenance login rescue and press Enter.3. Enter the password for rescue user at the password prompt and press Enter. The setup

script is executed. After the setup script is finished, the system automatically logs you out.

To log into the CLI using ssh over a local area network connection:

1. Connect to the UltraBand 1000 using sshfrom any machine on your LAN. A login prompt isdisplayed.

2. Enter adminat the login prompt and press Enter.3. Enter the password at the password prompt and press Enter. The CLI prompt (console>) is

displayed.

To get help in the CLI:

To view a list of available commands in the CLI, enter helpor press ?.To log out of the system:

Enter exitat the CLI prompt.

CLI Command Editing Features

The TABkey provides auto-completion of command. If multiple choices are available, theyare displayed, option per line.

The ?key displays command and parameter hints. When basic command is incomplete,this key displays multiple completion options, one per line together with a brief

description. If a command is complete, pressing space + ? displays the next parameter hint.

Use the up and down arrow keys to navigate commands history


18/126


CLI Modes

The UltraBand 1000 supports several CLI modes:

Regular ModeIn Regular mode you can view system configuration and statistics, butcannot change any settings. While in Regular mode you are prompted with the regular CLIprompt: console>.

From Regular mode you can enter Enable mode or exit the CLI.

Enable ModeIn Enable mode, you can update the license or software, set the date,configure the login name and password. While in Enable mode you are prompted with the

enabled CLI prompt: console#.

From Enable mode, you can enter Configuration mode or Server mode, or return to

Regular mode by the exitcommand.

Configuration ModeIn Configuration mode you can configure any settings on thesystem. While in Configuration mode you are prompted with the config CLI prompt:configuration# .

From Configuration mode, you can return to Enable mode by exitcommand.

Please note that only one user may use Configuration mode at any given time. If you exit

Configuration mode without applying your changes, these changes are lost.

Server ModeIn Server mode, you can start, stop, or restart an individual server. You canalso set the servers log level. While in Server mode you are prompted with the CLI server

prompt: oper server # (for instance: oper server 1#).

From Server mode, you can exit back to Enable mode by exitcommand.

Rescue CLIIn addition to the standard CLI modes, the rescue CLI is to be used to recoverincorrect management network configuration and lost or forgotten CLI passwords.

While in rescue CLI mode you are prompted with the rescue CLI prompt: rescue@ce-1#.

In the rescue CLI mode, you can execute the following commands:

accessReset the white and black management access lists.

passwordsReset the admin and rescue passwords. networkConfigure following network parameters: IP address, netmask, default

gateway, and DNS server.

exitExit the rescue CLI mode. helpPrint the list of rescue CLI commands. This command can also be executed by

entering ?at the rescue CLI prompt.

After executing one of the above commands, you can perform another command or exit

the rescue CLI mode.


19/126


To switch from normal mode to Enable mode:

1. Enter enableat the CLI prompt. A password prompt is displayed.2. Enter the Enable mode password and press Enter. You are now logged in to Enable mode.

The prompt changes to the enabled CLI prompt.

The default password for Enable mode is equal to system serial number. Please make

sure to change it following the installation. For instructions on how to change

passwords, refer toConfiguring Passwords on page23.

While logged into Enable mode, you may sometimes need to run configuration commands. To

do this you must change to Configuration mode.

To switch to Configuration mode:

Enter configat the enabled CLI prompt. You are now in Configuration mode.

To exit Configuration mode:

Enter exitat the CLI config prompt. You are returned to Enable mode.To switch to Server mode:

Enter oper server at the enable CLI prompt, whereis the number of the server you want to control (for instance: 1). You

are now in Server mode.

To exit Server mode:

Enter exitat the CLI server prompt. You are returned to Enable mode.To switch from the enabled user to the normal user:

Enter exitat the enabled CLI prompt. You are returned to the Regular mode.

TFTP Server

To set up UltraBand 1000 for files uploading and downloading, you must have an external TFTP

server running. You download files to the UltraBand 1000 using a TFTP server in order to:

Update the UltraBand 1000 software. Update the UltraBand 1000 license. Update the configuration by means of changes to the configuration file.Before downloading a file to the UltraBand 1000, place the file onto the TFTP server.


20/126


Working With the Configuration File

The configuration file is used to configure the operational modes, cache settings, and SNMP

settings for the UltraBand 1000. The configuration file is a well-formed, valid XML file.

To change the configuration file:

1. Download the current configuration file: Enter export at the CLI config prompt, where

is the IP address of your TFTP server andis the name of

the file to which to write the current configuration.

The configuration file is then uploaded to your TFTP server.

2. Edit the configuration file using a text or XML editor.When editing the file, ensure that you only edit the field values and do not change or erasethe XML markup tags. If you inadvertently change the XML tags, the configuration will be

rejected when you attempt to load it.

3. When you have completed editing the file, save your changes.4. Download the changed configuration file to the UltraBand 1000:

a. Ensure that the changed configuration file is located on your TFTP server.b. Enter import at the CLI config prompt, whereis the IP address of your TFTP server andis the name of

the changed configuration file.After performing the above steps, the changed configuration is downloaded to the system,

but it is not yet loaded as the new configuration.

5. You can display or discard the new configuration before loading it. To display the currently loaded configuration, enter show configat the CLI prompt. To display the new configuration, which was loaded, but not yet applied, enter

displayat the CLI config prompt.

To show the differences between the current configuration and the downloadedchanged configuration, enter diffat the CLI config prompt.

To apply the new configuration in place of the current configuration, enter applyatthe CLI config prompt.

To discard the new configuration without making any changes to the currentconfiguration, enter discardat the CLI config prompt.

To restore the old configuration after applying a new configuration, enter restoreatthe CLI config prompt.


21/126


Each time you enter restoreyou revert to an older version of the configuration.

After reverting to an older configuration, the newer configuration is discarded and

cannot be restored.

Configuration File Sections

The configuration file has three main sections:

mgmt-configThe information in this section is for informational purposes only. Afterdownloading the configuration file from the system, this section displays the network

settings on the system.

commonUse this section to define the default settings for all servers. Any settings in theindividual server sections override the fields in this section.

server id=, where is the number of the caching engine server (slot numberminus 1).

Use this section to define the settings for an individual server. Aside from the network

configuration section, the fields in this section are contained in a servicesub-section and

are identical to the fields in the servicesub-section of the common section. The settings in

this section override the fields in the common section.

Accessing UltraBand 1000 SNMP Information

The UltraBand 1000 provides a robust set of SNMP status information, which you can monitor

using any standard SNMP tools. All status information available via SNMP is also available

using status commands in the CLI. The SNMP is provided using a private MIB (SNMP v2)

environment.


22/126


3

Configuring UltraBand 1000

This chapter describes the steps necessary to configure and perform maintenance on the

system if you need to make any changes. The types of configuration described in this chapterinclude the following:

The main Operational Features (Quick Jumpstart). CLI-based configuration:

Configuring Passwords. Configuring Management Network. Configuring Local Time.

File-based configuration: Configuring SNMP. Configuring L4/L7 Switch. Configuring P2P Protocols. Configuring Bandwidth Management. Configuring Traffic Forwarding Options. Configuring Caching Policies. Configuring Server Virtual IP Address. Configuring Server Data IP Address.


23/126


Main Operational Features (Quick Jumpstart)

The following configuration elements need to be configured initially, to jumpstart the system.

Detailed configuration instructions are provided later-on in this chapter.

CLI-based configuration: Configuring Management Network.

File-based configuration: Configuring SNMP/NTP. Configuring P2P Protocols. Configuring Traffic Forwarding OptionsWhen deploying a UB1000 Grid platform,

there are several different supported layer7 devices configurations that can be used.

Symmetric / asymmetric connection modes with single/multiple port connections are

possible, when configuring layer7 devices with the UB1000 Grid platform. Supportedconfigurations are outlined hereafter.

Allot 2500 integration. Sandvine integration in divert mode. Multi-port network link failure handling. VLAN tagging full support. UB1000 GridAllot integration - work with Allot as a redirector. Multi-Alteon support.

Asymmetric traffic support: The ability to work with more than one tunneling modewith Allot.

Multi interface support: Improve connectivity options, by adding support to work with more than one

physical Ethernet interface. Support is available for:

Allot in promiscuous mode. Alteon in multi-tunnel mode.

VLAN tagging (802.1q) support (partialonly for asymmetric & one port). The ability to work with packets that have the VLANS tagged.

The UltraBand 1000 Platform Features

The following is a list of system features that are available in the UltraBand platform. Some of

these features are configurable through the platform configuration file and some through the

CLI.


24/126


Caching Specific Features

Black list of hashesSpecificHASHes can be marked as non-cacheable. These HASHes willnot be cached or provided to the users if already cached starting from the time a

command to do so is given. The black list is maintained using CLI, allowing the

administrator to add, remove or view the list of HASH-ID(s) in the black-list.

Selective cachingDeals with the ability to control and dynamically change the popularitydecisions related to file caching. Stages will be changed dynamically as oppose to fixing a

decision through a static configuration.

Small memory bufferWhen the traffic is very low because of a configuration of theshaper, the memory buffer size might be too large (in memory) for this shaper. This

feature allows control over the buffer size, to optimize memory use and tailor it to the way

the traffic is shaped. If the buffer size does not match the shaped traffic sizethe cache

will be filled-up too slow.

Controlling the buffer size is done through the cluster-conf, using the following statement:

8000

Bandwidth-per-connection managementAllows control (Bandwidth - management)over the cache-out sessions. This allows placing a top limit on the cache-out sessions.

This is controlled in the cluster.conf file, by adding the following statements:

1

100000

Administrative state LockedAllows locking a specific server from handling traffic. (Thisfeature applies only to UltraBand 1000 systems)

locked

Upstream cachingLast mile architecture suffers from limited upstream resources whichare gravely affected from Peer-to-Peer symmetrical traffic pattern. Upstream caching

relives network congestion byproviding cached pieces to Peers in other zones, directly

from the cache instead of the last mile user.

HTTP cachingUltraBand caches any large HTTP documents (such as, video files, videostreaming and images) in order to reduce bandwidth usage, and to improve user

experience through accelerated document download time. Transparent HTTP caching is


25/126


implemented; therefore any standard HTTP contained document can be cashed regardless

of the URL associated with it.

Support for this protocol is configured through the cluster.conf file.

Add the following configuration statement to the section in Cluster.conf forthe platform to support the HTTP protocol:

1

ARES protocol supportAres Galaxy is an open source P2P file sharing application andprotocol that uses its own decentralized supernode/leaf network. Support for this protocol

is configured through the cluster.conf file.

Add the following configuration syntax to the section in Cluster.conf for the

platform to support the ARES protocol:

1

Foxy supportFoxy is a Gnutella client.Support for this protocol is configured through thecluster.conf file.


platform to support the Foxy client:

1

PANDO supportThe UltraBand platform supports the PANDO protocol. Pando is aproprietary software for P2P file sharing. It's mainly aimed at sending files using both Peer-

to-peer and Client-server architectures that would normally be too large to send via more

conventional means.

Pando uses a 256-bit end-to-end encryption method to secure communication among

peers.

The primary difference with traditional BitTorrent file transfer operation is that a copy of

the shared file is uploaded to Pando's servers and remains there for a limited time, seeding

it. In this way, the file remains available even after the original sender goes offline.

Support for this protocol is configured using the cluster.conf file.


platform to support the PANDO protocol:

1


26/126


Platform Specific Features

CFS: Cluster File SystemA distributed file-system, which can operate seamlessly over n-times storage devices/disks. This provides a very large storage for each cache engine,

enabling very fast data retrieval of cached data. The CFS is a content aware file-system,

optimized specifically for the content it stores. It uses less IO operations to service theamount of cached information it serves. Faster data throughput is achieved.

Platform Operational Specific Features

Duplicate logs to external syslogThe ability to duplicate the eventlog sent to syslog andtransfers the information to a syslog external server, while the system is running.

This is configurable through the cluster.conf file (Configuring the IP of the external syslog

in the cluster.conf):

192.168.0.154

Start/stop forwarding using a CLI command is supported. Please refer to theeventlog

forward/stopcommands inEnable Mode Commandson page51.

Automatic idle session logoutThe timeout interval of an idle CLI session, after which thesession is terminated. Can be configured through a CLI command.

Management ACL (Access Control List)Provides an approved (white list) and a denied(black-list) of system management features of the platform. These are the CLI and the WEB

(UBview) management interfaces. This is done using IP subnet ranges (added/removed

through the linux firewall). Configuration is done using the cluster.conf configuration file.

There are two options for specifying the ACLs:

Option 1Allow some IP address and block all the rest.This can be done by defining some good IPs in the white list, and block all the rest:

192.168.1.1

192.168.1.2

Option 2Block some IPs, allow the rest:

80.122.12.1

80.122.12.2

SNMP Traps forwardingThe platform generates SNMP traps upon certain events.Forwarding these traps to an external server is supported.


27/126


Controlling the traps forwarding is done through the clusted.conf file, with the following

statements related to the IP of the traps server, SNMP communities etc. The following

statements needs to be present in the cluster.conf:

10.11.12.1

gdcbhv

nkppui

ffff

E-mail alertsIn addition to SNMP traps, it is possible to forward critical platform alerts toa specific e-mail server.

This is controlled through the cluster.conf file, where the following statements needs to be

added:

194.90.1.5

[email protected]

Export CDRThe platform tracks each cache-out session and writes out a CDR recordrelated to the session when it ends. The CDR recording files are created periodically and

can be retrieved using FTP.The set of CDR files are created managed periodically. The

following is a sample CDR record:

Time thread_id log info06-07-08 07:38:16.980 0x51822940 [cdr:Statistics]

Protocol hash reason for closureHTTP, 75053B09EC96DAE2D47748DA18F3EF8A618D1738, DOWNLOADER,

bytes sent connection length in seconds4751360, 12,

Downloader ip:port uploader ip:port213.190.209.114:1531, 74.125.4.150:80

UB1000 using iSCSI and Dell PowerVault MD3000iThe UB1000 platform is now fullyintegrated with the Dell MD3000i SAN storage solution. The Dell PowerVault MD3000i can

consolidate up to sixteen (16) fully redundant hosts, expand to support up to 5.7TB of data

(using 380GB SAS drives) and provides wizard based installation, intuitive management,

advanced data protection software.

Supporting the PowerVault MD3000i increases the storage capacity of the UB1000

platform and allows the creation of a clustered file-system (using two or more UB1000

platforms).
mailto:[email protected]%3c/alert-emailmailto:[email protected]%3c/alert-email


28/126


Traffic Specific Features

TOS coloring supportAdd ability to color packetsso that the shaper or anothernetwork entity can follow these marks (for example: not shape these packets).

Here is an example of how to color only CACHE_OUT with 8:

0

CACHE_OUT

8

1

20

cache-out

mark-with-8

CLI-based Configuration

Configuring Passwords

To change the password required to log in to the CLI:

Enter access user-password at the enabled CLI prompt, whereis the new password for the normal user. The password is changed.

To change the password required to access Enable mode:

Enter access enable-password at the enabled CLI prompt, whereis the new password for the enabled user. The password is changed.

Recovering Passwords

Should you lose or forget the initial CLI password or Enable mode password, you can reset

them to their default values through special rescue CLI. The rescue CLI is available from serial

console only. For further information, refer toRescue CLIon page13.


29/126


Configuring Management Network

You must configure the IP address, netmask, and gateway address for the management server

in order to access the CLI using a LAN connection.

To set up IP address:

1. Enter network ipaddr at the CLI config prompt, whereis the IP address you want to use for the UltraBand 1000, and

is the netmask in xxx.xxx.xxx.xxx. notation.

2. Enter network default_gw at the CLI config prompt, where is the IP address of the desired gateway.

After performing the above steps, IP networking is set up for the management server.

To test the IP setup:

1. Enterping at the enabled CLI prompt, whereis an IPaddress on your local area network. This tests the connectivity from the UltraBand 1000 to

the entered IP address. If you cannot reach the destination, check your IP address and

netmask settings.

2. Enter traceroute at the enabled CLI prompt, whereisan IP address to which you want to trace a connection. This shows the network routing

between the management interface of UltraBand 1000 and the entered IP address. If you

cannot reach the desired destination, check your IP address and gateway address settings.

Configuring Local TimeYou configure local time on the UltraBand 1000 either manually or through the use of a

Network Time Server via NTP.

To view the time on the system:

Enter show timeat the CLI prompt.To configure local time manually:

Enter time at the configuration# CLI prompt, whereisthe new date and time (two digits each for month, date, year, hours, and minutes). The

date and time are set.

Please note that the configuration# CLI prompt requires Enabled mode privileges. For

more information, seeUltraBand 1000 CLI Commandson page32.

To configure local time using NTP:

You can configure NTP either using the CLI or using the configuration file.


30/126


Using the CLI:

1. Enter configat the enabled CLI prompt. You are now in Configuration mode.2. Enter ntp server-ip at the CLI config prompt, where

is the IP address of the NTP server.

Instead of, you can enterfor the local server.

3. Enter ntp timezone at the CLI config prompt, whereis thelocal time zone according to its GMT offset.

4. Apply configuration using apply.Using the configuration file:

Edit the following fields in the configuration file:

common ntp server-ipThe IP address of the NTP server. common ntp timezoneThe time zone according to its GMT offset.

After one of the above procedures, NTP is configured.

Managing the Caching Service

To stop, start, or restart the UltraBand 1000:

Enter oper service at the enabled CLI prompt, where: stopstops the caching service. startstarts the service after it has been stopped. restartperforms a soft restart of the caching service by stopping and restarting each

server one-by-one. This option should be used to restart caching service with minimal

impact to the transit traffic.

The caching service stops, starts, or restarts as specified.

Managing Servers

To stop, start, or reset a single server:

Enter stop, start, or restartat the CLI server prompt, where: stopstops the servers operation. startstarts the server after it has been stopped. Restartperforms a soft reload by stopping and restarting the server.


31/126


The server changes operation as specified.

Resetting Management Service

In Configuration mode, only one user can perform configuration operations at a time.

Should this user terminal get stuck, in order to recover the ability to configure the system, you

need to reset the management service.

To reset the UltraBand 1000:

Enter resetat the CLI server prompt.This will reset all active CLI sessions in the system. Please use this option with caution.

File-based Configuration

When configuring software settings in the configuration file, you can set fields in the common

section to apply to all servers, or in the specific section for an individual server. The fields in

the individual servers section override the fields in the common sectionfor that server.

Sample configuration files can be found inSample Configuration Setupson page91.

Configuring SNMP

To set up SNMP:

Edit the following fields in the configuration file: common snmp trap-ipThe IP address of the SNMP trap server. common snmp snmp-read-communityThe SNMP read community name,

for viewing network status and statistics.

common snmp snmp-write-communityThe SNMP write communityname, for executing commands on the system.

common snmp snmp-trap-communityThe SNMP trap community namefor receiving SNMP traps.

Configuring L4/L7 Switch Type

To configure L4/L7 switch type:

Edit the following field in the configuration file:


32/126


common (or server) service net switch-typeEnter either L4or L7to select the desired switching type.

Configuring P2P Protocols

To configure P2P protocols:

Edit the following field in the configuration file: common (or server) service proto enable-kazaa

Enables or disables the Kazaa protocol. 1: enabled, 0: disabled.

common (or server) service proto enable-bittorrentEnables or disables the BitTorrent protocol. 1: enabled, 0: disabled.

common (or server) service proto enable-edkEnables or disables the eDonkey protocol. 1: enabled, 0: disabled.

common (or server) service proto enable-gnutellaEnables or disables the gnutella protocol. 1: enabled, 0: disabled.

common (or server) service proto enable-aresEnables or disables the Ares protocol. 1: enabled, 0: disabled.

common (or server) service proto enable-httpEnables or disables the HTTP protocol. 1: enabled, 0: disabled.

Configuring Bandwidth Management

To configure bandwidth management:

Edit the following field in the configuration file: common (or server) service bandwidth-management

enable-bandwidth-management Enables or disables the bandwidth management

service. 1: enabled, 0: disabled.

common (or server) service bandwidth-managementbandwidth-per-connectionSets the maximum bandwidth per connection, in

bytes/second.


33/126


Configuring Traffic Forwarding Options

These options must match your network configuration, and should not be changed unless you

change gateway configuration on your network.

UltraBand 1000 supports the following traffic forwarding modes:

Table 3: Traffic Forwarding Modes

Forwarding Mode Corresponding Topology

TUNNEL Single router is on either side of L4/L7 switch.

MULTI_GW Subscribers side of the L4/L7 switch has multiple routers.

PROMISCUOUS The L4/L7 switch forwards traffic via two dedicated ports

without changing L2 addresses (as-is).

BOUNCE The platform sends packets back using the same interface

while swapping the source and destination MAC addresses.

To configure traffic forwarding options:

Edit the following field in the configuration file: common (or server) service net fwd-modeThe forwarding

mode as described above.

common (or server) service net gwIP addresses of twoedges of the tunnel, gw1 and gw2, are specified here . This configuration is used only

when TUNNEL forwarding mode is configured.

common (or server) service net default-gwIP address ofthe default gateway in data network. Please note that in TUNNEL mode either gw1 or

gw2 should be used as default gateway.

Configuring Caching Policies

The following general caching policy settings can also be set in the configuration file.

To configure caching policies:

Edit the following field in the configuration file: common (or server) service policy enable-uploader-

disconnectEnables or disables automatically disconnecting a download from the

cache if the remote peer (uploader) shuts down a connection or becomes unavailable:

1: enabled. 0: disabled.


34/126


common (or server) service policy cache-directionIndicates in which direction to enable caching:

WORLD2ISP: traffic coming into the ISP en-route to subscribers machines. ISP2WORLD: traffic from subscribers going out to the Internet.ALL: all traffic in either direction.

common (or server) service policy upload_cache_outIndicates the percentage of upstream P2P traffic that mustcome from the internal

cache:

0%: disabled (all the upstream traffic can come from local peers). 1-99%: the specified percentage of the upstream traffic must come from the

UltraBand 1000 cache storage and the remainder can come from local peers.

100%: the upstream traffic can only come from the internal cache.Configuring Server Virtual IP Address

Each individual server has a virtual IP address that must match the IP address in the L4/L7

switch. This IP is used for health monitoring, load balancing and forwarding from the L4/L7

switch.

Certain redirectors can use virtual IP addresses to query cache server health. While the

redirector receives responses on this virtual IP address, it can also redirect traffic there.

Therefore, defining a number of virtual IP addresses per server regulates the amount ofredirected traffic by dividing the traffic into manageable chunks.

The TUNNEL and MULTI_GW traffic forwarding modes can be used with these redirectors.

Specify a virtual IP address or multiple virtual addresses for these modes in each server section

of the cluster configuration file. Up to 10 different virtual IP addresses can be configured on

each server.

To set the virtual IP address for a server:

Edit the following field in the configuration file: server vipThe virtual IP address of the server.Each server can have up to 10 virtual IP addresses.

Configuring Server Data IP Address

Each individual server has a data IP address that must be in the same subnet with the

gateways.

Edit the following fields in the configuration file:


35/126


server ipaddrThe IP address of data interface of the server. server netmaskThe IP netmask of data interface of the server.

Upgrading the System

This section describes how to upgrade the UltraBand 1000 in the following cases:

New softwareYou download new software versions of the UltraBand 1000, which aredelivered as a file.

New software licenseYou download new versions of the UltraBand 1000 softwarelicense, which is delivered as a file.

Upgrading UltraBand 1000 Software

To install a new software version:

1. Enter show systemidat the CLI prompt. The system serial number is displayed.2. Send a request by email for a software upgrade along with the serial number to PeerApp.

PeerApp will send you a software upgrade file.

3. Place the new software upgrade file on your TFTP server.4. Enter upgrade at the enabled CLI prompt, where

is the IP address of your TFTP server andis the name of the new

software upgrade file.

An automatic upgrade process will start.

If the version upgrade includes changes to management service, your CLI session may be

disconnected in the end of upgrade process.

If the management service is running, it is automatically restarted after the upgrade

process is complete.

Upgrading UltraBand 1000 License

To view information about your installed license:

Enter show licenseat the CLI prompt. Information about the installed license isdisplayed, including the version number and enabled features.


36/126


To install a new software license:

1. Place the new license file on your TFTP server.2. Enter license get at the enabled CLI prompt, whereis the IP address of your TFTP server andis the name of the new license

file

3. Enter license activateto apply the license.


37/126


4

UltraBand 1000 CLI Commands

The UltraBand 1000 platform is controlled using a set of CLI commands, allowing full control

over its operational states. The CLI commands are divided into two categories:

Regular mode commandsProvides the ability to display versioning/licensing informationand to access/manipulate the system log. This mode does not support system

configuration changes.

Enable mode commandsProvides full control over the system configuration, cachecontent manipulation, networking behavior, licensing, platform operation state, and

managing the software version the system runs.

This CLI interpreter is accessible through a unique username and password. The username is

admin and the password is platform specific.

The following is a sample authentication session:

login as: adminUsing keyboard-interactive authentication.Password:PeerApp management:Cli version - 2.3.124Snmp version - PeerApp management node software version 2.3.124console>

This chapter provides a reference for all the CLI commands. Refer toCLI Referenceon page117

for a full list of available CLI commands.


38/126


Regular Mode Commands

The following commands are accessible in Regular mode. These commands are also available

in Enable mode.

Table 4: Regular Mode Commands

Command Description

arp Displays ARP table.

cache Provides access to cache operations.

direction Calculates the visible subnets on the interface.

dmesg Displays the dmesg.

dstat Displays the Report Central Processing Unit (CPU),

physical disks, network, paging and operating-system

statistics, and I/O statistics.

enable Enters Enable mode.

eventlog Provides access to event log operations.

exit Exits the current mode.

help Displays the list of Regular mode commands.

ifconfig Displays the interface(s).

iostat Displays extended I/O statistics.

jumbo Sends jumbo echo messages.

ping Sends echo messages.

show Displays run-time information.

tcpdump Dumps the traffic on the appropriate network

interface.

traceroute Displays the route used by the packet to reach its

destination.

who Displays the list of users who are currently logged in.

arp

The arpcommand displays the ARP table.

Command Parameters

None.


39/126


Sample Use

Display the ARP table.console> arpAddress HWtype HWaddress Flags Mask Iface

ce-3 ether 00:15:C5:FD:75:A0 C eth0.50ce-5 ether 00:15:C5:FD:32:89 C eth0.50ce-7 ether 00:15:C5:FD:2F:B9 C eth0.50ce-1 ether 00:15:C5:FD:75:FF C eth0.50ce-2 ether 00:15:C5:FD:7C:F8 C eth0.50ce-6 ether 00:15:C5:FD:77:BC C eth0.50192.168.3.4 ether 00:17:65:C7:10:46 C eth0ce-8 ether 00:15:C5:FD:74:DD C eth0.50ce-9 ether 00:15:C5:FD:38:E7 C eth0.5010.11.18.200 ether 00:1E:C9:D6:37:F3 C eth0.6010.11.18.202 ether 00:1E:4F:23:B9:06 C eth0.6010.11.18.201 ether 00:1E:C9:D6:9C:3D C eth0.60ce-4 ether 00:15:C5:FC:FF:0D C eth0.50console>

cache

The cachecommand provides access to the cache operations that are available in Regular

mode.

Command Parameters

hashdisplays the cache metadata using a hash ID. listdisplays cache content in one of the following modes:

displaydisplays cache content. exportexports cache content to a TFTP server, where the server name and file

location are specified as: .

The file to which the content is exported must exist, and must have write access to all.

If localhostis used as the parameter, then the file will be located

under the/tftpboot/ folder. You can only use localhostif you have root access on the

localhost server. Otherwise, you must use an external tftp server and not the caching

server.

Additional parameters for this command are available in Enable mode. Refer tocache

on page53 for a description of the Enable mode parameters.

summarydisplays CMDB statistics summary.


40/126


Sample Use

Display the cache metadata using a hash ID.console> cache hash 8486EE794FCA431669A7B504E525D151819F1C78xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

HTTP 8486EE794FCA431669A7B504E525D151819F1C78 ST:WATCHED HITS:4 IPS:1 VL:9SZ:10491894 MP:0 FF:yes FS:1221182430 LS:1221399563 CO:10 MB FF:100.00PFF:0.00 checksum 2184D853EED84F9B752C8A70D31E602B2C82B4DAHits: 4First seen: Fri Sep 12 04:20:30 2008Last access: Sun Sep 14 16:39:23 2008Volume id: 9Cached File size: 10491894Max piece: 0Full File: yesFull File Size: 10491894BT_last_start: 0BT_last_end: 10491894

max known bt piece size 0cache out in MB 10File fill factor 100.00total full pieces 0 (0.00)HTTP checksum is 2184D853EED84F9B752C8A70D31E602B2C82B4DA

piece bit mask 0x20RANGES -------------- RANGES0 00000000[00000000] 10491894[10491894](END)

Display cache content.console> cache list displayHASH PROTOCOL SIZE AGE77AF15685AD9D74912F62B8DE0E6DF7E210EF763 HTTP 10145830 8040E590F65C21581564842CCBAA21762739407D3 HTTP 10536367 89D76BF54B923A5F56496160481247F9188924E7C2 HTTP 10592621 125F7A7BF126D70F109DD6FB8A65F7AF305B5B8C53 HTTP 10493439 11C98700E8AF5F86AD5C9820626FA19459121860DD HTTP 10631808 114AB73FDBCF01795C683F2DD14DA2D2DA71C73BF8 HTTP 10383044 1114E757C83703F829A04E226F5946D1FC67652E5F HTTP 10631280 89DAF5A753A66B0905B90A8E8461CF26D7F5E9A5B8 HTTP 10554929 10

Export cache content to a file on a TFTP server.console> cache list export 192.168.77.14 cache-listconsole>

Display CMDB statistics summary.Console> cache summaryhashes counter is 821461Version Verify success**********************************************#########################################################Total size in DB: EDK 0 bytes [0.00 MB] [0.00 GB]Total size in DB: BTR 0 bytes [0.00 MB] [0.00 GB]Total size in DB: PANDO 0 bytes [0.00 MB] [0.00 GB]Total size in DB: GNUTL 0 bytes [0.00 MB] [0.00 GB]Total size in DB: ARES 0 bytes [0.00 MB] [0.00 GB]Total size in DB: HTTP 8484469097815 bytes [8091420.27 MB] [7901.78 GB]Total size in DB: KAZ 0 bytes [0.00 MB] [0.00 GB]


41/126


#########################################################EDK: Number of total hashes 0 Number of files 0BTR: Number of total hashes 0 Number of files 0PANDO: Number of total hashes 0 Number of files 0GNUTL: Number of total hashes 0 Number of files 0ARES: Number of total hashes 0 Number of files 0HTTP: Number of total hashes 821460 Number of files 821460

KAZ: Number of total hashes 0 Number of files 0#########################################################Avarage file size in storage HTTP: 10328523.72 bytes [9.85 MB]#########################################################Full file size in cmdb: EDK 0Full file size in cmdb: BTR 0Full file size in cmdb: PANDO 0Full file size in cmdb: GNUTL 0Full file size in cmdb: ARES 0Full file size in cmdb: HTTP 798356Full file size in cmdb: KAZ 0#########################################################EDK average age of: hashes none stored files noneBTR average age of: hashes none stored files none

PANDO average age of: hashes none stored files noneGNUT average age of: hashes none stored files noneARES average age of: hashes none stored files noneHTTP average age of: hashes 369844 stored files 369844KAZ average age of: hashes none stored files none#########################################################BTR: Max piece 0 average pieces per file none#########################################################Console>

direction

The directioncommand calculates the visible subnets on the specified interface.

Command Parameters

interface namethe interface for which to display the subnets.Sample Use

Display the visible subnets on the interface eth0.console> direction eth0tcpdump: WARNING: eth0: no IPv4 address assignedtcpdump: verbose output suppressed, use -v or -vv for full protocol decodelistening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes10 packets captured24 packets received by filter0 packets dropped by kernel/opt/pang/bin/check_direction.sh: line 7: [: =: unary operator expectedtcpdump: WARNING: eth0: no IPv4 address assignedtcpdump: verbose output suppressed, use -v or -vv for full protocol decodelistening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes1000 packets captured2001 packets received by filter0 packets dropped by kernel

6 00:14:22:6e:32:33


42/126


959 00:14:22:b1:a0:b44 00:17:65:c7:10:01

31 00:17:65:c7:10:46console>

dmesg

The dmesgcommand displays the message buffer of the kernel (dmesg).

Command Parameters

None.

Sample Use

Display the dmesg.console> dmesge1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, FlowControl: RX/TXip_tables: (C) 2000-2006 Netfilter Core Team802.1Q VLAN Support v1.8 Ben Greear All bugs added by David S. Miller eth0.50: add 01:00:5e:00:00:01 mcast address to master interfaceeth0.60: add 01:00:5e:00:00:01 mcast address to master interfaceLoading iSCSI transport class v2.0-724.iscsi: registered transport (tcp)IA-32 Microcode Update Driver: v1.14a e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, FlowControl: RX/TXInstalling knfsd (copyright (C) 1996 [email protected]).NET: Registered protocol family 10lo: Disabled Privacy Extensionseth0.50: add 33:33:00:00:00:01 mcast address to master interfaceeth0.50: add 33:33:ff:b1:a0:b4 mcast address to master interfaceeth0.60: add 33:33:00:00:00:01 mcast address to master interfaceeth0.60: add 33:33:ff:b1:a0:b4 mcast address to master interfaceMobile IPv6NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directoryNFSD: starting 90-second grace periodiscsi: registered transport (iser)eth0.60: no IPv6 routers presenteth0: no IPv6 routers present

eth0.50: no IPv6 routers presenteth1: no IPv6 routers presente1000: eth1: e1000_watchdog_task: NIC Link is Downe1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, FlowControl: NoneNET: Registered protocol family 17device eth1 entered promiscuous modeaudit(1220975346.793:2): dev=eth1 prom=256 old_prom=0 auid=4294967295device eth1 left promiscuous modeaudit(1220975347.669:3): dev=eth1 prom=0 old_prom=256 auid=4294967295device eth0 entered promiscuous modeaudit(1220975351.138:4): dev=eth0 prom=256 old_prom=0 auid=4294967295device eth0 left promiscuous modeaudit(1220975353.134:5): dev=eth0 prom=0 old_prom=256 auid=4294967295ip6_tables: (C) 2000-2006 Netfilter Core Team


43/126


Netfilter messages via NETLINK v0.30.nf_conntrack version 0.5.0 (2047 buckets, 16376 max)monitor[4050]: segfault at 0000000000002336 rip 0000000000002336 rsp00000000407e4088 error 14monitor[19592]: segfault at 0000000000002336 rip 0000000000002336 rsp00000000407e4088 error 14monitor[13295]: segfault at 0000000000002336 rip 0000000000002336 rsp

00000000407e4088 error 14monitor[6335]: segfault at 0000000000002336 rip 0000000000002336 rsp00000000407e4088 error 14device eth1 entered promiscuous modeaudit(1222071719.088:6): dev=eth1 prom=256 old_prom=0 auid=4294967295device eth1 left promiscuous modeaudit(1222071730.929:7): dev=eth1 prom=0 old_prom=256 auid=4294967295device eth1 entered promiscuous modeaudit(1222071730.949:8): dev=eth1 prom=256 old_prom=0 auid=4294967295device eth1 left promiscuous modeaudit(1222071863.612:9): dev=eth1 prom=0 old_prom=256 auid=4294967295device eth0 entered promiscuous modeaudit(1222071878.921:10): dev=eth0 prom=256 old_prom=0 auid=4294967295device eth0 left promiscuous mode

audit(1222071878.945:11): dev=eth0 prom=0 old_prom=256 auid=4294967295device eth0 entered promiscuous modeaudit(1222071878.965:12): dev=eth0 prom=256 old_prom=0 auid=4294967295device eth0 left promiscuous modeaudit(1222071890.950:13): dev=eth0 prom=0 old_prom=256 auid=4294967295(END)

dstat

The dstatcommand displays a report of the Central Processing Unit (CPU), physical disks,

network, paging and operating-system statistics, and I/O statistics.

Command Parameters

[-N ] []

Where:

ethxa physical Ethernet interface on the server that runs the dstat command (i.e., themanagement server). For example: eth0, eth1, or eth2.

totalthe accumulated traffic on all Ethernet interfaces on the server. countthe number of updates to display before exiting. If omitted, the output will

continue to display until stopped with .

Sample Use

Display the accumulated traffic on all Ethernet interfaces on the server.console> dstat -N total----total-cpu-usage---- -dsk/total- -net/total- ---paging-- ---system--usr sys idl wai hiq siq| read writ| recv send| in out | int csw10 3 86 1 0 1|5431B 253k| 0 0 | 15B 27B|1917 3308


44/126


0 0 99 1 0 0| 0 95k| 22k 11k| 0 0 | 430 10340 0 100 0 0 0| 0 6827B| 20k 9447B| 0 0 | 400 11552 0 97 1 0 0| 0 20k| 22k 10k| 0 0 | 418 12100 0 99 0 0 0| 0 17k| 20k 9526B| 0 0 | 402 12310 0 100 0 0 0| 0 0 | 21k 10k| 0 0 | 418 12465 4 90 1 0 0| 0 44k| 20k 9435B| 0 0 | 422 14380 0 100 0 0 0| 0 0 | 20k 9703B| 0 0 | 403 1096

0 0 99 1 0 0| 0 61k| 21k 9853B| 0 0 | 416 10650 0 99 0 0 0| 0 56k| 22k 10k| 0 0 | 428 10715 2 92 0 0 1| 0 0 | 182k 182k| 0 0 |2254 481169 15 13 2 0 1| 249k 231k| 28k 16k| 0 0 | 534 176250 14 5 30 0 0|2769k 855k| 27k 17k| 0 0 |1197 278530 9 38 22 0 0|7723k 568k| 28k 16k| 0 0 | 756 37620 0 99 0 0 0| 0 43k| 26k 14k| 0 0 | 446 13021 1 96 2 0 0|2731B 1392k| 25k 13k| 0 0 | 457 12403 0 97 0 0 0| 0 0 | 27k 15k| 0 0 | 450 11581 0 97 1 0 0| 0 176k| 25k 14k| 0 0 | 449 10870 0 99 0 0 0| 0 0 | 24k 14k| 0 0 | 428 11562 0 98 0 0 0| 0 99k| 25k 14k| 0 0 | 453 13157 1 91 0 0 1| 0 0 | 185k 185k| 0 0 |2251 4863

console>

enable

The Enable command enables you to switch to Enable mode. Enable mode provides access to

CLI commands which enables you to make configuration changes. These configuration changes

include cache content manipulation, networking behavior, licensing, and managing the

software version the system runs.

Command Parameters

None.

The user is prompted for a password.

The default password for the enable command is configured when the system is

installed and defaults to the system-id. You can view the system-idby using the show

systemidcommand. It is strongly recommended to change the default enable

command password immediately after the initial installation.

Sample Use

Switch to Enable mode.console> enablePassword:console#


45/126


eventlog

The eventlogcommand enables the user to view or export the content of the event log. The

event log lists all log messages sent to the system log by all the UltraBand service components

(applications, CLI and SNMP).

Command Parameters

exportexports event log content to a TFTP server, where the server name and filelocation are specified as: .

The file to which the content is exported must exist, and must have write access to all.

showdisplays the event log entries.Additional parameters for this command are available in Enable mode. Refer to

eventlogon page63 for a description of the Enable mode parameters.

taildisplays the online event log entries.Sample Use

Export event log content to a file on a TFTP server.console> eventlog export 192.168.77.14 eventlog-exportedconsole>

Display event log content.console> eventlog showMay 21 10:22:21 ce-1 pang[1787]: stored byte count 16214342008, found bytecount 16214342008May 21 10:22:21 ce-1 pang[1787]: CMDB verifiedMay 21 10:22:22 ce-1 pang[1787]: Operational state has been set to enabledMay 21 10:22:22 ce-1 pang[1787]: Device state has been set to startedMay 21 10:22:22 ce-1 pang[1787]: PANG startedMay 21 10:22:25 ce-1 pang[1787]: all interfaces (1) are down , will go todisable mode

May 21 10:22:25 ce-1 pang[1787]: Operational state has been set to disabledMay 21 10:22:25 ce-1 pang[1787]: detected major: operational mode has beenchangedMay 21 10:23:41 ce-1 pang_cli[3341]: Enter enable mode.../var/log/peerapp/peerapp_system2008.05.21.log (END)

Display event log online entries.console> eventlog tailSep 22 13:19:34 ce-9 logger: snmpd Cache synchronization The list of orphanedfs files is in fs_diff.4353


46/126


Sep 22 13:19:52 ce-9 logger: snmpd Cache synchronization finished .Sep 22 13:21:17 ce-4 pang[27529]: volume stat availability

owner total free used usageSep 22 13:21:17 ce-4 pang[27529]: /mnt/vol7 mounted active

ce-4 364 28 336 92.30Sep 22 13:21:17 ce-4 pang[27529]: /mnt/vol17 mounted_cmdb active

ce-4 271 22 249 91.75

Sep 22 13:21:17 ce-4 pang[27529]: /mnt/vol20 mounted activece-4 364 31 333 91.47

Sep 22 13:25:10 ce-1 pang[5949]: volume state availabilityowner total free used usage

Sep 22 13:25:10 ce-1 pang[5949]: /mnt/vol25 mounted_cmdb activece-1 271 29 242 89.28



exit

The exitcommand exits the current CLI session and mode. If in Enable mode, the exit

command returns the session to Regularmode. If already in Regularmode, the session

terminates and the user is logged out of the current session.

Command Parameters

None.

Sample Use

Exit the current CLI session.console> exit>

help

The helpcommand displays the CLI commands with a short description for the current mode.

In other words, if the user is in Regular mode, then the help command displays the Regularmode commands with a short description of each command.

The helpcommand can also be accessed by typing + ?. The ? is not echoed on the

screen.

Command Parameters

None.


47/126


Sample Use

Display the list of CLI commands that are available in Regular mode.console> helpapache_restart Restart apapche

arp Show arp tablecache Cache operationsdirection Calculate seen subnets on interfacedmesg Display dmesgdstat Display a report of the Central Processing Unit (CPU),

physical disks, network paging and operating systemstatistics and I/O statistics

enable Enter privileged modeeventlog Event log commandsexit Exit current modehelp Commands descriptionifconfig Display interface(s)iostat Display IO statisticsjumbo Send jumbo echo messages

ping Send echo messagesshow Show run-time informationtcpdump Dump traffic on appropriate network interfacetraceroute Discover the route to destinationwho Show currently logged users

ifconfig

The ifconfigcommand displays details of the interface(s).

Command Parameters

None.

Sample Use

Display the interface details.console> ifconfigeth0 Link encap:Ethernet HWaddr 00:14:22:B1:A0:B4

inet6 addr: fe80::214:22ff:feb1:a0b4/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1463990287 errors:3758 dropped:0 overruns:0 frame:3758TX packets:675895448 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:4000RX bytes:302621863774 (288602.6 Mb) TX bytes:58113731670 (55421.5 Mb)

eth0.50 Link encap:Ethernet HWaddr 00:14:22:B1:A0:B4inet addr:10.11.12.1 Bcast:10.11.12.255 Mask:255.255.255.0inet6 addr: fe80::214:22ff:feb1:a0b4/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:1447835692 errors:0 dropped:0 overruns:0 frame:0TX packets:659332108 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0RX bytes:275154029204 (262407.3 Mb) TX bytes:54568703151 (52040.7 Mb)

eth0.60 Link encap:Ethernet HWaddr 00:14:22:B1:A0:B4


48/126


inet addr:10.11.18.1 Bcast:10.11.18.255 Mask:255.255.255.0inet6 addr: fe80::214:22ff:feb1:a0b4/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:10524402 errors:0 dropped:0 overruns:0 frame:0TX packets:10319345 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0RX bytes:5678122056 (5415.0 Mb) TX bytes:771163658 (735.4 Mb)

eth0:1 Link encap:Ethernet HWaddr 00:14:22:B1:A0:B4inet addr:192.168.3.170 Bcast:192.168.3.255 Mask:255.255.255.0UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth1 Link encap:Ethernet HWaddr 00:14:22:B1:A0:B5inet6 addr: fe80::214:22ff:feb1:a0b5/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:38002 errors:0 dropped:0 overruns:0 frame:0TX packets:6 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:4000RX bytes:2280120 (2.1 Mb) TX bytes:468 (468.0 b)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0inet6 addr: ::1/128 Scope:HostUP LOOPBACK RUNNING MTU:16436 Metric:1RX packets:652978316 errors:0 dropped:0 overruns:0 frame:0TX packets:652978316 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0RX bytes:68844152406 (65654.8 Mb) TX bytes:68844152406 (65654.8 Mb

peerapp ultraband 1000 administration guide - grid configuration

Documents