Specifications
40
HP also can provide more broad-based services such as site surveys, installation services, and actual
management of the network, depending on customer needs.
More information can be found at www.hp.com/rnd/services/index.htm or by contacting a local ProCurve
sales office.
Appendix A: out-of-band management port
The out-of-band management (OOBM) interface provides an 10/100 Ethernet-based isolated management
interface to access the switch via SNMP, HTTP, SSH, and Telnet. As a truly isolated port, it is not connected to
the switching fabric and runs an IP stack that is separate from the in-band data plane. In a typical deployment,
the OOBM port should be connected to an isolated management network, both physically and logically, to
provide better security and allow for remote, lights-out management of the network. Figure A-1 highlights the
typical use model for an Ethernet out-of-band management network.
O
O
B
M
O
O
B
M
O
n
b
o
a
r
d
O
n
b
o
a
r
d
A
d
m
i
n
i
s
t
r
a
t
o
r
O
n
b
o
a
r
d
A
d
m
i
n
i
s
t
r
a
t
r
o
r
Data LAN
Management/
ILO LAN
D
a
t
a
D
a
t
a
sFlow collector
Mgmt.
V
L
A
N
f
o
r
s
F
l
o
w
Applications supported over OOBM
SSH, Telnet, TFTP, HTTP, SNTP, RADIUS, TACACS,
DNS, syslog, ping, and traceroute
Limitations
• sFlow must be captured in-band.
• IPv6 host capabilities, LLDP, ACLs are not
yet available
• Separate IP stacks for OOBM, and
InBand so DNS resolution is separated for
each IP stack
Administrator
Figure A-1: Out-of-band management use model
OOBM availability
The OOBM port is available on 6600-48G, 6600-48G-4XG, and 6600-24XG products and is enabled using
K.14.32 code or later.
Applications supported with OOBM port
The following applications are supported with the OOBM port: SSH, Telnet, TFTP, HTTP, SNTP, RADIUS,
TACACS, DNS, syslog, ping, and traceroute.
OOBM limitations
•sFlow: It is not possible to send sFlow samples to a collector over the OOBM port sFlow must be captured
and sent in-band.
•OOBM futures: Features to be implemented in the future, though no time frame has been committed, include
IPv6 host capabilities, LLDP discovery, and ACLs.
•DNS resolution: Because the OOBM supports a separate IP stack, DNS resolution is separated from the
in-band plane.