You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/ipmDevGlobal_cmd.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ For example:
102
102
Cold Reset Command
103
103
~~~~~~~~~~~~~~~~~~
104
104
105
-
This command directs the **Target** to perform a 'Cold Reset' of itself. The device reinitalizes its event, communcation, and sensor funtioncs. Self Test, if implemented, will be also run.
105
+
This command directs the **Target** to perform a 'Cold Reset' of itself. The device reinitalizes its event, communication, and sensor funtioncs. Self Test, if implemented, will be also run.
Copy file name to clipboardExpand all lines: docs/source/ipmiMsgSupport_cmd.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,13 +84,13 @@ This is not equivalent with a single IPMI command, but represents a high level A
84
84
| **establish()** |
85
85
+------------------------------+
86
86
87
-
creates and activates a session of the ``ipmi.session`` instance with the given authentication and privilige level. Multiple IPMI commands are used to establish the session. The following steps are done during the session establishment for an RMCP interface:
87
+
creates and activates a session of the ``ipmi.session`` instance with the given authentication and privilege level. Multiple IPMI commands are used to establish the session. The following steps are done during the session establishment for an RMCP interface:
88
88
89
89
- ping the **Target** IP address
90
90
- issue a **"Get Channel Authentication Capabilities"** command
91
91
- issue a **"Get Session Challenge"** command
92
92
- issue an **"Activate Session"** command
93
-
- issue a **"Set Session Privilege Level"** command (privilige is set always to ADMINISTRATOR level)
93
+
- issue a **"Set Session Privilege Level"** command (privilege is set always to ADMINISTRATOR level)
94
94
95
95
If ``keep_alive_interval`` argument for the interface instantiation was set to a nonzero value then the channel is kept alive by regularly sending the **"Get Device ID"** IPMI command.
96
96
@@ -109,7 +109,7 @@ This command is used to retrieve capability information about a particular chann
You should pass the channel number to ``channel``, and the requested maximum privilige level to ``priv_lvl``.
112
+
You should pass the channel number to ``channel``, and the requested maximum privilege level to ``priv_lvl``.
113
113
114
114
Example:
115
115
@@ -121,7 +121,7 @@ Example:
121
121
Master Write-Read Command
122
122
~~~~~~~~~~~~~~~~~~~~~~~~~
123
123
124
-
This command can be used for low level |I2C|/SMBus write, read, or write-read accesses to the IPMB or private busses behind a management controller. The command can also be used for providing low-level access to devices that provide an SMBus slave interface.
124
+
This command can be used for low level |I2C|/SMBus write, read, or write-read accesses to the IPMB or private buses behind a management controller. The command can also be used for providing low-level access to devices that provide an SMBus slave interface.
* **'mock'** - This interface uses the ipmitool raw command to "emulate" an :abbr:`RMCP(Remote Management Control Protocol)` session. It uses the session information to assemble the correct ipmitool parameters. Therefore, a session must be established before any request can be sent.
25
25
26
-
Then you create an instance of the ``pyipmi.Ipmi`` object using the ``interface`` instance just created, and set also the required parameteres of the interface type. You should also set the :abbr:`IPMI(Intelligent Platform Management Interface)` **Target**, otherwise different runtime errors shall be expected later on when invoking methods of this library. Finally, you can try to establish a session. If there is a connection problem (no response), then you get the following error during session establishment:
26
+
Then you create an instance of the ``pyipmi.Ipmi`` object using the ``interface`` instance just created, and set also the required parameters of the interface type. You should also set the :abbr:`IPMI(Intelligent Platform Management Interface)` **Target**, otherwise different runtime errors shall be expected later on when invoking methods of this library. Finally, you can try to establish a session. If there is a connection problem (no response), then you get the following error during session establishment:
27
27
28
28
.. error::
29
29
@@ -261,7 +261,7 @@ ipmitool command:
261
261
IPMB with Aardvark
262
262
******************
263
263
264
-
For :abbr:`IPMB(Intelligent Platform Management Bus)` interface with Aardvark tool you should use the followig code:
264
+
For :abbr:`IPMB(Intelligent Platform Management Bus)` interface with Aardvark tool you should use the following code:
265
265
266
266
.. code:: python
267
267
@@ -345,7 +345,7 @@ in which case debug, info and warning messages are all recorded in the **'ipmi_d
345
345
346
346
.. note::
347
347
348
-
It is assumed in all code examples that the instantiation of the ``pyipmi.Ipmi`` object is called **ipmi**, thus **ipmi** will preceed all the methods and attributes of the ``pyipmi.Ipmi`` object.
348
+
It is assumed in all code examples that the instantiation of the ``pyipmi.Ipmi`` object is called **ipmi**, thus **ipmi** will proceed all the methods and attributes of the ``pyipmi.Ipmi`` object.
0 commit comments