{ "content": [ { "type": "text", "text": "# openipmi_conparms(7) (man)\n\n**Summary:** openipmicmdparms - Connection parmeters for OpenIPMI\n\n**Synopsis:** smi smi-num\nlan [-U username] [-P password] [-p[2] port] [-A authtype] [-L privilege] [-s] [-Ra auth alg]\n[-Ri integ alg] [-Rc conf algo] [-Rl] [-Rk bmc key] [-H hackname] host [ host]\n\n## Flags\n\n| Flag | Long | Arg | Description |\n|------|------|-----|-------------|\n| -U | — | — | Use the given username for the LAN connection. If none is given, then no username is used. |\n| -P | — | — | The password to use for the connection. If none is given, the user is assumed to have an empty password |\n| -p | — | — | The UCP port to connect to. This defaults to the standard 623 port, so it is not nec‐ essary unless a special port is re |\n| -A | — | — | The authentication type to use, one of rmcp+, md5, md2, straight, or none. If you don't supply this, the most secure one |\n| -L | — | — | The privilege to use for the connection. Lower privileges cannot execute some com‐ mands. Privileges are: callback, user |\n| — | — | — | Set the RMCP+ authentication algorithm to use. Options are: bmcpick, rakpnone, rakphmacsha1, and rakphmacmd5. The bmcpic |\n| — | — | — | The RMCP+ integrity algorithm to use. This ensures that the data has not be altered between the sender and receiver. Val |\n| — | — | — | The RMCP+ confidentiality (encryption) algorithm to use. This keeps evesdroppers from seeing the data. Valid values are: |\n| — | — | — | the username. This allows the same name to have different passwords with different privilege levels. |\n| — | — | — | If the system requires two-key lookups, this specifies the second key (the BMC key) to use. This is ignored if two-key l |\n| -H | — | — | Well, it always happens. Things in the field don't work quite like they are supposed to. There was some vagueness in the |\n| -s | — | — | dresses/ports that are equivalent. If this is specified, a second host must be sup‐ plied. This is not the same as two c |\n\n## See Also\n\n- ipmish(8)\n- openipmicmd(8)\n- solterm(1)\n\n## Section Outline\n\n- **NAME** (3 lines)\n- **SYNOPSIS** (6 lines)\n- **DESCRIPTION** (4 lines)\n- **OPTIONS** (5 lines) — 12 subsections\n - -U (4 lines)\n - -P (4 lines)\n - -p (5 lines)\n - -A (5 lines)\n - -L (5 lines)\n - -Ra (5 lines)\n - -Ri (6 lines)\n - -Rc (6 lines)\n - -Rl (4 lines)\n - -Rk (4 lines)\n - -H (17 lines)\n - -s (14 lines)\n- **SEE ALSO** (3 lines)\n- **KNOWN PROBLEMS** (3 lines)\n- **AUTHOR** (5 lines)\n\n## Full Content\n\n### NAME\n\nopenipmicmdparms - Connection parmeters for OpenIPMI\n\n### SYNOPSIS\n\nsmi smi-num\n\nlan [-U username] [-P password] [-p[2] port] [-A authtype] [-L privilege] [-s] [-Ra auth alg]\n[-Ri integ alg] [-Rc conf algo] [-Rl] [-Rk bmc key] [-H hackname] host [ host]\n\n### DESCRIPTION\n\nThe connection parameters for OpenIPMI vary depending on the connection type. This document\ndescribes the standard connection types; others may be available from OEMs.\n\n### OPTIONS\n\nsmi-num\nThe SMI interface for the local connection. There may be more than one BMC connection\non a system and they are generally numbered, like /dev/ipmi0, /dev/ipmi1, etc.\n\n#### -U\n\nUse the given username for the LAN connection. If none is given, then no username is\nused.\n\n#### -P\n\nThe password to use for the connection. If none is given, the user is assumed to have\nan empty password\n\n#### -p\n\nThe UCP port to connect to. This defaults to the standard 623 port, so it is not nec‐\nessary unless a special port is required. Note that since you can have two connec‐\ntions (hosts), -p is for the first host and -p2 is for the second host.\n\n#### -A\n\nThe authentication type to use, one of rmcp+, md5, md2, straight, or none. If you\ndon't supply this, the most secure one available is chosen, in the order given in the\nprevious list.\n\n#### -L\n\nThe privilege to use for the connection. Lower privileges cannot execute some com‐\nmands. Privileges are: callback, user, operator, admin, and oem. The default is ad‐‐\nmin.\n\n#### -Ra\n\nSet the RMCP+ authentication algorithm to use. Options are: bmcpick, rakpnone,\nrakphmacsha1, and rakphmacmd5. The bmcpick option is used by default, which means\nthe BMC picks the algorithm it wants to use.\n\n#### -Ri\n\nThe RMCP+ integrity algorithm to use. This ensures that the data has not be altered\nbetween the sender and receiver. Valid options are: bmcpick, none, hmacsha1,\nhmacmd5, and md5. The bmcpick option is used by default, which means the BMC picks\nthe algorithm it wants to use.\n\n#### -Rc\n\nThe RMCP+ confidentiality (encryption) algorithm to use. This keeps evesdroppers from\nseeing the data. Valid values are: bmcpick, aescbc128, xrc4128, and xrc40. The\nbmcpick option is used by default, which means the BMC picks the algorithm it wants to\nuse.\n\n#### -Rl\n\nthe username. This allows the same name to have different passwords with different\nprivilege levels.\n\n#### -Rk\n\nIf the system requires two-key lookups, this specifies the second key (the BMC key) to\nuse. This is ignored if two-key lookups are not enabled by the BMC.\n\n#### -H\n\nWell, it always happens. Things in the field don't work quite like they are supposed\nto. There was some vagueness in the first IPMI specs and different vendors inter‐\npreted RMCP+ in different ways. This allows different options to be supported. Try\ndifferent hacks if your RMCP+ systems don't authenticate properly. These are:\n\n\nrakp3wrongrolem\nSome systems use the incorrect Role(m) field in a specific authentication mes‐\nsage (the RAKP3 message). This is a common problem.\n\n\nrmcppintegsik\nThe original IPMI 2.0 spec specified the incorrect key to use for the integrity\nkey. This forces use of the Session Initiation Key. The default is to use\nK(1)\n\n#### -s\n\ndresses/ports that are equivalent. If this is specified, a second host must be sup‐\nplied. This is not the same as two connections to two different BMCs. This must be a\nconnection to the same BMC.\n\n\nhost The IP address (either by name lookup or specified directly) to connect to. If the -s\nis specified, two hosts must be supplied.\n\n\nThe -Ra, -Ri, -Rc, -Rk and -Rl options only apply to RMCP+ connections and will be ignored if\nthe connection does not support RMCP+ or if a non-RMCP+ authentication type is specified.\n\n### SEE ALSO\n\nipmish(8), openipmicmd(8), solterm(1)\n\n### KNOWN PROBLEMS\n\nThis is excessively complicated, but the defaults should be good.\n\n### AUTHOR\n\nCorey Minyard \n\n\n\nOpenIPMI 05/13/03 openipmiconparms(7)\n\n" } ], "structuredContent": { "command": "openipmi_conparms", "section": "7", "mode": "man", "summary": "openipmicmdparms - Connection parmeters for OpenIPMI", "synopsis": "smi smi-num\nlan [-U username] [-P password] [-p[2] port] [-A authtype] [-L privilege] [-s] [-Ra auth alg]\n[-Ri integ alg] [-Rc conf algo] [-Rl] [-Rk bmc key] [-H hackname] host [ host]", "flags": [ { "flag": "-U", "long": null, "arg": null, "description": "Use the given username for the LAN connection. If none is given, then no username is used." }, { "flag": "-P", "long": null, "arg": null, "description": "The password to use for the connection. If none is given, the user is assumed to have an empty password" }, { "flag": "-p", "long": null, "arg": null, "description": "The UCP port to connect to. This defaults to the standard 623 port, so it is not nec‐ essary unless a special port is required. Note that since you can have two connec‐ tions (hosts), -p is for the first host and -p2 is for the second host." }, { "flag": "-A", "long": null, "arg": null, "description": "The authentication type to use, one of rmcp+, md5, md2, straight, or none. If you don't supply this, the most secure one available is chosen, in the order given in the previous list." }, { "flag": "-L", "long": null, "arg": null, "description": "The privilege to use for the connection. Lower privileges cannot execute some com‐ mands. Privileges are: callback, user, operator, admin, and oem. The default is ad‐‐ min." }, { "flag": "", "long": null, "arg": null, "description": "Set the RMCP+ authentication algorithm to use. Options are: bmcpick, rakpnone, rakphmacsha1, and rakphmacmd5. The bmcpick option is used by default, which means the BMC picks the algorithm it wants to use." }, { "flag": "", "long": null, "arg": null, "description": "The RMCP+ integrity algorithm to use. This ensures that the data has not be altered between the sender and receiver. Valid options are: bmcpick, none, hmacsha1, hmacmd5, and md5. The bmcpick option is used by default, which means the BMC picks the algorithm it wants to use." }, { "flag": "", "long": null, "arg": null, "description": "The RMCP+ confidentiality (encryption) algorithm to use. This keeps evesdroppers from seeing the data. Valid values are: bmcpick, aescbc128, xrc4128, and xrc40. The bmcpick option is used by default, which means the BMC picks the algorithm it wants to use." }, { "flag": "", "long": null, "arg": null, "description": "the username. This allows the same name to have different passwords with different privilege levels." }, { "flag": "", "long": null, "arg": null, "description": "If the system requires two-key lookups, this specifies the second key (the BMC key) to use. This is ignored if two-key lookups are not enabled by the BMC." }, { "flag": "-H", "long": null, "arg": null, "description": "Well, it always happens. Things in the field don't work quite like they are supposed to. There was some vagueness in the first IPMI specs and different vendors inter‐ preted RMCP+ in different ways. This allows different options to be supported. Try different hacks if your RMCP+ systems don't authenticate properly. These are: rakp3wrongrolem Some systems use the incorrect Role(m) field in a specific authentication mes‐ sage (the RAKP3 message). This is a common problem. rmcppintegsik The original IPMI 2.0 spec specified the incorrect key to use for the integrity key. This forces use of the Session Initiation Key. The default is to use K(1)" }, { "flag": "-s", "long": null, "arg": null, "description": "dresses/ports that are equivalent. If this is specified, a second host must be sup‐ plied. This is not the same as two connections to two different BMCs. This must be a connection to the same BMC. host The IP address (either by name lookup or specified directly) to connect to. If the -s is specified, two hosts must be supplied. The -Ra, -Ri, -Rc, -Rk and -Rl options only apply to RMCP+ connections and will be ignored if the connection does not support RMCP+ or if a non-RMCP+ authentication type is specified." } ], "examples": [], "see_also": [ { "name": "ipmish", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/ipmish/8/json" }, { "name": "openipmicmd", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/openipmicmd/8/json" }, { "name": "solterm", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/solterm/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 3, "subsections": [] }, { "name": "SYNOPSIS", "lines": 6, "subsections": [] }, { "name": "DESCRIPTION", "lines": 4, "subsections": [] }, { "name": "OPTIONS", "lines": 5, "subsections": [ { "name": "-U", "lines": 4, "flag": "-U" }, { "name": "-P", "lines": 4, "flag": "-P" }, { "name": "-p", "lines": 5, "flag": "-p" }, { "name": "-A", "lines": 5, "flag": "-A" }, { "name": "-L", "lines": 5, "flag": "-L" }, { "name": "-Ra", "lines": 5 }, { "name": "-Ri", "lines": 6 }, { "name": "-Rc", "lines": 6 }, { "name": "-Rl", "lines": 4 }, { "name": "-Rk", "lines": 4 }, { "name": "-H", "lines": 17, "flag": "-H" }, { "name": "-s", "lines": 14, "flag": "-s" } ] }, { "name": "SEE ALSO", "lines": 3, "subsections": [] }, { "name": "KNOWN PROBLEMS", "lines": 3, "subsections": [] }, { "name": "AUTHOR", "lines": 5, "subsections": [] } ] } }