Manuale d’uso / di manutenzione del prodotto HP-UX 11i v2 del fabbricante HP (Hewlett-Packard)
Vai alla pagina of 113
HP-UX Routing Services Administrator’ s Guide HP-UX 11i v2 Edition 1 Manufacturing P art Number: B2355-90777 August 2003 U .S .A. © Copyright 2003 Hewlett-P ackard Development Company L.
2 Legal Notices The information in this document is subject to change without notice. Hewlett-P ackard makes no warranty of any kind with regard to this manual, including , but not limited to , the implied warranties of merchantability and fitness f or a particular purpose.
3 © Copyright 1989-93 The Open Software F oundation, Inc . © Copyright 1986 Digital Equipment Corporation. © Copyright 1990 Motorola, Inc. © Copyright 1990, 1991, 1992 Cornell University © Copyri.
4.
Contents 5 About This Document 1. Overview The mrouted Routing Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Multicasting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6 D: Major Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 E: Major Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 7 Tracing gated Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Operational User Interface for gated – gdc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 The gated Routing T able .
Contents 8.
9 About This Document This manual describes the various routing daemons supported in the HP-UX 11i v2 operating system.It is one of the five new manuals documenting the Internet Services suite of products. See “Related Documentation” on page 11 for a list of the other new Internet Services manuals .
10 Publishing History T able 2 provides , for a particular document, the manufacturing part number , the respective operating systems, and the publication date . What Is in This Document HP-UX Routing Services Administrator’s Guide is divided into chapters , each of which contain information about configuring the routing services .
11 Related Documentation F or more information about the Internet Services suite of products , see the following books: • HP-UX Internet Services Administrator’s Guide Provides an overview of the Internet Services products and describes how to install and configure them on your HP-UX 11i v2 operating system.
12 Many sections of this manual refer to RFCs for more information about certain networking topics . These documents publicize Internet standards , new research concepts , and status memos about the Internet.
13 a hot link to the manpage itself . From the HP-UX command line, you can enter “ man audit ” or “ man 5 audit ” to view the manpage. See man (1). Book Title The title of a book. On the W eb and on the Instant Information CD , it may be a hot link to the book itself .
14 • The version of HP-UX that you are using..
Chapter 1 15 1 Overview A router is a device that has multiple network interfaces and that transfers Internet Protocol (IP) packets from one network or subnet to another within an internetwork. In many IP-related documents, this device is also referred to as a gatewa y .
Overview Chapter 1 16 manual. The router stores all the routing information in the form of a routing table. Routing tables contain the routes to reach a particular network, and also identify the router to which the datagram packet can be passed for this purpose.
Overview The mrouted Routing Daemon Chapter 1 17 The mrouted Routing Daemon mrouted (pronounced “M route D”) is a routing daemon that forwards IP multicast datagrams, within an autonomous network, through routers that support IP multicast addressing.
Overview The mrouted Routing Daemon Chapter 1 18 of the multicast datagrams. Y ou can achieve this by using topological knowledge of the network to implement a multicast forwarding algorithm called Truncated Reverse P ath Broadcasting (TRPB).
Overview The mrouted Routing Daemon Chapter 1 19 In this figure, the mrouted router R1 receives a multicast packet from node M. Because R1 is configured as one end of a tunnel, R1 encapsulates the IP multicast packet in a standard unicast IP packet addressed to the mrouted router R2.
Overview The mrouted Routing Daemon Chapter 1 20 Normally , IP multicast addresses are mapped to 802.3 or Ethernet multicast addresses. The IP multicasting addressing sc heme, similar to Ethernet’ s scheme, uses the datagram’s destination address to indicate multicast delivery .
Overview The mrouted Routing Daemon Chapter 1 21 also defines IGMP message types that enable hosts to join and leave multicast groups, and that allow multicast routers to query one another for routing information.
Overview The gated Routing Daemon Chapter 1 22 The gated Routing Daemon gated (pronounced “gate D”) is a routing daemon that updates routing tables in internetwork routers.
Overview The gated Routing Daemon Chapter 1 23 • gated translates among several protocols, passing information within or between IP routing domains or autonomous systems.
Overview The gated Routing Daemon Chapter 1 24 Routing Protocols F or routing purposes , networks and gateways are logically grouped into autonomous system (AS). Companies and organizations that want to connect to the Internet and form an AS must obtain a unique AS number from the Internet Assigned Numbers Authority (IANA).
Overview The gated Routing Daemon Chapter 1 25 • HELLO is designed to work with routers called Fuzzballs. Most installations use RIP or OSPF instead of HELLO . The HELLO protocol is no longer supported on HP-UX. Y ou can use RIP or OSPF instead, because they are internal routing protocols.
Overview The gated Routing Daemon Chapter 1 26 gated supports the following exterior gatewa y protocols: • The External Gatewa y Protocol (EGP) permits a node on the NSFNET backbone to exchange information with other backbone nodes about reaching a destination.
Overview The gated Routing Daemon Chapter 1 27 packets . It is used instead of, or in addition to , a statically configured default router . Router discovery consists of two parts: a server part that runs on routers , and a client part that runs on hosts .
Overview The gated Routing Daemon Chapter 1 28.
Chapter 2 29 2 Configuring mrouted This chapter describes how to configure mrouted and the various configuration commands in mrouted . It also provides information on starting and verifying the mrouted installation.
Configuring mrouted Chapter 2 30 routing support tools. This chapter discusses the following topics: • “How to Configure mrouted” on page 31 • “Starting mrouted” on page 36 • “V erif.
Configuring mrouted How to Configure mr outed Chapter 2 31 How to Configure mrouted When the mrouted daemon starts , it automatically reads the default configuration file /etc/mrouted.conf . Y ou can override the default configuration file by specifying an alternate file while invoking mrouted .
Configuring mrouted How to Configure mr outed Chapter 2 32 Y ou can use the phyint command to disable multicast routing on the physical interface identified by the local IP address, local-addr (see Figure 2-1), or to associate a nondefault metric or threshold with the specified physical interface.
Configuring mrouted How to Configure mr outed Chapter 2 33 NO TE A phyint command must precede a tunnel command. All the phyint and tunnel command options must be placed on a single line except for the boundary and altnet options , which can begin on a separate line.
Configuring mrouted How to Configure mr outed Chapter 2 34 The TTL value of forwarded packets is only compared with the threshold value; it is not decremented by the threshold .
Configuring mrouted How to Configure mr outed Chapter 2 35 those leaf subnets do not contain members of the multicast destination group. Use only nonpruning mode for testing.
Configuring mrouted Starting mrouted Chapter 2 36 Starting mrouted Y ou can start mrouted from the HP-UX prompt or from within a shell script by issuing the following command: /etc/mrouted [-p] [-c config_file ] [-d debug_level ] The -p option disables pruning by overriding the pruning on statement within the /etc/mrouted.
Configuring mrouted V erifying mrouted Operation Chapter 2 37 V erifying mrouted Operation Y ou can use one or more of the following methods to verify mrouted operation: • Retrieve the virtual interface table and the multicast routing table to verify if appropriate virtual interfaces (vifs) are configured.
Configuring mrouted Displaying mr outed Routing T ables Chapter 2 38 Displaying mrouted Routing T ables mrouted contains three routing tables: the virtual interface table , the multicast routing table , and the multicast routing cache table.
Configuring mrouted Displaying mr outed Routing T ables Chapter 2 39 The multicast routing table displays connectivity information for each subnet from which a multicast datagram can originate. The multicast routing cache table is a duplicate copy of the kernel forwarding cache table.
Configuring mrouted Displaying mr outed Routing T ables Chapter 2 40 F or more information on signals , type man 1M mrouted at the HP-UX command prompt, and see the Signals section.
Configuring mrouted Multicast Routing Support T ools Chapter 2 41 Multicast Routing Support T ools This section describes various multicast routing support tools. The mrinfo T ool mrinfo is a multicast routing tool that requests configuration information from mrouted and prints the information to the standard output.
Configuring mrouted Multicast Routing Support T ools Chapter 2 42.
Chapter 3 43 3 Configuring gated gated handles multiple routing protocols. Y ou can configure the gated daemon to perform all or any combination of the supported protocols.
Configuring gated Chapter 3 44 The HP-UX 11i v2 operating system supports gated 3.5.9. This chapter contains information about how to configure gated on various routing protocols . It also describes how to specify the tracing options and route preference in gated , and discusses certain troubleshooting measures .
Configuring gated Configuration Overview Chapter 3 45 Configuration Overview Upon startup, gated reads the configuration file to decide how each protocol must be used to manage routing. By default, it uses the configuration file named /etc/gated.
Configuring gated Configuration Overview Chapter 3 46 If you do not want to use any of the gated 3.5.9 features added at HP-UX 10.30, and do not have any tracing configured in your gated 3.0 /etc/gated.conf configuration file, you can continue to use your 3.
Configuring gated Configuration Overview Chapter 3 47 3. Add statements for any additional configuration information. See “Customizing Routes” on page 90, “Specifying Tracing Options” on page 92, and “Specifying Route Preference” on page 94 for other configuration options.
Configuring gated Configuration Overview Chapter 3 48 NO TE Y ou can also use the command gdc checkconf to parse the /etc/gated.conf file for syntax errors. gdc issues a message to indicate the parsing errors. If there are any errors , the error output is saved to a file for further inspection.
Configuring gated Configuration Overview Chapter 3 49 1. Retain a copy of the gated 3.0 configuration file, because you cannot specify the same file for input and output while running the conv_config conversion tool. F or example, if you are using /etc/gated.
Configuring gated Configuring the RIP Protocol Chapter 3 50 Configuring the RIP Protocol RIP uses hopcount to determine the shortest path to a destination. Hopcount is the number of routers a packet must pass through to reach its destination. If a path is directly connected, it has the lowest hopcount of 1.
Configuring gated Configuring the RIP Protocol Chapter 3 51 trustedgateways router_list ; sourcegateways router_list ; traceoptions traceoptions ; }]; Curly braces ({}) are part of the syntax for the RIP protocol statement. Square brackets ([]) are not part of the syntax; they are used here to indicate optional parameters.
Configuring gated Configuring the RIP Protocol Chapter 3 52 Range: 1 – 16 • query authentication [none|[[simple|md5] password ]] specifies the authentication, if any , that is required for query packets that do not originate from routers. If authentication consisting of only a password is required, specify simple password or password .
Configuring gated Configuring the RIP Protocol Chapter 3 53 • [secondary] authentication [none|[simple|md5] password ] specifies the type of authentication for RIP V ersion 2 pac kets (it is ignored for V ersion 1 packets). secondary indicates that the secondary authentication is defined; otherwise, the primary authentication is defined.
Configuring gated Configuring the RIP Protocol Chapter 3 54 Simple RIP Configuration A simple RIP configuration consists of RIP routers and end nodes that listen to information exchanged by the RIP routers , as shown in Figure 3-1.
Configuring gated Configuring the RIP Protocol Chapter 3 55 With one interface , A can listen to RIP traffic on the network but does not forward routing information. Routers must be multicasting RIP packets on this network for A to learn about them and update its routing table.
Configuring gated Configuring the RIP Protocol Chapter 3 56 Figure 3-2 Example of Large RIP Network A: Cluster Node (or Isolated Node) Y ou need not run gated at this node, because it is on a LAN with only one router . Set a static default route to the cluster server (B) in the /etc/rc.
Configuring gated Configuring the RIP Protocol Chapter 3 57 B: Cluster (or Root) Server Node Run gated to get routing information about the 121.0.0.0 network. Set up /etc/gated.conf as follows: interfaces { interface 130.15.0.6 121.1.0.92 passive ; }; rip yes { interface 130.
Configuring gated Configuring the RIP Protocol Chapter 3 58 rip yes { interface 121.1.0.10 version 2 multicast; }; static { default interface 121.1.0.10 preference 255 ; }; With one interface , C can listen to RIP traffic on the network but does not forward routing information.
Configuring gated Configuring the RIP Protocol Chapter 3 59 The options for limiting RIP routing information imported by gated in the RIP protocol definition in the /etc/gated.conf file are as follows: • The noripin clause in the interface definition informs gated not to process RIP information received through the listed interfaces.
Configuring gated Configuring the OSPF Protocol Chapter 3 60 Configuring the OSPF Protocol Open Shortest P ath First (OSPF) is a link-state routing protocol that distributes routing information between routers in a single autonomous system (AS). Each OSPF router transmits a packet with a description of its local links to all other OSPF routers .
Configuring gated Configuring the OSPF Protocol Chapter 3 61 Figure 3-3 Areas Defined in an Autonomous System Internal routers have all their directly connected networks in the same area. In Figure 3-3, routers A, B , and H are internal routers. Routers that are connected to multiple areas are called area border routers .
Configuring gated Configuring the OSPF Protocol Chapter 3 62 Multi-access networks (networks that can be accessed through two or more neighbor routers) must have one of the routers identified as a designated router. Designated routers initiate OSPF protocol functions on behalf of the network.
Configuring gated Configuring the OSPF Protocol Chapter 3 63 it is not required that an AS boundary router be a backbone router . An AS boundary router learns about routes other than its attached AS through exchanges with other routing protocols or through configuration information.
Configuring gated Configuring the OSPF Protocol Chapter 3 64 6. F or multi-access networks, identify a designated router . F or NBMA networks , several routers can be designated router candidates. Designated routers are specified in the interface definitions (see “The interface Statement” on page 67).
Configuring gated Configuring the OSPF Protocol Chapter 3 65 The following sections explain other statements defined for the OSPF protocol configuration. Defining Areas Each OSPF router is associated with one or more areas . The area statement identifies an OSPF area.
Configuring gated Configuring the OSPF Protocol Chapter 3 66 Y ou can define various characteristics for an area and interfaces . The following sections describe the configuration statements that you can use in defining an area. The networks Statement The networks statement defines the address ranges that forms an OSPF area.
Configuring gated Configuring the OSPF Protocol Chapter 3 67 The following is an example of the network definition in the Router A ’ s /etc/gated.conf file: ospf yes area 0.0.0.1 networks { 193.2.1.16 mask 0xfffffff0 ; 193.2.1.32 mask 0xfffffff0 ; }; interface 193.
Configuring gated Configuring the OSPF Protocol Chapter 3 68 • A point-to-point network is a network that joins a single pair of routers. An example of a point-to-point network is a 56-KB serial line. The following sections describe each type of interface.
Configuring gated Configuring the OSPF Protocol Chapter 3 69 Default: None (you must specify a value) Range: Integer between 0 – 255 NO TE The hellointerval value must be the same for all OSPF routers.
Configuring gated Configuring the OSPF Protocol Chapter 3 70 Figure 3-6 shows an example of a router that is connected to a multicast network through the interface 193.2.1.35. Figure 3-6 Multicast Router Interface Example The following is an example of the multicast interface definition in the router’ s /etc/gated.
Configuring gated Configuring the OSPF Protocol Chapter 3 71 specified by the routerdeadinterval definition). The value of pollinterval must be larger than the value of hellointerval .
Configuring gated Configuring the OSPF Protocol Chapter 3 72 interface 193.2.1.35 nonbroadcast cost 5 { routers { 193.2.1.33 eligible ; 193.2.1.46 eligible ; }; priority 15 ; hellointerval 5 ; route.
Configuring gated Configuring the OSPF Protocol Chapter 3 73 • routerdeadinterval specifies the time interval (in seconds) for which the Hello packets are not received from a router before it is considered down or inactive by its neighbors. This value must be a multiple of the hellointerval value.
Configuring gated Configuring the OSPF Protocol Chapter 3 74 Figure 3-8 shows an example of a router (A) that is connected to a non-broadcast, point-to-point network through interface 193.2.1.1. Figure 3-8 P oint-to-P oint Router Interface Example The following is an example of the interface definition in router A ’ s /etc/gated.
Configuring gated Configuring the OSPF Protocol Chapter 3 75 Figure 3-9 shows an example of an area border router that is connected to area 0.0.0.2 through interface 193.
Configuring gated Configuring the OSPF Protocol Chapter 3 76 Defining Backbones The OSPF backbone distributes routing information between areas . Y ou can define backbones with the same statements and clauses as areas . Y ou need not define the stub statement for a backbone .
Configuring gated Configuring the OSPF Protocol Chapter 3 77 backbone { interface 15.13.115.156 { enable ; transitdelay 20 ; priority 20 ; hellointerval 30 ; routerdeadinterval 120 ; retransmitinter.
Configuring gated Configuring the OSPF Protocol Chapter 3 78 configured on a per -interface basis. If a router has interfaces to more than one network, different passwords can be configured.
Configuring gated Configuring the OSPF Protocol Chapter 3 79 retransmitinterval 10 ; pollinterval 20 ; authkey " travis " ; }; }; Cost The outbound side of each router interface is associated with a configurable cost. Lower cost interfaces are more likely to be used in forwarding data traffic .
Configuring gated Configuring the OSPF Protocol Chapter 3 80 In Figure 3-12, there are two possible packet routes between nodes A and D: one route goes through node B and the other route goes through node C .
Configuring gated Configuring the OSPF Protocol Chapter 3 81 gated supports the use of route information from other autonomous systems that use other routing protocols, suc h as EGP . AS boundary routers send AS external link advertisements and flood the AS with advertisements (with the exception of configured stub areas).
Configuring gated Configuring the OSPF Protocol Chapter 3 82 value can be an unsigned 31-bit number . Y ou can also specify tag as as_tag , where as_tag is an unsigned 12-bit number that is automatically assigned. • type determines how ASE routes imported into OSPF are treated.
Configuring gated Configuring the OSPF Protocol Chapter 3 83 Sample OSPF Configuration Figure 3-13 shows an example of two areas . Area 1 is a non-stub area, while area 2 is configured as a stub area. Node B is an area border router between the two areas.
Configuring gated Configuring the OSPF Protocol Chapter 3 84 # Router A Configuration (non-stub area) OSPF yes { area 0.0.0.1 { interface 193.2.1.35 cost 5 { priority 5 ; enable ; hellointerval 5 ; routerdeadinterval 20 ; retransmitinterval 10 ; }; }; }; The configuration for the internal router A is for a multicast interface.
Configuring gated Configuring the OSPF Protocol Chapter 3 85 }; area 0.0.0.1 { interface 193.2.1.33 cost 5 { priority 15 ; enable ; hellointerval 5 ; routerdeadinterval 20 ; retransmitinterval 10 ; }; }; area 0.
Configuring gated Configuring the OSPF Protocol Chapter 3 86 The routing table on node A contains routes to 193.2.1.32 and 193.2.1.16. The routing table on node C in the stub area contains routes only to LAN 1 and a default router .
Configuring gated Configuring RDP Chapter 3 87 Configuring RDP Y ou can use Router Discovery Protocol (RDP), a standard protocol, to inform hosts of the presence of routers to which they can send packets . Y ou can also use RDP instead of host wiretapping routing protocols (for example, RIP).
Configuring gated Configuring RDP Chapter 3 88 configured on the physical interface. If advertisements are sent to a net or subnet broadcast, only that network’ s or subnet’s address is included in the advertisement.
Configuring gated Configuring RDP Chapter 3 89 The host also deletes any routes learned from ICMP redirect s pointing to the invalid addresses. Also , if a router advertisement is not received befor.
Configuring gated Customizing Routes Chapter 3 90 Customizing Routes gated maintains the routing table in user space, and synchronizes this table with the kernel routing table. This section describes statements for setting up customized routes in the Static class of the gated configuration file, /etc/gated.
Configuring gated Customizing Routes Chapter 3 91 Setting Interface States gated times out routes that pass through interfaces not receiving any RIP , OSPF , or BGP packets .
Configuring gated Specifying T racing Options Chapter 3 92 Specifying T racing Options Trace options specify the desired level of tracing output from gated . Tracing output provides useful system information for setting up a node on the network. Use trace options to set up a node and to send a certain type of tracing to a log file.
Configuring gated Specifying T racing Options Chapter 3 93 Some of the options specified in T able 3-2 do not apply to all of the protocols . F or more information on options applicable for each protocol and for the different trace options available within the configuration file , type man 4 gated.
Configuring gated Specifying Route Preference Chapter 3 94 Specifying Route Preference gated maintains a routing table that consists of the route information learned from OSPF and from other active routing protocols, suc h as RIP or EGP . Y ou can also configure static routes in the /etc/gated.
Configuring gated Specifying Route Preference Chapter 3 95 Y ou can define preference in the /etc/gated.conf file configuration file in the following instances: • In the static route definition in the Static class . This preference definition sets the preference for static routes.
Configuring gated Specifying Route Preference Chapter 3 96 • In a defaults statement in the OSPF protocol configuration. This preference definition specifies the preference value of ASE routes that are imported into OSPF . See “ AS External Routes (AS Boundary Routers Only)” on page 80 for more information.
Configuring gated Importing and Expor ting Routes Chapter 3 97 Importing and Exporting Routes Y ou can propagate routes from one routing protocol to another using the import and export control statements . Routes are imported into a gated forwarding table and exported out to the routing protocols .
Configuring gated Importing and Expor ting Routes Chapter 3 98 Examples of import and export Statements The following import statement imports a BGP route for network 195.1.1 to the gated forwarding table with a preference of 15: import proto bgp as 1 { 195.
Configuring gated Starting gated Chapter 3 99 Starting gated T o start gated , complete the following steps: 1. Set the environment variable GATED to 1 in the file /etc/rc.config.d/netconf to start gated automatically upon system startup. 2. Reboot your system, or issue the following command to run the gated startup script: /sbin/init.
Configuring gated Starting gated Chapter 3 100 F or more information about the command-line options , type man 1M gated at the HP-UX prompt. V erifying That gated Is Running Issue the following comma.
Configuring gated T roubleshooting gated Chapter 3 101 T roubleshooting gated This section describes the following techniques for troubleshooting gated and some common problems encountered with gated.
Configuring gated T roubleshooting gated Chapter 3 102 NO TE In gated 3.5.9 , the two statements in the Trace class ( tracefile and traceoptions ) are combined into one traceoptions statement. Therefore, the tracefile statement is eliminated. F or details about the new syntax, type man 4 gated.
Configuring gated T roubleshooting gated Chapter 3 103 gdc determines the state of gated and produces a reliable exit status during errors , which is useful in shell scripts that manipulate gated . The syslogd facility is used to log all the commands and error messages generated during gdc operation.
Configuring gated T roubleshooting gated Chapter 3 104 Common Problems This section discusses the common problems experienced during gated operation. Problem 1: gated does not act as expected. First, check the syslogd output for any syntax errors that may have been flagged.
Configuring gated T roubleshooting gated Chapter 3 105 Interface Configuration Without strictintfs Option Specified The following configuration references a non-existent interface, but does not in.
Configuring gated T roubleshooting gated Chapter 3 106 lan2 Index 3 Address 802.2 8:0:9:3d:2c:b1 Change: <> State: <> Refcount: 2 Up-down transitions: 0 198.1.1.17 Metric: 0 MTU: 1436 Refcount: 4 Preference: 0 Down: 120 Change: <> State: <Up Broadcast Multicast > Broadcast Address: 198.
Configuring gated T roubleshooting gated Chapter 3 107 Normally , gated deletes the route configured in the /etc/rc.config.d/netconf file. T o solve this problem, configure a static default route as described in the section “Installing Static Routes” on page 90.
Configuring gated T roubleshooting gated Chapter 3 108 Y ou may have to repeat this process several times to trac k down the original source of the route. If you expect the route to go through a different router , turn on gated tracing . The tracing tells you which routers are advertising this route and the values attached to those routes.
109 Index A all hosts group , 19 area border router , 61 configuration example , 75 area statement in /etc/gated.conf file , 65 areas , OSPF , 63 example configuration , 65 AS , 23 See autonomous system Assigned Numbers Authority , 63 authentication in OSPF , 77 authkey statement in /etc/gated.
Index 110 priority statement , 68 query authentication clause , 52 retain clause , 90 retransmitinterval statement , 68 , 72 rip statement , 50 ripin clause , 52 ripout clause , 52 routerdeadinterval .
Index 111 IP type of service routing feature , 24 K kernel routing table , 22 , 100 L link state advertisement , 62 M management information base See MIB metricin clause in /etc/gated.
Index 112 password authentication in OSPF , 78 configuration example , 78 phyint command in mrouted , 32 point-to-point network interface , 68 , 72 configuration example , 74 pollinterval statement in /etc/gated.conf file , 71 , 73 preference clause in /etc/gated.
Index 113 TOS routing feature , 24 traceoptions statement in /etc/gated.conf file , 53 tracing gated , 92 , 99 , 101 transmitdelay statement in /etc/gated.conf file , 68 TRPB , 18 Truncated Reverse P ath Broadcasting , 18 See TRPB trustedgatewa ys clause in /etc/gated.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il HP (Hewlett-Packard) HP-UX 11i v2 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del HP (Hewlett-Packard) HP-UX 11i v2 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso HP (Hewlett-Packard) HP-UX 11i v2 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul HP (Hewlett-Packard) HP-UX 11i v2 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il HP (Hewlett-Packard) HP-UX 11i v2, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del HP (Hewlett-Packard) HP-UX 11i v2.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il HP (Hewlett-Packard) HP-UX 11i v2. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo HP (Hewlett-Packard) HP-UX 11i v2 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
