![FNGi DHCPatriot Version 6 Скачать руководство пользователя страница 9](http://html1.mh-extra.com/html/fngi/dhcpatriot-version-6/dhcpatriot-version-6_operation-manual_2313249009.webp)
Chapter 1: Requirements
Network and Router Requirements
The customers must use DHCP (see rfc1542 -
http://www.faqs.org/rfcs/rfc1542.html
) to
obtain their dynamic IP Address. The DHCPatriot system does not support other
broadband authentication protocols such as PPPoE.
The gateway routers that the customers are connected to must support the DHCP
Relay Agent protocol (see “BOOTP Relay Agent” rfc1542 Section 4 -
www.faqs.org/rfcs/rfc1542.html
) (Cisco® defines this as the ‘ip helper-address’
command). This is important as the DHCPatriot system cannot exist on the same
physical LAN as the customers. It expects to be separated from the customers and
interact with a DHCP Relay Agent. Further, the device’s DHCP Relay Agent protocol
implementation must support DHCP Failover (see
http://tools.ietf.org/html/draft-ietf-dhc-
) (Cisco® devices that support ‘ip helper-address’ support DHCP Failover
without special modification).
The DHCPatriot system must NOT be located in a separately uplinked network from the
customer network. For example, if you have a remote POP (Point-Of-Presence) that is
not directly linked to your network, but which, instead, uses some other backbone
provider to link the customers to the Internet, then a single DHCPatriot system cannot
be used centrally in this situation. An additional system will be needed for that separate
pop. In other words, the customer traffic must not leave your routing control before
arriving at the DHCPatriot system. If this is not the case, then the policy based routing
will not work for the optional authentication.
Some routers in the network will need to support policy based routing. Most Cisco®
routers and layer 3 switches support policy based routing in order for the optional
authentication to function.
Optional External Equipment
The DHCPatriot system may use either the Built-in Authentication, or an optional
external RADIUS server for authentication and accounting of customers. It must use
one method or the other. Note: The RADIUS server must at least respond with the
Framed-IP-Address attribute set to 255.255.255.254.
Power and Cabling Requirements
**PLEASE NOTE: This section applies to only AC powered DHCPatriot systems. DC
powered systems use 48 volt DC.**
Each DHCPatriot device has a single power supply. This power supply is AC
(Alternating Current) compatible only. DO NOT plug the devices into DC (Direct
Chapter 1: Requirements
9
DHCPatriot Version 6 Operations Manual This document © 2017 First Network Group Inc. All Rights Reserved
Содержание DHCPatriot Version 6
Страница 1: ...Operations Manual Version 6...
Страница 2: ......