Management and Configuration Guide K/KA/KB.15.15

10.1.131.51 is alive, time = 15 ms
Switch 41# ping 10.255.255.42 Ping switch in adjacent rack.
The destination address is unreachable. Oops! Its on the management network.
Switch 41# ping source oobm 10.255.255.42 Go through the management port
10.255.255.42 is alive, time = 2 ms and it works fine.
Switch 41#
Concepts
Management communications with a managed switch can be:
In band—through the networked data ports of the switch
Out of band—through a dedicated management port (or ports) separate from the data ports
Out-of-band ports have typically been serial console ports using DB-9 or specially wired 8-pin
modular (RJ-style) connectors. Some recent HP switches have added networked OOBM ports.
Figure 280 (page 511) shows management connections for a typical switch.
Figure 280 Management ports
OOBM operates on a "management plane" that is separate from the "data plane" used by data
traffic on the switch and by in-band management traffic. That separation means that OOBM can
continue to function even during periods of traffic congestion, equipment malfunction, or attacks
on the network. In addition, it can provide improved switch security: a properly configured switch
can limit management access to the management port only, preventing malicious attempts to gain
access via the data ports.
Network OOBM typically occurs on a management network that connects multiple switches. It has
the added advantage that it can be done from a central location and does not require an individual
physical cable from the management station to each switch's console port.
Of the switches covered by this manual, network OOBM is available on:
HP Switch 6600-24XG switch (J9265A)
HP Switch 6600-48G switch (J9451A)
HP Switch 6600-48G-4XG switch (J9452A)
Table 34 (page 512) summarizes the switch management ports.
Concepts 511