Extreme Networks Altitude 4000 Series, Справочное руководство, Страница: 103 / 521

System Profile Configuration
Altitude
TM
4000 Series Access Point System Reference Guide
103
5 Select the Include Hostname in DHCP Request checkbox to include a hostname in a DHCP lease for a
requesting device. This feature is enabled by default.
6 Select the DHCP Persistent Lease checkbox to retain the lease that was last used by the access point if
the access point’s DHCP server resource were to become unavailable. This feature is enabled by
default.
7 Select the OK button located at the bottom right of the screen to save the changes. Select Reset to
revert to the last saved configuration.
Profile Network Configuration and Deployment Considerations
“Profile Network Configuration”
Before defining a profile’s network configuration, refer to the following deployment guidelines to
ensure the profile configuration is optimally effective:
●
Administrators often need to route traffic to interoperate between different VLANs. Bridging VLANs
are only for non-routable traffic, like tagged VLAN frames destined to some other device which will
untag it. When a data frame is received on a port, the VLAN bridge determines the associated
VLAN based on the port of reception.
●
Static routes, while easy, can be overwhelming within a large or complicated network. Each time
there is a change, someone must manually make changes to reflect the new route. If a link goes
down, even if there is a second path, the router would ignore it and consider the link down.
●
Static routes require extensive planning and have a high management overhead. The more routers
that exist in a network, the more routes needing to be configured. If you have N number of routers
and a route between each router is needed, then you must configure N x N routes. Thus, for a
network with nine routers, you’ll need a minimum of 81 routes (9 x 9 = 81).