この製品のマニュアルセットは、偏向のない言語を使用するように配慮されています。このマニュアルセットでの偏向のない言語とは、年齢、障害、性別、人種的アイデンティティ、民族的アイデンティティ、性的指向、社会経済的地位、およびインターセクショナリティに基づく差別を意味しない言語として定義されています。製品ソフトウェアのユーザーインターフェイスにハードコードされている言語、RFP のドキュメントに基づいて使用されている言語、または参照されているサードパーティ製品で使用されている言語によりドキュメントに例外が存在する場合があります。シスコのインクルーシブランゲージに対する取り組みの詳細は、こちらをご覧ください。
このドキュメントは、米国シスコ発行ドキュメントの参考和訳です。リンク情報につきましては、日本語版掲載時点で、英語版にアップデートがあり、リンク先のページが移動/変更されている場合がありますことをご了承ください。あくまでも参考和訳となりますので、正式な内容については米国サイトのドキュメントを参照ください。
目次
この章は、次の項で構成されています。
グローバル障害ポリシーは、障害がクリアされた日時、フラッピング間隔(障害発生とクリア状態の間の時間)、および保持間隔(システムで障害が発生していた時間)など、Cisco UCS ドメインの障害のライフサイクルを制御します。
Cisco UCS の障害には次のライフサイクルがあります。
ある状況がシステムで発生し、Cisco UCS Manager は障害を生成します。 これはアクティブな状態です。
障害が軽減されると、フラッピングまたはフラッピングを防ぐことを目的としたソーキング間隔になります。 障害が発生し、すぐに何度かクリアされると、フラッピングが発生します。 フラッピング間隔のうち、グローバル障害ポリシーに指定されている期間は、障害の重要度が保持されます。
フラッピング間隔中に同じ条件が再発生した場合は、障害がアクティブ状態に戻ります。 フラッピング間隔中に同じ条件が再発生しない場合は、障害がクリアされます。
クリアされた障害は保持期間になります。 この期間があるため、障害が発生した状態が改善され、さらに障害が早々に削除されていない場合でも管理者が障害に気付くことができます。 保持期間のうち、グローバル障害ポリシーに指定された期間はクリアされた障害が保持されます。
保持期間にその状態が再発すると、障害はアクティブな状態を返します。 この状況が再発生しない場合は、障害が削除されます。
This example configures the fault collection policy to retain cleared fault messages for 30 days, sets the flapping interval to 10 seconds, and commits the transaction.
UCS-A# scope monitoring UCS-A /monitoring # scope fault policy UCS-A /monitoring/fault-policy # set clear-action retain UCS-A /monitoring/fault-policy* # set flap-interval 10 UCS-A /monitoring/fault-policy* # set retention-interval 30 0 0 0 UCS-A /monitoring/fault-policy* # commit-buffer UCS-A /monitoring/fault-policy #
The following example shows how to delete the fault suppression task called task1:
UCS-A# scope chassis 1 UCS-A/chassis # delete fault-suppress-task task1 UCS-A/chassis* # commit-buffer
The following example shows how to display the suppressed faults for a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # show fault suppressed Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Chassis Phys Maint UCS-A/chassis #
The following example shows how to display the fault suppression task called task1:
UCS-A# scope chassis 1 UCS-A/chassis # scope fault-suppress-task task1 UCS-A/chassis/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Chassis Phys Maint UCS-A/chassis/fault-suppress-task #
The default-iom-maint suppression policy is selected by default.
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope [chassis chassis-num | fex fex-num] | Enters chassis mode for the specified chassis or FEX. |
ステップ 2 | UCS-A /chassis|fex # scope iom iom-id | Enters chassis I/O module mode for the selected I/O module. |
ステップ 3 | UCS-A/chassis|fex/iom # create fault-suppress-task name | Creates a fault-suppress-task on the IOM, and enters the fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
ステップ 4 | UCS-A/chassis|fex/iom/fault-suppress-task # create local-schedule | Creates a local schedule and enters local-schedule mode. |
ステップ 5 | UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule # create occurrence single-one-time | Creates a one-time occurrence, and enters single-one-time mode. |
ステップ 6 | UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds | Specifies the date and time that this occurrence should run. |
ステップ 7 | UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} | Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step. |
ステップ 8 | UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a fault suppression task called task2 for the IOM on a chassis, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # create fault-suppress-task task2 UCS-A/chassis/iom/fault-suppress-task* # create local-schedule UCS-A/chassis/iom/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/chassis/iom/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/chassis/iom/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The following example shows how to create a fault suppression task called task2 for the IOM on a FEX, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope fex 1 UCS-A/fex # scope iom a UCS-A/fex/iom # create fault-suppress-task task2 UCS-A/fex/iom/fault-suppress-task* # create local-schedule UCS-A/fex/iom/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/fex/iom/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/fex/iom/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The default-iom-maint suppression policy is selected by default.
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope [chassis chassis-num | fex fex-num] | Enters chassis mode for the specified chassis or FEX. |
||
ステップ 2 | UCS-A /chassis|fex # scope iom iom-id | Enters chassis I/O module mode for the selected I/O module. |
||
ステップ 3 | UCS-A/chassis|fex/iom # create fault-suppress-task name | Creates a fault-suppress-task on the IOM, and enters the fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
||
ステップ 4 | UCS-A/chassis|fex/iom/fault-suppress-task # set schedule name | Specifies the schedule that you want to use.
|
||
ステップ 5 | UCS-A/chassis|fex/iom/fault-suppress-task # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a fault suppression task called task1 for the IOM on a chassis, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # create fault-suppress-task task1 UCS-A/chassis/iom/fault-suppress-task* # set schedule weekly_maint UCS-A/chassis/iom/fault-suppress-task* # commit-buffer
The following example shows how to create a fault suppression task called task1 for the IOM on a FEX, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope fex 1 UCS-A/fex # scope iom a UCS-A/fex/iom # create fault-suppress-task task1 UCS-A/fex/iom/fault-suppress-task* # set schedule weekly_maint UCS-A/fex/iom/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope [chassis chassis-num | fex fex-num] | Enters chassis mode for the specified chassis or FEX. |
ステップ 2 | UCS-A /chassis|fex # scope iom iom-id | Enters chassis I/O module mode for the selected I/O module. |
ステップ 3 | UCS-A/chassis|fex/iom # delete fault-suppress-task name | Deletes the specified fault suppression task. |
ステップ 4 | UCS-A/chassis|fex/iom # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to delete the fault suppression task called task1 for an IOM on a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # delete fault-suppress-task task1 UCS-A/chassis/iom* # commit-buffer
The following example shows how to delete the fault suppression task called task1 for an IOM on a FEX:
UCS-A# scope fex 3 UCS-A/fex # scope iom a UCS-A/fex/iom # delete fault-suppress-task task1 UCS-A/fex/iom* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope [chassis chassis-num | fex fex-num] | Enters chassis mode for the specified chassis or FEX. |
||
ステップ 2 | UCS-A /chassis|fex # scope iom iom-id | Enters chassis I/O module mode for the selected I/O module. |
||
ステップ 3 | UCS-A/chassis|fex/iom # scope fault-suppress-task name | Enters fault-suppress-task mode.
|
||
ステップ 4 | UCS-A/chassis|fex/iom/fault-suppress-task # set schedule name | Applies a different schedule.
|
||
ステップ 5 | UCS-A/chassis|fex/iom/fault-suppress-task # scope local-schedule | Enters local-schedule mode. |
||
ステップ 6 | UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule # scope occurrence single-one-time | Enters single-one-time mode. |
||
ステップ 7 | UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds | Specifies the date and time that this occurrence should run. |
||
ステップ 8 | UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} | Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step. |
||
ステップ 9 | UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to change the date and the fault suppression policy of the fault suppression task called task2 for an IOM on a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # scope fault-suppress-task task2 UCS-A/chassis/iom/fault-suppress-task # scope local-schedule UCS-A/chassis/iom/fault-suppress-task/local-schedule # scope occurrence single-one-time UCS-A/chassis/iom/fault-suppress-task/local-schedule/single-one-time # set date dec 31 2013 11 00 00 UCS-A/chassis/iom/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The following example shows how to apply a different schedule to the fault suppression task called task1 for an IOM on a FEX:
UCS-A# scope fex 3 UCS-A/fex # scope iom a UCS-A/fex/iom # scope fault-suppress-task task1 UCS-A/fex/iom/fault-suppress-task # set schedule monthly-maint UCS-A/fex/iom/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope [chassis chassis-num | fex fex-num] | Enters chassis mode for the specified chassis or FEX. |
||
ステップ 2 | UCS-A /chassis|fex # scope iom iom-id | Enters chassis I/O module mode for the selected I/O module. |
||
ステップ 3 | UCS-A/chassis|fex/iom # show fault suppressed | Displays the suppressed faults for the IOM.
|
||
ステップ 4 | UCS-A/chassis|fex/iom # scope fault-suppress-task name | Enters fault-suppress-task mode. |
||
ステップ 5 | UCS-A/chassis|fex/iom/fault-suppress-task # show detail expand | Displays the schedule or fixed time interval for the task. |
The following example shows how to display the suppressed faults for an IOM on a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # show fault suppressed Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Iom Maint UCS-A/chassis/iom #
The following example shows how to display the fault suppression task called task1 for an IOM on a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # scope fault-suppress-task task1 UCS-A/chassis/iom/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Iom Maint UCS-A/chassis/iom/fault-suppress-task #
The following example shows how to display the fault suppression task called task1 for an IOM on a FEX:
UCS-A# scope fex 3 UCS-A/fex # scope iom a UCS-A/fex/iom # scope fault-suppress-task task1 UCS-A/fex/iom/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Iom Maint UCS-A/chassis/iom/fault-suppress-task #
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope fex fex-num | Enters fex mode for the specified FEX. |
||
ステップ 2 | UCS-A/fex # create fault-suppress-task name | Creates a fault-suppress-task on the fex, and enters the fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
||
ステップ 3 | UCS-A/fex/fault-suppress-task # set schedule name | Specifies the schedule that you want to use.
|
||
ステップ 4 | UCS-A/fex/fault-suppress-task # set fault-suppress-policy policy-name | Specifies the fault suppression policy that you want to apply. This can be one of the following: |
||
ステップ 5 | UCS-A/fex/fault-suppress-task # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a fault suppression task called task1 for the FEX, apply the scheduler called weekly_maint and the default-fex-all-maint policy to the task, and commit the transaction:
UCS-A# scope fex 1 UCS-A/fex # create fault-suppress-task task1 UCS-A/fex/fault-suppress-task* # set schedule weekly_maint UCS-A/fex/fault-suppress-task* # set fault-suppress-policy default-fex-all-maint UCS-A/fex/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope fex fex-num | Enters fex mode for the specified FEX. |
ステップ 2 | UCS-A/fex # delete fault-suppress-task name | Deletes the specified fault suppression task. |
ステップ 3 | UCS-A/fex # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to delete the fault suppression task called task1:
UCS-A# scope fex 1 UCS-A/fex # delete fault-suppress-task task1 UCS-A/fex* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope fex fex-num | Enters fex mode for the specified FEX. |
||
ステップ 2 | UCS-A/fex # show fault suppressed | Displays the suppressed faults for the FEX.
|
||
ステップ 3 | UCS-A/fex # scope fault-suppress-task name | Enters fault-suppress-task mode. |
||
ステップ 4 | UCS-A/fex/fault-suppress-task # show detail expand | Displays the schedule or fixed time interval for the task. |
The following example shows how to display the suppressed faults for a FEX:
UCS-A# scope fex 1 UCS-A/fex # show fault suppressed Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default FEX Phys Maint UCS-A/fex #
The following example shows how to display the fault suppression task called task1:
UCS-A# scope fex 1 UCS-A/fex # scope fault-suppress-task task1 UCS-A/fex/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default FEX Phys Maint UCS-A/fex/fault-suppress-task #
The default-server-maint suppression policy is selected by default.
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope server [chassis-num/server-num | dynamic-uuid] | 指定したサーバのサーバ モードを開始します。 |
ステップ 2 | UCS-A/server # create fault-suppress-task name | Creates a fault-suppress-task on the server, and enters the fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
ステップ 3 | UCS-A/server/fault-suppress-task # create local-schedule | Creates a local schedule and enters local-schedule mode. |
ステップ 4 | UCS-A/server/fault-suppress-task/local-schedule # create occurrence single-one-time | Creates a one-time occurrence, and enters single-one-time mode. |
ステップ 5 | UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds | Specifies the date and time that this occurrence should run. |
ステップ 6 | UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} | Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step. |
ステップ 7 | UCS-A/server/fault-suppress-task/local-schedule/single-one-time # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a fault suppression task called task2 for the server, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope server 1/1 UCS-A/server # create fault-suppress-task task2 UCS-A/server/fault-suppress-task* # create local-schedule UCS-A/server/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/server/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/server/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The default-server-maint suppression policy is selected by default.
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope server [chassis-num/server-num | dynamic-uuid] | 指定したサーバのサーバ モードを開始します。 |
||
ステップ 2 | UCS-A/server # create fault-suppress-task name | Creates a fault-suppress-task on the server, and enters the fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
||
ステップ 3 | UCS-A/server/fault-suppress-task # set schedule name | Specifies the schedule that you want to use.
|
||
ステップ 4 | UCS-A/server/fault-suppress-task # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to creates a fault suppression task called task1 for the server, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope server 1/1 UCS-A/server # create fault-suppress-task task1 UCS-A/server/fault-suppress-task* # set schedule weekly_maint UCS-A/server/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope server [chassis-num/server-num | dynamic-uuid] | 指定したサーバのサーバ モードを開始します。 |
ステップ 2 | UCS-A/server # delete fault-suppress-task name | Deletes the specified fault suppression task. |
ステップ 3 | UCS-A/server # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to delete the fault suppression task called task1:
UCS-A# scope server 1/1 UCS-A/server # delete fault-suppress-task task1 UCS-A/server* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope server [chassis-num/server-num | dynamic-uuid] | 指定したサーバのサーバ モードを開始します。 |
||
ステップ 2 | UCS-A/server # scope fault-suppress-task name | Enters fault-suppress-task mode.
|
||
ステップ 3 | UCS-A/server/fault-suppress-task # set schedule name | Applies a different schedule.
|
||
ステップ 4 | UCS-A/server/fault-suppress-task # scope local-schedule | Enters local-schedule mode. |
||
ステップ 5 | UCS-A/server/fault-suppress-task/local-schedule # scope occurrence single-one-time | Enters single-one-time mode. |
||
ステップ 6 | UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds | Specifies the date and time that this occurrence should run. |
||
ステップ 7 | UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} | Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step. |
||
ステップ 8 | UCS-A/server/fault-suppress-task/local-schedule/single-one-time # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to change the date and the fault suppression policy of the fault suppression task called task2:
UCS-A# scope server 1/1 UCS-A/server # scope fault-suppress-task task2 UCS-A/server/fault-suppress-task # scope local-schedule UCS-A/server/fault-suppress-task/local-schedule # scope occurrence single-one-time UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set date dec 31 2013 11 00 00 UCS-A/server/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The following example shows how to apply a different schedule to the fault suppression task called task1:
UCS-A# scope server 1/1 UCS-A/server # scope fault-suppress-task task1 UCS-A/server/fault-suppress-task # set schedule monthly-maint UCS-A/server/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope server [chassis-num/server-num | dynamic-uuid] | 指定したサーバのサーバ モードを開始します。 |
||
ステップ 2 | UCS-A/server # show fault suppressed | Displays the suppressed faults for the server.
|
||
ステップ 3 | UCS-A/server # scope fault-suppress-task name | Enters fault-suppress-task mode. |
||
ステップ 4 | UCS-A/server/fault-suppress-task # show detail expand | Displays the schedule or fixed time interval for the task. |
The following example shows how to display the suppressed faults for a server:
UCS-A# scope server 1/1 UCS-A/server # show fault suppressed Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Server Maint UCS-A/server #
The following example shows how to display the fault suppression task called task1:
UCS-A# scope server 1/1 UCS-A/server # scope fault-suppress-task task1 UCS-A/server/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Server Maint UCS-A/server/fault-suppress-task #
The default-server-maint suppression policy is selected by default.
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
ステップ 2 | UCS-A /org # scope service-profile profile-name | Enters service profile organization mode for the service profile. |
ステップ 3 | UCS-A /org/service-profile # create fault-suppress-task name | Creates a fault-suppress-task on the chassis, and enters the fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
ステップ 4 | UCS-A/org/service-profile/fault-suppress-task # create local-schedule | Creates a local schedule and enters local-schedule mode. |
ステップ 5 | UCS-A/org/service-profile/fault-suppress-task/local-schedule # create occurrence single-one-time | Creates a one-time occurrence, and enters single-one-time mode. |
ステップ 6 | UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds | Specifies the date and time that this occurrence should run. |
ステップ 7 | UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} | Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step. |
ステップ 8 | UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a fault suppression task called task2 under the accounting service profile, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # create fault-suppress-task task2 UCS-A/org/service-profile/fault-suppress-task* # create local-schedule UCS-A/org/service-profile/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The default-server-maint suppression policy is selected by default.
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
||
ステップ 2 | UCS-A /org # scope service-profile profile-name | Enters service profile organization mode for the service profile. |
||
ステップ 3 | UCS-A /org/service-profile # create fault-suppress-task name | Creates a fault-suppress-task on the chassis, and enters the fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
||
ステップ 4 | UCS-A/org/service-profile/fault-suppress-task # set schedule name | Specifies the schedule that you want to use.
|
||
ステップ 5 | UCS-A/org/service-profile/fault-suppress-task # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a fault suppression task called task1 under the accounting service profile, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # create fault-suppress-task task1 UCS-A/org/service-profile/fault-suppress-task* # set schedule weekly_maint UCS-A/org/service-profile/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
ステップ 2 | UCS-A /org # scope service-profile profile-name | Enters service profile organization mode for the service profile. |
ステップ 3 | UCS-A/org/service-profile # delete fault-suppress-task name | Deletes the specified fault suppression task. |
ステップ 4 | UCS-A/org/service-profile # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to delete the fault suppression task called task1:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # delete fault-suppress-task task1 UCS-A/org/service-profile* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
||
ステップ 2 | UCS-A /org # scope service-profile profile-name | Enters service profile organization mode for the service profile. |
||
ステップ 3 | UCS-A/org/service-profile # scope fault-suppress-task name | Enters fault-suppress-task mode.
|
||
ステップ 4 | UCS-A/org/service-profile/fault-suppress-task # set schedule name | Applies a different schedule.
|
||
ステップ 5 | UCS-A/org/service-profile/fault-suppress-task # scope local-schedule | Enters local-schedule mode. |
||
ステップ 6 | UCS-A/org/service-profile/fault-suppress-task/local-schedule # scope occurrence single-one-time | Enters single-one-time mode. |
||
ステップ 7 | UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds | Specifies the date and time that this occurrence should run. |
||
ステップ 8 | UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} | Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step. |
||
ステップ 9 | UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to change the date and the fault suppression policy of the fault suppression task called task2:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # scope fault-suppress-task task2 UCS-A/org/service-profile/fault-suppress-task # scope local-schedule UCS-A/org/service-profile/fault-suppress-task/local-schedule # scope occurrence single-one-time UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set date dec 31 2013 11 00 00 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The following example shows how to apply a different schedule to the fault suppression task called task1:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # scope fault-suppress-task task1 UCS-A/org/service-profile/fault-suppress-task # set schedule monthly-maint UCS-A/org/service-profile/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
||
ステップ 2 | UCS-A /org # scope service-profile profile-name | Enters service profile organization mode for the service profile. |
||
ステップ 3 | UCS-A/org/service-profile # show fault suppressed | Displays the suppressed faults for the server.
|
||
ステップ 4 | UCS-A/org/service-profile # scope fault-suppress-task name | Enters fault-suppress-task mode. |
||
ステップ 5 | UCS-A/org/service-profile/fault-suppress-task # show detail expand | Displays the schedule or fixed time interval for the task. |
The following example shows how to display the suppressed faults for a service profile:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # show fault suppressed UCS-A/org/service-profile # Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Server Maint UCS-A/org/service-profile #
The following example shows how to display the fault suppression task called task1:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # scope fault-suppress-task task1 UCS-A/org/service-profile/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Server Maint UCS-A/org/service-profile/fault-suppress-task #
The default-server-maint suppression policy is selected by default.
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
ステップ 2 | UCS-A/org # create fault-suppress-task name | Creates a fault-suppress-task for the organization, and enters fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
ステップ 3 | UCS-A/org/fault-suppress-task # create local-schedule | Creates a local schedule and enters local-schedule mode. |
ステップ 4 | UCS-A/org/fault-suppress-task/local-schedule # create occurrence single-one-time | Creates a one-time occurrence, and enters single-one-time mode. |
ステップ 5 | UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds | Specifies the date and time that this occurrence should run. |
ステップ 6 | UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} | Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step. |
ステップ 7 | UCS-A/org/fault-suppress-task/local-schedule/single-one-time # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a fault suppression task called task2 under the Root organization, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope org / UCS-A/org # create fault-suppress-task task2 UCS-A/org/fault-suppress-task* # create local-schedule UCS-A/org/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/org/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/org/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The default-server-maint suppression policy is selected by default.
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
||
ステップ 2 | UCS-A/org # create fault-suppress-task name | Creates a fault-suppress-task for the organization, and enters the fault-suppress-task mode. この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。 |
||
ステップ 3 | UCS-A/org/fault-suppress-task # set schedule name | Specifies the schedule that you want to use.
|
||
ステップ 4 | UCS-A/org/fault-suppress-task # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a fault suppression task called task1 under the Root organization, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope org / UCS-A/org # create fault-suppress-task task1 UCS-A/org/fault-suppress-task* # set schedule weekly_maint UCS-A/org/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
ステップ 2 | UCS-A/org # delete fault-suppress-task name | Deletes the specified fault suppression task. |
ステップ 3 | UCS-A/org # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to delete the fault suppression task called task1:
UCS-A# scope org / UCS-A/org # delete fault-suppress-task task1 UCS-A/org* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
||
ステップ 2 | UCS-A/org # scope fault-suppress-task name | Enters fault-suppress-task mode.
|
||
ステップ 3 | UCS-A/org/fault-suppress-task # set schedule name | Applies a different schedule.
|
||
ステップ 4 | UCS-A/org/fault-suppress-task # scope local-schedule | Enters local-schedule mode. |
||
ステップ 5 | UCS-A/org/fault-suppress-task/local-schedule # scope occurrence single-one-time | Enters single-one-time mode. |
||
ステップ 6 | UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds | Specifies the date and time that this occurrence should run. |
||
ステップ 7 | UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} | Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step. |
||
ステップ 8 | UCS-A/org/fault-suppress-task/local-schedule/single-one-time # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to change the date and the fault suppression policy of the fault suppression task called task2:
UCS-A# scope org / UCS-A/org # scope fault-suppress-task task2 UCS-A/org/fault-suppress-task* # scope local-schedule UCS-A/org/fault-suppress-task/local-schedule # scope occurrence single-one-time UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set date dec 31 2013 11 00 00 UCS-A/org/fault-suppress-task/local-schedule/single-one-time* # commit-buffer
The following example shows how to apply a different schedule to the fault suppression task called task1:
UCS-A# scope org UCS-A/org # scope fault-suppress-task task1 UCS-A/org/fault-suppress-task # set schedule monthly-maint UCS-A/org/fault-suppress-task* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。 |
||
ステップ 2 | UCS-A/org # show fault suppressed | Displays the suppressed faults for the organization
|
||
ステップ 3 | UCS-A/org # scope fault-suppress-task name | Enters fault-suppress-task mode. |
||
ステップ 4 | UCS-A/org/fault-suppress-task # show detail expand | Displays the schedule or fixed time interval for the task. |
The following example shows how to display the suppressed faults for an organization:
UCS-A# scope org Finance UCS-A/org # show fault suppressed UCS-A/org # Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Server Maint UCS-A/org #
The following example shows how to display the fault suppression task called task1:
UCS-A# scope org Finance UCS-A/org # scope fault-suppress-task task1 UCS-A/org/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Server Maint UCS-A/org/fault-suppress-task #
Cisco UCS コア ファイルが発生すると、ただちに Core File Exporter が使用され、それらのファイルが TFTP を介してネットワーク上の指定の場所にエクスポートされます。 この機能を使用することにより、tar ファイルをコア ファイルのコンテンツと一緒にエクスポートできます。
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope monitoring | Enters monitoring mode. |
ステップ 2 | UCS-A /monitoring # scope sysdebug | Enters monitoring system debug mode. |
ステップ 3 | UCS-A /monitoring/sysdebug # enable core-export-target | Enables the core file exporter. When the core file exporter is enabled and an error causes the server to perform a core dump, the system exports the core file via TFTP to the specified remote server. |
ステップ 4 | UCS-A /monitoring/sysdebug # set core-export-target path path | Specifies the path to use when exporting the core file to the remote server. |
ステップ 5 | UCS-A /monitoring/sysdebug # set core-export-target port port-num | Specifies the port number to use when exporting the core file via TFTP. The range of valid values is 1 to 65,535. |
ステップ 6 | UCS-A /monitoring/sysdebug # set core-export-target server-description description | Provides a description for the remote server used to store the core file. |
ステップ 7 | UCS-A /monitoring/sysdebug # set core-export-target server-name hostname | Specifies the hostname of the remote server to connect with via TFTP. |
ステップ 8 | UCS-A /monitoring/sysdebug # commit-buffer | Commits the transaction. |
The following example enables the core file exporter, specifies the path and port to use when sending the core file, specifies the remote server hostname, provides a description for the remote server, and commits the transaction.
UCS-A# scope monitoring UCS-A /monitoring # scope sysdebug UCS-A /monitoring/sysdebug # enable core-export-target UCS-A /monitoring/sysdebug* # set core-export-target path /root/CoreFiles/core UCS-A /monitoring/sysdebug* # set core-export-target port 45000 UCS-A /monitoring/sysdebug* # set core-export-target server-description CoreFile102.168.10.10 UCS-A /monitoring/sysdebug* # set core-export-target server-name 192.168.10.10 UCS-A /monitoring/sysdebug* # commit-buffer UCS-A /monitoring/sysdebug #
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope monitoring | Enters monitoring mode. |
ステップ 2 | UCS-A /monitoring # scope sysdebug | Enters monitoring system debug mode. |
ステップ 3 | UCS-A /monitoring/sysdebug # disable core-export-target | Disables the core file exporter. When the core file exporter is disabled core files are not automatically exported. |
ステップ 4 | UCS-A /monitoring/sysdebug # commit-buffer | Commits the transaction. |
The following example disables the core file exporter and commits the transaction.
UCS-A# scope monitoring UCS-A /monitoring # scope sysdebug UCS-A /monitoring/sysdebug # disable core-export-target UCS-A /monitoring/sysdebug* # commit-buffer UCS-A /monitoring/sysdebug #
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope monitoring | Enters monitoring mode. |
||
ステップ 2 | UCS-A /monitoring # {enable | disable} syslog console | Enables or disables the sending of syslogs to the console. |
||
ステップ 3 | UCS-A /monitoring # set syslog console level {emergencies | alerts | critical} | (任意) Select the lowest message level that you want displayed. If syslogs are enabled, the system displays that level and above on the console. The level options are listed in order of decreasing urgency.The default level is Critical. |
||
ステップ 4 | UCS-A /monitoring # {enable | disable} syslog monitor | Enables or disables the monitoring of syslog information by the operating system. |
||
ステップ 5 | UCS-A /monitoring # set syslog monitor level {emergencies | alerts | critical | errors | warnings | notifications | information | debugging} | (任意) Select the lowest message level that you want displayed. If the monitor state is enabled, the system displays that level and above. The level options are listed in order of decreasing urgency.The default level is Critical.
|
||
ステップ 6 | UCS-A /monitoring # {enable | disable} syslog file | Enables or disables the writing of syslog information to a syslog file. |
||
ステップ 7 | UCS-A /monitoring # set syslog file name filename | The name of the file in which the messages are logged. Up to 16 characters are allowed in the file name. |
||
ステップ 8 | UCS-A /monitoring # set syslog file level {emergencies | alerts | critical | errors | warnings | notifications | information | debugging} | (任意) Select the lowest message level that you want stored to a file. If the file state is enabled, the system stores that level and above in the syslog file. The level options are listed in order of decreasing urgency.The default level is Critical. |
||
ステップ 9 | UCS-A /monitoring # set syslog file size filesize | (任意) The maximum file size, in bytes, before the system begins to write over the oldest messages with the newest ones. The range is 4096 to 4194304 bytes. |
||
ステップ 10 | UCS-A /monitoring # {enable | disable} syslog remote-destination {server-1 | server-2 | server-3} | Enables or disables the sending of syslog messages to up to three external syslog servers. |
||
ステップ 11 | UCS-A /monitoring # set syslog remote-destination {server-1 | server-2 | server-3} level{emergencies | alerts | critical | errors | warnings | notifications | information | debugging} | (任意) Select the lowest message level that you want stored to the external log. If the remote-destination is enabled, the system sends that level and above to the external server. The level options are listed in order of decreasing urgency.The default level is Critical. |
||
ステップ 12 | UCS-A /monitoring # set syslog remote-destination {server-1 | server-2 | server-3} hostname hostname | The hostname or IP address of the specified remote syslog server. Up to 256 characters are allowed in the hostname. |
||
ステップ 13 | UCS-A /monitoring # set syslog remote-destination {server-1 | server-2 | server-3} facility {local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7} | (任意) The facility level contained in the syslog messages sent to the specified remote syslog server. |
||
ステップ 14 | UCS-A /monitoring # {enable | disable} syslog source {audits | events | faults} | This can be one of the following: |
||
ステップ 15 | UCS-A /monitoring # commit-buffer | Commits the transaction. |
This example shows how to enable the storage of syslog messages in a local file and commits the transaction:
UCS-A# scope monitoring UCS-A /monitoring # disable syslog console UCS-A /monitoring* # disable syslog monitor UCS-A /monitoring* # enable syslog file UCS-A /monitoring* # set syslog file name SysMsgsUCSA UCS-A /monitoring* # set syslog file level notifications UCS-A /monitoring* # set syslog file size 4194304 UCS-A /monitoring* # disable syslog remote-destination server-1 UCS-A /monitoring* # disable syslog remote-destination server-2 UCS-A /monitoring* # disable syslog remote-destination server-3 UCS-A /monitoring* # commit-buffer UCS-A /monitoring #
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope security | Enters security mode. |
ステップ 2 | UCS-A /security # show audit-logs | Displays the audit logs. |
The following example displays the audit logs:
UCS-A# scope security UCS-A /security # show audit-logs Audit trail logs: Creation Time User ID Action Description -------------------- ---------- -------- ---------------- ----------- 2013-01-04T19:05:36.027 internal 1055936 Creation Fabric A: local us er admin logge 2013-01-03T23:08:37.459 admin 1025416 Creation Uplink FC VSAN mem ber port A/1/3 2013-01-03T23:08:37.459 admin 1025417 Deletion Uplink FC VSAN mem ber port A/1/3 2013-01-03T23:08:02.387 admin 1025299 Creation Uplink FC VSAN mem ber port A/1/3 2013-01-03T23:08:02.387 admin 1025300 Deletion Uplink FC VSAN mem ber port A/1/3 2013-01-03T23:03:23.926 admin 1025096 Creation Uplink FC VSAN mem ber port A/1/3 UCS-A /security #
Cisco UCS Manager は、実行ごとにログ ファイルを生成します。 ログ ファイルのサイズは最大 20 MB で、最大 5 つのバックアップがサーバに保存できます。 ログ ファイル エクスポータにより、ログ ファイルを削除する前にリモート サーバにエクスポートすることができます。 ログ ファイル名には次の情報が含まれます。
(注) |
ログのエクスポートをイネーブルにしない場合は、バックアップ ファイルの最大限度に到達すると最も古いログ ファイルが削除されます。 |
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope monitoring | Enters monitoring mode. |
ステップ 2 | UCS-A /monitoring # scope sysdebug | Enters monitoring system debug mode. |
ステップ 3 | UCS-A /monitoring/sysdebug # scope log-export-policy | Enters log file export mode. |
ステップ 4 | UCS-A /monitoring/sysdebug/log-export-policy # set admin-state {disabled | enabled} | Whether log file exporting is enabled. |
ステップ 5 | UCS-A /monitoring/sysdebug/log-export-policy # set desc description | (任意) Provides a description for the log export policy |
ステップ 6 | UCS-A /monitoring/sysdebug/log-export-policy # set hostname hostname | Specifies the hostname of the remote server. |
ステップ 7 | UCS-A /monitoring/sysdebug/log-export-policy # set passwd | After you press Enter, you are prompted to enter the password. Specifies the password for the remote server username. This step does not apply if the TFTP protocol is used. |
ステップ 8 | UCS-A /monitoring/sysdebug/log-export-policy # set passwordless-ssh {no | yes} | Enables SSH login without a password. |
ステップ 9 | UCS-A /monitoring/sysdebug/log-export-policy # set proto {scp | ftp | sftp | tftp} | Specifies the protocol to use when communicating with the remote server. |
ステップ 10 | UCS-A /monitoring/sysdebug/log-export-policy # set path path | Specifies the path on the remote server where the log file is to be saved. |
ステップ 11 | UCS-A /monitoring/sysdebug/log-export-policy # set user username | Specifies the username the system should use to log in to the remote server. This step does not apply if the TFTP protocol is used. |
ステップ 12 | UCS-A /monitoring/sysdebug/log-export-policy # commit-buffer | Commits the transaction. |
The following example shows how to enable the log file exporter, specify the remote server hostname, set the protocol to scp, enable passwordless login, and commit the transaction.
UCS-A# scope monitoring UCS-A /monitoring # scope sysdebug UCS-A /monitoring/sysdebug # scope log-export-policy UCS-A /monitoring/sysdebug/log-export-policy # set admin-state enable UCS-A /monitoring/sysdebug/log-export-policy* # set hostname 10.10.1.1 UCS-A /monitoring/sysdebug/log-export-policy* # set path / UCS-A /monitoring/sysdebug/log-export-policy* # set user testuser UCS-A /monitoring/sysdebug/log-export-policy* # set proto scp UCS-A /monitoring/sysdebug/log-export-policy* # set passwd password: UCS-A /monitoring/sysdebug/log-export-policy* # set passwordless-ssh yes UCS-A /monitoring/sysdebug/log-export-policy* # commit-buffer UCS-A /monitoring/sysdebug/log-export-policy #
目次
- 障害、イベント、およびログの設定
- Configuring Settings for the Fault Collection Policy
- グローバル障害ポリシー
- Configuring the Fault Collection Policy
- Configuring Fault Suppression
- Configuring Fault Suppression for a Chassis
- Deleting Fault Suppression Tasks for a Chassis
- Viewing Suppressed Faults and Fault Suppression Tasks for a Chassis
- Configuring Fault Suppression for an I/O Module
- Configuring Fault Suppression Tasks for an IOM Using a Fixed Time Interval
- Configuring Fault Suppression Tasks for an IOM Using a Schedule
- Deleting Fault Suppression Tasks for an IOM
- Modifying Fault Suppression Tasks for an IOM
- Viewing Suppressed Faults and Fault Suppression Tasks for an IOM
- Configuring Fault Suppression for a FEX
- Configuring Fault Suppression Tasks for a FEX Using a Schedule
- Deleting Fault Suppression Tasks for a FEX
- Viewing Suppressed Faults and Fault Suppression Tasks for a FEX
- Configuring Fault Suppression for a Server
- Configuring Fault Suppression Tasks for a Server Using a Fixed Time Interval
- Configuring Fault Suppression Tasks for a Server using a Schedule
- Deleting Fault Suppression Tasks for a Server
- Modifying Fault Suppression Tasks for a Server
- Viewing Suppressed Faults and Fault Suppression Tasks for a Server
- Configuring Fault Suppression for a Service Profile
- Configuring Fault Suppression Tasks for a Service Profile Using a Fixed Time Interval
- Configuring Fault Suppression Tasks for a Service Profile Using a Schedule
- Deleting Fault Suppression Tasks for a Service Profile
- Modifying Fault Suppression Tasks for a Service Profile
- Viewing Suppressed Faults and Fault Suppression Tasks for a Service Profile
- Configuring Fault Suppression for an Organization
- Configuring Fault Suppression Tasks for an Organization Using a Fixed Time Interval
- Configuring Fault Suppression Tasks for an Organization Using a Schedule
- Deleting Fault Suppression Tasks for an Organization
- Modifying Fault Suppression Tasks for an Organization
- Viewing Suppressed Faults and Fault Suppression Tasks for an Organization
- Configuring Settings for the Core File Exporter
- Core File Exporter
- Configuring the Core File Exporter
- Disabling the Core File Exporter
- Configuring the Syslog
- Viewing Audit Logs
- ログ ファイル エクスポータ
- Exporting Log Files to a Remote Server
この章は、次の項で構成されています。
- Configuring Settings for the Fault Collection Policy
- Configuring Fault Suppression
- Configuring Settings for the Core File Exporter
- Configuring the Syslog
- Viewing Audit Logs
グローバル障害ポリシー
グローバル障害ポリシーは、障害がクリアされた日時、フラッピング間隔(障害発生とクリア状態の間の時間)、および保持間隔(システムで障害が発生していた時間)など、Cisco UCS ドメインの障害のライフサイクルを制御します。
Cisco UCS の障害には次のライフサイクルがあります。
ある状況がシステムで発生し、Cisco UCS Manager は障害を生成します。 これはアクティブな状態です。
障害が軽減されると、フラッピングまたはフラッピングを防ぐことを目的としたソーキング間隔になります。 障害が発生し、すぐに何度かクリアされると、フラッピングが発生します。 フラッピング間隔のうち、グローバル障害ポリシーに指定されている期間は、障害の重要度が保持されます。
フラッピング間隔中に同じ条件が再発生した場合は、障害がアクティブ状態に戻ります。 フラッピング間隔中に同じ条件が再発生しない場合は、障害がクリアされます。
クリアされた障害は保持期間になります。 この期間があるため、障害が発生した状態が改善され、さらに障害が早々に削除されていない場合でも管理者が障害に気付くことができます。 保持期間のうち、グローバル障害ポリシーに指定された期間はクリアされた障害が保持されます。
保持期間にその状態が再発すると、障害はアクティブな状態を返します。 この状況が再発生しない場合は、障害が削除されます。
Configuring the Fault Collection Policy
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope monitoring Enters monitoring mode.
ステップ 2 UCS-A /monitoring # scope fault policy Enters monitoring fault policy mode.
ステップ 3 UCS-A /monitoring/fault-policy # set clear-action {delete | retain} Specifies whether to retain or delete all cleared messages. If the retain option is specified, then the length of time that the messages are retained is determined by the set retention-interval command.
ステップ 4 UCS-A /monitoring/fault-policy # set flap-interval seconds Specifies the time interval (in seconds) the system waits before changing a fault state. Flapping occurs when a fault is raised and cleared several times in rapid succession. To prevent this, the system does not allow a fault to change state until the flapping interval has elapsed after the last state change. If the fault is raised again during the flapping interval, it returns to the active state, otherwise, the fault is cleared.
ステップ 5 UCS-A /monitoring/fault-policy # set retention-interval {days hours minutes seconds | forever} Specifies the time interval the system retains all cleared fault messages before deleting them. The system can retain cleared fault messages forever, or for the specified number of days, hours, minutes, and seconds.
ステップ 6 UCS-A /monitoring/fault-policy # commit-buffer Commits the transaction.
This example configures the fault collection policy to retain cleared fault messages for 30 days, sets the flapping interval to 10 seconds, and commits the transaction.
UCS-A# scope monitoring UCS-A /monitoring # scope fault policy UCS-A /monitoring/fault-policy # set clear-action retain UCS-A /monitoring/fault-policy* # set flap-interval 10 UCS-A /monitoring/fault-policy* # set retention-interval 30 0 0 0 UCS-A /monitoring/fault-policy* # commit-buffer UCS-A /monitoring/fault-policy #Deleting Fault Suppression Tasks for a Chassis
Viewing Suppressed Faults and Fault Suppression Tasks for a Chassis
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope chassis chassis-num 指定したシャーシでシャーシ モードを開始します。
ステップ 2 UCS-A/chassis # show fault suppressed Displays the suppressed faults for the chassis.
(注) Only faults owned by the selected component are displayed.
ステップ 3 UCS-A/chassis # scope fault-suppress-task name Enters fault-suppress-task mode.
ステップ 4 UCS-A/chassis/fault-suppress-task # show detail expand Displays the schedule or fixed time interval for the task.
The following example shows how to display the suppressed faults for a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # show fault suppressed Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Chassis Phys Maint UCS-A/chassis #The following example shows how to display the fault suppression task called task1:
UCS-A# scope chassis 1 UCS-A/chassis # scope fault-suppress-task task1 UCS-A/chassis/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Chassis Phys Maint UCS-A/chassis/fault-suppress-task #Configuring Fault Suppression Tasks for an IOM Using a Fixed Time Interval
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope [chassis chassis-num | fex fex-num] Enters chassis mode for the specified chassis or FEX.
ステップ 2 UCS-A /chassis|fex # scope iom iom-id Enters chassis I/O module mode for the selected I/O module.
ステップ 3 UCS-A/chassis|fex/iom # create fault-suppress-task name Creates a fault-suppress-task on the IOM, and enters the fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 4 UCS-A/chassis|fex/iom/fault-suppress-task # create local-schedule Creates a local schedule and enters local-schedule mode.
ステップ 5 UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule # create occurrence single-one-time Creates a one-time occurrence, and enters single-one-time mode.
ステップ 6 UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds Specifies the date and time that this occurrence should run.
ステップ 7 UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step.
ステップ 8 UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # commit-buffer Commits the transaction to the system configuration.
The following example shows how to create a fault suppression task called task2 for the IOM on a chassis, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # create fault-suppress-task task2 UCS-A/chassis/iom/fault-suppress-task* # create local-schedule UCS-A/chassis/iom/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/chassis/iom/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/chassis/iom/fault-suppress-task/local-schedule/single-one-time* # commit-bufferThe following example shows how to create a fault suppression task called task2 for the IOM on a FEX, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope fex 1 UCS-A/fex # scope iom a UCS-A/fex/iom # create fault-suppress-task task2 UCS-A/fex/iom/fault-suppress-task* # create local-schedule UCS-A/fex/iom/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/fex/iom/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/fex/iom/fault-suppress-task/local-schedule/single-one-time* # commit-bufferConfiguring Fault Suppression Tasks for an IOM Using a Schedule
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope [chassis chassis-num | fex fex-num] Enters chassis mode for the specified chassis or FEX.
ステップ 2 UCS-A /chassis|fex # scope iom iom-id Enters chassis I/O module mode for the selected I/O module.
ステップ 3 UCS-A/chassis|fex/iom # create fault-suppress-task name Creates a fault-suppress-task on the IOM, and enters the fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 4 UCS-A/chassis|fex/iom/fault-suppress-task # set schedule name Specifies the schedule that you want to use.
(注) The schedule must exist before you can use it in a fault suppression task. For more information about creating schedules, see Creating a Schedule.
ステップ 5 UCS-A/chassis|fex/iom/fault-suppress-task # commit-buffer Commits the transaction to the system configuration.
The following example shows how to create a fault suppression task called task1 for the IOM on a chassis, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # create fault-suppress-task task1 UCS-A/chassis/iom/fault-suppress-task* # set schedule weekly_maint UCS-A/chassis/iom/fault-suppress-task* # commit-bufferThe following example shows how to create a fault suppression task called task1 for the IOM on a FEX, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope fex 1 UCS-A/fex # scope iom a UCS-A/fex/iom # create fault-suppress-task task1 UCS-A/fex/iom/fault-suppress-task* # set schedule weekly_maint UCS-A/fex/iom/fault-suppress-task* # commit-bufferDeleting Fault Suppression Tasks for an IOM
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope [chassis chassis-num | fex fex-num] Enters chassis mode for the specified chassis or FEX.
ステップ 2 UCS-A /chassis|fex # scope iom iom-id Enters chassis I/O module mode for the selected I/O module.
ステップ 3 UCS-A/chassis|fex/iom # delete fault-suppress-task name Deletes the specified fault suppression task.
ステップ 4 UCS-A/chassis|fex/iom # commit-buffer Commits the transaction to the system configuration.
The following example shows how to delete the fault suppression task called task1 for an IOM on a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # delete fault-suppress-task task1 UCS-A/chassis/iom* # commit-bufferThe following example shows how to delete the fault suppression task called task1 for an IOM on a FEX:
UCS-A# scope fex 3 UCS-A/fex # scope iom a UCS-A/fex/iom # delete fault-suppress-task task1 UCS-A/fex/iom* # commit-bufferModifying Fault Suppression Tasks for an IOM
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope [chassis chassis-num | fex fex-num] Enters chassis mode for the specified chassis or FEX.
ステップ 2 UCS-A /chassis|fex # scope iom iom-id Enters chassis I/O module mode for the selected I/O module.
ステップ 3 UCS-A/chassis|fex/iom # scope fault-suppress-task name Enters fault-suppress-task mode.
(注) To apply a different schedule to the fault suppression task, go to Step 4. To change the fixed time interval of the fault suppression task, go to Step 5.
ステップ 4 UCS-A/chassis|fex/iom/fault-suppress-task # set schedule name Applies a different schedule.
(注) If you change from a fixed time interval to a schedule, the fixed time interval is deleted when you commit.
If you change from a schedule to a fixed time interval, the reference to the schedule is cleared when you commit.
ステップ 5 UCS-A/chassis|fex/iom/fault-suppress-task # scope local-schedule Enters local-schedule mode.
ステップ 6 UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule # scope occurrence single-one-time Enters single-one-time mode.
ステップ 7 UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds Specifies the date and time that this occurrence should run.
ステップ 8 UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step.
ステップ 9 UCS-A/chassis|fex/iom/fault-suppress-task/local-schedule/single-one-time # commit-buffer Commits the transaction to the system configuration.
The following example shows how to change the date and the fault suppression policy of the fault suppression task called task2 for an IOM on a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # scope fault-suppress-task task2 UCS-A/chassis/iom/fault-suppress-task # scope local-schedule UCS-A/chassis/iom/fault-suppress-task/local-schedule # scope occurrence single-one-time UCS-A/chassis/iom/fault-suppress-task/local-schedule/single-one-time # set date dec 31 2013 11 00 00 UCS-A/chassis/iom/fault-suppress-task/local-schedule/single-one-time* # commit-bufferThe following example shows how to apply a different schedule to the fault suppression task called task1 for an IOM on a FEX:
UCS-A# scope fex 3 UCS-A/fex # scope iom a UCS-A/fex/iom # scope fault-suppress-task task1 UCS-A/fex/iom/fault-suppress-task # set schedule monthly-maint UCS-A/fex/iom/fault-suppress-task* # commit-bufferViewing Suppressed Faults and Fault Suppression Tasks for an IOM
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope [chassis chassis-num | fex fex-num] Enters chassis mode for the specified chassis or FEX.
ステップ 2 UCS-A /chassis|fex # scope iom iom-id Enters chassis I/O module mode for the selected I/O module.
ステップ 3 UCS-A/chassis|fex/iom # show fault suppressed Displays the suppressed faults for the IOM.
(注) Only faults owned by the selected component are displayed.
ステップ 4 UCS-A/chassis|fex/iom # scope fault-suppress-task name Enters fault-suppress-task mode.
ステップ 5 UCS-A/chassis|fex/iom/fault-suppress-task # show detail expand Displays the schedule or fixed time interval for the task.
The following example shows how to display the suppressed faults for an IOM on a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # show fault suppressed Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Iom Maint UCS-A/chassis/iom #The following example shows how to display the fault suppression task called task1 for an IOM on a chassis:
UCS-A# scope chassis 1 UCS-A/chassis # scope iom a UCS-A/chassis/iom # scope fault-suppress-task task1 UCS-A/chassis/iom/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Iom Maint UCS-A/chassis/iom/fault-suppress-task #The following example shows how to display the fault suppression task called task1 for an IOM on a FEX:
UCS-A# scope fex 3 UCS-A/fex # scope iom a UCS-A/fex/iom # scope fault-suppress-task task1 UCS-A/fex/iom/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Iom Maint UCS-A/chassis/iom/fault-suppress-task #Configuring Fault Suppression Tasks for a FEX Using a Schedule
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope fex fex-num Enters fex mode for the specified FEX.
ステップ 2 UCS-A/fex # create fault-suppress-task name Creates a fault-suppress-task on the fex, and enters the fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 3 UCS-A/fex/fault-suppress-task # set schedule name Specifies the schedule that you want to use.
(注) The schedule must exist before you can use it in a fault suppression task. For more information about creating schedules, see Creating a Schedule.
ステップ 4 UCS-A/fex/fault-suppress-task # set fault-suppress-policy policy-name Specifies the fault suppression policy that you want to apply. This can be one of the following:
ステップ 5 UCS-A/fex/fault-suppress-task # commit-buffer Commits the transaction to the system configuration.
The following example shows how to create a fault suppression task called task1 for the FEX, apply the scheduler called weekly_maint and the default-fex-all-maint policy to the task, and commit the transaction:
UCS-A# scope fex 1 UCS-A/fex # create fault-suppress-task task1 UCS-A/fex/fault-suppress-task* # set schedule weekly_maint UCS-A/fex/fault-suppress-task* # set fault-suppress-policy default-fex-all-maint UCS-A/fex/fault-suppress-task* # commit-bufferDeleting Fault Suppression Tasks for a FEX
Viewing Suppressed Faults and Fault Suppression Tasks for a FEX
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope fex fex-num Enters fex mode for the specified FEX.
ステップ 2 UCS-A/fex # show fault suppressed Displays the suppressed faults for the FEX.
(注) Only faults owned by the selected component are displayed.
ステップ 3 UCS-A/fex # scope fault-suppress-task name Enters fault-suppress-task mode.
ステップ 4 UCS-A/fex/fault-suppress-task # show detail expand Displays the schedule or fixed time interval for the task.
The following example shows how to display the suppressed faults for a FEX:
UCS-A# scope fex 1 UCS-A/fex # show fault suppressed Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default FEX Phys Maint UCS-A/fex #The following example shows how to display the fault suppression task called task1:
UCS-A# scope fex 1 UCS-A/fex # scope fault-suppress-task task1 UCS-A/fex/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default FEX Phys Maint UCS-A/fex/fault-suppress-task #Configuring Fault Suppression Tasks for a Server Using a Fixed Time Interval
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope server [chassis-num/server-num | dynamic-uuid] 指定したサーバのサーバ モードを開始します。
ステップ 2 UCS-A/server # create fault-suppress-task name Creates a fault-suppress-task on the server, and enters the fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 3 UCS-A/server/fault-suppress-task # create local-schedule Creates a local schedule and enters local-schedule mode.
ステップ 4 UCS-A/server/fault-suppress-task/local-schedule # create occurrence single-one-time Creates a one-time occurrence, and enters single-one-time mode.
ステップ 5 UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds Specifies the date and time that this occurrence should run.
ステップ 6 UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step.
ステップ 7 UCS-A/server/fault-suppress-task/local-schedule/single-one-time # commit-buffer Commits the transaction to the system configuration.
The following example shows how to create a fault suppression task called task2 for the server, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope server 1/1 UCS-A/server # create fault-suppress-task task2 UCS-A/server/fault-suppress-task* # create local-schedule UCS-A/server/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/server/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/server/fault-suppress-task/local-schedule/single-one-time* # commit-bufferConfiguring Fault Suppression Tasks for a Server using a Schedule
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope server [chassis-num/server-num | dynamic-uuid] 指定したサーバのサーバ モードを開始します。
ステップ 2 UCS-A/server # create fault-suppress-task name Creates a fault-suppress-task on the server, and enters the fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 3 UCS-A/server/fault-suppress-task # set schedule name Specifies the schedule that you want to use.
(注) The schedule must exist before you can use it in a fault suppression task. For more information about creating schedules, see Creating a Schedule.
ステップ 4 UCS-A/server/fault-suppress-task # commit-buffer Commits the transaction to the system configuration.
The following example shows how to creates a fault suppression task called task1 for the server, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope server 1/1 UCS-A/server # create fault-suppress-task task1 UCS-A/server/fault-suppress-task* # set schedule weekly_maint UCS-A/server/fault-suppress-task* # commit-bufferDeleting Fault Suppression Tasks for a Server
Modifying Fault Suppression Tasks for a Server
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope server [chassis-num/server-num | dynamic-uuid] 指定したサーバのサーバ モードを開始します。
ステップ 2 UCS-A/server # scope fault-suppress-task name Enters fault-suppress-task mode.
(注) To apply a different schedule to the fault suppression task, go to Step 3. To change the fixed time interval of the fault suppression task, go to Step 4.
ステップ 3 UCS-A/server/fault-suppress-task # set schedule name Applies a different schedule.
(注) If you change from a fixed time interval to a schedule, the fixed time interval is deleted when you commit.
If you change from a schedule to a fixed time interval, the reference to the schedule is cleared when you commit.
ステップ 4 UCS-A/server/fault-suppress-task # scope local-schedule Enters local-schedule mode.
ステップ 5 UCS-A/server/fault-suppress-task/local-schedule # scope occurrence single-one-time Enters single-one-time mode.
ステップ 6 UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds Specifies the date and time that this occurrence should run.
ステップ 7 UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step.
ステップ 8 UCS-A/server/fault-suppress-task/local-schedule/single-one-time # commit-buffer Commits the transaction to the system configuration.
The following example shows how to change the date and the fault suppression policy of the fault suppression task called task2:
UCS-A# scope server 1/1 UCS-A/server # scope fault-suppress-task task2 UCS-A/server/fault-suppress-task # scope local-schedule UCS-A/server/fault-suppress-task/local-schedule # scope occurrence single-one-time UCS-A/server/fault-suppress-task/local-schedule/single-one-time # set date dec 31 2013 11 00 00 UCS-A/server/fault-suppress-task/local-schedule/single-one-time* # commit-bufferThe following example shows how to apply a different schedule to the fault suppression task called task1:
UCS-A# scope server 1/1 UCS-A/server # scope fault-suppress-task task1 UCS-A/server/fault-suppress-task # set schedule monthly-maint UCS-A/server/fault-suppress-task* # commit-bufferViewing Suppressed Faults and Fault Suppression Tasks for a Server
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope server [chassis-num/server-num | dynamic-uuid] 指定したサーバのサーバ モードを開始します。
ステップ 2 UCS-A/server # show fault suppressed Displays the suppressed faults for the server.
(注) Only faults owned by the selected component are displayed.
ステップ 3 UCS-A/server # scope fault-suppress-task name Enters fault-suppress-task mode.
ステップ 4 UCS-A/server/fault-suppress-task # show detail expand Displays the schedule or fixed time interval for the task.
The following example shows how to display the suppressed faults for a server:
UCS-A# scope server 1/1 UCS-A/server # show fault suppressed Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Server Maint UCS-A/server #The following example shows how to display the fault suppression task called task1:
UCS-A# scope server 1/1 UCS-A/server # scope fault-suppress-task task1 UCS-A/server/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Server Maint UCS-A/server/fault-suppress-task #Configuring Fault Suppression Tasks for a Service Profile Using a Fixed Time Interval
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A /org # scope service-profile profile-name Enters service profile organization mode for the service profile.
ステップ 3 UCS-A /org/service-profile # create fault-suppress-task name Creates a fault-suppress-task on the chassis, and enters the fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 4 UCS-A/org/service-profile/fault-suppress-task # create local-schedule Creates a local schedule and enters local-schedule mode.
ステップ 5 UCS-A/org/service-profile/fault-suppress-task/local-schedule # create occurrence single-one-time Creates a one-time occurrence, and enters single-one-time mode.
ステップ 6 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds Specifies the date and time that this occurrence should run.
ステップ 7 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step.
ステップ 8 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # commit-buffer Commits the transaction to the system configuration.
The following example shows how to create a fault suppression task called task2 under the accounting service profile, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # create fault-suppress-task task2 UCS-A/org/service-profile/fault-suppress-task* # create local-schedule UCS-A/org/service-profile/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time* # commit-bufferConfiguring Fault Suppression Tasks for a Service Profile Using a Schedule
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A /org # scope service-profile profile-name Enters service profile organization mode for the service profile.
ステップ 3 UCS-A /org/service-profile # create fault-suppress-task name Creates a fault-suppress-task on the chassis, and enters the fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 4 UCS-A/org/service-profile/fault-suppress-task # set schedule name Specifies the schedule that you want to use.
(注) The schedule must exist before you can use it in a fault suppression task. For more information about creating schedules, see Creating a Schedule.
ステップ 5 UCS-A/org/service-profile/fault-suppress-task # commit-buffer Commits the transaction to the system configuration.
The following example shows how to create a fault suppression task called task1 under the accounting service profile, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # create fault-suppress-task task1 UCS-A/org/service-profile/fault-suppress-task* # set schedule weekly_maint UCS-A/org/service-profile/fault-suppress-task* # commit-bufferDeleting Fault Suppression Tasks for a Service Profile
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A /org # scope service-profile profile-name Enters service profile organization mode for the service profile.
ステップ 3 UCS-A/org/service-profile # delete fault-suppress-task name Deletes the specified fault suppression task.
ステップ 4 UCS-A/org/service-profile # commit-buffer Commits the transaction to the system configuration.
Modifying Fault Suppression Tasks for a Service Profile
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A /org # scope service-profile profile-name Enters service profile organization mode for the service profile.
ステップ 3 UCS-A/org/service-profile # scope fault-suppress-task name Enters fault-suppress-task mode.
(注) To apply a different schedule to the fault suppression task, go to Step 4. To change the fixed time interval of the fault suppression task, go to Step 5.
ステップ 4 UCS-A/org/service-profile/fault-suppress-task # set schedule name Applies a different schedule.
(注) If you change from a fixed time interval to a schedule, the fixed time interval is deleted when you commit.
If you change from a schedule to a fixed time interval, the reference to the schedule is cleared when you commit.
ステップ 5 UCS-A/org/service-profile/fault-suppress-task # scope local-schedule Enters local-schedule mode.
ステップ 6 UCS-A/org/service-profile/fault-suppress-task/local-schedule # scope occurrence single-one-time Enters single-one-time mode.
ステップ 7 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds Specifies the date and time that this occurrence should run.
ステップ 8 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step.
ステップ 9 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # commit-buffer Commits the transaction to the system configuration.
The following example shows how to change the date and the fault suppression policy of the fault suppression task called task2:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # scope fault-suppress-task task2 UCS-A/org/service-profile/fault-suppress-task # scope local-schedule UCS-A/org/service-profile/fault-suppress-task/local-schedule # scope occurrence single-one-time UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time # set date dec 31 2013 11 00 00 UCS-A/org/service-profile/fault-suppress-task/local-schedule/single-one-time* # commit-bufferThe following example shows how to apply a different schedule to the fault suppression task called task1:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # scope fault-suppress-task task1 UCS-A/org/service-profile/fault-suppress-task # set schedule monthly-maint UCS-A/org/service-profile/fault-suppress-task* # commit-bufferViewing Suppressed Faults and Fault Suppression Tasks for a Service Profile
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A /org # scope service-profile profile-name Enters service profile organization mode for the service profile.
ステップ 3 UCS-A/org/service-profile # show fault suppressed Displays the suppressed faults for the server.
(注) Only faults owned by the selected component are displayed.
ステップ 4 UCS-A/org/service-profile # scope fault-suppress-task name Enters fault-suppress-task mode.
ステップ 5 UCS-A/org/service-profile/fault-suppress-task # show detail expand Displays the schedule or fixed time interval for the task.
The following example shows how to display the suppressed faults for a service profile:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # show fault suppressed UCS-A/org/service-profile # Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Server Maint UCS-A/org/service-profile #The following example shows how to display the fault suppression task called task1:
UCS-A# scope org / UCS-A/org # scope service-profile accounting UCS-A/org/service-profile # scope fault-suppress-task task1 UCS-A/org/service-profile/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Server Maint UCS-A/org/service-profile/fault-suppress-task #Configuring Fault Suppression Tasks for an Organization Using a Fixed Time Interval
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A/org # create fault-suppress-task name Creates a fault-suppress-task for the organization, and enters fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 3 UCS-A/org/fault-suppress-task # create local-schedule Creates a local schedule and enters local-schedule mode.
ステップ 4 UCS-A/org/fault-suppress-task/local-schedule # create occurrence single-one-time Creates a one-time occurrence, and enters single-one-time mode.
ステップ 5 UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds Specifies the date and time that this occurrence should run.
ステップ 6 UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step.
ステップ 7 UCS-A/org/fault-suppress-task/local-schedule/single-one-time # commit-buffer Commits the transaction to the system configuration.
The following example shows how to create a fault suppression task called task2 under the Root organization, set the start date to January 1, 2013 at 11:00, and commit the transaction:
UCS-A# scope org / UCS-A/org # create fault-suppress-task task2 UCS-A/org/fault-suppress-task* # create local-schedule UCS-A/org/fault-suppress-task/local-schedule* # create occurrence single-one-time UCS-A/org/fault-suppress-task/local-schedule/single-one-time* # set date jan 1 2013 11 00 00 UCS-A/org/fault-suppress-task/local-schedule/single-one-time* # commit-bufferConfiguring Fault Suppression Tasks for an Organization Using a Schedule
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A/org # create fault-suppress-task name Creates a fault-suppress-task for the organization, and enters the fault-suppress-task mode.
この名前には、1 ~ 16 文字の英数字を使用できます。 -(ハイフン)、_(アンダースコア)、:(コロン)、および . (ピリオド)は使用できますが、それ以外の特殊文字とスペースは使用できません。また、オブジェクトが保存された後で、この名前を変更することはできません。
ステップ 3 UCS-A/org/fault-suppress-task # set schedule name Specifies the schedule that you want to use.
(注) The schedule must exist before you can use it in a fault suppression task. For more information about creating schedules, see Creating a Schedule.
ステップ 4 UCS-A/org/fault-suppress-task # commit-buffer Commits the transaction to the system configuration.
The following example shows how to create a fault suppression task called task1 under the Root organization, apply the scheduler called weekly_maint to the task, and commit the transaction:
UCS-A# scope org / UCS-A/org # create fault-suppress-task task1 UCS-A/org/fault-suppress-task* # set schedule weekly_maint UCS-A/org/fault-suppress-task* # commit-bufferDeleting Fault Suppression Tasks for an Organization
Modifying Fault Suppression Tasks for an Organization
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A/org # scope fault-suppress-task name Enters fault-suppress-task mode.
(注) To apply a different schedule to the fault suppression task, go to Step 3. To change the fixed time interval of the fault suppression task, go to Step 4.
ステップ 3 UCS-A/org/fault-suppress-task # set schedule name Applies a different schedule.
(注) If you change from a fixed time interval to a schedule, the fixed time interval is deleted when you commit.
If you change from a schedule to a fixed time interval, the reference to the schedule is cleared when you commit.
ステップ 4 UCS-A/org/fault-suppress-task # scope local-schedule Enters local-schedule mode.
ステップ 5 UCS-A/org/fault-suppress-task/local-schedule # scope occurrence single-one-time Enters single-one-time mode.
ステップ 6 UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set date month day-of-month year hour minute seconds Specifies the date and time that this occurrence should run.
ステップ 7 UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds} Specifies the maximum length of time that this task can run. To run the task until it is manually stopped, enter none or omit this step.
ステップ 8 UCS-A/org/fault-suppress-task/local-schedule/single-one-time # commit-buffer Commits the transaction to the system configuration.
The following example shows how to change the date and the fault suppression policy of the fault suppression task called task2:
UCS-A# scope org / UCS-A/org # scope fault-suppress-task task2 UCS-A/org/fault-suppress-task* # scope local-schedule UCS-A/org/fault-suppress-task/local-schedule # scope occurrence single-one-time UCS-A/org/fault-suppress-task/local-schedule/single-one-time # set date dec 31 2013 11 00 00 UCS-A/org/fault-suppress-task/local-schedule/single-one-time* # commit-bufferThe following example shows how to apply a different schedule to the fault suppression task called task1:
UCS-A# scope org UCS-A/org # scope fault-suppress-task task1 UCS-A/org/fault-suppress-task # set schedule monthly-maint UCS-A/org/fault-suppress-task* # commit-bufferViewing Suppressed Faults and Fault Suppression Tasks for an Organization
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope org org-name 指定した組織の組織モードを開始します。 ルート組織モードを開始するには、org-name として / を入力します。
ステップ 2 UCS-A/org # show fault suppressed Displays the suppressed faults for the organization
(注) Only faults owned by the selected component are displayed.
ステップ 3 UCS-A/org # scope fault-suppress-task name Enters fault-suppress-task mode.
ステップ 4 UCS-A/org/fault-suppress-task # show detail expand Displays the schedule or fixed time interval for the task.
The following example shows how to display the suppressed faults for an organization:
UCS-A# scope org Finance UCS-A/org # show fault suppressed UCS-A/org # Fault Suppress Task: Name Status Global Schedule Suppress Policy Name ------------------ ------------------ --------------- -------------------- task1 Active test_schedule1 Default Server Maint UCS-A/org #The following example shows how to display the fault suppression task called task1:
UCS-A# scope org Finance UCS-A/org # scope fault-suppress-task task1 UCS-A/org/fault-suppress-task # show detail expand Fault Suppress Task: Name: task1 Status: Active Global Schedule: test_schedule1 Suppress Policy Name: Default Server Maint UCS-A/org/fault-suppress-task #Core File Exporter
Cisco UCS コア ファイルが発生すると、ただちに Core File Exporter が使用され、それらのファイルが TFTP を介してネットワーク上の指定の場所にエクスポートされます。 この機能を使用することにより、tar ファイルをコア ファイルのコンテンツと一緒にエクスポートできます。
Configuring the Core File Exporter
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope monitoring Enters monitoring mode.
ステップ 2 UCS-A /monitoring # scope sysdebug Enters monitoring system debug mode.
ステップ 3 UCS-A /monitoring/sysdebug # enable core-export-target Enables the core file exporter. When the core file exporter is enabled and an error causes the server to perform a core dump, the system exports the core file via TFTP to the specified remote server.
ステップ 4 UCS-A /monitoring/sysdebug # set core-export-target path path Specifies the path to use when exporting the core file to the remote server.
ステップ 5 UCS-A /monitoring/sysdebug # set core-export-target port port-num Specifies the port number to use when exporting the core file via TFTP. The range of valid values is 1 to 65,535.
ステップ 6 UCS-A /monitoring/sysdebug # set core-export-target server-description description Provides a description for the remote server used to store the core file.
ステップ 7 UCS-A /monitoring/sysdebug # set core-export-target server-name hostname Specifies the hostname of the remote server to connect with via TFTP.
ステップ 8 UCS-A /monitoring/sysdebug # commit-buffer Commits the transaction.
The following example enables the core file exporter, specifies the path and port to use when sending the core file, specifies the remote server hostname, provides a description for the remote server, and commits the transaction.
UCS-A# scope monitoring UCS-A /monitoring # scope sysdebug UCS-A /monitoring/sysdebug # enable core-export-target UCS-A /monitoring/sysdebug* # set core-export-target path /root/CoreFiles/core UCS-A /monitoring/sysdebug* # set core-export-target port 45000 UCS-A /monitoring/sysdebug* # set core-export-target server-description CoreFile102.168.10.10 UCS-A /monitoring/sysdebug* # set core-export-target server-name 192.168.10.10 UCS-A /monitoring/sysdebug* # commit-buffer UCS-A /monitoring/sysdebug #Disabling the Core File Exporter
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope monitoring Enters monitoring mode.
ステップ 2 UCS-A /monitoring # scope sysdebug Enters monitoring system debug mode.
ステップ 3 UCS-A /monitoring/sysdebug # disable core-export-target Disables the core file exporter. When the core file exporter is disabled core files are not automatically exported.
ステップ 4 UCS-A /monitoring/sysdebug # commit-buffer Commits the transaction.
Configuring the Syslog
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope monitoring Enters monitoring mode.
ステップ 2 UCS-A /monitoring # {enable | disable} syslog console Enables or disables the sending of syslogs to the console.
ステップ 3 UCS-A /monitoring # set syslog console level {emergencies | alerts | critical} (任意) Select the lowest message level that you want displayed. If syslogs are enabled, the system displays that level and above on the console. The level options are listed in order of decreasing urgency.The default level is Critical.
ステップ 4 UCS-A /monitoring # {enable | disable} syslog monitor Enables or disables the monitoring of syslog information by the operating system.
ステップ 5 UCS-A /monitoring # set syslog monitor level {emergencies | alerts | critical | errors | warnings | notifications | information | debugging} (任意) Select the lowest message level that you want displayed. If the monitor state is enabled, the system displays that level and above. The level options are listed in order of decreasing urgency.The default level is Critical.
(注) Messages at levels below Critical are displayed on the terminal monitor only if you have entered the terminal monitor command.
ステップ 6 UCS-A /monitoring # {enable | disable} syslog file Enables or disables the writing of syslog information to a syslog file.
ステップ 7 UCS-A /monitoring # set syslog file name filename The name of the file in which the messages are logged. Up to 16 characters are allowed in the file name.
ステップ 8 UCS-A /monitoring # set syslog file level {emergencies | alerts | critical | errors | warnings | notifications | information | debugging} (任意) Select the lowest message level that you want stored to a file. If the file state is enabled, the system stores that level and above in the syslog file. The level options are listed in order of decreasing urgency.The default level is Critical.
ステップ 9 UCS-A /monitoring # set syslog file size filesize (任意) The maximum file size, in bytes, before the system begins to write over the oldest messages with the newest ones. The range is 4096 to 4194304 bytes.
ステップ 10 UCS-A /monitoring # {enable | disable} syslog remote-destination {server-1 | server-2 | server-3} Enables or disables the sending of syslog messages to up to three external syslog servers.
ステップ 11 UCS-A /monitoring # set syslog remote-destination {server-1 | server-2 | server-3} level{emergencies | alerts | critical | errors | warnings | notifications | information | debugging} (任意) Select the lowest message level that you want stored to the external log. If the remote-destination is enabled, the system sends that level and above to the external server. The level options are listed in order of decreasing urgency.The default level is Critical.
ステップ 12 UCS-A /monitoring # set syslog remote-destination {server-1 | server-2 | server-3} hostname hostname The hostname or IP address of the specified remote syslog server. Up to 256 characters are allowed in the hostname.
ステップ 13 UCS-A /monitoring # set syslog remote-destination {server-1 | server-2 | server-3} facility {local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7} (任意) The facility level contained in the syslog messages sent to the specified remote syslog server.
ステップ 14 UCS-A /monitoring # {enable | disable} syslog source {audits | events | faults} This can be one of the following:
ステップ 15 UCS-A /monitoring # commit-buffer Commits the transaction.
This example shows how to enable the storage of syslog messages in a local file and commits the transaction:
UCS-A# scope monitoring UCS-A /monitoring # disable syslog console UCS-A /monitoring* # disable syslog monitor UCS-A /monitoring* # enable syslog file UCS-A /monitoring* # set syslog file name SysMsgsUCSA UCS-A /monitoring* # set syslog file level notifications UCS-A /monitoring* # set syslog file size 4194304 UCS-A /monitoring* # disable syslog remote-destination server-1 UCS-A /monitoring* # disable syslog remote-destination server-2 UCS-A /monitoring* # disable syslog remote-destination server-3 UCS-A /monitoring* # commit-buffer UCS-A /monitoring #Viewing Audit Logs
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope security Enters security mode.
ステップ 2 UCS-A /security # show audit-logs Displays the audit logs.
The following example displays the audit logs:
UCS-A# scope security UCS-A /security # show audit-logs Audit trail logs: Creation Time User ID Action Description -------------------- ---------- -------- ---------------- ----------- 2013-01-04T19:05:36.027 internal 1055936 Creation Fabric A: local us er admin logge 2013-01-03T23:08:37.459 admin 1025416 Creation Uplink FC VSAN mem ber port A/1/3 2013-01-03T23:08:37.459 admin 1025417 Deletion Uplink FC VSAN mem ber port A/1/3 2013-01-03T23:08:02.387 admin 1025299 Creation Uplink FC VSAN mem ber port A/1/3 2013-01-03T23:08:02.387 admin 1025300 Deletion Uplink FC VSAN mem ber port A/1/3 2013-01-03T23:03:23.926 admin 1025096 Creation Uplink FC VSAN mem ber port A/1/3 UCS-A /security #ログ ファイル エクスポータ
Cisco UCS Manager は、実行ごとにログ ファイルを生成します。 ログ ファイルのサイズは最大 20 MB で、最大 5 つのバックアップがサーバに保存できます。 ログ ファイル エクスポータにより、ログ ファイルを削除する前にリモート サーバにエクスポートすることができます。 ログ ファイル名には次の情報が含まれます。
(注)
ログのエクスポートをイネーブルにしない場合は、バックアップ ファイルの最大限度に到達すると最も古いログ ファイルが削除されます。
Exporting Log Files to a Remote Server
手順
コマンドまたはアクション 目的 ステップ 1 UCS-A# scope monitoring Enters monitoring mode.
ステップ 2 UCS-A /monitoring # scope sysdebug Enters monitoring system debug mode.
ステップ 3 UCS-A /monitoring/sysdebug # scope log-export-policy Enters log file export mode.
ステップ 4 UCS-A /monitoring/sysdebug/log-export-policy # set admin-state {disabled | enabled} Whether log file exporting is enabled.
ステップ 5 UCS-A /monitoring/sysdebug/log-export-policy # set desc description (任意) Provides a description for the log export policy
ステップ 6 UCS-A /monitoring/sysdebug/log-export-policy # set hostname hostname Specifies the hostname of the remote server.
ステップ 7 UCS-A /monitoring/sysdebug/log-export-policy # set passwd After you press Enter, you are prompted to enter the password.
Specifies the password for the remote server username. This step does not apply if the TFTP protocol is used.
ステップ 8 UCS-A /monitoring/sysdebug/log-export-policy # set passwordless-ssh {no | yes} Enables SSH login without a password.
ステップ 9 UCS-A /monitoring/sysdebug/log-export-policy # set proto {scp | ftp | sftp | tftp} Specifies the protocol to use when communicating with the remote server.
ステップ 10 UCS-A /monitoring/sysdebug/log-export-policy # set path path Specifies the path on the remote server where the log file is to be saved.
ステップ 11 UCS-A /monitoring/sysdebug/log-export-policy # set user username Specifies the username the system should use to log in to the remote server. This step does not apply if the TFTP protocol is used.
ステップ 12 UCS-A /monitoring/sysdebug/log-export-policy # commit-buffer Commits the transaction.
The following example shows how to enable the log file exporter, specify the remote server hostname, set the protocol to scp, enable passwordless login, and commit the transaction.
UCS-A# scope monitoring UCS-A /monitoring # scope sysdebug UCS-A /monitoring/sysdebug # scope log-export-policy UCS-A /monitoring/sysdebug/log-export-policy # set admin-state enable UCS-A /monitoring/sysdebug/log-export-policy* # set hostname 10.10.1.1 UCS-A /monitoring/sysdebug/log-export-policy* # set path / UCS-A /monitoring/sysdebug/log-export-policy* # set user testuser UCS-A /monitoring/sysdebug/log-export-policy* # set proto scp UCS-A /monitoring/sysdebug/log-export-policy* # set passwd password: UCS-A /monitoring/sysdebug/log-export-policy* # set passwordless-ssh yes UCS-A /monitoring/sysdebug/log-export-policy* # commit-buffer UCS-A /monitoring/sysdebug/log-export-policy #