IEKANALYZER(8)

πŸ’… IEKANALYZER(8) β€” like, the ipmiutil_ekanalyzer page, bestie

okay so welcome to the System Manager's Manual entry for ipmiutil_ekanalyzer, and no cap, this one's a whole journey πŸŽ€


✨ NAME ✨

ipmiutil_ekanalyzer β€” run FRU-Ekeying analyzer with FRU files πŸ¦‹


✨ SYNOPSIS ✨

ipmiutil ekanalyzer [-mx -NPRUEFJTVY] commands (deprecated, see ifru instead)
heads up bestie: this whole thing is deprecated, and the page literally tells you to go look at ifru instead. it's giving "we keep the old thing around for the vibes" πŸ’€

✨ DESCRIPTION ✨

So ipmiutil ekanalyzer is this program that analyzes FRU Ekeying information from files saved from PICMG IPMI systems. literally what it does πŸ’…

Big warning first though: this function is disabled by default in ipmiutil-2.9.9 and later. like, not me being dramatic, it's just off unless you turn it on 🌸

The whole invocation looks like this:

ekanalyzer command xx=filename1 xx=filename2 [rc=filename3]
NOTE: this command can support a maximum of 8 files per command line. eight. that's the cap. don't push it πŸ™ˆ

Here's the cast of characters, aka what the filenames actually mean:

  • filename1 β€” a binary file that stores FRU data of a Carrier or an AMC module.
  • filename2 β€” a binary file that stores FRU data of an AMC module. ✨ These binary files can be generated from this command:
ipmiutil fru -i id -d filename
  • filename3 β€” a configuration file used for configuring On-Carrier Device ID or OEM GUID. This file is optional, so no pressure 🫢

And xx? That's the file type tag. It can take the following values:

  • oc β€” On-Carrier device
  • a1 β€” AMC slot A1
  • a2 β€” AMC slot A2
  • a3 β€” AMC slot A3
  • a4 β€” AMC slot A4
  • b1 β€” AMC slot B1
  • b2 β€” AMC slot B2
  • b3 β€” AMC slot B3
  • b4 β€” AMC slot B4
  • sm β€” Shelf Manager

✨ OPTIONS ✨

the flags, the flags, the flags πŸŽ€ every single one, right here:

  • -m 002000 β€” Show FRU for a specific MC (e.g. bus 00, sa 20, lun 00). This could be used for PICMG or ATCA blade systems. The trailing character, if present, indicates SMI addressing if s, or IPMB addressing if i or not present. iykyk πŸ”₯
  • -x β€” Causes extra debug messages to be displayed. more words = more knowledge, periodt.
  • -N nodename β€” Nodename or IP address of the remote target system. If a nodename is specified, the IPMI LAN interface is used. Otherwise the local system management interface is used.
  • -P/-R rmt_pswd β€” Remote password for the nodename given. The default is a null password.
  • -U rmt_user β€” Remote username for the nodename given. The default is a null username.
  • -E β€” Use the remote password from the environment variable IPMI_PASSWORD. 🧚
  • -F drv_t β€” Force the driver type to one of the following: imb, va, open, gnu, landesk, lan, lan2, lan2i, kcs, smb. Note that lan2i means lan2 with intelplus. The default is to detect any available driver type and use it.
  • -J β€” Use the specified LanPlus cipher suite (0 thru 17): 0=none/none/none, 1=sha1/none/none, 2=sha1/sha1/none, 3=sha1/sha1/cbc128, 4=sha1/sha1/xrc4_128, 5=sha1/sha1/xrc4_40, 6=md5/none/none, ... 14=md5/md5/xrc4_40. Default is 3.
  • -T β€” Use a specified IPMI LAN Authentication Type: 0=None, 1=MD2, 2=MD5, 4=Straight Password, 5=OEM.
  • -V β€” Use a specified IPMI LAN privilege level: 1=Callback level, 2=User level, 3=Operator level, 4=Administrator level (default), 5=OEM level.
  • -Y β€” Yes, do prompt the user for the IPMI LAN remote password. The alternatives for the password are -E or -P.

✨ COMMANDS ✨

the available commands for ekanalyzer are, and buckle up because the examples are long:

carrier (default) oc=filename1 oc=filename2 ...

Display point to point physical connectivity between carriers and AMC modules. πŸ’–

Example:

# ipmiutil ekanalyzer print carrier oc=fru oc=carrierfru
From Carrier file: fru
   Number of AMC bays supported by Carrier: 2
   AMC slot B1 topology:
      Port 0 =====> On Carrier Device ID 0, Port 16
      Port 1 =====> On Carrier Device ID 0, Port 12
      Port 2 =====> AMC slot B2, Port 2
   AMC slot B2 topology:
      Port 0 =====> On Carrier Device ID 0, Port 3
      Port 2 =====> AMC slot B1, Port 2
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
From Carrier file: carrierfru
   On Carrier Device ID 0 topology:
      Port 0 =====> AMC slot B1, Port 4
      Port 1 =====> AMC slot B1, Port 5
      Port 2 =====> AMC slot B2, Port 6
      Port 3 =====> AMC slot B2, Port 7
   AMC slot B1 topology:
      Port 0 =====> AMC slot B2, Port 0
   AMC slot B1 topology:
      Port 1 =====> AMC slot B2, Port 1
   Number of AMC bays supported by Carrier: 2

(yes it says AMC slot B1 topology: twice, that's literally what the manual shows, don't come for me πŸ™ˆ)

power xx=filename1 xx=filename2 ...

Display power supply information between carrier and AMC modules. ⚑

all xx=filename xx=filename ...

Display both physical connectivity and power supply of each carrier and AMC modules.

🌈 frushow xx=filename

Convert a binary FRU file into human readable text format. Use the -v option to get more display information. πŸ‘‘

🌈 summary [match | unmatch | all]

match (default) xx=filename xx=filename ...

Display only matched results of Ekeying match between an On-Carrier device and an AMC module or between 2 AMC modules.

Example:

# ipmiutil ekanalyzer summary match oc=fru b1=amcB1 a2=amcA2
On-Carrier Device vs AMC slot B1
 AMC slot B1 port 0 ==> On-Carrier Device 0 port 16
  Matching Result
  From On-Carrier Device ID 0
    Channel ID 11 || Lane 0: enable
    Link Type: AMC.2 Ethernet
    Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link
    Link Group ID: 0 || Link Asym. Match: exact match
  To AMC slot B1
    Channel ID 0 || Lane 0: enable
    Link Type: AMC.2 Ethernet
    Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link
    Link Group ID: 0 || Link Asym. Match: exact match
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 AMC slot B1 port 1 ==> On-Carrier Device 0 port 12
  Matching Result
  From On-Carrier Device ID 0
    Channel ID 6 || Lane 0: enable
    Link Type: AMC.2 Ethernet
    Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link
    Link Group ID: 0 || Link Asym. Match: exact match
  To AMC slot B1
    Channel ID 1 || Lane 0: enable
    Link Type: AMC.2 Ethernet
    Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link
    Link Group ID: 0 || Link Asym. Match: exact match
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
On-Carrier Device vs AMC slot A2
 AMC slot A2 port 0 ==> On-Carrier Device 0 port 3
  Matching Result
  From On-Carrier Device ID 0
    Channel ID 9 || Lane 0: enable
    Link Type: AMC.2 Ethernet
    Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link
    Link Group ID: 0 || Link Asym. Match: exact match
  To AMC slot A2
    Channel ID 0 || Lane 0: enable
    Link Type: AMC.2 Ethernet
    Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link
    Link Group ID: 0 || Link Asym. Match: exact match
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
AMC slot B1 vs AMC slot A2
 AMC slot A2 port 2 ==> AMC slot B1 port 2
  Matching Result
  From AMC slot B1
    Channel ID 2 || Lane 0: enable
    Link Type: AMC.3 Storage
    Link Type extension: Serial Attached SCSI (SAS/SATA)
    Link Group ID: 0 || Link Asym. Match: FC or SAS interface {exact match}
  To AMC slot A2
    Channel ID 2 || Lane 0: enable
    Link Type: AMC.3 Storage
    Link Type extension: Serial Attached SCSI (SAS/SATA)
    Link Group ID: 0 || Link Asym. Match: FC or SAS interface {exact match}
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

unmatch xx=filename xx=filename ...

Display the unmatched results of Ekeying match between an On-Carrier device and an AMC module or between 2 AMC modules. πŸ’”

all xx=filename xx=filename ...

Display both matched result and unmatched results of Ekeying match between two cards or two modules. the whole picture, bestie 🌸


✨ SEE ALSO ✨

ialarms(8) iconfig(8) icmd(8) idiscover(8) ievents(8) ifirewall(8) ifru(8) ifruset(8) ifwum(8) igetevent(8) ihealth(8) ihpm(8) ilan(8) ipicmg(8) ireset(8) isel(8) isensor(8) iserial(8) isol(8) isunoem(8) iwdt(8) ipmiutil(8) ipmi_port(8)

the whole friend group, honestly 🫢


✨ WARNINGS ✨

See http://ipmiutil.sourceforge.net/ for the latest version of ipmiutil and any bug fix list. πŸ”₯


Copyright (C) 2009 Kontron America, Inc.

See the file COPYING in the distribution for more details regarding redistribution.

This utility is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY. 😭


πŸ‘‘ AUTHOR πŸ‘‘

So this whole thing was written by Andy Cress β€” <arcress at users.sourceforge.net> 🫢 like, the actual human behind the analyze-iness. Ngl, absolute legend behaviour. If you've got thoughts, glowing or otherwise, that's the inbox πŸ’Œ


And that's the whole page, bestie β€” you made it to the end πŸŽ€ This edition is Version 1.0, dated 09 Sep 2010, living its best life under the name IEKANALYZER(8) in the manual pages. Iconic. Periodt. πŸ’…βœ¨ 🌸

πŸ“¦ where this page comes from