With Infoblox you’re almost doing everything through the WebUI on the Infoblox Grid Master. At least the daily business such as adding/changing/deleting/moving/whatever DNS, DHCP, and IPAM stuff. Even troubleshooting is almost done through this HTTPS-based GUI. However, some circumstances require the use of the CLI on an Infoblox appliance/VM, called “Remote Console Access” aka SSH. Here are the most common troubleshooting CLI commands for Infoblox DDI. Samples on how to use the IPMI/LOM features round things up:
Note that this blogpost is a living document. Whenever I use some “new” commands for troubleshooting issues, I will update it. In case there are any useful commands missing, please write a comment!
Prerequisites
Unless you’re using the serial console (or the remote console through VMware or the like), you need to enable the SSH access in the GUI through: Grid Manager -> Grid Properties -> Security -> Advanced -> Enable Remote Concole Access.
After that you have remote SSH access with your admin account to any Grid member, either through the MGMT or the LAN1 port, depending on your config. (Note: If you’re using remote authentication such as RADIUS, those outgoing authentication connections will be sourced from the MGMT or LAN1 port as well, again depending on your config.)
Furthermore you should set the prompt to something other than the (annoying) default of “Infoblox >”. This must be done on the Grid master and applies to all members afterwards. Choose one of those:
set prompt user@hostname set prompt user@ip
In HA scenarios you get an additional (A) or (P) depending on the device state. Example:
Infoblox > Infoblox > set prompt user@hostname admin_weberjoh@dnsrz (A) > admin_weberjoh@dnsrz (A) > admin_weberjoh@dnsrz (A) > set prompt user@ip admin_weberjoh@192.168.0.4 (A) > admin_weberjoh@192.168.0.4 (A) > admin_weberjoh@192.168.0.4 (A) >
General Stuff
The very basics:
help show version #Version and serial number show status #Grid and HA status, hostname, Grid Master IP show hardware_status #temperature, power, fan show uptime show cpu #memory, swap, io, system, cpu show memory #little more memory details, same as Linux command "free" show ntp show date show license #list of all licenses incl. epiration dates set license #paste a new license set temp_license #active 60-days trial licenses set membership #become a Grid member set nogrid #removes this member from the Grid reboot #reboot the system (which also clears the caches)
The following “show config …” commands are the same as within the GUI, e.g., Data Management -> DNS -> Members -> View -> View Configuration. However, sometimes it’s a bit easier to have a quick look through the CLI. Only working on the members when the appropriate services are enabled:
show config { dns | dhcp | dhcpv6 }Show, tail, or follow log files of different types. Optionally with /regex/:
show log [ syslog | debug | audit ]
show log [ syslog | debug | audit ] /regex/
show log [ syslog | debug | audit ] tail {number-of-line}
show log [ syslog | debug | audit ] follow [/regex/]
Network ‘n Interfaces
(Note that I was not able to use ping via IPv6 on NIOS version 8.3.4. Maybe a bug?)
set network #set basic LAN1 IP addresses and optionally become a Grid member
show network #show LAN1/HA/Mgmt port IP addresses
set interface #speed and duplex for LAN1/HA/Mgmt interfaces on hardware devices
show interface #much more details for all interfaces (incl. tunnels!) such as packets, errors, etc.
ping { hostname | ip } [v6] #well, that's ping ;) optionally via IPv6
traceroute { hostname | ip } [v6] #traceroute via legacy IP or IPv6
show ipv6_neighbor all #IPv6 neighbors (NDP) for all interfaces
show arp #ARP cache for all interfaces
reset arp #clear the ARP cache
dig & expertmode dig
There are two slightly different digs on the CLI. The normal one when using it directly on the CLI (which is customized by Infoblox in some way), and the one under “expertmode” which has a couple of more options.
Normal dig:
Infoblox > dig
Synopsis:
dig [@server_address] <hostname> [type] [opt...]
-- type can be any of the following
a, a6, aaaa, afsdb, any, apl, axfr, cert, cname,
dhcid, dlv, dname, dnskey, ds, gpos, hinfo, hip,
ipseckey, isdn, ixfr=serial_number, key, keydata, kx, loc,
maila, mailb, mb, md, mf, mg, minfo, mr, mx,
naptr, none, ns, nsap, nsap_ptr, nsec, nsec3,
nsec3param, null, nxt, opt, ptr, px, rp, rrsig,
rt, sig, soa, spf, srv, sshfp, tkey, tsig, txt,
unspec, wks, x25
The default is type "a"
-- opt is one or more of the following
-x (shortcut for in-addr lookups; hostname is an IP address)
-b address (bind to source address)
-y name:key (specify named base64 tsig key)
+vc (TCP mode)
+norecurse (Disable recursive mode)
+short (Disable everything except short form of answer)
+nssearch (Search all authoritative nameservers)
+trace (Trace delegation down from root)
+cdflag (Request server perform no DNSSEC validation)
+dnssec (Request that server sends DNSSEC records)
+multiline (Print records like SOA and DNSKEY in multi-line format)
dig [@server_address] <ip-address> inverse
Description:
Perform a DNS lookup and print the results.
Infoblox >
Infoblox > dig weberlab.de
; <<>> DiG 9.10.2-ECS-M3 <<>> +noedns weberlab.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40294
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;weberlab.de. IN A
;; ANSWER SECTION:
weberlab.de. 60 IN A 87.190.30.116
;; Query time: 11 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Mar 15 17:35:03 CET 2019
;; MSG SIZE rcvd: 45
Infoblox >Expertmode dig:
Infoblox > set expertmode
"Disclaimer: The expert mode CLI commands are designed for advanced users.
Ensure that you have proper knowledge and expertise when using these commands.
Improper usage of commands may affect your system performance and stability."
Expert Mode > dig
; <<>> DiG 9.10.2-ECS-M3 <<>>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50543
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;. IN NS
;; ANSWER SECTION:
. 257092 IN NS i.root-servers.net.
. 257092 IN NS m.root-servers.net.
. 257092 IN NS e.root-servers.net.
. 257092 IN NS h.root-servers.net.
. 257092 IN NS k.root-servers.net.
. 257092 IN NS c.root-servers.net.
. 257092 IN NS g.root-servers.net.
. 257092 IN NS b.root-servers.net.
. 257092 IN NS f.root-servers.net.
. 257092 IN NS d.root-servers.net.
. 257092 IN NS j.root-servers.net.
. 257092 IN NS l.root-servers.net.
. 257092 IN NS a.root-servers.net.
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Mar 15 16:35:33 UTC 2019
;; MSG SIZE rcvd: 239
Expert Mode >
Expert Mode > dig -h
Usage: dig [@global-server] [domain] [q-type] [q-class] {q-opt}
{global-d-opt} host [@local-server] {local-d-opt}
[ host [@local-server] {local-d-opt} [...]]
Where: domain is in the Domain Name System
q-class is one of (in,hs,ch,...) [default: in]
q-type is one of (a,any,mx,ns,soa,hinfo,axfr,txt,...) [default:a]
(Use ixfr=version for type ixfr)
q-opt is one of:
-x dot-notation (shortcut for reverse lookups)
-i (use IP6.INT for IPv6 reverse lookups)
-f filename (batch mode)
-b address[#port] (bind to source address/port)
-p port (specify port number)
-q name (specify query name)
-t type (specify query type)
-c class (specify query class)
-u (display times in usec instead of msec)
-k keyfile (specify tsig key file)
-y [hmac:]name:key (specify named base64 tsig key)
-4 (use IPv4 query transport only)
-6 (use IPv6 query transport only)
-m (enable memory usage debugging)
d-opt is of the form +keyword[=value], where keyword is:
+[no]vc (TCP mode)
+[no]tcp (TCP mode, alternate syntax)
+time=### (Set query timeout) [5]
+tries=### (Set number of UDP attempts) [3]
+retry=### (Set number of UDP retries) [2]
+domain=### (Set default domainname)
+bufsize=### (Set EDNS0 Max UDP packet size)
+ndots=### (Set NDOTS value)
+subnet=addr (Set edns-client-subnet option)
+subnet-source-prefix-only=### (Set edns-client-subnet
option with specified SOURCE PREFIX-LENGTH
while FAMILY and ADDRESS set to 0)
+[no]edns[=###] (Set EDNS version) [0]
+ednsflags=### (Set EDNS flag bits)
+ednsopt=###[:value] (Send specified EDNS option)
+noednsopt (Clear list of +ednsopt options)
+[no]ednsnegotiation (Set EDNS version negotiation)
+[no]search (Set whether to use searchlist)
+[no]showsearch (Search with intermediate results)
+[no]defname (Ditto)
+[no]recurse (Recursive mode)
+[no]ignore (Don't revert to TCP for TC responses.)
+[no]fail (Don't try next server on SERVFAIL)
+[no]besteffort (Try to parse even illegal messages)
+[no]aaonly (Set AA flag in query (+[no]aaflag))
+[no]adflag (Set AD flag in query)
+[no]cdflag (Set CD flag in query)
+[no]cl (Control display of class in records)
+[no]cmd (Control display of command line)
+[no]comments (Control display of comment lines)
+[no]rrcomments (Control display of per-record comments)
+[no]crypto (Control display of cryptographic fields in records)
+[no]question (Control display of question)
+[no]answer (Control display of answer)
+[no]authority (Control display of authority)
+[no]additional (Control display of additional)
+[no]stats (Control display of statistics)
+[no]short (Disable everything except short
form of answer)
+[no]ttlid (Control display of ttls in records)
+[no]all (Set or clear all display flags)
+[no]qr (Print question before sending)
+[no]nssearch (Search all authoritative nameservers)
+[no]identify (ID responders in short answers)
+[no]trace (Trace delegation down from root [+dnssec])
+[no]dnssec (Request DNSSEC records)
+[no]expire (Request time to expire)
+[no]nsid (Request Name Server ID)
+[no]sigchase (Chase DNSSEC signatures)
+trusted-key=#### (Trusted Key when chasing DNSSEC sigs)
+[no]topdown (Do DNSSEC validation top down mode)
+[no]split=## (Split hex/base64 fields into chunks)
+[no]multiline (Print records in an expanded format)
+[no]onesoa (AXFR prints only one soa record)
+[no]keepopen (Keep the TCP socket open between queries)
+[no]opcode[###] (Set the opcode of the request)
global d-opts and servers (before host name) affect all queries.
local d-opts and servers (after host name) affect only that lookup.
-h (print help and exit)
-v (print version and exit)
Expert Mode >
Expert Mode >
Expert Mode > dig weberlab.de
; <<>> DiG 9.10.2-ECS-M3 <<>> weberlab.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5968
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;weberlab.de. IN A
;; ANSWER SECTION:
weberlab.de. 60 IN A 87.190.30.116
;; Query time: 10 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Mar 15 16:36:36 UTC 2019
;; MSG SIZE rcvd: 56
Expert Mode >
Expert Mode >
Expert Mode > set expertmode off
Infoblox >
Traffic Capture & tcpdump
You can easily use the traffic capture within the GUI (Grid -> Grid Manager -> select member -> Traffic Capture):
However, in HA scenarios you can only start/stop and download the traffic capture on the current active node and NOT on the passive one. :( Hence you need to use the CLI. At first you can use the
set traffic_capture ...command along with
show traffic_capture_status. Finally you need to copy the two captures (one from each cluster member) via
set traffic_capture transfer scp <server-ip> <user-name> <user-password>. You cannot specify a server-name but only the mere IP. You can use a dash for the password to have a prompt for it instead of typing it in plain text. Also note that the filenames, unless you specify their names, do NOT tell you on which cluster member they were taken. Example:
Infoblox > set traffic_capture on port all duration 60 Traffic capture started successfully. Infoblox > show traffic_capture_status Traffic capture is running. 4KB captured. <wait until the capture is finished> Infoblox > show traffic_capture_status Traffic capture is stopped. 13KB captured. Infoblox > set traffic_capture transfer scp 87.190.30.112 weberjoh - Enter password: WARNING: This operation may take a long time to complete Do you want to proceed? (y or n):y scp succeeds ib1.weberdns.de_0_2019-02-19-12-31-03_tcpdumpLog.tar.gz is uploaded to scp server 87.190.30.112 successfully
Please note that if you’re capturing on “All” interfaces instead of a single one such as LAN1 or HA, you will loose the original Ethernet frame header. Wireshark will only display a “Linux cooked capture” then which includes only the source MAC address but not the destination MAC and so on.
tcpdump
Another way of troubleshooting network/DNS/DHCP issues is to use tcpdump in the hidden expertmode CLI section. With this you can use tcpdump as always except that you can’t write (-w filename) the output somewhere. Hence I am using it with specific capture filters, -v or even -vv, and PuTTY logging. ;)
You need to set the interface via “-i”. The NICs are:
- NIC1 = eth0 = MGMT
- NIC2 = eth1 = LAN1
- NIC3 = eth2 = HA
- NIC4 = eth3 = LAN2
set expertmode tcpdump -i eth2 #or with some options and capture filters: tcpdump -i eth2 -vv "host 192.168.0.1 or 172.16.22.53" Ctrl+c #to stop set expertmode offSample run:
Infoblox > set expertmode
"Disclaimer: The expert mode CLI commands are designed for advanced users.
Ensure that you have proper knowledge and expertise when using these commands.
Improper usage of commands may affect your system performance and stability."
Expert Mode >
Expert Mode > tcpdump
Please specify the interface with the -i option.
Expert Mode > tcpdump -i eth2 -v "host 87.190.30.114 or 213.61.29.182"
tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size 262144 bytes
16:42:30.023465 IP (tos 0x0, ttl 64, id 9702, offset 0, flags [none], proto UDP (17), length 71)
192.0.2.177.19826 > 213.61.29.182.53: 8833 [1au] A? pa.weberlab.de. (43)
16:42:30.031405 IP (tos 0x0, ttl 57, id 19465, offset 0, flags [none], proto UDP (17), length 1303)
213.61.29.182.53 > 192.0.2.177.19826: 8833*- 2/3/7 pa.weberlab.de. A 193.24.227.9, pa.weberlab.de. RRSIG (1275)
16:42:30.034387 IP (tos 0x0, ttl 64, id 41623, offset 0, flags [none], proto UDP (17), length 71)
192.0.2.177.34258 > 87.190.30.114.53: 20807 [1au] AAAA? pa.weberlab.de. (43)
16:42:30.044030 IP (tos 0x0, ttl 55, id 19194, offset 0, flags [none], proto UDP (17), length 836)
87.190.30.114.53 > 192.0.2.177.34258: 20807*- 0/4/1 (808)
^C
4 packets captured
4 packets received by filter
0 packets dropped by kernel
Expert Mode > set expertmode off
Infoblox >
DNS Related
Aka standard BIND output:
show dns stats show dns cache [name-of-the-view] show dns cache_ex /regex/ [name-of-the-view] show dns cache_size [name-of-the-view]
Note that regex version of “show dns cache_ex” which is quite useful. Sample:
Infoblox > show dns cache_ex /weberlab/
weberlab.de. 86396 DS 13179 10 2 (
weberlab.de. 86396 RRSIG DS 8 2 86400 (
weberlab.de. 56 DNSKEY 257 3 10 (
weberlab.de. 56 DNSKEY 256 3 10 (
weberlab.de. 56 RRSIG DNSKEY 10 2 60 (
20190505113757 20190405103757 13179 weberlab.de.
weberlab.de. 56 RRSIG DNSKEY 10 2 60 (
20190505113757 20190405103757 36935 weberlab.de.
fg2.weberlab.de. 56 A 194.247.4.10
fg2.weberlab.de. 56 RRSIG A 10 3 60 (
20190505105415 20190405103758 36935 weberlab.de.
Infoblox >
Anycast Routing (OSPF, BGP)
Easy one:
show ipv6_bgp [ route | neighbor | summary | community | config ] show bgp [ route | neighbor | summary | config ] show ipv6_ospf [interface | neighbor | database | route | config ] show ospf [ interface | neighbor | database | route | config ]
Maintenance Mode
There’s a hidden CLI mode for maintenance purposes. You can enter it via:
set maintenancemode
Here you can show/delete backups and core dumps:
show backup grid
delete backup grid { all | filename }
show coresummary
show cores
delete cores { all | filename }Sample for showing/deleting a backup:
Infoblox > set maintenancemode Maintenance Mode > show backup grid Backup files present on the system Filename Size ----------------------------------------------------- BACKUP_2019_02_02_03_00.tar.gz 17367 k BACKUP_2019_03_07_03_30.tar.gz 17842 k BACKUP_2019_03_08_03_30.tar.gz 17854 k BACKUP_2019_03_09_03_30.tar.gz 17854 k BACKUP_2019_03_10_03_30.tar.gz 17854 k BACKUP_2019_03_11_03_30.tar.gz 17854 k BACKUP_2019_03_12_03_30.tar.gz 17857 k BACKUP_2019_03_13_03_30.tar.gz 17879 k BACKUP_2019_03_14_03_31.tar.gz 17889 k BACKUP_2019_03_15_03_30.tar.gz 17899 k Maintenance Mode > Maintenance Mode > Maintenance Mode > delete backup grid BACKUP_2019_02_02_03_00.tar.gz Backup file BACKUP_2019_02_02_03_00.tar.gz deleted Maintenance Mode > Maintenance Mode > set maintenancemode off Infoblox >
Sample of coresummary on the Grid master (without any files ;)):
Infoblox > set maintenancemode Maintenance Mode > show coresummary +-------------------------------------------+-----------+-----------------------+ | Member|Cores count| Latest core file| +-------------------------------------------+-----------+-----------------------+ | infoblox.weberlab.de (194.247.5.15)| 0| None| +-------------------------------------------+-----------+-----------------------+ | ib1.weberdns.de (193.24.227.239)| 0| None| +-------------------------------------------+-----------+-----------------------+ | ib2.weberdns.de (194.247.5.16)| 0| None| +-------------------------------------------+-----------+-----------------------+ | ib3-report.weberdns.de (194.247.5.17)| 0| None| +-------------------------------------------+-----------+-----------------------+ | ib4-recursive.weberdns.de (193.24.227.240)| 0| None| +-------------------------------------------+-----------+-----------------------+ Maintenance Mode > Maintenance Mode > show cores Core files present on the system Filename Size Date ------------------------------------------------------------------------------ There are no core files. Maintenance Mode > Maintenance Mode > set maintenancemode off Infoblox >
Furthermore you can watch a process list in this maintenance mode via:
show process refresh {interval} {dns | dhcp | snmp | grid | mssync}Sample run:
Infoblox > set maintenancemode Maintenance Mode > Maintenance Mode > show process refresh 2 dns Wed Apr 10 18:03:47 2019 Command invoked ==> show process refresh 2 dns PID VIRT(kb) RES(kb) SHR(kb) %CPU %MEM Uptime Command 22162 7898m 29m 10m 0.0 0.2 0:00.03 named 22163 7898m 29m 10m 0.0 0.2 0:00.08 named 22164 7898m 29m 10m 0.0 0.2 0:00.11 named 22165 7898m 29m 10m 0.0 0.2 0:00.04 named 22166 7898m 29m 10m 0.0 0.2 0:00.02 named 22176 7898m 29m 10m 0.0 0.2 0:00.02 named 22190 7898m 29m 10m 0.0 0.2 0:00.00 named 22198 7898m 29m 10m 0.0 0.2 0:00.03 named [Press <enter> to return to prompt] q Maintenance Mode > Maintenance Mode > set maintenancemode off Infoblox >
IPMI aka LOM
Using the Intelligent Platform Management Interface port which is called Lights Out Management on Infoblox you can power on/off the device, get the sensor values, read out the system event log, and finally open a serial console session (which is great!). I am using ipmitool on Linux:
sudo apt-get install ipmitool. Here are some samples:
Power off/on/status
troublemaker@ibp02troublet01:~$ ipmitool -H 192.168.102.35 -U ThisIsTheUser -P ThisIsThePassword -L OPERATOR -I lanplus power off Chassis Power Control: Down/Off troublemaker@ibp02troublet01:~$ ipmitool -H 192.168.102.35 -U ThisIsTheUser -P ThisIsThePassword -L OPERATOR -I lanplus power on Chassis Power Control: Up/On troublemaker@ibp02troublet01:~$ ipmitool -H 192.168.102.35 -U ThisIsTheUser -P ThisIsThePassword -L OPERATOR -I lanplus power status Chassis Power is on
Sensors
troublemaker@ibp02troublet01:~$ ipmitool -H 192.168.102.35 -U ThisIsTheUser -P ThisIsThePassword -L OPERATOR -I lanplus sensor CPU Temp | 28.000 | degrees C | ok | 0.000 | 0.000 | 0.000 | 95.000 | 100.000 | 100.000 PCH Temp | 29.000 | degrees C | ok | 0.000 | 5.000 | 10.000 | 90.000 | 95.000 | 100.000 System Temp | 24.000 | degrees C | ok | -10.000 | -5.000 | 0.000 | 80.000 | 85.000 | 90.000 Peripheral Temp | 23.000 | degrees C | ok | -10.000 | -5.000 | 0.000 | 80.000 | 85.000 | 90.000 VcpuVRM Temp | 38.000 | degrees C | ok | -5.000 | 0.000 | 5.000 | 95.000 | 100.000 | 105.000 DIMMA1 Temp | na | | na | na | na | na | na | na | na DIMMA2 Temp | 27.000 | degrees C | ok | -5.000 | 0.000 | 5.000 | 80.000 | 85.000 | 90.000 DIMMB1 Temp | na | | na | na | na | na | na | na | na DIMMB2 Temp | 27.000 | degrees C | ok | -5.000 | 0.000 | 5.000 | 80.000 | 85.000 | 90.000 FAN1 | 9700.000 | RPM | ok | 300.000 | 500.000 | 700.000 | 25300.000 | 25400.000 | 25500.000 FAN2 | 9500.000 | RPM | ok | 300.000 | 500.000 | 700.000 | 25300.000 | 25400.000 | 25500.000 FAN3 | 9500.000 | RPM | ok | 300.000 | 500.000 | 700.000 | 25300.000 | 25400.000 | 25500.000 FAN4 | 9200.000 | RPM | ok | 300.000 | 500.000 | 700.000 | 25300.000 | 25400.000 | 25500.000 FAN5 | 9500.000 | RPM | ok | 300.000 | 500.000 | 700.000 | 25300.000 | 25400.000 | 25500.000 FAN6 | 9300.000 | RPM | ok | 300.000 | 500.000 | 700.000 | 25300.000 | 25400.000 | 25500.000 12V | 12.000 | Volts | ok | 10.173 | 10.299 | 10.740 | 12.945 | 13.260 | 13.386 5VCC | 4.948 | Volts | ok | 4.246 | 4.298 | 4.480 | 5.390 | 5.546 | 5.598 3.3VCC | 3.299 | Volts | ok | 2.789 | 2.823 | 2.959 | 3.554 | 3.656 | 3.690 VBAT | 3.103 | Volts | ok | 2.407 | 2.494 | 2.610 | 3.509 | 3.596 | 3.712 Vcpu | 0.804 | Volts | ok | 0.111 | 0.111 | 0.111 | 1.596 | 1.758 | 1.776 VDIMMAB | 1.173 | Volts | ok | 0.948 | 0.975 | 1.047 | 1.344 | 1.425 | 1.443 0.95V VCCIO | 0.960 | Volts | ok | 0.870 | 0.897 | 0.942 | 1.194 | 1.221 | 1.248 1.5VSB | 1.509 | Volts | ok | 1.320 | 1.347 | 1.401 | 1.644 | 1.671 | 1.698 5VSB | 4.896 | Volts | ok | 4.246 | 4.298 | 4.480 | 5.390 | 5.546 | 5.598 3.3VSB | 3.214 | Volts | ok | 2.789 | 2.823 | 2.959 | 3.554 | 3.656 | 3.690 1.05V VCCSA | 1.050 | Volts | ok | 0.861 | 0.888 | 0.960 | 1.086 | 1.149 | 1.176 1.2V BMC | 1.200 | Volts | ok | 1.020 | 1.047 | 1.092 | 1.344 | 1.371 | 1.398 1.0V PCH | 0.996 | Volts | ok | 0.870 | 0.897 | 0.942 | 1.194 | 1.221 | 1.248 Chassis Intru | 0x0 | discrete | 0x0000| na | na | na | na | na | na PS1 Status | 0x1 | discrete | 0x0100| na | na | na | na | na | na PS2 Status | 0x1 | discrete | 0x0100| na | na | na | na | na | na
System Event Log
troublemaker@ibp02troublet01:~$ ipmitool -H 192.168.102.35 -U ThisIsTheUser -P ThisIsThePassword -L OPERATOR -I lanplus sel list 1 | 01/25/2019 | 12:24:48 | Unknown #0xff | | Asserted 2 | 01/25/2019 | 12:26:18 | Power Supply #0xc9 | Failure detected () | Asserted 3 | 01/25/2019 | 12:26:18 | Power Supply #0xc9 | Power Supply AC lost () | Asserted 4 | 01/25/2019 | 12:27:04 | Power Supply #0xc9 | Failure detected () | Deasserted 5 | 01/25/2019 | 12:27:04 | Power Supply #0xc9 | Power Supply AC lost () | Deasserted 6 | 02/13/2019 | 12:27:11 | Power Supply #0xc9 | Failure detected () | Asserted 7 | 02/13/2019 | 12:27:11 | Power Supply #0xc9 | Power Supply AC lost () | Asserted 8 | 02/13/2019 | 12:30:29 | Power Supply #0xc9 | Failure detected () | Deasserted 9 | 02/13/2019 | 12:30:29 | Power Supply #0xc9 | Power Supply AC lost () | Deasserted a | 02/13/2019 | 12:32:57 | Power Supply #0xc8 | Failure detected () | Asserted b | 02/13/2019 | 12:32:57 | Power Supply #0xc8 | Power Supply AC lost () | Asserted c | 02/13/2019 | 12:37:28 | Power Supply #0xc8 | Failure detected () | Deasserted d | 02/13/2019 | 12:37:28 | Power Supply #0xc8 | Power Supply AC lost () | Deasserted
Serial Console aka Serial over LAN (SOL)
This is very cool. Terminate the session with
~.:
troublemaker@ibp02troublet01:~$ ipmitool -H 192.168.102.35 -U ThisIsTheUser -P ThisIsThePassword -L OPERATOR -I lanplus sol activate
[SOL Session operational. Use ~? for help]
Disconnect NOW if you have not been expressly authorized to use this system.
login: admin_weberjoh
password:
Infoblox NIOS Release 8.3.3-380481 (64bit)
Copyright (c) 1999-2017 Infoblox Inc. All Rights Reserved.
type 'help' for more information
Infoblox > show status
Grid Status: ID Grid Master
HA Status: Passive
Hostname: dnsrz.weberlab.intern
Infoblox >
Infoblox > exit
Good Bye
Disconnect NOW if you have not been expressly authorized to use this system.
login:
~. [terminated ipmitool]
troublemaker@ibp02troublet01:~$
troublemaker@ibp02troublet01:~$
IPMI on Windows
I wasn’t able to use all IPMI commands that easy on Windows. However, using ipmiutil I was able to power off and on the devices:
X:\software\ipmi util\ipmiutil-3.1.3-win64>ipmiutil power -d -N 192.168.102.35 -U ThisIsTheUser -P ThisIsThePassword -V 3 ipmiutil reset ver 3.13 Connecting to node 192.168.102.35 -- BMC version 2.38, IPMI version 2.0 Power State = 00 (S0: working) ipmiutil reset: powering down ... chassis_reset(0) ok ipmiutil reset: IPMI_Reset ok ipmiutil power, completed successfully X:\software\ipmi util\ipmiutil-3.1.3-win64>ipmiutil power -u -N 192.168.102.35 -U ThisIsTheUser -P ThisIsThePassword -V 3 ipmiutil reset ver 3.13 Connecting to node 192.168.102.35 -- BMC version 2.38, IPMI version 2.0 Power State = 05 (S5: soft off) ipmiutil reset: powering up ... chassis_reset(1) ok ipmiutil reset: IPMI_Reset ok ipmiutil power, completed successfully
Support Bundle
Always good to know: Download of the support bundle for every single member via Grid -> Grid Manager -> Members -> select member -> Download -> Support Bundle:
Factory Reset
In order to reset the configuration to its defaults you can use one of these commands:
reset database #delete config but keep network settings and licenses reset all #delete config but keep licenses reset all licenses #delete EVERYTHING
Pound It. Noggin’. Cu!
Featured image “Screwdrivers on white background. Top view” by Marco Verch is licensed under CC BY 2.0.