Instruction Manual

If no bays are specified when setting the <ip address>, then all the bays are assigned an
IP address in the range starting from the <ip address>.
The keyword NONE can be used in the place of <ip address>, <netmask>, or <gateway>
to clear the IP address.
NOTE: Link-local IP addresses can be assigned to blades, iLOs, and interconnect bays within
an enclosure. Link-local addresses are intended only for use within a segment of a network
and can be used for network configurations that do not required allocated IP addresses on
the network.
The firewall rules on the OA will prevent these addresses from being visible outside of the
local management subnet within an enclosure.
• Access level/Bay level:
Administrator, Operator
• Restrictions:
The <ip address> and <netmask> must be in the form ###.###.###.###, where
each ### ranges from 0 to 255.
◦
◦ The <domain name> is a string containing letters (a-z, A-Z), digits (0-9), or a dash (-).
SHOW EBIPA
• Command:
SHOW EBIPA [INTERCONNECT | BLADE]
• Description:
Displays EBIPA information.
◦ The INTERCONNECT argument displays EBIPA information for interconnects only.
◦ The BLADE argument displays EBIPA information for blades only.
◦ The local keyword will appear in the EBIPA Address column if link-local addressing is
enabled for the bay.
◦ The command will display an additional row for each bay showing the IP address, port,
and protocol of each proxied protocol if the optional requirement to provide access to
the blade iLOs using proxy ports on the active OA is implemented
• Access level/Bay level:
All
• Restrictions:
None
• Example:
fugu-oa> show ebipa
EBIPA Device Server Settings
Bay Enabled EBIPA/Current Netmask Gateway DNS Domain
--- ------- ------------- ------- --------------- --------------- ------
1 No 0.0.0.0 0.0.0.0 16.119.107.163
1A No 0.0.0.0
1B No 0.0.0.0
2 No 0.0.0.0 0.0.0.0 16.119.106.131
2A No 0.0.0.0
2B No 0.0.0.0
3 No 0.0.0.0 1.2.3.4 16.119.108.217
3A No 0.0.0.0
3B No 0.0.0.0
4 No 0.0.0.0 0.0.0.0 16.119.107.119
SHOW EBIPA 53