Avaya Connecting ASN Routers and BNX Platforms to a Network Manual de usuario descargar pdf (Pagina 52)

Connecting ASN Routers and BNX Platforms to a Network

3-2

Preparing Conﬁguration and Image Files

Unless the ASN will use the default (generic) conﬁguration ﬁle and software

image that ship on its local ﬁle system, you must create

• A unique conﬁguration ﬁle for each remote router

• A uniform software image that all routers in your network can use

Creating Conﬁguration Files

Prepare network conﬁguration ﬁles as follows:

1. Use the Conﬁguration Manager in local mode to create a conﬁguration

ﬁle for each ASN.

Refer to Conﬁguring Routers or Conﬁguring Customer Access and Trunks

(BNX Software), depending on the type of installed software, for instructions.

2. Record the name of each conﬁguration ﬁle and corresponding ASN for

later reference.

When you name configuration files, keep the following in mind:

• Conﬁguration ﬁles that you save on a BOOTP server do not have to be

named conﬁg.

• Conﬁguration ﬁlenames must begin with an alphabetical character. The

remaining characters must be alphanumeric and may also include the

underscore (_) character. You cannot use spaces.

• Conﬁguration ﬁlenames can consist of 1 to 15 characters, including a dot

(.). We recommend that you limit ﬁlenames to eight characters to ensure

that all operating systems Bay Networks supports can recognize the

names.

• Conﬁguration ﬁlename extensions are optional and must follow a

filename and a dot. We recommend that you limit filename extensions to

three characters.

• BOOTP allows a maximum number of 49 characters in a path, including

slashes, ﬁlename, optional dot, and ﬁlename extension.

3. If the BOOTP server and Site Manager do not reside on the same

workstation, transfer the conﬁguration ﬁles to the BOOTP server.

1 2 ... 47 48 49 50 51 52 53 54 55 56 57 ... 105 106

Sin comentarios

Avaya Connecting ASN Routers and BNX Platforms to a Network Manual de usuario Pagina 52