Category Archives: HPE

Reset HP A5800 Switch to Factory Default Configuration

On the test, I reset the configuration on the HP A5800 Series Switch JC103A.

And so, connect to the device and see what files are in the device’s memory:

dir

By default, the configuration is saved in the file config.cfg, let’s say that it is, so we’ll delete it:

delete config.cfg

We removed the configuration file, now we will reboot the device:

reboot

On the offer to keep the configuration we will refuse and on the next issue agree to the reboot:

This command will reboot the device. Current configuration will be lost, save current configuration? [Y/N]:n
This command will reboot the device. Continue? [Y/N]:y

Done, the switch will start with the default configuration, after which you can begin to configure, for example, as I described in the article – Настройка HP 5800

You can also try to reset the configuration as follows:

reset saved-configuration
reboot

Either through the Boot menu, to open it, when you turn on the device, press Ctrl+D and pressing the number 5, we select in the menu the reset of the configuration:

5. Restore to factory default configuration

Then, press 0 to select the reboot:

0. Reboot

When starting the switch, make sure that the configuration is reset:

display current-configuration
display saved-configuration

Solution of error “The transceiver type is not supported by port hardware” on HP A5800

I noticed once on the switch HP A5800 Series Switch JC103A, when inserting the module Foxgate SFP-1SM-1550nm-10SC (10km), the following error:

%Apr 26 12:18:56:384 2000 HP OPTMOD/4/MODULE_IN:
 GigabitEthernet1/0/24: The transceiver is UNKNOWN_SFP_PLUS.
%Apr 26 12:18:56:524 2000 HP OPTMOD/5/CHKSUM_ERR:
 GigabitEthernet1/0/24: The checksum of transceiver information is bad!
%Apr 26 12:18:56:674 2000 HP OPTMOD/3/TYPE_ERR:
 GigabitEthernet1/0/24: The transceiver type is not supported by port hardware!

Alternatively, you can try running the command:

transceiver phony-alarm-disable

But in my case this command did not help.
Also noticed that the error did not occur when inserting a similar module is not at 10km, but at 3km – Foxgate SFP-1SM-1550nm-3SC 3km.

The problem was solved by updating the firmware of the switch, as I did in the article – HP A5800 Firmware Upgrade
I updated the firmware from “A5800_5820X-CMW520-R1809P11” to “A5800_5820X-CMW520-R1810P13”.
After the upgrade, both modules were working and there were no errors in the console.

See also:
Using third-party SFP modules in Cisco switches

Solving the problem when upgrading iLO 3 “98% Receiving Image…”

Updated somehow iLO 3 from version 1.10 to 1.88, on the HP ProLiant DL380 G7 server and the process stopped at “98% Receiving Image…”

So, if the firmware version of iLO 3 is lower than 1.28, then you must first upgrade to version 1.28, and then higher.

That’s the whole solution to the problem.

Configuring PIM on HP A5800 Switch

First make a copy of the configuration file on the tftp server:

backup startup-configuration to 192.168.1.100

To configure the PIM on the HP A5800 switch, connect to the switch via telnet and enter the following commands:

1) Enable the multicast routing switch and pim-sm in vlan 963 which comes from the provider.

system-view
multicast routing-enable
interface Vlan-interface 963
ip address 172.24.24.158 255.255.255.252
pim sm
quit

2) Turn on pim-sm and igmp in vlan 964 on which IPTV will be broadcast to the local network.

interface Vlan-interface 964
ip address 172.25.25.25 255.255.192.0
pim sm
igmp enable
quit

3) We’ll assign the static ip from which the multicast is broadcast.

pim
static-rp 10.0.200.200
quit

4) Add the route to ip from which the multicast is broadcast.

ip route-static 10.0.200.200 255.255.255.255 Vlan-interface963 172.24.24.157

5) Suppose that we accept multicast on vlan 963 tag.

interface Bridge-Aggregation1
port hybrid vlan 963 tagged

6) We will configure any free port for iptv verification and connect to it a computer for example with a playlist in the VLC player.

interface GigabitEthernet1/0/5
port access vlan 964

To test the health and diagnostics, you can use for example the following commands:

display pim interface
display pim interface verbose
display pim rp-info
display pim bsr-info
display pim neighbor
display pim routing-table
display igmp interface
display pim control-message counters
display pim claimed-route

HP Printers SNMP OID’s

On the test, I will use the HP LaserJet P2055dn printer.

Here is a list of tested OIDs for obtaining various SNMP information:
1.3.6.1.2.1.43.11.1.1.8.1.1 (Maximum number of copies of toner)
1.3.6.1.2.1.43.11.1.1.9.1.1 (Remaining number of copies of toner)
1.3.6.1.2.1.43.12.1.1.4.1.1 (Toner color)
1.3.6.1.2.1.43.10.2.1.4.1.1 (Number of pages printed)
1.3.6.1.2.1.43.5.1.1.17.1 (Serial number of the printer)

To see a list of all possible oid’s, you can run the command in Linux:

snmpwalk -v 1 -c public 192.168.24.112

You can check the specific oid with the command:

snmpget -v 2c -c public 192.168.24.112 1.3.6.1.2.1.43.11.1.1.9.1.1

SNMP OIDs for the HP 5800 Switch

I’ll list some of the OIDs I used:
Determine the OID of the processor load by running the command in Linux:

snmpwalk -v 2c -c сommunity host .1.3.6.1.4.1.25506.2.6.1.1.1.1.6
snmpwalk -v 2c -c сommunity host .1.3.6.1.2.1.47.1.1.1.1.7

As a result of the execution of the first command, a list of OIDs will be displayed, those in which a value greater than 0 means CPU loading. If the switches are stacked, then the OID with a value greater than zero will be greater than one. The second team is looking at the description, ours will be “Board”.

Determine the OID of memory usage:

snmpwalk -v 2c -c сommunity host .1.3.6.1.4.1.25506.2.6.1.1.1.1.8

Determine the OID of the temperature:

snmpwalk -v 2c -c сommunity host .1.3.6.1.4.1.25506.2.6.1.1.1.1.12

OID to view the ARP list:

.1.3.6.1.2.1.3.1.1

We look in what vlan are ip:

.1.3.6.1.2.1.2.2.1.2

See also:
SNMP OID and MIB for interfaces

Resetting the iLO password via hponcfg on HP servers

On the test, I change the iLO password to the standard Administrator user on the HP ProLiant DL380 G7 server, the password is generated randomly from the manufacturer and installed in the BIOS, it can also be seen on the pull-out ribbon and attached to the server.

Therefore, in order not to restart the server to change the password, create a file with the name reset_password.xml for example and add content to it:

<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="password">
<USER_INFO MODE="write">
<MOD_USER USER_LOGIN="Administrator">
<PASSWORD value="password specify here only"/>
</MOD_USER>
</USER_INFO>
</LOGIN>
</RIBCL>

Where Administrator, this is the user name, password – do not touch, there can be any text, but only indicate the desired password to the user in the PASSWORD value.

We export the file:

sudo hponcfg -f reset_password.xml

In case of an error, you can output the report to the log.txt file with the command:

sudo hponcfg -f reset_password.xml -l log.txt

See also:
Configuring iLO through hponcfg

SNMP OID List for iLO4

I made a template for Zabbix today to monitor iLO 4 on the HP DL380p G8 server and had to investigate several OIDs.

You can check the OID from Linux with the command:
snmpwalk 192.168.1.5 -c КОМЬЮНИТИ -v 2c OID

Below is a list and description for OID coolers, processors, temperature sensors, logical drives (RAID), hard disks, network controller iLO, RAM.

Fans:
.1.3.6.1.4.1.232.6.2.6.7.1.2.0 (Fan Index)
.1.3.6.1.4.1.232.6.2.6.7.1.3.0 (Fan Locale (1=other, 2=unknown, 3=system, 4=systemBoard, 5=ioBoard, 6=cpu, 7=memory, 8=storage, 9=removable media, 10=power supply, 11=ambent, 12=chassis, 13=bridge card, 14=management board, 15=backplane, 16=network slot, 17=blade slot, 18=virtual)
.1.3.6.1.4.1.232.6.2.6.7.1.4.0 (Fan Present (1=other, 2=absent, 3=present)
.1.3.6.1.4.1.232.6.2.6.7.1.5.0 (Fan Present (1=other, 2=tachOutput, 3=spinDetect)
.1.3.6.1.4.1.232.6.2.6.7.1.6.0 (Fan Speed (1=other, 2=normal, 3=high)
.1.3.6.1.4.1.232.6.2.6.7.1.9.0 (Fan Condition (1=other, 2=ok, 3=degraded, 4=failed)

Temperature:
.1.3.6.1.4.1.232.6.2.6.8.1.2.0 (Temperature Sensor Index)
.1.3.6.1.4.1.232.6.2.6.8.1.3.0 (Temperature Sensor Locale (1=other, 2=unknown, 3=system, 4=systemBoard, 5=ioBoard, 6=cpu, 7=memory, 8=storage, 9=removable media, 10=power supply, 11=ambent, 12=chassis, 13=bridge card)
.1.3.6.1.4.1.232.6.2.6.8.1.7.0 (Threshold Type (1=other, 5=blowout, 9=caution, 15=critical, 16=noreaction)
.1.3.6.1.4.1.232.6.2.6.8.1.4.0 (Temperature Celsius)
.1.3.6.1.4.1.232.6.2.6.8.1.5.0 (TemperatureThreshold)
.1.3.6.1.4.1.232.6.2.6.8.1.6.0 (TemperatureCondition)

CPU:
.1.3.6.1.4.1.232.1.2.2.1.1.1 (CPU Index)
.1.3.6.1.4.1.232.1.2.2.1.1.3 (CPU Name)
.1.3.6.1.4.1.232.1.2.2.1.1.4 (CPU Speed in MHz)
.1.3.6.1.4.1.232.1.2.2.1.1.5 (CPU Step)
.1.3.6.1.4.1.232.1.2.2.1.1.6 (CPU status (1=unknown, 2=ok, 3=degraded, 4=failed, 5=disabled)
.1.3.6.1.4.1.232.1.2.2.1.1.15 (Number of enabled CPU cores)
.1.3.6.1.4.1.232.1.2.2.1.1.25 (Number of available CPU threads)
.1.3.6.1.4.1.232.1.2.2.1.1.26 (CPU power status (1=unknown, 2=Low Powered, 3=Normal Powered, 4=High Powered)

Logical Drives:
.1.3.6.1.4.1.232.3.2.3.1.1.2.0 (Logical Drive Index)
.1.3.6.1.4.1.232.3.2.3.1.1.1.0 (Logical Drive Controller)
.1.3.6.1.4.1.232.3.2.3.1.1.3.0 (Logical Drive Fault Tolerance (1=other, 2=none, 3=RAID 1/RAID 1+0 (Mirroring), 4=RAID 4 (Data Guard), 5=RAID 5 (Distributed Data Guard), 7=RAID 6 (Advanced Data Guarding), 8=RAID 50, 9=RAID 60, 10=RAID 1 ADM (Advanced Data Mirroring), 11=RAID 10 ADM (Advanced Data Mirroring with Striping))
.1.3.6.1.4.1.232.3.2.3.1.1.9.0 (Logical Drive Size in Mb)
.1.3.6.1.4.1.232.3.2.3.1.1.4.0 (Logical Drive Status (1=other, 2=ok, 3=Failed, 4=Unconfigured, 5=Recovering, 6=Ready Rebuild, 7=Rebuilding, 8=Wrong Drive, 9=Bad Connect, 10=Overheating, 11=Shutdown, 12=Expanding, 13=Not Available, 14=Queued For Expansion, 15=Multi-path Access Degraded, 16=Erasing, 17=Predictive Spare Rebuild Ready, 18=Rapid Parity Initialization In Progress, 19=Rapid Parity Initialization Pending, 20=No Access – Encrypted with No Controller Key, 21=Unencrypted to Encrypted Transformation in Progress, 22=New Logical Drive Key Rekey in Progress, 23=No Access – Encrypted with Controller Encryption Not Enabled, 24=Unencrypted To Encrypted Transformation Not Started, 25=New Logical Drive Key Rekey Request Received)
.1.3.6.1.4.1.232.3.2.3.1.1.11.0 (Logical Drive Condition (1=other, 2=ok, 3=degraded, 4=failed)

Drives:
.1.3.6.1.4.1.232.3.2.5.1.1.2.0 (Drive Index)
.1.3.6.1.4.1.232.3.2.5.1.1.5.0 (Drive Bay)
.1.3.6.1.4.1.232.3.2.5.1.1.64.0 (Drive Location)
.1.3.6.1.4.1.232.3.2.5.1.1.3.0 (Drive Vendor)
.1.3.6.1.4.1.232.3.2.5.1.1.51.0 (Drive Serial Number)
.1.3.6.1.4.1.232.3.2.5.1.1.45.0 (Drive Size in Mb)
.1.3.6.1.4.1.232.3.2.5.1.1.65.0 (Drive Link Rate (1=other, 2=1.5Gbps, 3=3.0Gbps, 4=6.0Gbps, 5=12.0Gbps))
.1.3.6.1.4.1.232.3.2.5.1.1.70.0 (Drive Current Temperature)
.1.3.6.1.4.1.232.3.2.5.1.1.71.0 (Drive Temperature Threshold)
.1.3.6.1.4.1.232.3.2.5.1.1.72.0 (Drive Maximum Temperature)
.1.3.6.1.4.1.232.3.2.5.1.1.6.0 (Drive Status (1=Other, 2=Ok, 3=Failed, 4=Predictive Failure, 5=Erasing, 6=Erase Done, 7=Erase Queued, 8=SSD Wear Out, 9=Not Authenticated)
.1.3.6.1.4.1.232.3.2.5.1.1.37.0 (Drive Condition (1=other, 2=ok, 3=degraded, 4=failed)
.1.3.6.1.4.1.232.3.2.5.1.1.9.0 (Drive Reference Time in hours)

iLO NIC:
.1.3.6.1.4.1.232.9.2.5.2.1.1 (iLO location)
.1.3.6.1.4.1.232.9.2.5.1.1.2 (iLO NIC model)
.1.3.6.1.4.1.232.9.2.5.1.1.4 (iLO NIC MAC)
.1.3.6.1.4.1.232.9.2.5.1.1.5 (iLO NIC IPv4)
.1.3.6.1.4.1.232.9.2.5.1.1.9 (iLO NIC speed)
.1.3.6.1.4.1.232.9.2.5.1.1.14 (iLO NIC FQDN)
.1.3.6.1.4.1.232.9.2.5.2.1.2 (Tx bytes)
.1.3.6.1.4.1.232.9.2.5.2.1.3 (Tx packets)
.1.3.6.1.4.1.232.9.2.5.2.1.6 (Tx discard packets)
.1.3.6.1.4.1.232.9.2.5.2.1.7 (Tx error packets)
.1.3.6.1.4.1.232.9.2.5.2.1.9 (Rx bytes)
.1.3.6.1.4.1.232.9.2.5.2.1.10 (Rx packets)
.1.3.6.1.4.1.232.9.2.5.2.1.13 (Rx discard packets)
.1.3.6.1.4.1.232.9.2.5.2.1.14 (Rx error packets)
.1.3.6.1.4.1.232.9.2.5.2.1.15 (Rx unknown packets)

Memory:
.1.3.6.1.4.1.232.6.2.14.13.1.1 (Memory Index)
.1.3.6.1.4.1.232.6.2.14.13.1.13 (Location)
.1.3.6.1.4.1.232.6.2.14.13.1.9 (Manufacturer)
.1.3.6.1.4.1.232.6.2.14.13.1.10 (Part Number)
.1.3.6.1.4.1.232.6.2.14.13.1.6 (Size in Kbytes)
.1.3.6.1.4.1.232.6.2.14.13.1.8 (Memory Technology)
.1.3.6.1.4.1.232.6.2.14.13.1.7 (Memory Type)
.1.3.6.1.4.1.232.6.2.14.13.1.19 (Memory status (1=other, 2=notPresent, 3=present, 4=good, 5=add, 6=upgrade, 7=missing, 8=doesNotMatch, 9=notSupported, 10=badConfig, 11=degraded, 12=spare, 13=partial)
.1.3.6.1.4.1.232.6.2.14.13.1.20 (Memory condition (1=other, 2=ok, 3=degraded, 4=degradedModuleIndexUnknown)