Avaya 38DHB0002UKDD manual Addressing on the Local Subnet, Warnings

Models: 38DHB0002UKDD

1 144
Download 144 pages 17.45 Kb
Page 33
Image 33
Addressing on the Local Subnet

The Configuration Tree Functions

The System Configuration Menu - Page 33

Addressing on the Local Subnet

Before completing the System Configuration menu, the operation of the local subnet must be considered. This may consist entirely of the devices connected to the IPNC via a hub, with the IPNC handling all addressing as a Dynamic Host Configuration Protocol (DHCP ) server. In this case, the configuration is minimal. In other cases, the IPNC may be connected to an external hub or router and hence is part of a larger network that may use either dynamic or static addressing.

CAUTION: It is critical to set up all IP addresses correctly to avoid contention.

A DHCP server assigns IP addresses to clients automatically as they boot up on a TCP/IP network. In default, when started, the IPNC sends a request for a DHCP address to the local network. If none is received, the IPNC assumes the role of a DHCP server and manages all addressing for both LAN devices and dial-in users. When operating as a DHCP server the IPNC uses it's own address as the starting address from which it will allocate new addresses to registering devices. See DHCP mode selection in The LAN1/2 Tab on page 35. If the IPNC is configured as part of an existing subnet that already uses another DHCP server, the mode can be set to Client, in order to leave control of the addressing with the existing server.

Note: On start up, the IPNC automatically becomes a client if it receives an address, e.g. if the IPNC finds a DHCP server already present on the network.

The DHCP mode can be also set to Dial In. In this mode, the IPNC manages DHCP addressing for users with dialled access whilst the existing server manages addressing on the subnet. Addresses are allocated to dial-in users as they log on in the usual way, but the maximum number of addresses allowed must be specified.

WARNINGS

1.IP addresses must not be in a range used by other DHCP servers.

2.In order for the IPNC's DHCP detection status to operate correctly, the IPNC must be connected to the LAN BEFORE being powered up (inserted into the INDeX). If this is not done there is the potential of having TWO DHCPs on the same LAN!

If the lLocal network uses static IP addressing, DHCP must be either set to Dial In or Disabled. In this case, the system must be given an IP address within the local subnet range and not in use elsewhere on the network. The addresses for dial-in users follow in sequence from the IPNC’s allocated address. For example, if the current subnet address range ends at 123.234.21.10:

123.234.21.11 - Is the address of the IPNC

123.234.21.12 - Is the first address given to a dial-in user

123.234.21.13 - Is the second address given to a dial-in user, and so on.

INDeX IPNC Cassette Administration Manual

The Configuration Tree Functions - Page 33

38DHB0002UKDD – Issue 7 (22/11/02)

The System Configuration Menu

Page 33
Image 33
Avaya 38DHB0002UKDD manual Addressing on the Local Subnet, Warnings