Specifications

PowerConnect 6024/6024F Release Notes
Release Notes | Page 7
RN-CA-UG-04. The functioning of
BootP
The device incorporates BootP and DHCP clients that solicit an IP address to
use as the system IP address on each interface. The BootP client is
operational on system startup only if no IP interface is defined and DHCP client
is not configured to work. This is the factory default setting. The BootP client
will continuously try to find a BootP server by sending BootP requests to all
VLANs and ports (including the out-of-band management port) until either of
the following events occurs:
1) A BootP server replies in which case the reply is used to provide the system
with an IP address on the interface, on which the reply is received (all other
interfaces have to be assigned IP addresses by other means).
2) The user starts to manually configure the system (command-line activity of
any kind is detected on the serial console port).
An IP address will be considered static by the device when either a) acquired
automatically via BootP or b) set manually via a management interface.
RN-CA-UG-05. The supported
OSPF features.
The device supports the following OSPF features:
* Virtual links
* ECMP
* OSPF default cost of an OSPF interface.
* Cryptographic authentication.
At present the device does not support all other OSPF features.
Corrections and Additions to the CLI Reference Guide
CLI Command Description of Change
RN-CA-CLIRG-01. CLI command
“passwords min-length”
User Guidelines: The length of passwords that were defined before the
minimum password length requirement was configured is not checked on
subsequent logins. This command is not enforced retroactively.
RN-CA-CLIRG-02. CLI command
“ip address dhcp”
Every in-band port of the switch can potentially become a routing port.
Therefore, when an interface is defined on an in-band port (or a VLAN of which
it is the member), no default-gateway is configured. After dynamic assignment
of the IP interface, you may assign a default route manually.
RN-CA-CLIRG-03. CLI command
“ospf”
The correct syntax is ospf [area-id]. (The ospf command area parameter is
optional.)
Note the following user guidelines (detailed further in this document):
* If the specified area-id has not yet been created, using the ip interface
configuration ospf area command, then it is auto-created using this command.
* Note that an OSPF area that is auto-created is not displayed in the
configuration file.
* Note that an auto-created OSPF area is deleted only after a subsequent
reboot, if the OSPF interface is deleted.
* If no area is designated, the backbone area is associated with the IP
interface. If the backbone has not yet been created, it is auto-created.
* Note that the negation of the area command does not appear in the
configuration file, because it is, in fact, the default. However, it does appear
when using the "show ospf” command, because it was automatically created.
RN-CA-CLIRG-04. CLI command
“ip route”
If reject-route is designated, this will discard all packets matching this route per
RFC-2096, and handle them as reject-route. These routes are treated as
unreachable networks, and an "ICMP unreachable route" is returned.