Configuring GX7 to deliver SNMP traps

Size: px

Start display at page:

Download "Configuring GX7 to deliver SNMP traps"

Maud Stewart
6 years ago
Views:

1 Configuring GX7 to deliver SNMP traps Introduction This document defines a method for manually configuring the GX7 to provide hardware diagnostic data via SNMP trap notifications for the configured trap receivers. The data is provided by the Baseboard Management Controller (BMC) on the GX7 motherboard. The BMC is managed via the Intelligent Platform Management Interface (IPMI). The system utiltity 'ipmitool' is used to configure the BMC and retrieve available data. The document focuses on enabling a remote trap receiver to receive SNMP notifications when any of the fan sensors that are monitored by the BMC violates a threshold. A number of steps must be completed to enable SNMP notifications to be processed by a remote trap receiver: 1. Configure the BMC 2. Configure the BMC LAN 3. Configure an alert destination 4. Configure the event filtering policy table 5. Configure the event filtering table 6. Validating an SNMP notification is generated A detailed description of these steps is provided by this document. Limitations Any customization applied to BMC configuration may not persist through upgrades to the BMC firmware. In the event that the BMC firmware is upgraded, the customization may need to be reapplied. The GX7 supports the following traps for this procedure: trapovertemperaturewarning (Over Upper Non Critical threshold) trapovertemperaturecritical (Over Upper critical threshold) trapovertemperaturewarningcleared trapovertemperaturecleared trapunderanalogvoltagecritical (Under Lower critical threshold) trapoveranalogvoltagecritical (Over Upper critical threshold) trapunderanalogvoltagecriticalcleared trapoveranalogvoltagecriticalcleared trapfancriticalunderspeed (Under lower critical threshold) trapfancriticalunderspeedcleared trapwatchdogreset (System reset) trapwatchdogpowerdown (System power down) trapwatchdogpowercycle (System power cycle) BMC firmware that shows a BMC LAN MAC address of 00:11:09:5b:7e:42 must be programmed to contain a unique BMC LAN MAC address. Please see the 'Configuring the BMC' section for further details. For all other GX7 systems, the BMC LAN MAC address must not be programmed.

2 Configuring the BMC A convenient method to configure the BMC LAN is to run the script attached to the technote on to the GX7 system. The script is:./snmp-notification.sh -t static -i n g I M 00:D0:C9:B7:AC:3E This script configures the following options: Option Setting IP address Netmask Gateway IP address of alert destination MAC address of alert destination 00:D0:C9:B7:AC:3E The script has the following arguments: #./snmp-notification.sh -h snmp-notifications.sh [-h] [-t <srctype>] [-i <sourceip>] [-m <sourcemac>] [-n <netmask>] [-g <default gateway IP>] [-c <channel>] -I <destinationips> -M <destinationmacs> -h Print this usage information. -c <channel number>. Default is 4 -t <static or dhcp>. If static, <sourceip> is required. -i <sourceip> where sourceip has format x.x.x.x -m <sourcemac> where sourcemac has format x:x:x:x:x:x. Only use this option if your BMC MAC adddress is set to 00:11:09:5b:7e:42 -n <netmask> where netmask has format x.x.x.x -g <default gateway IP> where default gateway IP has format x.x.x.x -I <destinationips> A comma separated list of IP addresses where each destinationip has format x.x.x.x -M <destinationmacs> A comma separated list of MAC addresses where each destinationmac has format x:x:x:x:x:x The BMC MAC address must only be programmed if it contains a factory default value 00:11:09:5b:7e:42, otherwise, it must not be programmed. To check your BMC LAN MAC address run the following command: # ipmitool lan print Set in Progress : Set Complete Auth Type Support : NONE MD2 MD5 PASSWORD Auth Type Enable : Callback : NONE MD2 MD5 PASSWORD : User : NONE MD2 MD5 PASSWORD : Operator : NONE MD2 MD5 PASSWORD : Admin : NONE MD2 MD5 PASSWORD : OEM : IP Address Source : Static Address IP Address : Subnet Mask : MAC Address : 00:11:09:5b:7e:42

3 Please refer to the list of GX7 BMC LAN MAC addresses attached to this technote. The BMC LAN MAC address should be set according to the Chassis Serial number. The Chassis Serial number is determined by running the following command: # ipmitool fru print 0 Chassis Type : Main Server Chassis Chassis Part Number : AdvanTech Chassis Serial : TPA Board Mfg Date : Fri May 14 15:49: Board Mfg : AMI Board Product : AdvanTech Board Serial : Board Part Number : AdvanTech Product Manufacturer : AdvanTech Product Name : FWA-6500 Product Part Number : AdvanTech Product Version : 2.0 Product Serial : Product Asset Tag : In the event that your Chassis Serial number is not present in the list, contact IBM support. If you do not want to use the script, the following sections provide detailed descriptions of each BMC configuration stage. Configuring the BMC LAN To enable SNMP traps to be sent the BMC LAN interface must be configured. It is possible to configure the LAN interface statically or via DHCP. The following subset provides enough data to enable the user to understand how to configure their BMC LAN: ipmitool lan help ipmitool lan set help ipmitool lan print ipmitool lan set 4 ipsrc <type> ipmitool lan set 4 ipaddr <x.x.x.x> ipmitool lan set 4 macaddr <x:x:x:x:x:x> Show the available lan commands Show the available commands for configuring the LAN Print the current LAN configuration Set the LAN type to 'static' or 'dhcp' Set the BMC LAN IP address to x.x.x.x Set the BMC LAN mac address The BMC LAN is always channel 4. At a minimum it is necessary to configure the IP channel address and netmask. It is likely that a default gateway IP needs to be set. The user should also ensure that the snmp value is set to public. The other BMC LAN fields are defaulted to suitable value. Here are some examples of configuring the BMC LAN: # ipmitool lan set 4 ipsrc dhcp # ipmitool lan set 4 snmp public Setting LAN SNMP Community String to public # ipmitool lan print Set in Progress : Set Complete

4 Auth Type Support : NONE MD2 MD5 PASSWORD Auth Type Enable : Callback : NONE MD2 MD5 PASSWORD : User : NONE MD2 MD5 PASSWORD : Operator : NONE MD2 MD5 PASSWORD : Admin : NONE MD2 MD5 PASSWORD : OEM : IP Address Source : DHCP Address IP Address : Subnet Mask : MAC Address : 00:11:09:5b:7e:42 SNMP Community String : public IP Header : TTL=0x00 Flags=0x00 Precedence=# ipmitool lan set 4 ipsrc dhcp skippy:~ # ipmitool lan set 4 snmp public Setting LAN SNMP Community String to public skippy:~ # ipmitool lan print Set in Progress : Set Complete Auth Type Support : NONE MD2 MD5 PASSWORD Auth Type Enable : Callback : NONE MD2 MD5 PASSWORD : User : NONE MD2 MD5 PASSWORD : Operator : NONE MD2 MD5 PASSWORD : Admin : NONE MD2 MD5 PASSWORD : OEM : IP Address Source : DHCP Address IP Address : Subnet Mask : MAC Address : 00:11:09:5b:7e:42 SNMP Community String : public IP Header : TTL=0x00 Flags=0x00 Precedence=0x00 TOS=0x00 BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled Gratituous ARP Intrvl : 5.0 seconds Default Gateway IP : Default Gateway MAC : 00:00:00:00:00:00 Backup Gateway IP : Backup Gateway MAC : 00:00:00:00:00: q VLAN ID : Disabled 802.1q VLAN Priority : 0 RMCP+ Cipher Suites : 1,2,3,6,7,8,11,12,0 Cipher Suite Priv Max : aaaaaaaaaaaaaaa : X=Cipher Suite Unused : c=callback : u=user : o=operator : a=admin : O=OEM 0x00 TOS=0x00 BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled Gratituous ARP Intrvl : 5.0 seconds Default Gateway IP : Default Gateway MAC : 00:00:00:00:00:00 Backup Gateway IP : Backup Gateway MAC : 00:00:00:00:00: q VLAN ID : Disabled 802.1q VLAN Priority : 0 RMCP+ Cipher Suites : 1,2,3,6,7,8,11,12,0 Cipher Suite Priv Max : aaaaaaaaaaaaaaa : X=Cipher Suite Unused : c=callback : u=user

5 : o=operator : a=admin : O=OEM Once the BMC LAN is configured it is possible to configure SNMP alert destinations. Configuring an Alert Destination The GX7 alert destination channel is always 4. Alert destinations 1-4 can be used as SNMP destinations. The following commands configure alert destination 1: ipmitool lan alert help ipmitool lan alert print Show the LAN alert configuration commands Print all of the alert destination configuration data ipmitool lan alert print 4 1 Print the alert destination for channel 4 index 1 ipmitool lan alert 4 1 ipaddr <x.x.x.x> ipmitool lan alert 4 1 macaddr <x:x:x:x:x:x> ipmitool lan alert 4 1 gateway default ipmitool lan alert 4 1 type pet ipmitool lan alert set 4 1 ack off ipmitool lan alert set 4 1 retry 5 ipmitool lan alert set 4 1 time 30 Set the alert destination IP address to x.x.x.x Set the alert destination MAC address to x:x:x:x:x:x Set the gateway to be used by the alert destination Set the destination type as pet or oem Set acknowledgement off Set retries to 5 (only used if ack is on) Set time between retries to 30 seconds (only used if ack is on) Here are some examples that show how alert destination 1 is configured: #<command> # ipmitool lan alert 4 1 ipaddr #<command> # ipmitool lan alert 4 1 macaddr 11:22:33:44:55:66 #<command> # ipmitool lan alert 4 1 gateway default #<command> # ipmitool lan alert 4 1 type pet #<command> # ipmitool lan alert print 4 1 Alert Destination : 1 Alert Acknowledge : Unacknowledged Destination Type : PET Trap Retry Interval : 0 Number of Retries : 0 Alert Gateway : Default Alert IP Address : Events that are configured to generate traps can now be sent to the alert destination. Configuring the Event Filter Policy Table The event filter policy provides a means of designating which sensors should generate an SNMP trap notification and the alert destination to send them too. The commands that must be run are:

6 ipmitool pef help ipmitool raw 0x4 0x12 0x1 0x1 ipmitool raw 0x4 0x12 0x9 0x1 0x10 0x41 0x00 ipmitool pef list Show all of the event filtering commands Enable event filtering Byte 4: Index into the event filtering table Byte 6: Use channel 4 alert destination 1 List the events configured to trigger SNMP trap notifications At a minimum, event filtering must be enabled, the PEF policy must be modified to use a configured alert destination and the event filtering table must contain entries pertinent to the SNMP notifications that the user wishes to observe. Configuring the Event Filter Table The BMC provides means for up to 16 events to result in an SNMP notification. The only way to manipulate some of the PEF configuration is via the ipmitool raw command. The following commands enable traps on the set of sensors that the GX7 supports: ipmitool raw 0x04 0x12 0x06 0x02 0xc0 0x1 0x1 0x10 0x20 0xff 0x04 0x40 0x10 0x ipmitool raw 0x04 0x12 0x06 0x02 0xc0 0x01 0x01 0x10 0x20 0xff 0x04 0x42 0x01 ipmitool raw 0x04 0x12 0x06 0x03 0xc0 0x01 0x01 0x10 0x20 0xff 0x04 0x5a 0x01 ipmitool raw 0x04 0x12 0x06 0x04 0xc0 0x01 0x01 0x10 0x20 0xff 0x04 0x5b 0x01 ipmitool raw 0x04 0x12 0x06 0x05 0xc0 0x01 0x01 0x10 0x20 0xff 0x04 0x61 0x01 ipmitool raw 0x04 0x12 0x06 0x06 0xc0 0x01 0x01 0x10 0x20 0xff 0x04 0x62 0x01 Enable traps on system fan1 Enable traps on system fan2 Enable traps on power supply 1 fan 1. 0 indicates supply is removed or faulty Enable traps on power supply 1 fan 2. 0 indicates supply is removed, off, or faulty Enable traps on power supply 2 fan 1. 0 indicates supply is removed, off or faulty Enable traps on power supply 2 fan 2. 0 indicates supply is removed or faulty The configuration can be confirmed: # ipmitool pef list 1 active, pre-configured 0x11 Fan 64 Critical Threshold 2 active, pre-configured 0x11 Fan 66 Critical Threshold 3 active, pre-configured 0x11 Fan 90 Critical Threshold 4 active, pre-configured 0x11 Fan 91 Critical Threshold 5 active, pre-configured 0x11 Fan 97 Critical Threshold

7 6 active, pre-configured 0x11 Fan 98 Critical Threshold 7 inactive 8 inactive 9 inactive 10 inactive 11 inactive 12 inactive 13 inactive 14 inactive 15 inactive 16 inactive Validating SNMP Notification The easiest way to validate the operation of traps is to remove the redundant power supply. The following command is also useful: ipmitool sel list List system events. This should be run prior to and after removing the power supply to establish an event got raised locally on the system under test Provided the network configuration is correct, the SNMP notification should be viewable in the alert destination SNMP trap receiver. An event will also be present in the event list.

BMC User Guide. May 2018

BMC User Guide. May 2018 BMC User Guide May 2018 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to